Wednesday, April 26th 2017

Microsoft Advises Against Installing The Creators Update Manually

Apparently, Microsoft is alerting would-be Creators Update takers that doing so manually (as in, before its automatic update roll-out through Windows Update itself) may result in a bad first experience. Microsoft is therefore suggesting that the majority of Windows 10 users should wait for the Windows Update version of the (ahem) update, due to concerns with some hardware compatibility problems.

In a blog post, Microsoft give the example of a user who reported issues between a Bluetooth connectivity accessory (Broadcom-based) for their PC and Windows 10 Creators Update, which resulted in Microsoft blocking all machines with similar hardware from being able to update until issues are solved. I for one must say I manually updated my system on April 7th and found nothing wanting, so these really do seem like hardware-specific snags. Microsoft is apparently doing everything in its power to make sure adopters of the latest version of Windows find a hassle-free experience on the other side of their screens, which is commendable. This does seem like a sensible solution to the problem, with power users (or simply users who don't care about warnings and are confident on their success and hardware compatibility) still being able to update, while less tech-savy customers are left waiting for a proven version for their hardware configuration. Here's hoping that doesn't take long, since the 3D-version of Paint really brought back childhood joy (for some of us, at least.)

Source: Blog.Windows.com, Tom's Hardware
Add your own comment

22 Comments on Microsoft Advises Against Installing The Creators Update Manually

#1
bonehead123
In other words, if you don't know EXACTLY how to fix stuff when sh*t happens, let windblows update itself and you will be happy, or so they want you to believe :slap: :fear: .
Posted on Reply
#2
cdawall
where the hell are my stars
I do clean installs with the new build and haven't seen any issues as of yet. Will have to keep an eye out for cheap units with Broadcom junk however.
Posted on Reply
#3
ssdpro
I never understand all the drama people find themselves in. People cry if their screen seems a little more red than they like. People cry if their junk butt broadcom controller needs an update and someone didn't check it. People need to get over this drama when everything isn't immediately perfect for their weird obscure config.

I did a manual clean install of creators update on a Z170 system. There is no long story to tell. I put in the USB, extracted the ISO, rebooted to it and installed. When it finished 20 minutes later, I checked my email and checked cnn.com to see if anything had happened in the world. I got some email and it turns out some things happened in the world.
Posted on Reply
#4
silentbogo
Too late... already did it. :laugh:
Downloaded the tool, cancelled the installation, and immediately got the "privacy settings" popup from Windows Update, which MS was talking about.
4 days later everything seems fine.
Posted on Reply
#5
dorsetknob
"YOUR RMA REQUEST IS CON-REFUSED"
Raevenlord said:
Apparently, Microsoft is alerting would-be Creators Update takers that doing so manually (as in, before its automatic update roll-out through Windows Update itself) may result in a bad first experience. Microsoft is therefore suggesting that the majority of Windows 10 users should wait for the Windows Update version of the (ahem) update, due to concerns with some hardware compatibility problems.
Really :laugh::laugh::laugh::laugh::roll::roll::roll: Microsoft having a Vista flashback:roll::banghead:
Posted on Reply
#6
Batou1986
I did the upgrade a few weeks back when CE went gold.
It did not end well, a bunch of service permissions got screwed up and resulted in cascading service failures.
Posted on Reply
#7
NBH
I updated manually and one of my video players kept crashing so I reverted back. A few days later I upgraded again and everything works fine. It is confusing when the update itself is also being updated, I guess you just have to get lucky with the timing to get a later version with potential bugs fixed.
Posted on Reply
#8
dorsetknob
"YOUR RMA REQUEST IS CON-REFUSED"
NBH said:
, I guess you just have to get lucky with the timing to get a later version with potential bugs fixed.
There is no lucky timing Its a Rolling Beta+ Version
Everyone that installs it is an unpaid Snooped on Beta+ tester
Some are happy with this others hate this
Posted on Reply
#9
IvanP91v
I did the update manually on a Z170 mobo and lost USB3.0 connectivity, did a clean reinstall with the ISO that was updated to 1703 and have no USB3.0 again.

Installed 1607 from an older ISO and have USB3.0.

Good job Microsoft.
Posted on Reply
#10
TheOne
I do like that the new Media Creator tool allows you to select from a list of your drives instead of auto detecting, the Anniversary tool had issues detecting certain USB drives.

I've been using my old X58 system as a kind of test bed, updated both ways before April 11th, didn't really notice any problems, but I don't really use the system.
Posted on Reply
#11
thevoiceofreason
I have trouble with USB audio in the Creators Update. It's like they don't even test this stuff.
Posted on Reply
#12
XiGMAKiD
ssdpro said:
I never understand all the drama people find themselves in. People cry if their screen seems a little more red than they like. People cry if their junk butt broadcom controller needs an update and someone didn't check it. People need to get over this drama when everything isn't immediately perfect for their weird obscure config.
Because some people love drama and do it for the sake of the drama
Posted on Reply
#13
MrGenius
Wish I hadn't done it. But I did. And got more headaches than I bargained for. Whatever. Could be worse I guess.
Posted on Reply
#14
Camm
Had this last night whilst trying to use a MSDN provided image, installer would bluescreen, with I'm assuming the culprit to be the new 1080 Ti I installed.

Used the older 1607 image and no dramas. Man, I like rolling releases, but Microsoft needs to tighten their QA more.
Posted on Reply
#15
FYFI13
Had to roll back one of the laptops as after upgrading i faced "access denied/object not found" party. No issues on my gaming rig though.
Posted on Reply
#16
Live OR Die
I've been running it for 3 weeks no issues here haha.
Posted on Reply
#17
jmcslob
I did the manual update last weekend.. All is good... Which is unusual for me and windows 10...
Posted on Reply
#18
FYFI13
FYFI13 said:
Had to roll back one of the laptops as after upgrading i faced "access denied/object not found" party. No issues on my gaming rig though.
Scratch that. Can not use Windows Store and Windows Update. Tried to do clean install, twice (from different ISO images), same thing. 3:1

Posted on Reply
#19
DRDNA
I did the manual update on my laptop in my sig and kept getting Watchdog Timer Driver can not load please reboot to install the driver; I would get this message at every reboot and felt its now more an error than a message. I then rolled back no problem and all was back to normal. Then I backed up the rig and was getting ready to fresh install the Creator update but then Windows update caught the Creators update and I figure hell why not try it again this way and when it updated to Creator everything was perfect! Hmmm go figure!
Posted on Reply
Add your own comment