Reread the first post in this thread.
Blocking issues are a high priority for us to address as quickly as possible. If we detect that your device may have an issue, such as an application incompatibility, we will not install the update until that issue is resolved, even if you “Check for updates”. We do this so that you avoid encountering any known problems.
Exactly. Even though I can find no blocks for my system, I feel no need to attempt a manual check for updates. My system has received a half dozen CUs and SUs since v. 1809 was originally offered, all via WU auto update. I have NO reason to update to v 1809 until MS deems it so. Telemetry is running on my system, so it can provide the information needed.
Finally, lots of new drivers are being rolled out from OEM for my laptops and desktop.
I've been using OEM drivers with my Dell laptops without major problems other then the occasional Windows update offering to downgrade some drivers to an older version.
The October update is only being offered on my desktop and just one of my laptops so far, I think Dell is a little behind on releasing new drivers for the update.
Checked for updates a few hours ago on my wife’s old laptop, Dell Inspiron 5040n, and got 1809. Since it’s so slow it took a long time to download and install. Everything looks good and no problems so far. Used MCT to update a Dell XPS 8300 a few days ago and it’s running find as well. I’ll be holding off for another month or two on my other two desktops just to be safe as they’re both production PC that I’d rather not risk.
Now, isn't that great.....?
A quick background.
I decided to upgrade my laptop by replacing the HDD with a Samsung 860 SSD. Although the image of 1803 I created is still in my backup disk, I thought that it would be a good idea not to restore it on the SSD but to go for a clean install, to avoid mistakes of the past.
So I did and installed 1803, partitioning the system with a revised script, from @Kari's excellent tutorial.
Everything went very fast and the first thing I did, as soon as the installation finished, was to defer Windows Update for 30 days, to avoid for now installation of 1809.
Having done that I started to update drivers and apply my all-version tweaks before I make an image of the fresh installation.
After a 3-hour break (my football team was playing against AC Milan for the Europa League...Yeah, we did it!!!) I came back to my laptop to create a Macrium Full image. During my absence I was offered the latest Windows updates, as Tuesday was Patch-day, so I asked it to download them and that brought my fresh installation to 17134.471.
After restart, I got a notification, from Windows Update, that my PC was missing some critical features, so I said what the f..., install them too....before imaging!
Huuuge mistake!!!Why?
Because miraculously and although Feature Updates were still deferred for 30 days, the "missing features" where installed... i.e. 1809!!!!
So I'm now on 17763.194, without any further notice!....and guess what, I went to the Advanced Update settings and zeroed the defer days, as Microsoft had decided not to honor their own setting.
So guys, I think that they are pushing 1809...just be aware!
And a final note... It took me directly to Windows 10 v1809 Build 17763.194, as I don't have KB4471332 in history
Last edited by ddelo; 14 Dec 2018 at 04:03.
Why is it a "Huuuge mistake!!!", something doesn't work ?Now, isn't that great.....?
A quick background.
I decided to upgrade my laptop by replacing the HDD with a Samsung 860 SSD. Although the image of 1803 I created is still in my backup disk, I thought that it would be a good idea not to restore it on the SSD but to go for a clean install, to avoid mistakes of the past.
So I did and installed 1803, partitioning the system with a revised script, from @Kari's excellent tutorial.
Everything went very fast and the first thing I did, as soon as the installation finished, was to defer Windows Update for 30 days, to avoid for now installation of 1809.
Having done that I started to update drivers and apply my all-version tweaks before I make an image of the fresh installation.
After a 3-hour break (my football team was playing against AC Milan for the Europa League...Yeah, we did it!!!) I came back to my laptop to create a Macrium Full image. During my absence I was offered the latest Windows updates, as Tuesday was Patch-day, so I asked it to download them and that brought my fresh installation to 17134.471.
After restart, I got a notification, from Windows Update, that my PC was missing some critical features, so I said what the f..., install them too....before imaging!
Huuuge mistake!!!
Because miraculously and although Feature Updates were still deferred for 30 days, the "missing features" where installed... i.e. 1809!!!!
So I'm now on 17763.194, without any further notice!....and guess what, I went to the Advanced Update settings and zeroed the defer days, as Microsoft had decided not to honor their own setting.
So guys, I think that they are pushing 1809...just be aware!
And a final note... It took me directly to Windows 10 v1809 Build 17763.194, as I don't have KB4471332 in history
Not really...so far so good Mike...but I had decided to wait some more time, let's say until January's patch Tuesday.
That's why I had deferred Feature updates.
But our friends in MS, skipped the deferred setting and installed 1809. That was the mistake. The fact that I trusted that set defer for so many days would be honored by MS.
As mentioned I just cleaned installed. Once I install everything back, we'll see if there will be any problem.
For instance I'm just starting installing my HP LaserJet MFP.... I have seen reports with problems with HP printers. Let's see how it will go.
Quote
