I mostly get this error 0x800f0988 while windows try to install new CU via windows update as well as when I try to install the LCU in CAB format via DISM & that too in most of my systems, it a prolonged issue for me & never been able to pinpoint the actual reason for this error, so the only option left for me is either clean installation or in place update/upgrade (via later ISO) Can anyone help me to figure it out what exactly causes this issue, few things to add 1. All my devices with this issue are in W10 21H2 Pro, from v1202 to v1348 2. All other updates like SSU/DotNET/MSRT etc install fine via windows update settings 3. If I reinstall windows via the fresh installation or in-place update/upgrade with the help of the latest version ISO, it definitely gets fixed but after one CU or two, the same error returns 4. Googled it & tried all the suggested fix/workaround, no luck. So not sure what exactly breaking this so asking here to the community for help.
1. Because only CU uses PSFX format (and SafeOS dynamic update) all other updates are normal self-contained format 2. Don't run Update cleanup (DISM /StartComponentCleanup) except once monthly, after sucessful patch tuesday CU and disable schedule task "Microsoft\Windows\Servicing\StartComponentCleanup" 3. You can restore RTM components, or install the baseless CU as explained here (for 17763, but same for 19041) https://forums.mydigitallife.net/threads/help-me-installing-this-update.84304/
I've had CUs fail on systems that are as bone stock as possible and CUs work on heavily modified systems over and over for years without issue. I don't even bother trying to diagnose failed updates (because it almost never works), this is what I do: 1. Go to UUP Dump and get the build that matches the build that is failing to update, I do not select the cleanup option. 2. Integrate the current SSU and CU that is failing to install into that image and again, I do not select the cleanup option. 3. Do an in place upgrade using this build from desktop. This works in almost all cases making it pretty pointless to even bother looking into it further.
in 21H2 when I connect the headphones a notification message appears to click on the "OK" button to activate, but only activate the headphones if I click outside the "OK" button, but inside of the notification message. so, the "OK" button does nothing. I have this bug in windows 11 too, is the same bug, I don't have this bug on 21H1 version.
I have been doing the same (in-place upgrade) for almost a year for this CU update issue, this issue was not there in earlier but lately its become common ( not sure about the majority or others but at least for me), but want to find out what exactly breaking the CU every time I did either in-place upgrade or Clean install. & for the 'I do not select the cleanup option.' part, that you wrote twice in both of your points, that option is optional while making an ISO via UUP, checking the cleanup option while making an ISO (via UUP or any other method/tool) with proper compatible DISM mode/method, doesn't break anything (unless the cleanup method is wrong or incompatible or brute to remove necessary files as well), that option is only to remove the obsolete/redundant/old updates to trim the final ISO size.
ok, found that scheduled task now & disabled it manually, any other thing to check? & about that task, as you advise, running that manually once in every month PT after updating to the latest build, will not break anything? Or should I completely keep that task in disabled state & what if I never run that task, not even manually?
I know what it does but after seeing a lot of failures installing CUs I suspect that occasionally superseded components might sometimes actually be needed. I do the cleanup after the in-place upgrade but leave everything in the ESD file to ensure that anything that is needed, is actually there.
I'm a little bit lost with all this links postage and stuff. There's any link with SVF including all languages package for latest Win10 version? I think is it 10.0.19044.1387, right? I remember an cloud.mail.ru link posted somewhere here, that's is periodically updated with latest revisions and laguages (svf).
Thanks a lot. Sorry for laziness but there's a lot of messages and links right here. Is somewhat confusing lol.
--- Windows 10, version 2004 or 20H2 11C Local Experience Packs (LXPs) (updated Dec 2021) [ID: 8334] --- Code: ca8d18e2afdfcf9db98f618892eaa25e9e71d6f17b001bcc0560074436510902 *mul_windows_10_version_2004_or_20h2_11c_local_experience_packs_lxps_updated_dec_2021_x86_x64_arm64_dvd_35dc332d.iso
I am new to win10 updates and upgrade mechanism . I have 2004 i want to transformer it to 21H2 through Aboudis script, because i have added multi languages to 2004 ISO before .
From the post you quoted yourself, you need: LCU(it contains the SSU) NDP35-48 Critical DU for .NET35 DU for SafeOS DU for Sources Defender cab by steven4554 Win 10 21H2 EP All you have to do is use the links in said post. Not needed, answer to second question defeats the purpose of downloading the whole FU package(unless you need it for a specific reason).
Enthousiast always keeps that post up-to-date with the latest available updates. Just like for 18362/18363(190x), the same exact updates from that post apply to all 1904x(20Hx/21Hx) builds. The "x" depends on the EP update you use from that same post. 19041. 19042, 19043 and 19044 are all the same - 19041 with an EP update applied.