This is caused by the latest Windows Cumulative update. Many users have reported the same error, me included. Uninstalling the update fixes it and you need to stop windows updates until a fix comes.
Yes. I have done memtest86 and KarhuRAMtest with no errors (i run everything at stock settings too and never had a BSOD on this machine). This new update is the first time i'm having issues with windows. And after doing some research it seems the issues i'm having are not uncommon with the new...
I used the DISM /remove-package command via command prompt and got the update uninstalled and everything is working again. Windows is showing up as build 22631.3007 so it seems to have worked. I also stopped the windows updates so it won't install again. Just gotta find a way to stop it for a...
Can someone explain how i can roll back this update? I started getting the explorer.exe errors and my MS account is somehow screwed up now as well. Not letting me log in to my e-mail, xbox app or the ms store.
I can't see a way to remove this update.
Yea. After some research it seems the update can't be uninstalled since it came with a Servicing Stack Update as well. The SSU can't be uninstalled so you can't uninstall the LCU.
Apparently my issue with the explorer.exe error during shutdown is caused by my usb dongle for xbox controller. There are many posts on reddit with the same issue after this windows update.
Going to uninstall this one since it should fix the issue.
Anything i need to know when removing an...
I'm getting somekind of explorer.exe error during shutdown after this update. It goes by pretty fast so i've not had enough time to read it properly. Something about "memory could not be read" or something like that. It has happened 2 out of 3 times now when i shutdown my pc.
I had this same issue with edge being added to startup and running in the background until yesterday. It's no longer in the startup programs and doesn't leave anything running when i close it. I didn't change any settings etc. It just did it by itself. This was also before edge got updated today.