I did it at first run, failed lcu, installed 21H1 EP, reboot and installed the lcu again, failed too. Running them separately with reboot after SSU install. EDIT: Same errors or do you mean the lcu already contains the ssu?
That was mistake, but it's not the cause of error Code: HRESULT_FROM_WIN32(ERROR_SXS_ASSEMBLY_MISSING) #419485# from Windows::ServicingAPI::CCSITransaction::ICSITransaction_PinDeployment(Flags = 0, a = dual_basicdisplay.inf, version 10.0.19041.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}, type [l:14]'dualModeDriver', cb = (null), s = (null), rid = 'Microsoft-Windows-Client-Desktop-Required-Package0110~31bf3856ad364e35~amd64~~10.0.19041.899.36A3EC335106A2D20250726F5763EDC628D2DDE23E3DD4093E55EA98C2E63268', rah = (null), manpath = (null), catp[gle=0x80073701] amd64_dual_basicdisplay.inf_31bf3856ad364e35_10.0.19041.1 exist in your WinSxS? otherwise, it's just another faulty beta LCU
try to make lastest iso using 9.8 script from official iso first public release and patch files (including du). at last got iso files dll replaced from du package. (before 9.8 got sources\dlls was newer than du package) the 9.8 notes says: Further enhancement to prevent setup.exe conflict (if ISO files dates are newer than DU) why is the iso files are older than DU?
Have to check, the clone is gone, now running the lcu without the ssu*, but have to go out, will report back asap *same error.
When you integrate (or install) updates with dism, the added files take the current date/time of integration updating MVS ISO boot.wim with LCU = new files inside \sources take the current date/time copying those files to ISO \sources = same current date/time, which will be newer than DU files adding DU to ISO \sources later, the files restore original DU date/time (except setup.exe) updating UUP ISO boot.wim with DU = new files inside \sources keep the DU date/time copying those files to ISO \sources = same DU date/time aside from this confusion, did you encounter an issue?
Thanks for the explanation. I just hope that the versions of dll and exe and mui in the sources are kept up to date. Will this cause a conflict?
This was installed on my 19042.868 ISO installation i made using W10UI_9.8 here: https://forums.mydigitallife.net/threads/windows-10-hotfix-repository.57050/page-608#post-1650072
Beta LCU KB5000842 = 2021-03-06 OOB LCU KB5001567 = 2021-03-12 KB5000842 is expecting KB5000802 (19041.867) or RTM 19041.1 component
I'm not sure if my online updates apply to this scenario, because I think your focus is on using updated media. But I was able to update from 19043.867 to 19043.868 to 19043.899 by applying updates in the following sequence: 1) Windows10.0-KB5001567-x64_LCU_19041.868.1.0.MSU (Note: MSU) 2) SSU-19041.897-x64.cab (DISM) 3) Windows10.0-KB5000842-x64_LCU_19041.899.1.8.cab (DISM) No errors.
When you would have ran cleanup after .867, and then installed .868, .899 would not have installed, even WU in the beta channel can't install it in the shown scenario.
Sometimes it is interesting to look at what packages are superseded. By the time 19043.899 is installed, there are several superseded packages.
Updated the 1809 Updates Overview: https://forums.mydigitallife.net/th...-17763-xxx-pc-rs5.77945/page-216#post-1490183 Updated the 1903/9 Updates Overview: https://forums.mydigitallife.net/th...pc-19h1-2-release.79259/page-148#post-1525792
Hi, I got promoted to install the KB4023057 update. I never got this updated before, could it be because i didn't now use the Cleanup option in W10UI?