Windows 10: Windows 11 CPU staying pegged at 100%

All of a sudden my system is pegging at 100% CPU and stays peggedCan't find any rhyme or reason as to why it's doing this. I rolled off this weeks Windows 11 updates as the behavior just started but it does not appear to be helping

:)

 

Windows Defender pegs CPU at 100% utilization when scanning obfuscated .NET applications

Yes, I know - I've been following
your thread in TechNet forums, too.

 

CPU 100% on Boot

The issue first arose as a pegged 100% CPU usage on system interrupts a few months back, and seems to coincide with a windows update from then. I would usually be able to solve this via a hard power cycle. I performed a windows update last night, and now
(other than booting in safe mode), I cannot use my computer as the CPU is pegged at 100% which makes it freeze shortly after logging in. I cannot even bring up the task manager. I have tried a clean boot, and even that does not work, but booting in safe mode
does work (I'm just glad that I enabled the boot menu awhile back).

Is there a way, other than safe mode, that I might be able to start my computer up with having a pegged CPU?

 

Windows Defender pegs CPU at 100% utilization when scanning obfuscated .NET applications

Have you gone through the steps to reproduce the problem? I suggest you do that to verify what I posted as this is not a problem with my machine.

To prove that point I just built a brand new Windows 10 virtual machine from scratch and duplicated the problem.

Here's the answers to your questions

Re: 1 - Today. It's a Hyper-V virtual machine.

Re: 2 - It was a clean install from en_windows_10_enterprise_version_1703_updated_march_2017_x64_dvd_10189290.iso

Re: 3 - Microsoft

Re: 4 - No

Re: 5 - No

Re: 6 - No. It was a bare metal install

Re: 7 - Today. The install version was Version 1703 (OS Build 15063.0)

Re: 8 - March 2017, by Microsoft

Re: 9 - No. It was installed to the unused space during setup

Re: 9 (I assume you meant 10) - Yes. It is a VM

After doing a bare-metal build I tested the application and it launched immediately. I then checked for updates and installed all that were available. After the updates installed I then relaunched the application. It took 16 seconds for the application to
launch and the CPU was pegged at 100% utilization. Once the app loaded CPU utilization dropped down to 0%. The source code for the application was included in my original thread.