What you want to do first is identify and whitelist not each individual file being run in the SDKs and emulators, but the executables in the SDK and the emulators themselves that are running the files.ĭo this first, and only proceed to whitelisting the individual files if the first step doesn't solve the problem. However I think you're complicating the problem. It also allows you to search for individual threads and in-use files and identify the process(es) that are using them. ProcExp shows applications in a hierarchical view ('tree view') that lists processes as parents and children. Run ProcExp when you are running ProcMon and as you find entries in the ProcMon log that you suspect may be causing the slowness, find them in ProcExp's list of processes. Your list should now filter and you can view and log files the engine touches as it touches them.Īnother tool that can add information to this process is Process Explorer, also from SysInternals: For help with your password, see Change or reset your Windows password. For more info about Microsoft Defender Firewall, see Turn Microsoft Defender Firewall on or off.
For more info about Windows Security, see Stay protected with Windows Security. You can do this using ProcMon from SysInternals:
