Many user foders (Documents, Downloads.) are redirected (using directory junctions) to E.Temporary folders are redirected (using directory junctions) to B:.User profile folders are on D:, not on C.The disk is partitioned (C:, D:, E:, B:).
What all four compoters have in common and in which respect they differ from most others are: Two of my notebooks are Win10 Home, two are Win10 Pro, one is in a domain, the other three are not. This shows that the update error is systematic and was introduced in the new cumulative updates since 2021-05. But more importantly, the upgrade fails on all my four notebooks, with the same error code 0x800f0922. I've run DISM and SFC many times with no effect. I am pretty sure that the problem is not caused by my system being corrupted.
All attempts to install any newer cumulative update ends with error 0x800f0922, after rollback is performed when 98% of the update is installed (after two reboots). I am unable to install any cumulative update since 2021-05 (the last successfully installed is "2021-04 Cumulative Update for Windows 10 version 20H2 for 圆4 based systems - KB5001330). I have exactly the same problem as you do. in a few cases this is the error code i get if it helps. 0x800f0922 curious if anyones found any tricks for this one. been trying all the usual tricks to reset windows update components w/ no luck.in some cases a full in place upgrade helps but thats a 3+hr ordeal so hoping thats not the ultimate fix here. it installs fine initially but then the post install reboot it build up to around the 98% mark and flips to unable to complete update, undoing changes (and sits there for 20-25 min) and then is fine again for a while. been having struggles with the kb5004237 and/or kb5004945 but gotten around that with some earlier update manual updates but most recently and most consistently the kb5005033 update which i almost never can get to work. when we did the silent upgrade via PDQ deploy we used the /dynamicupdate disabled trigger to save some deployment time and just let our WSUS server catch them up which has been working fine for the most part. Been having a lot of issues with our 2004 and 20H2 windows desktops after upgrading from 1909 with Updates recently.
0 kommentar(er)
