Windows 10: Waiting 11 days for creators update...

The Creators Update privacy settings update was installed on my pc on 18th May, and I am still waiting for the creators update to appear. Since then the update kb3150513 for version 1607 has been installed again.I would be interested to know how long other users have had to wait.*Smile

:)

 

Creator update problem

Assuming Creators Update has been installed for seven (7) days or less, see
https://betanews.com/2017/04/11/how-to-rollback-and-uninstall-windows-10-creators-update/

 

Windows 10 Creator Update

Hi

Windows 10 Creators Update Privacy Settings for x64-based Systems (KB4013214)

Successfully installed on 11/07/2017 but I am still waiting for Windows 10 Creator Update to install

 

See if you can choose to update now by viewing windows updates Most often it will perform the download. You can then delay the reboot and installation indefinitely by remembering to reset it (max 6 days each time). If you want to download and install now and do not see the link you can perform the upgrade from this Microsoft web site by clicking update now:

Download Windows 10

 

I tried to do it using the upgrade assistant but ran into a DPC watchdog violation error halfway through the install. Had to reinstall from a back up after that, as I was stuck in a loop (this was before the privacy setting update appeared). I've since read that Microsoft recommends waiting for the upgrade to be offered, which is what I am now doing.I thought it would have appeared by now, though.

 

You have a problem that is causing the upgrade to fail. Until you fix that problem, you won't upgrade to Creator's Update by any means.

 

Since that upgrade failure, The privacy settings update was installed - I thought that was progress?

 

To look into the upgrade failure these are some of the steps that can be done:
1) Open administrative command prompt then copy and paste this command:
C:\$Windows.~BT\Sources\Panther
2) It will produce a folder in which some of the files are hidden. Open these logs and post via onedrive share link into the forum

setupact.log

setuperr.log

Open administrative command prompt and run:
3) run sfc /scannow
4) run dism /online /cleanup-image /restorehealth
Using onedrive post a share link into the forum for each the cbs and dism log

%windir%\logs\cbs\cbs.log | find /i "[SR]" >> C:\cbslog.txt & notepad C:\cbslog.txt
%windir%\logs\dism\dism.log | find /i "[SR]" >> C:\dismlog.txt & notepad C:\dismlog.txt

 

Other things that you can try:

1) remove all attached hardware from the computer that is not essential
2) turn off any antivirus temporarily when you are ready to attempt the upgrade
3) perform a clean boot using msconfig to turn off all non-Microsoft applications/drivers and using task manager to turn of items on boot
How to perform a Clean Boot in Windows 10 - TechNet Articles - United States (English) - TechNet Wiki

https://support.microsoft.com/en-us/...oot-in-windows
4) run administrative command prompt: chkdsk /scan (if any problems are detected plan to run overnight chkdsk /x /f /r
5) make sure that sfc /scannow reports that it found no integrity violations and dism /online /cleanup-image /restorehealth completed successfully
5) attempt windows 10 upgrade using the Microsoft web site in the earlier post:
Download Windows 10

If there are any error messages please report them in the forum

6) alternatively you can attempt now to perform an in place upgrade using a windows 10 iso. If that is successful at repairing any problems with the operating system/registry that may have been preventing the upgrade then a windows upgrade may then work smoothly.

 

Thank you for your suggestions. I will look into it, but now I have to sleep to be ready for work later.Hope to speak to you again later.

 

Update:
I waited, and waited, then on 19th Nov I got the 'Check privacy settings' notification. The 'Preparing to install' phase took hours to complete, but eventually the upgrade started and went without a hitch. My PC was updated to Version 1709, bypassing the first Creators Update altogether, and everything seems to be working fine. Just when I was giving up hope!

 

That was a long sleep *Smile

How odd - not the skipping to 1709 bit, the fact that you never got offered 1703. Whatever lingering problem that may have stopped you getting the Creators Update as you should have done should now have been fixed by installing your new OS. Relax and enjoy.

Thanks for letting us know.

 

Rip van Winkle lives!
Maybe it had something to do with the recent updates for Windows Update reliability.