It seems so strange, but everything is right on machine. I am gonna test on my main desktop and another laptop tomorrow (in 15+ hours) and let you know.
It actually is released as 19042.538 not 19041.538 but the update itself is 19041 based, so applicable to both.
Installed and rebooted without error. Spoiler Code: ============================================================ [1] Target (x64): Current OS [2] Updates: "C:\Users\@#$%\Desktop\Security\Win10UI" [3] DISM: "Windows 10 ADK" [4] Enable .NET 3.5: YES [5] Cleanup System Image: NO [E] Extraction Directory: "C:\W10UItemp_8832" ============================================================ Change a menu option, press 0 to start the process, or 9 to exit: ============================================================ Running W10UI v8.5 ============================================================ ============================================================ Extracting files from update cabinets (.cab) *** This will require some disk space, please be patient *** ============================================================ 1/3: windows10.0-kb4562830-x64.cab [Enablement / EdgeChromium] 2/3: windows10.0-kb4574728-x64.cab [Setup DU] 3/3: windows10.0-kb4577063-x64.cab [LCU] 4/3: windows10.0-kb4577266-x64.cab [SSU] 5/3: windows10.0-kb4579793-x64.cab ============================================================ Checking Updates... ============================================================ ============================================================ Installing updates... ============================================================ Deployment Image Servicing and Management tool Version: 10.0.18362.1 Image Version: 10.0.19042.508 Processing 1 of 1 - Adding package Package_for_RollupFix~31bf3856ad364e35~amd64~~19041.538.1.7 [==========================100.0%==========================] The operation completed successfully. ============================================================ Removing temporary extracted files... ============================================================ ============================================================ Finished ============================================================ ============================================================ System restart is required to complete installation ============================================================ Press 9 to exit.
It worked on a couple test boxes that I have nothing at all installed on, so doing some trial and error now.
KB4577063 seems like a scene from the movie: "The Gods Must be Crazy". An MSFT plane flies over and throws a glass bottle out. One of us finds the bottle. None of us knows what it is. We all stand around, scratching our heads, trying to figure out what it is. Abbodi grabs the bottle and makes a run for it. Of course I'm just joking, but it does seem a bit humorous. Maybe tomorrow, we'll find out more about what it is!
I tried to install 19042.538 over 19042.508 and I got that "you cannot even keep your data" warning. That was with an ISO built from UUP, going to try a few more things. I have had success in the past building a WIM file that is the base image + SSU + currently installed CU (no cleanup) and then running : Dism /online /cleanup-image /restorehealth /Source:WIM:C:\Install.wim:1 /limitaccess After that a problematic new CU is more likely to install.
Why would you do that by ISO / inplace upgrade? Found: https://forums.mydigitallife.net/threads/windows-10-hotfix-repository.57050/page-528#post-1618444 Inplace upgrade is not fixed/enabled by MSFT on 19042.xxx. Uninstall the 20H2 EP (if available) and next you can do an inplace upgrade with keeping files and apps.