Managing Windows 10 Creators Update rollout for a seamless experience

JohnBurns said:

From what I understand, if you have Windows Home, you are forced to accept Creator Update. Is this correct?

Only Pro has the option to defer updates. For Home you will eventually get it through automatic windows updates. 'Eventually' could be not for some time though, the rollout is being phased and your turn may be a long way off. As it says in post #1...

The Creators Update will begin to roll out on April 11th. Like with the Anniversary Update we delivered last August, this update for Windows will proceed in phases.

Could be months before you get yours...

What if any is the problem with letting your computer stay on 1607 14393.970 and just wait for the update sometime after the 11th?

alphanumeric said:

None, many will just wait for it to arrive via Windows update. Those that can't wait do the upgrade manually.

TX, that is what I thought, no hurry here. I have my insider SSD primed and waiting. ._.

eddward said:

I have upgraded 1 desktop and 1 laptop from AU to CU and also have one warning about Windows Hello on both devices.

EventID 360:
Windows Hello for Business provisioning will not be launched.
Device is AAD joined ( AADJ or DJ++ ): Not Tested
User has logged on with AAD credentials: No
Windows Hello for Business policy is enabled: Not Tested
Local computer meets Windows hello for business hardware requirements: Not Tested
User is not connected to the machine via Remote Desktop: Yes
User certificate for on premise auth policy is enabled: Not Tested
Machine is governed by none policy.
See What's new in Active Directory Federation Services for Windows Server 2016 for more details.

So how to get rid of it ? Any registry hack ?

Windows Hello is not available on my devices.

Did you managed to resolve this? I am seeing it too. I noticed your thread was hyjacked and went completely off topic.

Sayjimwoo said:

Did you managed to resolve this? I am seeing it too. I noticed your thread was hyjacked and went completely off topic.

Yes, sort of. Only workaround right now is to disable event logging for this kind of events. Warning is most likely harmless, but right now I am not sure what else this may prevent from logging.
Navigate to Application and Services logs - Microsoft - Windows - User Device Registration - Admin and Disable Log in Actions... this should stop it.
But you know, it's not a real fix. I think we have to wait for Microsoft.

JohnnyGui said:

I've done a clean install of the Creators Update through the publicly released Media Creation Tool by Microsoft.
For some reason, I've been offered the following update by Windows Update:

"Windows Malicious Software Removal Tool for Windows Insider Preview and Server Technical Preview x64 - March 2017 (KB890830)"

How is this possible? Shouldn't this version not be an Inisder or Technical Preview?

Can someone please help me with this?

I've got this update as well after clean install, but I'm in Release preview ring now, so don't know, but I don't think there is something wrong.

eddward said:

Yes, sort of. Only workaround right now is to disable event logging for this kind of events. Warning is most likely harmless, but right now I am not sure what else this may prevent from logging.
Navigate to Application and Services logs - Microsoft - Windows - User Device Registration - Admin and Disable Log in Actions... this should stop it.
But you know, it's not a real fix. I think we have to wait for Microsoft.

Thanks, much appreciated. At least I don't have to see the log now until MS fix it.

I'm a little worried about installing this update today. Is there a way to delay it a little longer ? I'm on Windows 10 pro