Have you been pushed from Win10 version 1803?

Topic

New Reply

I’m seeing more reports of the way MS has said it will start to push people off of Win10 1803 – but I have yet to hear from anyone who’s been pushed.
[See the full post at: Have you been pushed from Win10 version 1803?]

Reply | Quote

Replies

I’m not sure if this qualifies, but my Win. 10 Home 1803 was almost forcibly updated a couple of weeks ago by Win. Update Agent; which (I am ashamed to say) quietly installed itself after I forgot to run Wushowhide before I did an update. It even managed to do this despite having my internet connection set to metered and having Win. Update blocker on. I managed to stop it before it finished by killing the Win. Update Agent process in Task Manager and uninstalling the program. That’ll teach me to never forget to run Wushowhide before I update. I thought I should share this as a warning to others who might fall prey to this nonsense from MS. The morals of the story; #1: be sure to run Wushowhide before you update. #2: Check your list of installed programs at least once every day to be sure Win. Update Agent hasn’t found a way to sneak back in. #3: The price of liberty from having MS forcibly upgrade your system without your express consent is eternal vigilance.

Reply | Quote

I thought there was a way to remove it within 30 days. Check. Hopefully you can recover.

Reply | Quote

You have 10 days to roll back to the previous version.

1 user thanked author for this post.

KP

Reply | Quote

I didn’t need to recover anything. I was luckily able to stop it before it made any permanent changes. How it happened was one evening when I was doing some web browsing then next thing I know the fan on my machine was running full blast for a long period of time like my machine was doing some intense updating or something, then I took a look at Task Manger and my processor use is like 100 percent and that’s how I could tell something was clearly amiss. I knew I had Windows Update Blocker on, so I didn’t think it could be that, then I checked to see what processes were going and that’s how I found out that Windows Update Manager had snuck its way on board. I then checked my installed programs and was able to confirm that Win. Update Manager was indeed the culprit. All this occurred within the space of like 30 seconds and by the time I figured out what was going on Windows notified me it was going to “update my machine” and that it needed to reboot itself before it could finish. It told me to “finish whatever work” I was doing and that it would reboot itself within 30 minutes no matter what I did. I said no thank you and shut all the Win. Update processes down and uninstalled the program.

After I stopped it, all seemed well, the update process stopped and the warning was gone, so I breathed a big sigh of relief. Everything seemed to be back to normal with no lingering ill effects. I was a little worried about having stopped it in the middle of updating, but like I said, I was 99 percent sure I had stopped it before it had made any changes. It seemed to have been in the the phase of the update where it had downloaded what it needed and it was getting ready to make changes, but it needed me to reboot before it actually could do anything. When I started it up the next day that’s when I got a bit of a scare. In the middle of its start up it gave me a screen where it said “We’re making changes to your Windows system. We’ll be done in a few minutes.” or something. My blood ran cold for few seconds, I thought that I might have gotten myself into some trouble interrupting the update and that maybe my machine might end up in a unbootable state and I might even have to reinstall Windows 10.

But everything was fine. After a couple of minutes the screen disappeared and Windows 10 1803 started up just like it always has for me. Like I said in my previous post above, all this happened despite me having my internet connection set to metered, having Win. Update Blocker installed with the update process turned off, and having given no consent to, or been given any notification by Windows that any sort of updating would be taking place. It just decided that’s what it wanted to do so it just did it and it decided to only tell me about after the fact. Like I also said in my previous post, all this happened because I had committed the unpardonable sin of forgetting to run Wushowhide before I updated Windows. I know my system didn’t (fortunately) get the full-forced-update-without-consent treatment. I just thought I should share my story as a warning to others, especially those who may not be paying nearly as much attention as I was.

Reply | Quote

Didn’t want to go from 1803 which was stable and working, but was forced over the past week. My main graphics production machine for the past 8 days has been in an upgrade fail mode. It would download the update (3+GB each time) run to 88% and then fail, making the machine unusable for video editing as it did. After resetting the upgrade deferral, erasing all in “Windows\Software Distribution,” and other tricks failed to stop the forced migration, I could either take the thing off the network (not possible- adobe software) or give in and use the upgrade assistant, which I did. This was on the 13th. After churning for over an hour on the i9, and another 4+ gigs of download, it came up with 1909… And yes, I saw the other AskWoody post about that coming next week. I’m here to tell you it’s here now. I’m still picking up the mess on the production machine, the networking and other permissions all being reset.

1 user thanked author for this post.

woody

Reply | Quote

I replied to the wrong post. @PKCano:

You have 10 days to roll back to the previous version.

https://www.askwoody.com/forums/topic/have-you-been-pushed-from-win10-version-1803/#post-2005982

Reply | Quote

I’m still on 1803 (PRO with 365 days deferral)

Reply | Quote

I was on version 1803 for as long as I could due to its stability.  I have Win 10 Pr0.  The feature delay date was set to 365 days.  I recently changed the delay date to 120 days and was shortly upgraded to 1809 which seems stable so far.  I have reset the delay date to 365 days.

1 user thanked author for this post.

abbodi86

Reply | Quote

https://www.askwoody.com/forums/topic/on-windows-1803-time-running-out-for-support-should-i-install-1903/#post-1983593

Per PKCano post #1983593

 

As of today, 10/16, it has been 147 days (or there about) since 1903 was declared ready, and 202 days for 1809.
If I wanted to upgrade the 1803 to 1809, I would lower the Feature deferral to somewhere between 148 and 201 (148 keeps 1903 away, if over 202 v1809 won’t show up). If I wanted v1903, I would make the setting below 146.

We are currently 31 days past 10/16.  Shouldn’t the OP by changing to a 120 day delay received version 1903?

If so, has the Feature deferral “days delay trick” been changed?

How would we on 1803 ensure we get 1903?  Or even 1909?

Windows 10 Pro x64 v22H2 and Windows 7 Pro SP1 x64 (RIP)

Reply | Quote

So, add 31 to each of the numbers and read it again.

Reply | Quote

OK so 146 +31 = 177

“If I wanted v1903, I would make the setting below 177″

The OP selected 120 days and got v1809?

Windows 10 Pro x64 v22H2 and Windows 7 Pro SP1 x64 (RIP)

Reply | Quote

I bet it was 220 days (not 120)

1 user thanked author for this post.

woody

Reply | Quote

Win10 v1803 Pro VM November Update:
Settings: SAC, Feature=365, Quality=0, Automatic Updates=Enabled value 2, no pause.
Checked wushowhide: KB4519572 .NET, KB890830 MSRT, KB4525237 Nov CU
The SSU KB4523203 installed but was not listed in WU.
v1803 Build 17134.1130 – It appears MS respected the settings (at least for now)

2 users thanked author for this post.

abbodi86, woody

Reply | Quote

1803 Home tried to install 1903 Feature Update. I think it respected the Metered Connection on and failed. But I also saw it say Preparing to install which would imply downloaded. I ran WUShowHide to hide; which I also did last month so 1903 Features would not install.

I run Windows Defender updates, hence I suspect it changed something to allow 1903 try and install again, when I turned 1903 off last month (using WUShowHide).

1803 Pro is not being pushed yet.

1 user thanked author for this post.

woody

Reply | Quote

I have an example, Dell 2013 Desktop running 1803×64 Home, blocked from 1903 since May with Qualcomm/Atheros Bluetooth driver problems. On 1803 bluetooth does not work and Settings > Windows Update showed the “isn’t quite ready” warning. I don’t use bluetooth on this system and have tried various Dell Wifi/Bluetooth driver updates without success.

On Sat Oct 26, there was a “restart notice” to update to 1903, went to Setup > Windows Update, still shows “isn’t quite ready” but Windows had downloaded 1903 overnight. Normally I keep this system in “metered” but I must disabled “metered” sometime and forgot to reset the option.

Took a “snip” of the various 1903/1803 screen info, backed up a few files, and did a reboot. After a lot of thrashing 1903 installed without problems. System has run 1903 for 2+ weeks  no problems, bluetooth still does not work.

2 links for the 1903 bluetooth problems

May 28: “Windows 10 May 2019 Update Blocked by Old Bluetooth Drivers” https://www.bleepingcomputer.com/news/microsoft/windows-10-may-2019-update-blocked-by-old-bluetooth-drivers/

Oct 28: “Microsoft Removes Windows 10 1903 Update Block After Bluetooth Fix” https://www.bleepingcomputer.com/news/microsoft/microsoft-removes-windows-10-1903-update-block-after-bluetooth-fix/

Attached picture shows “screen-snip” the various messages about 1803 support ending, 1903 isn’t quite ready, and 1903 feature/restart. Some Stable-Genius in Redmond must have a sense of humor.

Reply | Quote

I am the person Woody was referring to in this post. And, yes, I did have the feature update set to delay for 365 days in 1803 PRO. However, I had not even installed 1803 until April, 2019. So the 365 days must be based on when a version was made available and not when the user sets the delay period?  Does anyone know?

I did post a while back asking for opinions as to which was least troublesome–1809 or 1903. (I previously had determined to be always a version or two behind, but that was before the accursed 1809 showed up and now I had thought it might be time to reconsider and skip 1809.)  I had pretty much made up my mind to update 1803 to 1903 on three (3) PRO machines (one desktop and two laptops.) But only one of the machines has to date been forced onto a newer version. So I think I will update the two machines still on 1803 to 1903 and update the laptop that got bumped to 1809 to 1903, too, once the other two seem to be working alright.

Reply | Quote

MikeyD215 wrote:

So the 365 days must be based on when a version was made available and not when the user sets the delay period?  Does anyone know?

Yes, it’s from the release date of each particular version.

Windows 11 Pro version 22H2 build 22621.2361 + Microsoft 365 + Edge

Reply | Quote

I’d be curious to hear from anyone who has specific stories to share about why holding back on an older version of Windows 10 has been a Good Idea for them.

1. I can imagine there could be hardware support reasons – e.g., a laptop for which the maker has stopped providing a GPU driver that actually works with the latest Windows.
   
2. I can imagine there could be performance reasons – certainly the latest version of Windows is the most bloated ever (Microsoft might say “feature rich” in place of “bloated”).
   
3. I can ONLY JUST BARELY imagine there might be an application that somehow could run on Windows 10 v17something or v18something – but not v190something. Could relate to item 1 above, I suppose. (I think that says “don’t buy a laptop and hope for more than a couple of years use from it”.)
   

In my own case my hardware systems are…

1. New enough that I find upgrading to the latest Windows 10 reasonable and preferable, and haven’t really had many problems I could attribute to being too quick to update to the latest.
   
2. One of them has Xeon x5690 CPUs, which are old enough that I’m just not going to move it off Windows 8.1, which it runs extremely well. So far I’m still able to run everything I want on it, though being brutally honest I do prefer the dark theme of Windows 10.
   

You might claim greater stability from the 1 or 2 year out-of-date Windows 10 versions, but I’m not sensing instability in the new versions, which I normally wait a few months after initial release to update. My desktop workstation in my office just runs every month all month between updates that reboot it, and I don’t think many folks use a Windows system much more vigorously than I do.

-Noel

Reply | Quote

Well! There are seekers looking for the latest bits even if they haven’t been tested and bricks systems; and folks who need stable software and play safe. The latter tend to allow Microsoft to get their act together before deploying updates/upgrades. It’s that simple, right?

Reply | Quote

I’m not here to generalize. I’d really like to hear any specific anecdotes where upgrading has led to heartbreak that was resolved by dropping back – or where holding back has demonstrably led to retention of desirable behavior or stability over what would have been gotten from the latest version.

I have no doubt such anecdotes exist, and I’m not trying to put anyone on the spot nor criticize their decisions. I just want to hear about them.

For what it’s worth I’ve asked this question a few times over recent years and I’ve heard very little feedback. So little, in fact, that coupled with my own fairly rich experience with multiple systems that I am having trouble believing that there ARE very many objective reasons not to move to each new version within 6 months of its release.

-Noel

Reply | Quote