MS's Spring Creator's Update is Apparently Very Buggy
And lacking really good features
Saturday, May 5, 2018 by DrJBHL | Discussion: Personal Computing
I don't know this from personal experience, but Martin Brinkmann tends to know what he's talking about, and he did the update...
You should read the article linked and, if possible, defer this update. He describes a method for W10 Home, as well, using the metered charge option.
Source:
https://www.ghacks.net/2018/05/05/here-is-why-you-may-want-to-skip-this-months-windows-updates/
Reply #22 Wednesday, May 9, 2018 2:06 PM
Check the Windows Event Log, Dave.
In my experience this is usually caused by a Windows service failing to start (or taking too long). Windows Services are started sequentially, so if one hangs the next one cannot be started until the hung service times out (which can take up to 30 seconds). This can delay the appearance of the Windows Desktop and the result is a black screen where only the mouse pointer is visible.
Using the Event Viewer (Control Panel -> Administrative Tools) right after Windows startup you can identify the service causing the problems by looking at the time interval between events (normally there's a ton of entries all happening in very quick succession after logon, but if you find an interval between two events of several seconds, Bob's your uncle).
You can then either disable or delay the startup of the service causing problems (so the others can start first without interference). Here (Win7) the only problems I ever had of this kind were with the Razer services.
Reply #24 Thursday, May 10, 2018 1:03 AM
I've chosen to defer all Windows updates in Win 10 since the early days, given how many of them came with issues and borked peoples machines. I will only get updates when they have been released for a while and the bugs have been ironed out, though sometimes I don't bother and simply hide those I don't want.
Reply #25 Thursday, May 10, 2018 9:08 AM
though sometimes I don't bother and simply hide those I don't want.
Reply #26 Thursday, May 10, 2018 3:17 PM
Check the Windows Event Log, Dave.
Well I think I found it. Disabled it, won't cause a problem (until I decide to use the utility again without remembering to enable it - that'll remind me.) Don't want to name it here since I could easily be wrong, other than to say it's nothing to do with Stardock or WinStep. Since it only caused a problem after updates, it'll be a few months before I feel like I've got it.
Thanks again Jorge.
Reply #27 Thursday, May 10, 2018 6:18 PM
The latest installment via yahoo news. The so called 'patch' for the 2018 creators update has caused infinite boot loops after installing.
Reply #28 Thursday, May 10, 2018 6:43 PM
I had some odd issues with the update. Most notably a slow login and issues with the Windows Store. I ended up resetting and it is now working fine on this update.
Reply #30 Thursday, May 10, 2018 10:53 PM
though sometimes I don't bother and simply hide those I don't want.
Color me stupid. I was unaware that you could hide updates with 10.
In Win 10 Pro you can hide problematic updates in the update options/settings. However, there are various programs available at majorgeeks.com that allow users to disable automatic updates and hide updates in both Win 10 Home and Pro.
Reply #31 Saturday, May 12, 2018 10:07 AM
Ok, I finally found a problem that caused me to have to reinstall Windowblinds on all my machines.
After the 1803 update, windowblinds would not skin the taskbar button preview popup that shows when you mouseover the button that has an open window.
All is well after reinstalling WB.
Reply #33 Tuesday, May 15, 2018 6:04 PM
I just booted into Win 10 and there were a bunch of updates for 1709 but I didn't get an update for 1803. I wonder if they stopped the update because people were having problems with it. I hit the update button twice I guess I'll try again later.
Reply #34 Tuesday, May 15, 2018 10:40 PM
Be nice if they would be kinda sorta transparent in what the hell is going on. But hey, Microsoft...
Reply #35 Wednesday, May 16, 2018 1:45 AM
Ahahahaha.
Bastard.
Some are that from birth. Me? A self made man. ![]()
As I was saying...more on 1803. How can they put out an update like that?
Reply #36 Wednesday, May 16, 2018 1:46 AM
I just booted into Win 10 and there were a bunch of updates for 1709 but I didn't get an update for 1803. I wonder if they stopped the update because people were having problems with it. I hit the update button twice I guess I'll try again later.
I'm still 1709, and they may have taken that pos off their servers. My advice ALMonty...don't push your luck.
Reply #37 Thursday, May 17, 2018 2:34 PM
All my 3 devices (1 desktop, a laptop and a tablet) auto-updated Windows 1803 updates, and everything is fine. After reading this kind of post on forums, i feel lucky!
I really hope i won't ever get to clean re-install on the tablet, drivers on chinese stuff are always hard to find ! /Crossfingers ![]()
Reply #38 Thursday, May 17, 2018 3:24 PM
Just bought a New Computer it had Win 10 v15 then I updated it
to v1803 ... and then loaded all my stuff back on and some of the
Stardock stuff still some more to go
BUT ALL is working Fine for me ... not Buggy ..
except for MS EDGE , you can trash that browser !!
Reply #40 Thursday, May 17, 2018 6:43 PM
They didn't pull the update because one of my machines is getting it right now. Wish me luck....
Please login to comment and/or vote for this skin.
Welcome Guest! Please take the time to register with us.
There are many great features available to you once you register, including:
- Richer content, access to many features that are disabled for guests like commenting on the forums and downloading skins.
- Access to a great community, with a massive database of many, many areas of interest.
- Access to contests & subscription offers like exclusive emails.
- It's simple, and FREE!







Reply #21 Wednesday, May 9, 2018 1:51 PM
black screen when booting Windows
Don't know if we're talking about the same "black screen", but if not this may be useful to someone else. For the last 9 months or so it has not been unusual for me to end up at a black screen after an update. It occurs after logging on at the login screen. The mouse and keyboard are responsive and the mouse is visible but otherwise the screen is black. It didn't happen to me after the update we're talking about in the OP, but it did happen again after today's follow-up update.
My routine, which has worked consistently (so far), is to give the machine an extra 15 seconds or so after the black screen pops up, then press [Alt][Cntrl][Del]. From the system menu that pops up, I can click on "Logoff" and it logs off. After logging back in, the machine is fine. After the 1 time things are fine after reboot or logoff, it has been a fairly consistent 1-time error after update.