Windows 10: Creators Update

I have a Dell Inspiron 15 Model 7537 and have no sign of the Creator's Update. I'll wait a while longer for it to appear on Windows Update based on your experience! Post 28 indicates the problem may be a driver error. Please post if you sort out the problem.

 

And we reach end of august some four and a half months after its initial release and still no sign of creators update reaching me through windows update. I am still determined to wait but so many people are still waiting for it. This drip feed from ms seems to be pretty ridiculous. How can they still be rolling it out when the next fall creators update is soon to arrive? Surely they should of finished rollout and unleashed it to the compatible machines on windows update. I think I have suffered because my pc despite being pretty modern and still very powerful (skylake cpu, SSD, nvidia 980ti) is suffering because it is unbranded as such. It's a custom built pc from uk company pc specialist and as such isn't on microsofts VIP list!

i know people can manually force it but it should come through windows update. That's the prescribed way of getting updates and at the end of the day most users are going to be unaware of these methods and rely on windows update to do its job.

 

I use the MCT/Media Creation Tool to get the latest Version which is 1703 but the Build always lags, what I got last week is Build 15063.0. During or after install it updates to the latest build, currently 15063.540. Since I have various clients and computers available and time I download both the 32-bit and 64-bit version in both the bootable 8GB USD Thumb drives and the .iso files used to create a DVD.

 

I do that too. There should be just enough space left on the USB to put on the 32 and 64 bit standalone packages for the 15063.540 Cumulative Update (KB4034674) - saves download time if you're installing on a lot of machines.

 

I shouldn't have bothered trying to install this garbage update in my W10 Pro VM.

It has displayed the "high quality" coding that I've come to expect from the W10.

After downloading 7.5 GB of updates and wasting 5 hours, the update has broken the graphics, so the system is unusable. *Mad
I can hear it start, but it's impossible to login or do anything else.

I eventually managed to get into the so-called Recovery tools:

• Safe Boot isn't an option
• Rollback doesn't work
• Reset doesn't work

Luckily I used a copy of the VM.

I guess it can never be updated again (which is probably a good thing given the constant W10 update debacles).

 

Indeed - I keep commenting on poor MS QA on the forum. Does Windows Update only offer you an update for a VM when the time is ready? I haven't been offered a CU update yet for my 3 year old Dell Laptop and have no intention of updating it until MS consider the time is right via Windows Update.

 

I downloaded a tool from MS and ran that.
It said everything was OK (at the beginning of the process).

I was finally able to get into Safe Mode by using the "bcdedit" command to change to the boot file.
However I couldn't install/uninstall anything.
Apart from that, it seemed to be running normally.

I still can't perform a normal boot.


It's only a few weeks until the next mega-update, so I thought that I'd better get the last one. *Sad

Update
I was able to uninstall the graphics driver and during the reboot W10 installed its default driver.

I'm now able to boot normally (I haven't risked trying to install the VM graphics driver again). *Smile

 

Gulp! Turned on pc this morning and checked for updates. It's coming through now. Very nerve wracking!

EDIT lots of testing later but initial thoughts good. Everything major seems to be working ok! Can't understand why it took so long get pushed though

 

See, you still got luckier than I did. When it came through on mine it took out all networking adapters thanks to the "Broadcom issue", if you recall. Lacking the know how to fix at the time I had to choice but to roll back to 1607. Haven't seen it coming back since, which I've never found an explanation for as to why either.

 

That issue is fixed now...

https://answers.microsoft.com/en-us/...=1492183836572

It should be safe to manually update to 1703 now. You may want to download the standalone package for the latest cumulative update from the Update Catalog before you try.
Cumulative Update KB4040724 Windows 10 v1703 Build 15063.632

 

Yeah I know, thanks Bree. I solved the problem by doing a fresh install of 1703 I was going to migrate all my stuff to. Just been too busy to do it since.

 

I'm still sitting on Anniversary Update despite having relatively new PC that I purchased in January (HP Omen PC 870-095, used as nice-looking but only boring home PC so nothing fancy software/hardware installed there) - and I'm really wondering what prevents Creators Update auto-update on it?
According to folks on HP forum as well as HP official release my PC is compatible and could be manually upgraded to CU - but that's exactly what I'm trying to avoid as I sense some unexplained troubles ahead: At the end of a day if I am not offered this update, then perhaps something's not kosher? I have some doubts about this Radeon for instance... Or perhaps I am being superstitious?.
I just find it quite bizarre that nearly half year after this OS was formally released a mere 30% of Win10 users was upgraded. And that there's another release just around the corner.
How many of you were offered it straight-away? For those who were offered it ar later stage, had anything of importance been updated, i.e. software driver etc.?

 

For the people that doesn't see CU available on Windows Update... if you upgraded 1511 to 1607, you probably have the "Defer Feature Updates" option in Windows Update, even if you are in home versions... supposedly because of a patch MS released in 2015...

If you have that cheked, uncheck it and probably WU will be able to download CU by it's own... I had that in my old HD in AU 1607

 

Not sure what was version was supplied by HP when I unpacked the box (all this excitement!) but it's quite possible that 1607 was deployed later.

I also remember reading quite recently somewhere on El Reg (top comments here) about 'defer' option working wrong way round (which I'm afraid would not surprise me at all, but that's another story).

So how do I check this on my PC though? It's home version, 'defer' option is not there, obviously, and registry settings seem okay to me?

 

I still don't have the CU on my 3 year old Dell laptop running Home. I don't have the Defer option - what's the patch you refer to?