CPU Usage has gone higher after windows 10 update

[vawa.id]

I just installed windows 10 update using windows update assistant, and things went bad. My CPU runs 25-80% in iddle state. I see task manager, nothing uses that many CPU. My games stutter, even watching youtube (chrome) causes glitching sound.

I have run windows in safe mode, and CPU runs under 11%. What should I do?

 

my spec:

i3 3210

rx 460 2gb

6 Gb ram

120 Gb SSD

512 Gb 2.5" 5400rpm HDD

[asus killer]

welcome to the underfull world of windows updates. I had the exact same problem on my laptop. Reverted the update and all is well, i recommend you do the same. 

[EarthWormJM2]

Is it a system task or windows updates/defender running in the background? Also, if you are having weird issues with Windows like that, the update could have not applied correctly or corrupted itself (common with Windows, woo). At which point it may be a good idea to re-install Windows.

[vawa.id]

2 hours ago, EarthWormJM2 said:

Is it a system task or windows updates/defender running in the background? Also, if you are having weird issues with Windows like that, the update could have not applied correctly or corrupted itself (common with Windows, woo). At which point it may be a good idea to re-install Windows.

2

The update is installed correctly, I believe.

But windows defender, man, it changed its name to Windows Security and it has a lot more option and most of them can't be disabled even in services.msc

[vawa.id]

This is what was written if I type 

Set-MpPreference -DisableRealtimeMonitoring $true

Set-MpPreference : Operation failed with the following error: 0x800106ba. Operation: Set-MpPreference. Target:
DisableRealtimeMonitoring.
At line:1 char:1
+ Set-MpPreference -DisableRealtimeMonitoring $true
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (MSFT_MpPreference:root\Microsoft\...FT_MpPreference) [Set-MpPreference],
   CimException
    + FullyQualifiedErrorId : HRESULT 0x800106ba,Set-MpPreference

 

The second one was successful, so I think I have to re-disable it after every update. thanks so much btw.