Microsoft starts forced upgrades to Win10 1809. Again. This time with a next generation machine learning model.

Topic

New Reply

Here we go again. Microsoft’s starting to push the Win10 1809 upgrade on Windows 10 Home machines, and on Win10 Pro machines that haven’t been properl
[See the full post at: Microsoft starts forced upgrades to Win10 1809. Again. This time with a next generation machine learning model.]

3 users thanked author for this post.

Great Lake Bunyip, lurks about

Reply | Quote

Replies

Heck, won’t be long they will be pushing out yet another one. So I guess Microsoft figures better push it out now. I personally dealt with many issues even after the delay, I consider it one of the worst roll outs yet.

2 users thanked author for this post.

lanceboil, banzaigtv

Reply | Quote

Looks like it’s time for all Windows 7 and 8.1 users to reinstall the GWX control panel, folks. I’ll install it once it gets updated to a newer version.

I am no longer an active member of the forums.

Reply | Quote

This is Microsoft rolling 1809 out to existing Windows 10 users. It is NOT upgrading users of older operating systems.

--Joe

4 users thanked author for this post.

Klaas Vaak, banzaigtv, Woody posting as an MVP, PKCano

Reply | Quote

Despite my Win 10 Pro 1803 machine being set to “Semi Annual Channel” with a 180 day deferment, I had a lovely note from Windows Update a few days ago informing me I had  a “Feature update to Windows 10, version 1803!  The latest feature update to Windows is ready to install! It’s been waiting for you to kick it off. These improvements help Windows run smoothly and securely. Select this option (Restart Now) to kick it off”

Needless to say I’ve not restarted yet.  I’ve been looking for a way to roll this back without going through the install but have not had any luck.

So apparently this found its way around my Windows Updates settings.  Curious if other admins are seeing this.

2 users thanked author for this post.

Great Lake Bunyip, woody

Reply | Quote

1803 was declared approved for business 7/10/2018. Has it been more than 180 days?

Reply | Quote

By my calculation it’s been 190+ days.

Oh boy.

1 user thanked author for this post.

Great Lake Bunyip

Reply | Quote

365 days is a MINIMUM (also the maximum, but….)

Reply | Quote

It forced the update on my system, disallowed deletion via control panel, and disallowed rollback (that’s the part that REALLY p****d me off).  So I went into Bios and deleted the HD.  Then I was able to successfully restore an earlier version from a reboot usb.

Reply | Quote

I can be as angry at Microsoft as anyone, but updates (a few days ago) from W10Pro-1803 to 1809 went without incident and so far, without subsequent problems.  They also installed much faster than previous updates – maybe 25 mins instead of hour or hours.  I thought I had updates stalled, but apparently not.  I am annoyed at Microsoft being coy about what it is about to do.  Thought Patch Tuesday was happening.

Computers:  Two-year old cheap Thinkjet, and 2-month old home made box (Asus Z370-A motherboard).  Both with run-of-the-mill software:  office 2016, VLC, the usual browsers, bunch of email clients, etc.

So, all in all, a decent experience, with unused backups.

1 user thanked author for this post.

b

Reply | Quote

_Reassigned Account wrote:

Heck, won’t be long they will be pushing out yet another one. So I guess Microsoft figures better push it out now. I personally dealt with many issues even after the delay, I consider it one of the worst roll outs yet.

It’ll be interesting to see what happens with “19H1″‘s release schedule.  There are people at Microsoft calling it “1903”, but one would hope that cooler heads will prevail and they’ll push this release out a bit.

It’s hard to see anyone getting upset if “1903” was skipped altogether and they went straight to “1908”.

3 users thanked author for this post.

Great Lake Bunyip, woody, BobbyB

Reply | Quote

My thoughts exactly 19H1 doesnt seem to hold much of anything save the promise of the elusive “Stability Version” although i’ll believe it when I see it.

Reply | Quote

So errr is this 1809 or 1901?? Give it another few releases the previous version’s going to meet up with the new version at this rate, either they skip one or go to a 12 Month release, but I am preaching to M$’s deaf ears and the rest of the converted alas.
My networking issues have all cleared up with Dec’s Cumm. update and indeed needs no special intervention either in Services, Drivers or running via GPOL netcfg -d at shutdown. Not a word nor can I discern anything about the issue from M$.
One niggle, trivial in nature I know, but late Decemeber they managed to mess up the UWP Weather App tile yet to be fixed, sporadic in nature on an 1803 Home Machine, none functioning on an 1809 Pro Machine. Wouldn’t care normally with the UWP apps but its -17C outside and Snowing so the onset of a potential major Snow Dump in the offing focuses one’s mind wonderfully. For those with similar Apps woes better to wait it out as I have tried WSRESET CMD including updating, normal uninstall and reinstall, Power shell remove and reinstall, Power Shell disable development mode oh and while I was in the I removed Xbox and the other tough to remove cruddy Apps. So its probably a waiting game to see if some one at The Store or Redmond actually figures out its broke and fix’s it.
All in all not bad as the Dark Theme saves the day, but its taken a long time to get here for a version that Pre Release was vaunted as a stable Version and if I remember correctly its the basis for the LTSC/B versions.

Reply | Quote

The Weather Network’s Windows 7 App still works great and also runs in Win 10 no problem.

 

https://www.theweathernetwork.com/weather-apps

2 users thanked author for this post.

Bill C., BobbyB

Reply | Quote

Not a bad app, but it is an ad server for Google ads, which take up 40% of its footprint. Uninstalled.

I iwll just use my iPhone weather app which is add free.

1 user thanked author for this post.

BobbyB

Reply | Quote

Thanks to gborn at:

https://borncity.com/win/2019/01/17/windows-10-update-kb4023057-re-released-1-16-2019/

Recommend un-installing the KB4023057 update, and check for multiple instances,

I used the Paint program to make some notes on gborn screenshot picture, all credit to @gborn.

5 users thanked author for this post.

Microfix, abbodi86, Great Lake Bunyip, BobbyB, columbia2011

Reply | Quote

Just as well that I have PMorph’s forced updates turned off completely then… 🙂

Reply | Quote

Back everything up, I’ve had an aborted 1809 leave a trashed OS. A few times.

Older and custom built machines are vulnerable.

Reply | Quote

Does a metered connection stop the upgrade?

Reply | Quote

Theoretically. But when Microsoft is pushing it, I think they bypass about everything except maybe Group Policy settings. Group Policy is not available to Win10 Home edition.

1 user thanked author for this post.

BobbyB

Reply | Quote

I would say that nobody is bypassing anything and all settings are honoured correctly, unless there is a bug.
The issue is that Microsoft makes all settings (on purpose) difficult to understand correctly and as such, most people who are not well versed in all the details of the operating system believe that the settings are not respected by the manufacturer.

1 user thanked author for this post.

BobbyB

Reply | Quote

ch100 wrote:

I would say that nobody is bypassing anything and all settings are honoured correctly, unless there is a bug. The issue is that Microsoft makes all settings (on purpose) difficult to understand correctly and as such, …

Well that, and those bugs do exist.

Like that one update that wasn’t supposed to need a reboot at all, was installed with “no reboot” too, and did still force a no-warning reboot on about 1% of systems, with Event Viewer claiming that it had been a normal patch reboot afterwards.

Reply | Quote

There is rarely an update not requiring a reboot and to be on the safe side, one should still reboot. Are you in an Enterprise environment to be so concerned about a reboot? Even so, why is such an issue to reboot desktop computers?

Reply | Quote

Mostly it’s just the principle of it.

I used to be an admin in a high-availability server room, it does leave a certain mindset…

Well that and in that particular case the reboot happened at a time when no updates should have been running at all, delayed due to another transient error. Some of our users have PCs hooked up to expensive instrumentation, the operation of which really shouldn’t be interrupted without warning. (Yes, I know, things like that should run on a proper RTOS but I didn’t get to design the things…)

Reply | Quote

Settings > System > About > Read the Microsoft Software License Terms:

“Updates. The software periodically checks for system and app updates, and downloads and installs them for you. You may obtain updates only from Microsoft or authorized sources, and Microsoft may need to update your system to provide you with those updates. By accepting this agreement, you agree to receive these types of automatic updates without any additional notice.”

It is my beleif that some of the terms of the Windows License agreement are coded at kernel level, and there is simply no way of getting around them other than keeping a permanent air gap, i.e. never ever ever connect a Windows machine to the internet.

Of course, that makes it fairly useless except for offline game playing or writing and printing documents.  If one intends to connect to the internet, one is, like it or not, connecting to Microsoft; it’s in the license.

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We were all once "Average Users". We all have our own reasons for doing the things that we do to our systems, we don't need anyone's approval, and we don't all have to do the same things.

Computer Specs

Reply | Quote

well woody it looks like running the Win10 v1809 media creation tool recently seems to download the RE-RE-released version of 1809 with KB4480116 cumulative update integrated (build 17763.253) as I read from this MDL forum thread.

maybe ask abbodi86 about this

Reply | Quote

EP wrote:

well woody it looks like running the Win10 v1809 media creation tool recently seems to download the RE-RE-released version of 1809 with KB4480116 cumulative update integrated (build 17763.253) as I read from this MDL forum thread.

Or you could’ve read that in another topic here already, too…

Reply | Quote

Two notes on KB4023057:

– It seems on Win10 Pro machines with Defer Quality Updates set, this update ignores the deferral. (It was released on the 15th, deferral is set to 4 days but it’s already trying to install on the 17th).

– Besides the 0x80070643 error mentioned on the Born City post, in the Application event log, we have MsInstaller Event ID 1005, “Product: Update for Windows 10 for x64-based Systems (KB4023057) — A later version of Update for Windows 10 for x64-based Systems (KB4023057) is already installed. Setup will now exit.”

So maybe uninstalling the version that is already installed is not the right approach, since it is newer than the one that is now being installed? I am inclined to just wait, let it keep failing, until Microsoft fixes the new update.

 

Reply | Quote

Definitely still not pushing this to folks in the office but finally decided to update my home laptop running Windows 10 pro.

The only way I could get it installed is by using the media creation tool. This may be because my laptop is an Alienware 17r3. Nearly all Alienware laptops were affected by all the spectre and meltdown patches with the exception of the 17r3 model. It appears Microsoft may be using some caution still depending on what your hardware is.

I was running 1803, I checked for updates and it installed the 2 most recent 1803 updates. After reboot I checked again and reported my system was fully up to date. I tried a couple more times and stayed that way.

A month or so ago I downloaded the media creation tool so I ran that version which was only a month or more old and it wouldn’t run. I went to the Microsoft site and noticed an updated version of media creation tool and it ran and installed with one scary moment.

During one of the reboots my laptop failed to boot and the bios was beeping repeatedly. At first I thought my drives were wiped and there was no boot device. I turned off the laptop and when I turned it back on it completed the update and now at 1809.

I did run the cpu and motherboard patches previously so spectre and meltdown were already patched prior to running the update.

Red Ruffnsore

Reply | Quote

Unless I’m mistaken, KB4023057 is one of the updates you want to avoid. Has something to do with getting your PC ready for the next forced update. Please correct me if I’m wrong.

Reply | Quote

So even if you disable windows update, hide every update using WUShowhide and whatnot-Microsoft/windows will bypass all of it to force the new 1809 on computers?

 

 

Reply | Quote

I use WUB (Windows Update Blocker) and Group Policy Editor, and it’s never failed me even once. Been using it since Build 1511.
WUB turns off Windows Update Service and makes the reg entry “read only” so MS can’t turn it back on again. Also using wushowhide with good results.

Reply | Quote

The only fix solution is to ditch the damn OS ! Im planing to use Linux for daily internet use cos im sick and tired of MS crap, viruses and other threats that plaque win user ! Im not saying Linux is ideal but 95% of such crap under Linux is not happening ! There is no detour and no way to simply replace windows cos there are toons of soft developed to run on win – so i plan to run win strictly offline and in virtual environment ! God damn ever/forever problematic MS OS! Luckily we now have AMD multicore performance Threadriper  CPU’s so running virtual Win under native hardware performance is no problem any more at home ! My opinion is that this is the only way to put MS OS under control and having reversible backups at mouse clicks !

Reply | Quote