Windows 10 Version 1809 Is Now in Broad Deployment, Available to Everyone

[Porthos]

Microsoft announced today that they are now designating Windows 10 October 2018 Update Build 1809 to be ready for broad deployment, rather than targeted deployment.

For users who have been unable to install build 1809 through Windows Update, you can check for new updates today or tomorrow and it should now be available.

 

[MDD1963]

That was a truly agonizing long 90 second download!

 

[nlinecomputers]

Ah yes so it finally released and 1903 is only 2-3 weeks away. I only installed this a few times and had problems on several. I've been only installing 1803 right now. Giving 1809 a pass.

 

[Slaters Kustum Machines]

I downloaded the 1903 preview the other day. I like the dark mode. As for 1809 I have been installing it on all new machines that come in and it works fine, but that's to be expected on a fresh install.

 

[Porthos]

Ah yes so it finally released and 1903 is only 2-3 weeks away.

It was "released" back in November. But this is saying that they are comfortable removing the upgrade blocks they had in place going full throttle. Some computers were blocked from using Windows update to receive it. Now any one can get it with a manual check for updates should see it now.

I only installed this a few times and had problems on several.

We all know our client hardware/software use is vast and even though I have 80 computers on it now with no issues others may not be so lucky.

 

[Porthos]

I downloaded the 1903 preview the other day.

I am almost ready to pull the trigger as well.

I like the dark mode.

I have been using dark mode in 1809 since almost the beginning.

 

[Slaters Kustum Machines]

I am almost ready to pull the trigger as well.

I have been using dark mode in 1809 since almost the beginning.

Well, SOB, I never even checked on 1809, which I have on this machine and sure enough, it's there, lol. I only have 1903 in a VM.

 

[Porthos]

I only have 1903 in a VM.

I watch the progress of the build and when it is close (no watermark and no expiration date) I will upgrade one of my live machines after doing an Image backup. 18362 seems to be the one. I might pull the trigger Sunday.

 

[nlinecomputers]

It was "released" back in November. But this is saying that they are comfortable removing the upgrade blocks they had in place going full throttle. Some computers were blocked from using Windows update to receive it. Now any one can get it with a manual check for updates should see it now.

Yes, I know that. My point is that the full throttle release of a build usually occurs one month after the release. One month after 1809 release it was still withdrawn. It was a clusterfrak of a release and just illustrates why there should one be one release a year not two. I am going to have clients that will get back to back upgrades or even skip the 1809 upgrade and that is not good for my clients.

 

[Porthos]

It was a clusterfrak of a release

True. That is why it has taken this long to make it fully available.

just illustrates why there should one be one release a year not two.

True I agree. But I like being able to offer twice a year upgrade/tuneup packaged twice a year. $$ I do have several that call for this after I release a newsletter.

I am going to have clients that will get back to back upgrades or even skip the 1809 upgrade and that is not good for my clients.

I have a feeling that 1903 will go out slowly and thus not be exactly back to back. Lesson hopefully learned from 1809.

 

[Sky-Knight]

1809 isn't even fully available yet (3-29-2019). Now I was able to get it to pop on my stations configured with zero days of delay in the Semi-Annual channel, and I just did all 8 stations here at home.

But here's the weird part... my wife's laptop is 10 Home, and it WOULD NOT pull the update. I had to feed it a USB key with 1809 on it and run setup.exe to force it. It completed, and all seems well so far.

The only snag I've found in my testing with 1809 in the field is I had one unit, fresh install of 1809, and when a user with redirected folders logged in, the event log blew chunks with permission errors. I had to rename the profile directory he was living in, log in a second time, it made new folders, then I had to copy all his files down to the workstation and put them back from the workstation side. Simply plopping the files into the correct folders on the server didn't work.

So it seems to me that 1809 is back to the same stupid redirected folder bugs that 1511 shipped with. yuck.

Semi-Annual shouldn't get 1903 until October or so, and if you're worried about that just use a GPO to set your delay to six months. I'm adjusting all of my policies to get 1809 out before the end of May, and then hold again for six months. I'll see 1903 in Oct / September at best. But I'm always working my stuff one version behind. Been that way since 1709.