Patch Lady – 11 days and counting

Topic

New Reply

You remember this?  Well today I had access to a Windows 10 Home laptop and it was still running 1803.  I honestly don’t think that Microsoft is pushi
[See the full post at: Patch Lady – 11 days and counting]

Susan Bradley Patch Lady/Prudent patcher

6 users thanked author for this post.

abbodi86, PhotM, Great Lake Bunyip, woody, Elly, Mr. Natural

Reply | Quote

Replies

https://www.askwoody.com/forums/topic/microsoft-starts-forced-upgrades-to-win10-1809-again-this-time-with-a-next-generation-machine-learning-model/#post-313602

Red Ruffnsore

Reply | Quote

Mr. Natural: Thanks for this information. After reading it, I can firmly assert that’s all because the learning machine is still learning and is of the next generation. So, in the space-time continuum, it is still located in the (probably) far future and beyond the reach of our light cone. Please, don’t let this worry you. There is plenty already available to worry about, if one is so inclined, and still well within our present light cone. Unless one has for last name ‘Nadella’ and, thus, communes often and long with the goddess of time.

Ex-Windows user (Win. 98, XP, 7); since mid-2017 using also macOS. Presently on Monterey 12.15 & sometimes running also Linux (Mint).

MacBook Pro circa mid-2015, 15" display, with 16GB 1600 GHz DDR3 RAM, 1 TB SSD, a Haswell architecture Intel CPU with 4 Cores and 8 Threads model i7-4870HQ @ 2.50GHz.
Intel Iris Pro GPU with Built-in Bus, VRAM 1.5 GB, Display 2880 x 1800 Retina, 24-Bit color.
macOS Monterey; browsers: Waterfox "Current", Vivaldi and (now and then) Chrome; security apps. Intego AV

1 user thanked author for this post.

Mr. Natural

Reply | Quote

I have three Win10 Home computers still running 1803 on a metered connection.
Of course, two are 9-year-old hardware. One has a 3-year-old CPU.

Reply | Quote

I’ve been checking for updates several times but no 1809 for me 🙁

1803 on Intel NUC i3 7100U BOXNUC7I3BNK.

Reply | Quote

Or simply use upgrade assistant.

 

Pro tip:

With HDDs defrag before the upgrade if defrag shows more than 3% fragmentation

Using the ISO, explorer mount and setup.exe the upgrade process is faster especially on older machines.

Microsoft still cannot explain why.

Reply | Quote

My daughter runs a MSI, gamer laptop, family version,  almost 2 years old, metered connection still on 1803! She was offered yesterday some updates, but not 1809. Myself I run an old Asus,  pro version, not metered connection but defered updates. I don’t look for updates and was not offered 1809. Later as possible, for 1809!!!

Reply | Quote

I saw 1809 get offered two days ago on 1803 Home.  Happened while I was working on another computer next to it, which I think was already 1809.

Reply | Quote

Have a desktop running 1803 and have been seeking pretty much every day now for a couple of months on it

Reply | Quote

Nope.  I was on 1703 with a 365 day feature update deferral, semi-annual channel, and I was just forced to 1709, not 1809, 1709.

Reply | Quote

I look after 3 Win 10 Home computers and the users are under orders not to seek…

All 3 are on metered connections and are fully imaged.  All 3 are still on v1803 and receiving updates.

I can understand the 10 year old machine opting out of the cycle but not the i3 and i7.  But the users are happy – and that means less work for me.

Reply | Quote

I just bought a laptop and it is sticking with 1803 even though I have been “seeking”.

Reply | Quote

I have an old PC Intel i3 (Ivy Bridge) with a HD with 500gb, 4GB RAM, and curiously always received the semiannual updates on launch day.

I’m in 1809 since October 2 and it’s working.

Reply | Quote

My backup machine, a locally built clone, installed Win10 1809 either late the week of Jan. 13th or late the week of Jan. 20th.  Which is very interesting, since that machine is rarely even on.  After everything I’ve read about seeking updates, I did not do that.  I left my laptop (a MS Surface Book) on for several all-day sessions, and nothing happened.  That surprised me as I would have expected at least it to be updated.  My machine, also a locally built clone has not been updated so far–but I it may be on the delayed track.

My wife’s machine–a locally built clone–updated very early on the morning of 1/20.  All of her data was wiped from the machine and the data partition was unformatted!!  Fortunately we had a full data backup–one onsite and one off–and I was able to reformat the D: partition and copy her data back, lickety-split, after I took the machine to the builder so they could check the drive–a Micron SSD–which was tested using Hard Drive Sentinel and found to be in excellent condition.  To my knowledge the machine has been fine ever since.

Reply | Quote

I am not a seeker.

I am working on an HP 8300 Elite ultra-slim right now. It has had 1809 installed.
My main system is a Lenovo S30. It’s still on 1803.
I know several people who are still on 1803.

I have to agree. Microshaft is not pushing 1809 as hard as they claim to be.

Byte me!

Reply | Quote

Here’s a post I left on Jan 17 (on the Ask Woody Blog, if I understand the forums hierarchy correctly).

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.

Jan 29 Update: still no problems

Reply | Quote

Are you kidding me? I came into work last Monday and almost all of out Windows 10 1803 computers had upgraded themselves to 1809. This happened despite having a WSUS server which did not have the 1809 Feature update approved. Looking into it, I found out there’s some BS called “Dual Scan” which means computers still look to external MS update severs as their default update download authority.

So yeah, complete nonsensical insanity.

Reply | Quote

Probably fixable with “Do not allow update deferral policies to cause scans against Windows Update”:

Improving Dual Scan on 1607

Reply | Quote

Yes that will fix it.

Susan Bradley Patch Lady/Prudent patcher

Reply | Quote

Dual scan : use latest ADMX from a 1809 machine  download is still bugged.

 

If you have setup any policy in the ADMX subkey of Windows Update >WuFB

Then you need to setup a policy in Windows update above. Called do not allow update deferral… This has to be enabled if you want to disable dual scan.

 

Anyone using Windows 10 should carefully recheck their policies many has changed there for good.

But it’s cluttered as all XP and Win 7 ADMX remain in addition.

 

https://blogs.technet.microsoft.com/yongrhee/2018/03/12/windows-10-v1607-dualscan-behavior-when-do-not-allow-update-deferral-policies-to-cause-scans-against-windows-update-is-set/

Reply | Quote

I decided to try to ‘upgrade’ my old Windows 7 (Home Premium) laptop to Windows 10 last week. Even though it warned me twice about a monitor incompatibility, the change to Win10 went through fine with no monitor issues. It did give me 1809 Home, which I decided to convert to Pro. This was on a circa 2011 Acer laptop with only 2 GB of RAM and a single core(!) AMD processor. Memory seems a little tight with Chrome running, but it does fit and actually works pretty fast. It’s just a backup computer, so I’m happy with it. I didn’t have any issues with 1809 as I was going through the laundry list of turning off all the stuff that Microsoft loves to turn on by default …

Reply | Quote

Mine is a one-year-old high-end HP laptop, but still at 1803. Today I was given an update for 1803 but nothing about 1809.

Reply | Quote

My sacrificial 1803 machine – a Surface Pro 3 with bone-stock settings (SACT/0/0) – announced within the past day that it was ready to upgrade to 1809.

1 user thanked author for this post.

Great Lake Bunyip

Reply | Quote

currently onsite at a small commercial customer.  three win10 pro machines that had been set to “semi annual targeted” and no deferment all got 1809 yesterday or today.  all machines now set for 90/15 day deferment.

one machine that got 1809 today was getting garbage when trying to print to a hp t790 plotter.  customer had tried reinstalling drivers fresh from hp, no dice.  I found a fresh (as in zero updates…) 1809, rebooted three times, set it to use hpgl2 not ps and the garbage out ceased, it plots ok.  they have to print drawings from a contractor website, they use ie11.  not sure where the actual fault is, but fresh hpgl2 drivers seemed to resolve it.

at this point I am still 100% convinced that unless you are in an industry that requires a native Windows OS (not a vm) you should not be running Windows.  every machine in my life say Apple on it and has been that way since 2007.  I have been in the game since 1987, got my mcse in 1997 and while the last 30 days seems to signal a change in M$ patch policies, btdt a couple times now and I have full confidence they will return to their bad old ways soon.

Hey look! Another Feature Update!

You mean I shouldn't click Check for Updates?

Where is the Any key?

1 user thanked author for this post.

doriel

Reply | Quote

1803 here! No sign of 1809 update pushed onto my computer. Been hiding the updates and staying away from Windows Updates too. No sign of any forced update onto my computer. All clear and safe on my end so far.

Reply | Quote

If any want to “try” to force 1809 to show up, you may need to update the Appraiser data

start command prompt as administrator and execute these command one by one

CompatTelRunner.exe -m:appraiser.dll -DoScheduledTelemetryRun
CompatTelRunner.exe -m:appraiser.dll -f:DailyGatedCheck
CompatTelRunner.exe -m:appraiser.dll -f:UpdateAvStatus
CompatTelRunner.exe -m:devinv.dll -f:CreateDeviceInventory
CompatTelRunner.exe -m:invagent.dll -f:RunUpdate
CompatTelRunner.exe -m:invagent.dll -f:RunUpdateW
CompatTelRunner.exe -m:generaltel.dll -f:GetCITData
CompatTelRunner.exe -maintenance
DeviceCensus.exe

Reply | Quote

Thanks abbodi! for most using the ISO, mount in explorer and run setup.exe or Windows upgrade assistant might be more obvious to get off the old release. It’s worth it.

Reply | Quote

This is on my wife’s computer; I’ve been using 1809 without problems since soon after release (seeker). After hearing about the problems, I held off on her unit; however. Update History shows Capture 2.jpg (attached), while winver shows Capture1.jpg (also attached).

[Edited]

Zig

Reply | Quote

The 1809 installer from October was the version that created that big mess. Obviously very buggy. A newer version of 1809 was released in November which includes all the bug fixes and a required patch prior to the 1809 install. You may want to download the media creation tool and re-run the 1809 installer.

Red Ruffnsore

Reply | Quote

Thanks to all; successfully upgraded today to 1809 using Media Creation Tool.

Zig

Reply | Quote

The idea is that Appraiser and Windows Update do more checks to insure your OS/configuration/programs are ready for 1809
ISO upgrade only focus on compatibily issues

1 user thanked author for this post.

Microfix

Reply | Quote

1809 has been sitting unapproved on the WSUS server which I manage for many weeks now. It appeared very early on, unlike 1803 and earlier releases which did not show up on WSUS until many weeks after release. I had to rebuild Windows from scratch on a PC at home over the holidays and went with 1809; it has been fine now for 5 weeks. I had the usual hoops to jump through to get my somewhat ancient Canon scanner working but nothing else has caused any problems.

Arthur J Davis
UK

Reply | Quote

I have three PCs (2 Home, 1 Pro) all running v1803. On one of the three, I have had ‘Feature update, v1809’ start installing in both Dec ’18 and Jan ’19 the first time I clicked [Check for updates]. I use a Metered connection and WUShowHide to install when I want, not when Redmond wants. This time there was no download, v1809 immediately started to install(!)

What is disturbing is that v1809 does not show in WUShowHide. In the past all updates and upgrades have shown. I fear that we are about to lose all control over forced windows updates per AskWoody’s recent post

https://www.askwoody.com/2018/and-yes-microsoft-has-given-itself-permission-to-install-win10-version-1809-on-any-win-10-pc-that-checks-for-updates/

 

Reply | Quote

I look after a number of PCs (laptops and desktops). I looked at four (which I have running most of the time) and one of the laptops updated to 1809 a couple of weeks ago – and I hadn’t noticed! The other three haven’t. I’ve got a couple more laptops I need to fire up, so they get the latest updates so I’ll see if they get the upgrade. One is a quite new one, the other is almost as old as me (in computer terms).

I accept all any any updates/upgrades and have not yet had any problems. YMMV

Eliminate spare time: start programming PowerShell

Reply | Quote