People in Beta and Dev channels shouldn't have any problems. They should be expert enough to do this.
Same here, I can't update from 19043.899 to 19043.906 using the latest KB5000842.msu update installed, but after restarting Windows, the version remains 19043.899 and there is no new KB5000842 in the update history/view installed update. However, when I add the two cabs via dism, everything works fine (KB5000981 SSU and KB5000842 LCU) What's the difference between combined KB5000842 msu with separated cabs (KB5000981 SSU and KB5000842 LCU)? Thank you.
Updated Win10ISO to 19041.906 using W10UI Success. Edge Chromium is By Defualt Installed & i forgot to set W10UI to Skip EDGE Chromium.
Edge Chromium is now integrated with the CU, afaik @abbodi1406 is working on a workaround for the next W10UI release.
Hmm so I guess a fix for the 906 install issue that some people are seeing isn't coming anytime soon like they said...
Excuse me, but I don't know English and I use the translator. I made an ISO image and installed it and this has been the result, Kind regards. . Edición Windows 10 Enterprise Versión 21H1 Instalado el 31/03/2021 Compilación del sistema operativo 19043.906 Experiencia Windows Feature Experience Pack 120.2212.551.0
Experiencia Windows Feature Experience Pack 120.2212.551.0 IS OLD This is current one Windows Feature Experience Pack 120.2212.3530.0
Yep, it finally appeared the other day on 21H1 systems too. Only dev channel builds have dotnetfx CU on uup dump (initial releases only, .1010 releases don't contain them).
I confirm getting error too. edit: create a batch file with these commands, and it will update no problems: Code: cd %ProgramFiles%\Windows Defender MpCmdRun.exe -removedefinitions -dynamicsignatures MpCmdRun.exe -SignatureUpdate
For me, even with ownership, did not let me overwrite some of the files, so ... meh. I guess I can wait
I want to update an iso with DU, abbodi1406 told me I need to update boot.wim index 2 with LCU so setup.exe version inside boot.wim matches the one inside sources folder, how can I know what is the version of setup.exe inside a LCU? (tried to use LCU .906 on boot.wim but it's setup.exe is not .900 which is the version of setup.exe in DU)
I'm on .906 (fresh install), after I used Windows Update the first time, I reboots and it never makes it back to Windows. The little circle just spins and spins with no HDD activity. Only fix is to hit the reset button. It does the automatic repair thing and then it boots up normally.
No I mean the one inside LCU, can I somehow see inside LCU cab file and see what setup.exe version I'll get if I apply this update into a boot.wim? To save time
I have no clue and that info i never needed to know either Maybe @abbodi1406 can tell. Just make sure that after integrating all updates these setup.exe files are matching: Code: boot.wim\2\sources\setup.exe & Code: ISO:\Sources\setup.exe