============================================================ Running W10UI v8.6 ============================================================ ============================================================ Extracting files from update cabinets (.cab) *** This will require some disk space, please be patient *** ============================================================ 1/1: windows10.0-kb4571744-x64_b6E6af8dcfe47947c5d2c44ba3e1fe7b8bb52441.cab [LCU] ============================================================ Checking Updates... ============================================================ ============================================================ Installing updates... ============================================================ Deployment Image Servicing and Management tool Version: 10.0.19041.329 Image Version: 10.0.19042.450 Processing 1 of 1 - Adding package Package_for_RollupFix~31bf3856ad364e35~amd64~~19041.487.1.10 [==========================100.0%==========================] An error occurred - Package_for_RollupFix Error: 0x8007000d Error: 13 DISM failed. No operation was performed. For more information, review the log file. The DISM log file can be found at C:\Windows\Logs\DISM\DismLCU.log ============================================================ Removing temporary extracted files... ============================================================ ============================================================ Finished ============================================================ Press 9 to exit.
Yeeehhh, many thanks. I restarted Windows and tried again with another dism command with restorehealth, but will fail everything. And your solution was ... after the first failure, try again and voilà the update installs without problems It doesn't work, the only option is a clean install from the update menu. The setup detect as ISO version 19041, while the host is 19042 and doesn't allow downgrade. Very strange, it seems to me that this CU update is bugged
That is often caused by a version mismatch or language integration issue. I don't believe that the CU is bugged, only that .450 (and everything that comes after) contain so many changes that the odds of failure are higher when something does not line up correctly. Back in the 1903/9 days I had an insanely hard system to update that failed on all of the usual fixes but I did eventually get it to work with the following steps: I took the first release of 1903 and integrated the last update that successfully installed without performing a cleanup after integration. In place upgrade, this was successful. I took that same image and integrated all of the current updates again without doing an cleanup. In place update, this was also successful. From that point forward all CUs and build upgrades have been successful.
Perhaps I'm not understanding your comment. I downloaded kb4562830 (the enablement package) on June 18th and then on August 24th. They are identical. Was there an earlier release of kb4562830 that is different from the one we have now?
You're right, it looks like they're the same even though its hash has changed, it's now called "new" here and it now updates Windows to .479 when previously it updated to .292. Weird.
KB4562830 gets you from 19041 to 19042. My understanding was that .479 was an intermediate 19041 Edge update. Perhaps what you are looking for is KB4570334 [SSU] + KB4571744 [CU] to get to 19041.487 or 19042.487.
Well, I just downloaded the latest CU, DU and EP and I already have the latest SSU and CU for .NET Framework installed.
Assuming you are running 19041, I'd recommend manually installing KB4562830 [EP] + KB4570334 [SSU] + KB4571744 [CU] + KB4569745 [NET] updates in that order. The DU isn't needed if you're not building a Windows 10 ISO. Plus there's the KB4561600 flash update as well.
I already have the latest build. I installed the latest EP and CU and I already had the previous EP and the latest SSU and CU for .NET Framework installed. I don't want Flash Player so I don't download its updates and I only download the latest DU when I want to build an ISO.
Flash Player is a security risk, which is why MS and Google are not supporting it anymore in their chromium web browsers in December 2020!