Replies

For those on the business end: The media creation tool has been updated as well, you can grab your ISOs there, and on WSUS I see both the full packages as well as the small activation packages…

“Windows 10” and “Windows 10, version 1903 and later” are the only checkmarks you need. The first option will cover al OSes from RTM to 1809. Also make sure to select the needed categories on the other tab on that window, selecting everything EXCEPT drivers, driver sets, definition upgrades and tools work fine for me. When I’ll get full .Net installations and stuff like Silverlight offered, I decline them, but I feel certain that I don’t miss anything that I may need…

2 users thanked author for this post.

Marcus Weldby, b

WSUS also got a new product to cater for, next to “Windows 10”, there is also “Windows 10, version 1903 and later” (as well as two sets for drivers, just like for previous versions).

This contains Flash player updates, service stack updates and CUs for Win and .Net for 1903, so don’t forget to mark this if you want to support version 1903 in your environment.

The intention of this is to probably segregate sets of Windows 10 updates, similar to all previous Windows versions, so you’re able to ignore older updates for like 1703…

I just helped a user on one of our unmanaged Win7 notebooks, 500 km away. We use Sophos as well. System got stuck after reboot, switched computer off with force, next normal reboot had the same effect again. After another forced reboot and going into safe mode, computer automatically reverted the update and user was able to work again. Thanks Microsoft…

Next to the Office updates On my WSUS I also found these windows 10 version 1809 updates:

2019-03 Kumulatives Update für .NET Framework 3.5 und 4.7.2 für Windows 10 Version 1809 (KB4489192)
2019-03 Kumulatives Update für .NET Framework 3.5 und 4.7.2 für Windows 10 Version 1809 für x64 (KB4489192)
2019-03 Kumulatives Update für Windows 10 Version 1809 für ARM64-basierte Systeme (KB4490481)
2019-03 Kumulatives Update für Windows 10 Version 1809 für x64-basierte Systeme (KB4490481)
2019-03 Kumulatives Update für Windows 10 Version 1809 für x86-basierte Systeme (KB4490481)
2019-03 Servicing Stack Update für Windows 10 Version 1809 für ARM64-basierte Systeme (KB4493510)
2019-03 Servicing Stack Update für Windows 10 Version 1809 für x64-basierte Systeme (KB4493510)
2019-03 Servicing Stack Update für Windows 10 Version 1809 für x86-basierte Systeme (KB4493510)

Seems it takes MS a bit longer to patch 1809, hopefully because it’s thoroughly tested…

1 user thanked author for this post.

woody

I’m taking care of about 310 client workstations, 250 are on Windows 10, the rest is still on Windows 7. We began migration tests with 1607, but the main Win10 rollout was with 1703. Fast forward another year I was asking myself the same question as Woody. Since this summer I did some tests with 1803 and haven’t encountered anything showstopping. Both fresh installations as well as in-place-upgrades were without major errors so far. This may be due to the fact that we mostly use standard “of the shelf” software and Dell hardware, which both didn’t give me much issues.

Thankfully I’m using WSUS to distribute any updates (at least after I was able to defeat MS’ newest trick called “Dual Mode”), so I can do some fine-grained tests on test computers and less important production machines before I approve anything to the broad public…

So far the only issues I’ve noticed are annoying, but minor:

1. After an upgrade, that system partition may get a drive letter, which messes with our client backup software and may irritate the users. This is quickly fixed with diskpart, still I’ll have to care of that manually. I’m planning to do the upgrades in batches, so this manageable.

2. After an upgrade, the Windows Update service doesn’t send any reports back to the WSUS, until someone manually presses “Look for Updates”. At least that was my observation, it may do so by itself after a while, though.