logoalt Hacker News

jiggawatts01/21/20251 replyview on HN

There's also the gotcha that a few years ago Microsoft decided that Defender can no longer be turned off or even uninstalled. Even if you install a third-party antimalware product, both will always run. Similarly, folder exclusion rules just stop it reporting viruses it finds, but it'll still scan them and even report them back to Microsoft's cloud services whether you like it or not.

This is so obnoxiously difficult to work around that Microsoft themselves couldn't do it for the Windows runner images used by both GitHub Actions and Azure DevOps. As a consequence, their performance tanked 4x and stayed there.

We're also seeing massive performance regressions for apps that have many small files, such as SQL Server Analysis Services. Basic operations such as backup, restore, or sync are 10x slower with no recourse.

Similarly, the IntelliJ IDEs have a feature to disable A/V scanning on your source code folders for performance. This now does nothing to improve performance.

This is so bad that Microsoft's own developers had to "hack in a workaround" called Dev Drive into Windows 11 so that they could get their work done despite the best efforts of their own company to slow them down. (This isn't included in Windows Server 2022, and hence isn't available for use by the GitHub Agent runner images.)

See:

https://github.com/actions/runner-images/issues/7320

and

https://github.com/actions/runner-images/issues/8380

I love the various associated PRs and commits futilely twiddling the A/V settings to no avail.


Replies

netdevphoenixlast Friday at 1:01 PM

>Even if you install a third-party antimalware product, both will always run

My understanding was that this was a response to attackers learning to disabling Defender by pretending that a third party AV was installed and to make sure that if the third party AV failed to operate, Defender would take over