I have an installer which installs an electron app, a DotNet windows service and a Python Windows service.
When the installer runs on a new machine and reaches the "Starting Services" step, Windows defender immediately maxes the CPU and the machine becomes unusable... it appears that the service start then times out eventually and reports that the services couldn't be started due to a permissions error - I think this is incorrect, since after a few attempts, the installer does eventually complete and the services run correctly
We're also seeing this on a machine with Norton, which also maxes CPU.
On machines where it does complete, it still maxes the CPU, but doesn't seem to time out
I can't disable AV for the install clearly, and Group policy to limit defender CPU load is not an option since this will be a user-installable system
Any ideas of things to check?
FOLLOW US
Get the latest news in Application Packaging