my pc wont install the the preview cumulative update, ive downloaded the latest uup dump, run the windows installer but, it wont let me migrate my data. Only option is a clean install from the upgrade menu.
Migrate your data, it's a CU, not an OS upgrade, or do you mean something else? Can you show the error?
Updated the 2004/2009 Updates Overview: https://forums.mydigitallife.net/th...-20h1-2-vb_release.80763/page-16#post-1571109
maybe have cleanup problem for my used. if had edge ep package. the winre.wim will not cleanup after patched. the old script had cleanup command but 8.4 - 8.6 drop the line after Code: if not defined edge goto :eof if defined edge ( %_dism2%:"!_cabdir!" %dismtarget% /LogPath:"%systemroot%\Logs\DISM\DismEdge.log" /Add-Package %edge% if !errorlevel! equ 1726 %_dism2%:"!_cabdir!" %dismtarget% /Get-Packages %_Nul1% )
It does cleanup Code: if defined callclean call :cleanup https://forums.mydigitallife.net/threads/windows-10-hotfix-repository.57050/page-516#post-1614823 can you show your log and options?
Code: Cleanup =1 ResetBase =1 WinRE =1 SkipEdge =0 package Code: windows10.0-kb4557964-x64_dc77fd0d308de6fc911bfef95c0ed500ee534238.cab windows10.0-kb4561600-x64_c1b68e8ebc584fba22606561477bfd8d6ca553d6-flash.msu windows10.0-kb4562830-x64_75cbce76d188e8fdab860946c0131789de35ea64-ep.cab windows10.0-kb4569745-x64-ndp48_7f8a54816ac281286046a4b00a79fe1b7ed12fd5-net48.msu windows10.0-kb4570334-x64_ba511aeaff89c0d9ed999541909dd50758280132-ssu.msu windows10.0-kb4571744-x64_b6e6af8dcfe47947c5d2c44ba3e1fe7b8bb52441-cu.cab windows10.0-kb4577588-x64_6b8350ff93ec732a96a578978266f70c0e90ec85-du.cab left side using v8.6 with edge-ep package, right side using not have edge-package. now i'm running script add "call :cleanup" after add edge. and looks cleaned.
============================================================ 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.