Eventhough the latest IE CU can technically still be installed on W8.1 Client, I wouldn't recommend it because some Client packages have been removed ! It's only a matter of time before this leads to problems one way or another. It seems that it was already the case with the 2025-07 IE CU as well. This is the list of files that will not get updated when installing it on W8.1 Client : Code: System32 + SysWOW64 folders actxprxy.dll inetcomm.dll inetres.dll hlink.dll iertutil.dll jsproxy.dll msrating.dll urlmon.dll wininet.dll WininetPlugin.dll in System32\migration SysWOW64\migration
Sadly I believe they will not bring back Client compatibility. I have extensively compared the File Information of Monthly Rollup 2025-06 and 2025-07+ For 2025-07+ they removed : Pretty much anything Bluetooth related Anything related to Infrared drivers Anything related to WorkFolders Anything related to Windows Defender Drivers for Mobile Broadband ClientESU Year 1,2,3 licenses Embedded and Entreprise licenses So it looks like they really intentionally wanted to cut down on non-Server related material
Where to find the list of no-longer-supported Server editions that have been removed? Windows Storage Server 2012 (R2) is removed?
New update at: https://forums.mydigitallife.net/posts/1893686 Hi, BitLocker too (previously part of SecureStartup), at least just by looking at changes from 2025-06 to 2025-09 MUMs. Did you have a LOADER_ROLLBACK_DETECTED blue screen or something else? The component that causes that BSOD seems to be Microsoft-Windows-BootEnvironment-OS-Loader. On the MUMs, it only has Server components declared at assembly.package.parent. However something still causes it to be installed on Client and other environments. Then if the drivers, declared at other MUMs are not installed, it goes kaboom. My two cents. Thank you. P.S.: I may update this post later as research continues. I've left some gifts as attachments: node.js analysis script and the results on 2025-09 CU. Edit 1: I tried to detonate the Windows 8.1 Client VM by doing unchecked and unpatched MUM installation using: Spoiler The script from: https://forums.mydigitallife.net/posts/1886700 with KB ID modified and slight code changes as documented below: Code: for /f %%f in ('dir /b "package_*_for_*.mum"') do ( echo %%f dism.exe /online /quiet /norestart /add-package /packagepath:%%f /ignorecheck ) It only detonates when using the MSU or the master update.mum !? Edit 2: Added a script that allows to mod the MUMs (Server to Client) that can then be installed with a patched SSU.
It just crashes into Recovery Mode without any error and I'm unable to get it back to boot into Windows properly. This only happens with Monthly Rollups 2025-07 and higher. Anything up to 2025-06 is fine. After some quick testing, it turns out it also happens to me with Datacenter edition (in Virtual Machine) so it looks like I may be encountering another problem related to 2025-07+ Monthly Rollups.
I said they removed the licenses (that were in previous Rollups) boot files and related components doesn't check for Server edition, it will install for all Servers
And if you integrate Monthly Rollup 2025-06 (or earlier) without LPP KB5017220, then update to Monthly Rollup 2025-07 (or higher) on live OS, it also works for you? EDIT : Nevermind, it also works for me now. I created new ISOs and all works fine now Looks like there was some kind of problem with my older ones...
Best way to update Client would be to just gather the changed files and copy them onto their directories, avoiding checks, SSUs, updates, etc altogether, and you’ll still be safe cause well, you use the files from the newer build. Or just install 2012 R2 and make it look like a client.
Best way is stop updating Client what difference does it make to stop at 2025-06 or 2026-10? it's the same end eventually updates are overrated