Thank you for being a valued part of the CNET community. As of December 1, 2020, the forums are in read-only format. In early 2021, CNET Forums will no longer be available. We are grateful for the participation and advice you have provided to one another over the years.

Thanks,

CNET Support

Question

May Win 10 update Crashes

May 8, 2018 5:40PM PDT

Today's (May Cool Windows Update crashed both my PCs. The updates were downloaded and installed but upon reboot, nothing but a black screen with the rotating circle. After 1 hour I had to use a rescue media to restore the PCs to an earlier time and disable further updates. Anyone else having a similar problem?

Discussion is locked

- Collapse -
Answer
Yes.
May 8, 2018 5:50PM PDT

I googled this one and it appears you are not alone.

Many are delaying the update.

- Collapse -
Answer
Was It The Version 1803 Update And Are They Using SSD's?
May 8, 2018 7:45PM PDT
- Collapse -
SSD: Yes, 1803: Not sure
May 9, 2018 5:29AM PDT

Yes, both my PCs have SSDs, but it was the May 8 update that caused the problem. I have disabled Windows update on both machines until I am comfortable the problem won't reoccur and don't know the exact ID of the update since disabling Update seems to also stops display of update history.

- Collapse -
Type "winver" In The Search Line, Press Enter
May 9, 2018 10:34AM PDT

It will bring up the Windows 10 version and build numbers. If you're on Version 1803, you've been updated to the newest Windows 10 April 20189 Update/upgrade which is causing the issue with SSD's and it was fully released on May 8, although it hasn't been fully distributed yet to all computers. (The first release of 1803 will show the build number as 17134.1. The patch Tuesday updated version will indicate 17134.4Cool If you're on Version 1709, then you're still on the previous version and build and the May 8 update you received was nothing more than the normal "patch Tuesday" update for version 1709.

So you may or may not be updated to the latest version and the May 8 problems with those updates vary based upon version number. Unfortunately, quite a few update types were released on May 8.

Hope this helps.

Grif

- Collapse -
Yes, 1803 Build 17134.1
May 9, 2018 11:28AM PDT

Thanks for the info, but iI am not sure whether it addresses my problem. The win version in my PC prior to yesterday's patch is 1803 Build 17134.1 . When Windows update ran yesterday, it downloaded and installed, but when the machine rebooted at the end of the update, after the BIOS loaded, all I got was a black screen with rotating circles. After an hour, I used a recovery media to revert back to the prior to Tuesday update configuration (above). I then disabled Windows update. Machine is functional, but I need to ultimately be able to re-enable windows update again without suffering the same consequence. Any help is appreciated.

- Collapse -
Then Try Running The Update Offline Like This:
May 11, 2018 9:55AM PDT

There are no sure things here, but as long as your computer is current running 1803 Build 17134.1, then first download the offline installer for the last Patch Tuesday Windows Update that arrived earlier this week. Click on the link below and download the appropriate 64 bit or 32 bit cumulative update file. (It's a large file so you'll want a fast connection to get it done in a reasonable amount of time.)

Microsoft Update Catalog Link for KB4103721
https://www.catalog.update.microsoft.com/Search.aspx?q=KB4103721

Once it's downloaded to your desktop, then make sure all hardware drivers are current, restart the computer, disconnect all USB devices from your computer, temporarily shut down your antivirus programs, get off the internet, and run the Cumulative Update installer. Restart the computer after the update is run. Reconnect any USB devices and re-enable your antivirus.

Or, as others have done, you can simply stretch out the update time in "Settings" and wait till MS comes up with a fix. Sorry.

Hope this helps.

Grif

Post was last edited on May 11, 2018 10:01 AM PDT

- Collapse -
Update to my recent post
May 11, 2018 6:01PM PDT

I just followed Grif's advice and checked Winver. My computer is running the Tuesday patch (17134.4Cool. So that may very well be why this install of 1803 was successful when the previous 2 attempts were not. Thanks for shedding light on this, Grif!

- Collapse -
Answer
Same problem . . .
May 9, 2018 12:21PM PDT

Yes, I encountered exactly the same thing. I did a system restore and was able to boot again, then disabled Windows Update service as a (very) temporary fix to prevent reinstalling. Two others beside myself report this problem on Krebs (here: https://krebsonsecurity.com/2018/05/microsoft-patch-tuesday-may-2018-edition/comment-page-1/#comment-466943 ) in the comment section. There's definitely an issue. I'd be very interested in anyone has tracked down the cause or if MS acknowledges it. Good luck. Let us know what works for you (if anything).

- Collapse -
Answer
Yes, I have had this problem, too.
May 11, 2018 5:54PM PDT

This has happened twice with 1803 (I think). The first time, it seemed to successfully install, but right after, I updated Advanced System Care and when the computer restarted, I got the black screen with the rotating circle. (I can't be sure if 1803 or the ASC update was the cause.) My Win 10 recovery USB would not work, but I finally got my computer's built-in recovery utility to restore the computer to Win 7.

I upgraded back to Win 10, made a new recovery USB and tried the 1803 build again (I guess I'm a sucker). Again, it seemed to install OK, but upon restart same black screen and rotating circle. This time, however, the recovery media did work, so it wasn't as big a deal to get everything back to the way it was.

Third time is the charm, I guess. 1803 installed with no problems a couple of days ago, and everything is running fine. I don't know what the difference was this time.

I do have an SSD; I didn't know about this issue until reading this thread.

It might be a good idea to delay updating for the time being.

- Collapse -
Win 10 1803 OS Build 17134.48
May 11, 2018 6:47PM PDT

As previously mentioned, on my laptop I used a recovery media to revert back to the pre-May 9 patch/update. The unit was then functional and I contacted Microsoft tech which took over the PC, put it in safe mode with networking, disabled all start-ups and then loaded the Tuesday Patch update. He then re-enabled several startups at a time and rebooted until the culprit was found. On the laptop it was an Intel persistence module - part of the graphics package- and not necessary for normal functioning. The laptop is now fully functional. Unfortunately, my desktop unit did not have that item and I tried to perform similar steps on it myself. Many hours later and multiple recoveries and resets it is now functional with all updates but I am not entirely sure what the true cause was. Perhaps Microsoft will ultimately determine the root cause and avoid problem with future patches/updates.

Thanks to everyone who provided suggestions.

- Collapse -
Answer
Micosoft recommends hold off KB4103721
May 12, 2018 3:39AM PDT

Last evening (Friday) I saw a post from Microsoft to hold off installing KB4103721 from May Patch Tuesday update to 1803. The patch is flawed and is "bricking" some machines. MS is working urgently on a new version of the patch.

This and 1803 have not been their finest hour!

- Collapse -
Answer
Try to turn off xmp
Jun 3, 2018 4:46AM PDT

I'm presently having samething and a lot of bsod.

I got to a lot of tests and tryouts.

I finally clean installed windows but surprised windows crashes again a soon as I entered games.

What works for me was clearing the cmos by jumping out the jumpers of the motherboard. My pc was running fine after that.

When every thing was fine, I went back to bios/uefi to reactivate xmp and boom system restarts and bugging again.

Reset cmos again and everything seems ok.

Xmp was enable for almost 1 year before this week. Now I can't turn it on. I suspect last windows update, or one of it's last build, to take part of it.

I will try it soon with linux or with a rolled back version of windows.