Current Status of Windows 10 October 2018 Update version 1809

bru said:

And no there is nothing preventing my computers from getting it.

What's preventing you from using the MCT to deploy it manually?

Dirk Gently said:

What's preventing you from using the MCT to deploy it manually?

Starting with Windows 10 Microsoft has made it clear that they want to control updates, so I let them. Its too bad they screw it up royally.

bru said:

Huh? MS said they again started again rolling out 1809 a while ago. Why would they stop it for the holidays? And even if they did what does patch Tuesday have to do with the 1809 update? I have yet to receive 1809 on five computers. Its clear MS has no idea what they are doing. It shouldn't take this long to issue an OS update. And no there is nothing preventing my computers from getting it.

Yes, v.1809 was re-released, and you can get it via a number of manual methods, but MS has put a "limit" on getting it via WU (either automatically or with a manual Check For Updates). As I understand it, the roll out via WU is being being controlled by MS for compatibility reasons. I'm not sure what those parameters are, but my system has not received v.1809 yet and I can find no published issues that should prevent it from receiving the FU. I'm just waiting until MS decides that my system should get it. v.1803 runs just fine, so I'm OK with the "if it ain't broke, don't fix it" mentality. Actually, I'm sort of waiting to see how long it will take for MS to "find" me.

jamis said:

Yes, v.1809 was re-released, and you can get it via a number of manual methods, but MS has put a "limit" on getting it via WU (either automatically or with a manual Check For Updates). As I understand it, the roll out via WU is being being controlled by MS for compatibility reasons. I'm not sure what those parameters are, but my system has not received v.1809 yet and I can find no published issues that should prevent it from receiving the FU. I'm just waiting until MS decides that my system should get it. v.1803 runs just fine, so I'm OK with the "if it ain't broke, don't fix it" mentality. Actually, I'm sort of waiting to see how long it will take for MS to "find" me.

My computers certainly aren't broke either and I doubt there's anything earthshaking in 1809 that I will even care about but for me the issue comes down to the fact that MS controls updating its OS and it can't even do it in a timely manner. I know I can manually update but all that does is let MS off the hook for not updating their product as promised.

f14tomcat said:

Have you tried with MCT? Just asking, cause lots have given up with the wait-for-no-reason scenario. If you are pretty sure you're compatible (I know, you said you were), get the MCT ISO and upgrade yourself. Make sure you have a good image backup first. Worst scenario is it won't work. Best is you're up and running 1809.

I answered that previously. I'm on the wait until I receive it (if ever) program I guess. I just find it sad that MS can't distribute its updates in a timely manner. I won't even get into issues with problems with updates, but when you can't even distribute them to your customers that is pretty bad.

slicendice said:

This isn't working for me! Edge bookmarks are totally borked up AGAIN! I have tens of duplicates of same bookmarks AGAIN! I just cleaned them up on all my devices where I use Edge. I will have to revert back to Chrome. I can't find squat in this mess.

Same here! Edge is a hot mess and it won't let me fix the problem. My favorite browser is still FF and I only use chrome or IE if a website forces me to.

Bree said:

Fat32 with an Active partition is an absolute requirement if you want boot on a legacy system. UEFI can boot from anything, a legacy BIOS can't.

No.

Bios can boot from either Ntfs or Fat32 formatted flash.
Uefi in native mode (Secure Boot enabled, legacy boot disabled) cannot boot from Ntfs.