Right, i believe this post showed that: https://forums.mydigitallife.net/threads/windows-10-hotfix-repository.57050/page-542#post-1623333 but the ssu is NOT integrated in the LCU, i showed that after installation of the 19042.388 ISO the SSU will be downloaded separately from the LCU.
I also saw this solution from Ten forums. I wish I had saw this solution months ago. I have done a lot of attempts by looking in CBS.logs and Components hive to solve the problem. It was giving me the error in Flash or Microsoft-Windows-Client-Desktop-Required files. Now I know which Sxs folders are essential. Thanks to Ben! Correction: The Ben's fix (Patch.cmd) dont't copy included SxS folder to %windir%\WinSxS. After extracting the cumulative update to the directory called "Upgrade", it copies the contents of the SxS directory into it. Then it proceeds to install with DISM. Of course, Ben's the solution package is only version 2004 but I hope, (with 7zip or Wimlib-imagex) extracting those SxS folders in install.wim to temp folder of current cumulative update could fix the 0x800f0988 error. Spoiler amd64_adobe-flash-for-windows_31bf3856ad364e35_10.0.19041.1_none_e190f18a08ed1a44 amd64_microsoft-windows-s..-installers-onecore_31bf3856ad364e35_10.0.19041.1_none_a1ad7e1744c3f0bf amd64_microsoft-windows-s..cingstack-onecoreds_31bf3856ad364e35_10.0.19041.1_none_6a498b47c108e412 amd64_microsoft-windows-s..ck-mof-onecoreadmin_31bf3856ad364e35_10.0.19041.1_none_cfb2f6ddce7358fb amd64_microsoft-windows-s..formers-shell-extra_31bf3856ad364e35_10.0.19041.1_none_9fffda291c87114e amd64_microsoft-windows-s..gstack-boot-onecore_31bf3856ad364e35_10.0.19041.1_none_0bb831550fd88e36 amd64_microsoft-windows-s..ingstack-base-extra_31bf3856ad364e35_10.0.19041.1_none_d4f5f8a162b118d8 amd64_microsoft-windows-s..k-transformers-core_31bf3856ad364e35_10.0.19041.1_none_2224a82f74ce9470 amd64_microsoft-windows-s..llers-onecore-extra_31bf3856ad364e35_10.0.19041.1_none_d9cbd0b162967138 amd64_microsoft-windows-s..ngstack-onecorebase_31bf3856ad364e35_10.0.19041.1_none_a676034d8141a350 amd64_microsoft-windows-s..ransformers-onecore_31bf3856ad364e35_10.0.19041.1_none_da47c33d9addbda2 amd64_microsoft-windows-s..stack-inetsrv-extra_31bf3856ad364e35_10.0.19041.1_none_ef21285d410753e4 amd64_microsoft-windows-s..stack-termsrv-extra_31bf3856ad364e35_10.0.19041.1_none_c8c1e002df10f7b6 amd64_microsoft-windows-servicingstack-inetsrv_31bf3856ad364e35_10.0.19041.1_none_eb1e3d3b06554d07 amd64_microsoft-windows-servicingstack-onecore_31bf3856ad364e35_10.0.19041.1_none_f44203ddbeab1e75 amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1_none_bf506ecc66a800df wow64_adobe-flash-for-windows_31bf3856ad364e35_10.0.19041.1_none_ebe59bdc3d4ddc3f x86_microsoft-windows-s..-installers-onecore_31bf3856ad364e35_10.0.19041.1_none_458ee2938c667f89 x86_microsoft-windows-s..cingstack-onecoreds_31bf3856ad364e35_10.0.19041.1_none_0e2aefc408ab72dc x86_microsoft-windows-s..ck-mof-onecoreadmin_31bf3856ad364e35_10.0.19041.1_none_73945b5a1615e7c5 x86_microsoft-windows-s..formers-shell-extra_31bf3856ad364e35_10.0.19041.1_none_43e13ea56429a018 x86_microsoft-windows-s..gstack-boot-onecore_31bf3856ad364e35_10.0.19041.1_none_af9995d1577b1d00 x86_microsoft-windows-s..ingstack-base-extra_31bf3856ad364e35_10.0.19041.1_none_78d75d1daa53a7a2 x86_microsoft-windows-s..k-transformers-core_31bf3856ad364e35_10.0.19041.1_none_c6060cabbc71233a x86_microsoft-windows-s..llers-onecore-extra_31bf3856ad364e35_10.0.19041.1_none_7dad352daa390002 x86_microsoft-windows-s..ngstack-onecorebase_31bf3856ad364e35_10.0.19041.1_none_4a5767c9c8e4321a x86_microsoft-windows-s..ransformers-onecore_31bf3856ad364e35_10.0.19041.1_none_7e2927b9e2804c6c x86_microsoft-windows-s..stack-termsrv-extra_31bf3856ad364e35_10.0.19041.1_none_6ca3447f26b38680 x86_microsoft-windows-servicingstack-inetsrv_31bf3856ad364e35_10.0.19041.1_none_8effa1b74df7dbd1 x86_microsoft-windows-servicingstack-onecore_31bf3856ad364e35_10.0.19041.1_none_9823685a064dad3f x86_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1_none_6331d348ae4a8fa9]
I also had issues once with flash in 20h1 build and once with something else in 20h2 (dont remember what it was anymore)... I really dont know what is the cause of this errors, however it looks like files get corrupted for unknown reason. Its really annoying, what is even more annoying is as far as I was googling back then, issue was not wide spread enough to be on MS radar....
The fix looks alot like the old basing the OS fix by @abbodi1406 The problems back then had to do with msft not correctly updating all files inside the IP updates from a certain range.
Did I miss something? Why does 19041.572 need to be updated to 19041.601 in order to install a Microsoft Edge update?
Nobody claimed or said that. This is the 19041.479 version being discussed: https://forums.mydigitallife.net/th...20h1-2-vb_release.80763/page-207#post-1614519
I'm not claiming anybody said that. I just looked at uupdump.ml and I'm seeing a Microsoft Edge update (KB4584229) to 19041.601 and I'm wondering why the build number needs to go to 601 to update Microsoft Edge. I'm just curious about it. Edit: Just realized that I'm posting this in the wrong thread. Sorry, I just woke up!
Thanks for your work Enthousiast. In the updates section for 1809 you have "DotnetCU 3.5 & 4.8" and "DotnetCU 3.5 & 4.7.2". Can I skip 4.7.2 or are both required?
The only website i can find people with those errors is deskcrapper, never seen it mentioned on here before.
Yes. This error (0x800f0988), which occurs in ambiguous situations, has rarely been mentioned. Google search: - site:forums.mydigitallife.net 0x800f0988 - site:reddit.com 0x800f0988 - site:tenforums.com 0x800f0988
What i know from @abbodi1406 the error mainly occurs on non english installs. I don't run non english windows, my wife does, still on 18362, not installing IP updates and never has any problems either.