Upgrading 1709 to 1803 offline using ISO

Topic

New Reply

I still have a Win 10 1709 installation. Since 1709 will be going out of support relatively soon, I’m looking to upgrade offline to 1803  (or 1809?) using an official MS ISO burned to DVD.

On my 1709 machine, I’ve studiously avoided the following KB’s using wub.exe and wushowhide:

KB4023057 — Upgrade Assistant v2 (WaaSMedic)
KB4023814 — Update Assistant tool
KB4056254 — OS Remediation System Service (OSRSS)
KB4134661 — notification of improved privacy experience on upgrade to 1803
KB4033631 — Compatibility Appraiser
KB4090007 — Intel microcode update for sceptre/meltdown

Are any of these already incorporated into the 1803 (or 1809?) ISO?   After the upgrade will I still be able to block these KB’s? Any wisdom on whether any of these KB’s should be installed before the upgrade?

Win10 Pro x64 22H2, Win10 Home 22H2, Linux Mint + a cat with 'tortitude'.

Reply | Quote

Replies

none of those patches you mentioned are included in the 1803 ISO as I checked the contents myself (I know because I created a usb flash install drive for v1803 several months ago). and yes you can use wushowhide.diagcab to hide/block those specific updates.

1 user thanked author for this post.

Steve S.

Reply | Quote

If you use the Media Creation Tool to create your install media I’m pretty sure you get the latest release including the last cumulative update.

--Joe

2 users thanked author for this post.

NetDef, Steve S.

Reply | Quote

I should have been more clear in my post: I do have an 1803 iso created by the MCT back before 1809 was released. I also have the current 1809 MCT iso. Just curious if the above listed KB’s are actually “rolled into” either of those iso files. Bottom line, I suppose, is that if they are in there, I don’t really have much choice once 1709 is EOS. 

Win10 Pro x64 22H2, Win10 Home 22H2, Linux Mint + a cat with 'tortitude'.

Reply | Quote

Alternative methods to using the MS MCT..

Download via heidoc-microsoft-windows-iso-download-tool

or direct download from windows10ISO with the choice of 1803 or 1809 using Linux/ Mac OS or even Windows (using a user agent in your browser set to Linux or Mac) to you get the initial release version which means you can pick patches if using WUmgr/ WUMT or similar 3rd party update control programs.

Windows - commercial by definition and now function...

1 user thanked author for this post.

Steve S.

Reply | Quote

I’ve been trying to use the “User Agent” browser trick to get 1803 on that official site, with zero luck.

Going to boot a Linux shell tonight and see if that works. (I need a “retail” ISO.)

~ Group "Weekend" ~

Reply | Quote

I’ve used HeiDoc before but not for Win 10 iso files. I’ll download the 1803 and 1809 versions they have there and run SHA-1 hashes to compare with what I get using the MCT iso files. Looks like HeiDoc has several versions of 1809. As you indicate, maybe the earlier 1809 doesn’t include some of the patches I’m blocking, allowing me to block them again.

I suppose it’s ultimately futile to push back against what MS want to do. That’s why I’ve got Linux while I keep Win 10 for gaming and other Windows-only stuff.

Win10 Pro x64 22H2, Win10 Home 22H2, Linux Mint + a cat with 'tortitude'.

Reply | Quote

Do you have Windows 10 professional?

If yes, why offline?

Set the Feature Deferral to 190 days, check for updates, and you will get 1803. Once done, be certain to set that back to 365.

If you have Home, then offline is the way to go. Be certain to clamp down WU before going online again.

If you are reading this future reader, that 190 days is no longer your number . . .

~ Group "Weekend" ~

1 user thanked author for this post.

Steve S.

Reply | Quote

I do have Win10 Pro. Why haven’t I done what you suggest? Well, I’m “old skool” and I like to reduce the variables. Clicking on “Check for Updates” isn’t what it used to be. MS isn’t what it used to be. They’ve burned a number of friends and family with some of their Windows 10 missteps.  So, I like to hang on to control to the extent possible rather than turning the update process over to MS update servers.

The end result may not be much different, but I’ll feel better getting there…

Win10 Pro x64 22H2, Win10 Home 22H2, Linux Mint + a cat with 'tortitude'.

1 user thanked author for this post.

Elly

Reply | Quote

NetDef – now that it’s March 17, how many days should I set the feature deferral to? I also want to upgrade from 1709 to 1803 and NOT to 1809.

(By the way, my PC dual-boots Win 7 Pro 64-bit and Win 10-Pro 64-bit. Sounds like your trick is the best way to protect my Win 7 partition, as maybe using the .iso will wipe the entire C:\ drive?)

Thanks.

Reply | Quote

A couple days ago – after some heavy internal dialogue – I decided I’d jump over 1803 and go straight to 1809 using the official ISO offline. It went relatively smoothly. For the sake of anyone who might read this thread in the future, I’ll post details of the methods and results over the weekend.

Win10 Pro x64 22H2, Win10 Home 22H2, Linux Mint + a cat with 'tortitude'.

Reply | Quote

Now on Windows 10 Pro x64 1809 build 17763.253.

I chose to skip 1803 and go straight to 1809 so I wouldn’t face another upgrade quite as soon. Since the known issues with 1809 seemed unlikely to be ones I’d face with my usage scenario, I went ahead and rolled the dice – after creating an image of the entire hard drive with Reflect, of course.

I also chose to do the upgrade offline using the official ISO I downloaded on 2/18/2019 which I burned to a DVD. This would prevent any new, potentially buggy March updates from being installed. Prior to the upgrade, I’d been using Wub.exe and wushowhide.diagcab in conjunction with the deferal options in Windows 10 Pro. Never had any surprises.

Following PKCano’s great advice for offline upgrading and ch100’s additional command line switches (https://www.askwoody.com/forums/topic/upgrading-win10-v1703-to-v1709-from-an-iso/), all went quite smoothly. Thank you both! The upgrade proceeded quickly and didn’t even try to go online (maybe because Wub.exe was set to ‘disabled’). After it rebooted a number of times, 1809 was installed and ready to go — sort of.

All of my programs and data were untouched. However, as PKCano recommends, thoroughly check all your critical Windows settings, Task Scheduler tasks, Group Policies, registry tweaks, etc., before going online again. Although most of my tweaks were untouched, I did find a number of things that needed resetting or fixing.

After verifying/resetting most of my prior customization of 1709, I went back online and used Wub.exe and wushowhide to make sure I only let through the March updates that I wanted (KB4487038, KB4483452 and Windows Defender virus updates). Interestingly, NONE of the KB’s I had previously hidden on 1709 showed up as installable or hidden. Either they’re incorporated into the 1809 ISO or aren’t being offered to this version of Windows at present. I rebooted and am now working on further customization and tweaking.

All in all, a smooth transistion. But be vigilant about unforseen changes to your tweaks!

Win10 Pro x64 22H2, Win10 Home 22H2, Linux Mint + a cat with 'tortitude'.

1 user thanked author for this post.

Lars220

Reply | Quote

My experience is that when you do a feature update, anything in wushowhide is cleared and starts over with anything new for the new release, since the updates are often specific to a given feature release.  You’ll still see common stuff like updates for Windows Defender and Malicious Software Removal too, but not other things unless the same KB is available for both feature releases.

So, what you said “Interestly, NONE of the KB’s I had previously hidden on 1709 showed up as installable or hidden” is what I would expect to see.

1 user thanked author for this post.

Steve S.

Reply | Quote