I had an issue in early builds of W11 with use of WSL 2 & Node, Github and VS Code. Something in the git change detection process caused Defender to decide it j

I had an issue in early builds of W11 with use of WSL 2 & Node, Github and VS Code. Something in the git change detection process caused Defender to decide it just decided it wanted 100% of a single thread on the 5600X system I was using. While coding it would just have a core screaming at well over 4Ghz. Just all of Mankind's greatest innovations that lead to 7nm lithography and incredible processor design just to be a space heater. I never did get it figured out at the time. It also re-enables itself. So that's cool.