How to absolutely, positively keep the Win10 1903 forced upgrade at bay

Topic

New Reply

Wit hWin10 1903 around the corner — some corner — now’s a very good time to set your Win10 machine so it won’t upgrade itself to 1903, no way, no ho
[See the full post at: How to absolutely, positively keep the Win10 1903 forced upgrade at bay]

3 users thanked author for this post.

abbodi86, AusJohn, Elly

Reply | Quote

Replies

With Microsoft alerted in time to a sever installation bug, after Windows 10 Insider Preview build 18362 was released to the Slow ring, we narrowly escaped 1809 like release fiasco with 1903.
Microsoft blocked Windows 10 build 18362 from the Slow ring.

Reply | Quote

that was due to beta testers unable to upgrade from build 18356.16 to 18362

1 user thanked author for this post.

woody

Reply | Quote

According to the Windows Experience blog:

“In the meantime, Build 18362 will no longer be offered to Insiders who are on Build 18356.16, so Insider PCs don’t continue to try and take Build 18362 and fail.”

If you are on another build it should download and install.

--Joe

Reply | Quote

After quite a bit of very random and maddening pain, my entire organization is skipping 1809 entirely.  Workstations that we tested have all been rolled back to 1803.

Problems include:  black screens on certain graphic intensive pro applications, severe and random performance issues pertaining to the same, weird complaints about spontaneous reboots from test users.  Local search not working (a throwback to 16xx ? ).

My flight of 1903 insider installations are more stable than the currently fully patched 1809 machines.

Just our two cents . . .  (and worth both pennies!)

~ Group "Weekend" ~

1 user thanked author for this post.

woody

Reply | Quote

Can someone explain me, why does microsoft needs to release upgrades  that needs alot of testing time in tight scheldules?

Is it really hard to make a 1 feature update per year?

Just someone who don't want Windows to mess with its computer.

Reply | Quote

You should be thankful that [they] don’t give us major updates every three months! It could happen.

Reply | Quote

Wasn’t v1809 supposed to be the good release that was supposed to be able to power business for a couple of years?

To be fair the only trouble I’ve had with Windows lately has been because of a [error-ridden] display driver release this month by nVidia – crashed the whole system it did.

I contacted nVidia then rolled it back to a prior driver release and have had no other trouble. Kind of uncommon for nVidia to get that wrong; they’ve been pretty solid for years.

Now, whether it’s Microsoft’s fault ultimately at the root or nVidia’s… I can’t really say. The very same driver release for Win 8.1 works just fine with the very same OpenGL applications.

Other than that, Win 10 v1809 seems to have a worse reputation than it deserves, based on my personal experience.

-Noel

Reply | Quote

Noel,

I agree I have had zero problems with 1809 on 3 machines other than the fact that MS still can’t seem to get everything to work properly on a small home network with SMBv1 disabled.

However, since SMBv1 problems aren’t much to worry about on a home network I just leave it enabled and things work just fine. As always YMMV!

May the Forces of good computing be with you!

RG

PowerShell & VBA Rule!
Computer Specs

Reply | Quote

It (1809) is the base for 2019 LTSC, which has been quite solid for me. Seems like it’s all the extra cruft that causes problems.

Reply | Quote

As a I run a computer shop, I periodically rejoin Insiders to check the current state of the upcoming feature update. I normally have updates set to pause for 60 days, so I can control when I run my tests. Last night I imaged my ThinkPad and then proceeded to rejoin Insiders and upgrade to Version 1903, build 18362.1. What happened has never happened t one of my machines during a feature update installation. My 64-GB SD card, used for SyncBack automated backups, was corrupted and unreadable after the update. It was fine immediately before the update as I had just used it. The feature update itself, with the exception of my SD card files being nuked, seems to be ready to go, IMO. However, the corruption of my SD card, and reassignment of the drive letter, is very disconcerting. I wonder if Microsoft even tested any machines with an SD card running.

GreatAndPowerfulTech

1 user thanked author for this post.

woody

Reply | Quote

See https://www.askwoody.com/2019/report-of-win10-version-1903-upgrade-trashing-an-sd-card/

Also… do you have a Realtek SD card reader?

Reply | Quote

RetiredGeek wrote:

Noel, I agree I have had zero problems with 1809 on 3 machines other than the fact that MS still can’t seem to get everything to work properly on a small home network with SMBv1 disabled. However, since SMBv1 problems aren’t much to worry about on a home network I just leave it enabled and things work just fine. As always YMMV! 

What type of  network issues? We have 1809 on a few mixed networks (SMBv1 enabled on only one) with no issues reported. Did have to enable Function Discovery Provider Host and Function Discovery Resource Publication services for 1 client that likes to browse their networked computers.

Reply | Quote

woody wrote:

Full step-by-step instructions coming up in Computerworld.

Is the Computerworld article already on-line? Thanks.

César

Reply | Quote

Woody told me yesterday it may be Mon before ComputerWorld publishes it.
Wait for the link to go live.

1 user thanked author for this post.

Cesar

Reply | Quote

well woody now that 1809 was late to the “business” party and recently made it to the SAC channel, this recent story from Softpedia news was asking whether the upcoming 1903 release is ready or not:

https://news.softpedia.com/news/so-is-windows-10-version-1903-ready-or-not-525494.shtml

Reply | Quote