Navigation section

Update failed: Cumulative Update for Windows 11, version 25H2 for x64-based Systems (KB5070773) (26200.6901)

Noted — thanks for the screenshot. I can see DISM RestoreHealth running from F:\sources\install.wim (index 6) and it’s about half complete.
I’ll stay quiet and wait — I won’t post any more commands.
When the operation finishes, reply here (or post “Done”) and I’ll give the single next step. If it errors, paste the final error text or attach the small DISM/CBS log excerpts and I’ll diagnose immediately.
Quick reminders while it runs:
  • Don’t power off or interrupt the PC.
  • Keep Kaspersky paused and Controlled Folder Access off until we finish the install/verification.
  • If the system requests a reboot when DISM completes, go ahead and reboot; then tell me when you’re back.
Ping me when it finishes.
 

PS C:\WINDOWS\system32> dir F:\sources\install.* Directory: F:\sources Mode LastWriteTime Length Name ---- ------------- ------ ---- --r--- 15/09/2025 21:57 6875518816 install.wim PS C:\WINDOWS\system32> DISM /Get-WimInfo /WimFile:F:\sources\install.wim Deployment Image Servicing and Management tool Version: 10.0.26100.5582 Details for image : F:\sources\install.wim Index : 1 Name : Windows 11 Home Description : Windows 11 Home Size : 22,210,088,637 bytes Index : 2 Name : Windows 11 Home N Description : Windows 11 Home N Size : 21,592,038,394 bytes Index : 3 Name : Windows 11 Home Single Language Description : Windows 11 Home Single Language Size : 22,187,952,138 bytes Index : 4 Name : Windows 11 Education Description : Windows 11 Education Size : 23,152,922,900 bytes Index : 5 Name : Windows 11 Education N Description : Windows 11 Education N Size : 22,518,969,111 bytes Index : 6 Name : Windows 11 Pro Description : Windows 11 Pro Size : 23,175,273,005 bytes Index : 7 Name : Windows 11 Pro N Description : Windows 11 Pro N Size : 22,540,028,526 bytes Index : 8 Name : Windows 11 Pro Education Description : Windows 11 Pro Education Size : 23,152,973,538 bytes Index : 9 Name : Windows 11 Pro Education N Description : Windows 11 Pro Education N Size : 22,518,994,880 bytes Index : 10 Name : Windows 11 Pro for Workstations Description : Windows 11 Pro for Workstations Size : 23,153,024,176 bytes Index : 11 Name : Windows 11 Pro N for Workstations Description : Windows 11 Pro N for Workstations Size : 22,519,020,649 bytes The operation completed successfully. PS C:\WINDOWS\system32> DISM /Online /Cleanup-Image /RestoreHealth /Source:wim:F:\sources\install.wim:6 /LimitAccess Deployment Image Servicing and Management tool Version: 10.0.26100.5582 Image Version: 10.0.26200.5670 [==========================100.0%==========================] The restore operation completed successfully. The operation completed successfully. PS C:\WINDOWS\system32>
 

Good — RestoreHealth completed successfully. That often fixes the commit errors that caused 0x800f0991. Next steps (exact commands). Run these from an elevated PowerShell / Admin Command Prompt.
Important before you start
  • Keep Kaspersky paused (or temporarily exit it) and Controlled Folder Access turned off until the install finishes.
  • I recommend you reboot once before installing so the RestoreHealth changes are fully committed.
Step A — reboot now
Restart-Computer
(When you return and are back at an elevated prompt, continue with Step B.
Step B — run the KB installer (preferred)
wusa "C:\Scratch\windows11.0-kb5070773-.msu" /quiet /norestart
Wait for wusa to finish:
while (Get-Process -Name wusa -ErrorAction SilentlyContinue) { Start-Sleep -Seconds 5 }
Write-Host "wusa finished"
Then reboot to complete the install:
Restart-Computer
Step C — verify installation after reboot
dism /Online /Get-Packages | findstr /I "KB5070773"
(or)
Get-HotFix | Where-Object { $_.HotFixID -eq 'KB5070773' }
If the KB appears, you’re done — re‑enable Kaspersky and Controlled Folder Access and test hardware.
If the MSU still does not install or KB5070773 is not recorded
1) Try the CAB fallback (install aggregated metadata + desktop deployment CABs from the extracted folder). Run (Admin):
DISM /Online /Add-Package /PackagePath:"C:\Scratch\KB5070773_extracted\onepackage.AggregatedMetadata.cab"
DISM /Online /Add-Package /PackagePath:"C:\Scratch\KB5070773_extracted\DesktopDeployment.cab"
Then reboot and re-run the verify command above.
2) If that also fails — collect these small logs and attach them (I’ll parse immediately and give the single next action):
Select-String -Path "$env:windir\Logs\DISM\dism.log" -Pattern '0x800f0991','Error','Failed' -Context 3,8 | Out-File "$env:USERPROFILE\Desktop\dism_err_excerpt.txt" -Encoding ascii
dism /Online /Get-Packages | Out-File "$env:USERPROFILE\Desktop\Packages_full.txt" -Encoding ascii
Select-String -Path "$env:windir\Logs\CBS\CBS.log" -Pattern 'KB5070773','0x800f0991','error' -Context 3,8 | Out-File "$env:USERPROFILE\Desktop\CBS_excerpt.txt" -Encoding ascii
Get-WindowsUpdateLog -LogPath "$env:USERPROFILE\Desktop\WindowsUpdate.log"
Attach those files and I’ll read the exact failure lines and tell you the single next step (most likely a specific CAB to apply or an in‑place repair if needed).
If you want me to wait while you run the reboot + wusa sequence, say “I’m running it now” and I’ll hold for the results. Otherwise run the steps above and paste the verification output when ready.
 

PS C:\WINDOWS\system32> DISM /Online /Cleanup-Image /RestoreHealth /Source:wim:F:\sources\install.wim:6 /LimitAccess

Deployment Image Servicing and Management tool
Version: 10.0.26100.5582

Image Version: 10.0.26200.5670

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.
PS C:\WINDOWS\system32>
 

Excellent — RestoreHealth finished successfully. Next (exact, minimal steps). Run these from an elevated PowerShell / Admin Command Prompt.
1) Reboot so the RestoreHealth changes commit:
Restart-Computer
(When you’re back, open an elevated prompt and continue.
2) Run the MSU installer (preferred):
wusa "C:\Scratch\windows11.0-kb5070773-.msu" /quiet /norestart
3) Wait for wusa to finish (optional PowerShell wait loop):
while (Get-Process -Name wusa -ErrorAction SilentlyContinue) { Start-Sleep -Seconds 5 }
Write-Host "wusa finished"
4) Reboot to complete the installation:
Restart-Computer
5) Verify the update installed:
dism /Online /Get-Packages | findstr /I "KB5070773"
(or)
Get-HotFix | Where-Object { $_.HotFixID -eq 'KB5070773' }
If KB5070773 appears — you’re done. Re‑enable Kaspersky and Controlled Folder Access and test your mouse.
If the MSU still fails or KB5070773 is not listed
  • Run these three small commands (elevated) and attach the resulting files here; I’ll parse them immediately and give the single next action:
Select-String -Path "$env:windir\Logs\DISM\dism.log" -Pattern '0x800f0991','Error','Failed' -Context 3,8 | Out-File "$env:USERPROFILE\Desktop\dism_err_excerpt.txt" -Encoding ascii
dism /Online /Get-Packages | Out-File "$env:USERPROFILE\Desktop\Packages_full.txt" -Encoding ascii
Select-String -Path "$env:windir\Logs\CBS\CBS.log" -Pattern 'KB5070773','0x800f0991','error' -Context 3,8 | Out-File "$env:USERPROFILE\Desktop\CBS_excerpt.txt" -Encoding ascii
Also keep the WindowsUpdate.log you generated earlier (or re-create it with Get-WindowsUpdateLog).
I’ll wait while you reboot and run step 2 — say “Running wusa now” and I’ll hold for your results; if it finishes, paste the verification output.
 

Running wusa now. Taking some time:

Untitled.webp
 

Got the screenshot — I can see wusa running. I’ll stay quiet and wait.
When the installer finishes, reply here (or paste the final message/output). I’ll then tell you the single next step (verify and — only if needed — the small log captures).
 

ChatGPT this is dragging out for longer than I thought. Do you see the finishing line in sight or are we still far away from resolution?
 

Short answer — you’re close and this is the right path. RestoreHealth completed successfully and the SSU is installed, so the heavy lifting is done. wusa now needs to finish committing the LCU (that can take several minutes). Don’t kill or interrupt it — let it finish and then run the few checks below.
What to expect
  • Best case: wusa finishes, you reboot, and KB5070773 shows in the installed packages — we’re done.
  • If it still fails to commit we’ll collect three tiny logs and choose one final action (apply specific CABs or run an in‑place repair). That’s the fallback but often not needed after a successful RestoreHealth+SSU.
Do this when wusa finishes (exact commands — run elevated)
1) Wait for wusa to exit (you already have the loop). After it exits, reboot to let commits complete:
Restart-Computer
2) After the reboot, verify the update installed:
dism /Online /Get-Packages | findstr /I "KB5070773"
If that returns a line for KB5070773 — success. Re‑enable Kaspersky and Controlled Folder Access and test the mouse.
If KB5070773 is NOT listed, run these three commands (they create small files you can attach) and paste/attach the files so I can parse them and tell you the single next step:
Select-String -Path "$env:windir\Logs\DISM\dism.log" -Pattern '0x800f0991','Error','Failed' -Context 3,8 | Out-File "$env:USERPROFILE\Desktop\dism_err_excerpt.txt" -Encoding ascii
dism /Online /Get-Packages | Out-File "$env:USERPROFILE\Desktop\Packages_full.txt" -Encoding ascii
Select-String -Path "$env:windir\Logs\CBS\CBS.log" -Pattern 'KB5070773','0x800f0991','error' -Context 3,8 | Out-File "$env:USERPROFILE\Desktop\CBS_excerpt.txt" -Encoding ascii
Also keep the WindowsUpdate.log you already made (or recreate with Get-WindowsUpdateLog).
If you want me to wait now, say “I’ll post results” and I’ll stand by. Otherwise run the reboot + verify when wusa finishes and paste the verification output — I’ll tell you the one follow-up step immediately.
 

Okay thanks. But we're done testing the mouse. The objective here is just installing KB5070773.
 

Understood — objective is just to get KB5070773 installed. You’re on the right path: RestoreHealth completed and SSU was applied, so the common blockers are already handled.
Short summary of what to do next (minimal, exact steps)
1) Let wusa finish (you already have the wait loop). If it’s still running, do nothing until it exits. This can take several minutes.
2) After wusa exits — reboot immediately to allow commits to complete:
Restart-Computer
3) After reboot — verify whether the update is recorded:
dism /Online /Get-Packages | findstr /I "KB5070773"
If that returns a package line for KB5070773, the install succeeded and we’re finished.
If KB5070773 is not recorded
Collect these small logs (run in an elevated PowerShell) and attach them here — I’ll parse them and give the single next command:
Select-String -Path "$env:windir\Logs\DISM\dism.log" -Pattern '0x800f0991','Error','Failed' -Context 3,8 | Out-File "$env:USERPROFILE\Desktop\dism_err_excerpt.txt" -Encoding ascii
dism /Online /Get-Packages | Out-File "$env:USERPROFILE\Desktop\Packages_full.txt" -Encoding ascii
Select-String -Path "$env:windir\Logs\CBS\CBS.log" -Pattern 'KB5070773','0x800f0991','error' -Context 3,8 | Out-File "$env:USERPROFILE\Desktop\CBS_excerpt.txt" -Encoding ascii
Also attach the WindowsUpdate.log (Get-WindowsUpdateLog -LogPath "$env:USERPROFILE\Desktop\WindowsUpdate.log") if you made one.
Notes / reminders
  • Keep Kaspersky paused and Controlled Folder Access off until the MSU commit completes and you verify.
  • If the MSU still fails after RestoreHealth + SSU + reboot, the most-likely next steps are either: (A) apply one or two specific CABs from the extracted package, or (B) run an in‑place repair (both are safe; I’ll give the exact single command after I see the logs).
  • If you’d like, I can wait here while wusa finishes and the reboot completes — say “I’ll post results” and I’ll stand by. Otherwise run the reboot + verify and paste the dism verification output (or attach the three log files above if it fails) and I’ll give the single next step.
 

You’re very close — RestoreHealth succeeded and that fixes the usual causes. I can’t open the three uploaded files (they arrived in a binary form I can’t read). To finish with one precise action I need the small text excerpts from the three files you created on the Desktop so I can read the exact failure lines.
Please run these three commands in an elevated PowerShell (copy/paste exactly) and then paste the three command outputs here (or attach the three resulting .txt files as plain text). Each output will be small.
1) Full package list (first ~60 lines)
Get-Content "$env:USERPROFILE\Desktop\Packages_full.txt" -Encoding ascii | Select-Object -First 60
2) DISM error excerpt (the small error block)
Get-Content "$env:USERPROFILE\Desktop\dism_err_excerpt.txt" -Encoding ascii | Select-String -Pattern '0x800f0991','Error','Failed','HRESULT' -CaseSensitive:$false -Context 5,5
3) CBS excerpt (lines mentioning KB5070773 / 0x800f0991)
Get-Content "$env:USERPROFILE\Desktop\CBS_excerpt.txt" -Encoding ascii | Select-String -Pattern 'KB5070773','0x800f0991','error' -CaseSensitive:$false -Context 5,5
If those commands produce nothing, instead paste the first ~40 lines of each file directly:
  • Open the file in Notepad and copy the top ~40 lines, then paste here.
Once I have those exact log snippets I will read the failure lines and tell you the single next command to run (very likely — install one small CAB or re-run one DISM command). I’ll wait for the pasted outputs (and I won’t post extra commands until you paste them).
 

Good — you’re almost there. Two quick checks and then the one or two commands that usually finish this.
Step 1 — Confirm whether KB5070773 is recorded
Run (Admin) and paste the output here:
dism /Online /Get-Packages | findstr /I "KB5070773"
If that returns a line for KB5070773, we’re done. If it returns nothing, continue.
Step 2 — Confirm the exact CAB filenames you extracted
Run (Admin) and paste the output here (this shows the CABs we’ll install):
Get-ChildItem "C:\Scratch\KB5070773_extracted" -Filter "*.cab" | Format-Table Name,Length -AutoSize
Step 3 — If KB5070773 is NOT recorded, install the two extracted CABs (run them in order)
Run each line (Admin) and wait for it to finish before the next:
DISM /Online /Add-Package /PackagePath:"C:\Scratch\KB5070773_extracted\onepackage.AggregatedMetadata.cab"
DISM /Online /Add-Package /PackagePath:"C:\Scratch\KB5070773_extracted\DesktopDeployment.cab"
After those finish, reboot:
Restart-Computer
Step 4 — Verify the update
After reboot, run (Admin):
dism /Online /Get-Packages | findstr /I "KB5070773"
If KB5070773 now appears — success.
If either DISM /Add-Package errors or KB5070773 still isn’t listed
Capture these three small text snippets and attach them (or paste the content) so I can read the exact failure lines and give the single next command:
Select-String -Path "$env:windir\Logs\DISM\dism.log" -Pattern '0x800f0991','Error','Failed' -Context 3,8 | Out-File "$env:USERPROFILE\Desktop\dism_err_excerpt.txt" -Encoding ascii
dism /Online /Get-Packages | Out-File "$env:USERPROFILE\Desktop\Packages_full.txt" -Encoding ascii
Select-String -Path "$env:windir\Logs\CBS\CBS.log" -Pattern 'KB5070773','0x800f0991','error' -Context 3,8 | Out-File "$env:USERPROFILE\Desktop\CBS_excerpt.txt" -Encoding ascii
Once you paste the small outputs from Step 1 and Step 2 (or the three files if there’s a failure), I’ll give the single next action.
 

Get-Content "$env:USERPROFILE\Desktop\dism_err_excerpt.txt" -Encoding ascii | Select-String -Pattern '0x800f0991','Error','Failed','HRESULT' -CaseSensitive:$false -Context 5,5

This command produces hundreds of lines:

I'm not sure what you want me to do?
Untitled.webp
 

You’re doing fine — that large dump is expected. I just need a much smaller, focused excerpt so I can read the failure lines and give the single next command.
Please run these three short commands (exact copy/paste) from an elevated PowerShell. They create small text files on your Desktop that are quick to read and safe to attach or paste here.
1) Extract only DISM error lines that mention the install failure codes (small file):
Select-String -Path "$env:windir\Logs\DISM\dism.log" -Pattern '0x800f0991','0x80070228','Time_InternalToPublic','Error','Failed' -CaseSensitive:$false -Context 5,5 | Out-File "$env:USERPROFILE\Desktop\dism_err_small.txt" -Encoding ascii
2) Save the first 60 lines of your package list (so I can see any KB entries):
dism /Online /Get-Packages | Out-File "$env:USERPROFILE\Desktop\Packages_full.txt" -Encoding ascii
Get-Content "$env:USERPROFILE\Desktop\Packages_full.txt" -Encoding ascii | Select-Object -First 60
3) Extract any CBS lines mentioning KB5070773 or the 0x800f0991 code:
Select-String -Path "$env:windir\Logs\CBS\CBS.log" -Pattern 'KB5070773','0x800f0991','error' -CaseSensitive:$false -Context 5,5 | Out-File "$env:USERPROFILE\Desktop\CBS_err_small.txt" -Encoding ascii
After those run, either attach the two small files (dism_err_small.txt and CBS_err_small.txt) from your Desktop, or paste the content of dism_err_small.txt and the first ~40 lines of Packages_full.txt here. That will let me see the exact failure lines and tell you the single next command to run.
If you prefer to paste instead of attaching, run this to print the small DISM excerpt to the console and paste the output here:
Get-Content "$env:USERPROFILE\Desktop\dism_err_small.txt" -Encoding ascii
I’ll wait for the small excerpts and won’t add extra commands until I see them.
 

PS C:\WINDOWS\system32> dism /Online /Get-Packages | findstr /I "KB5070773" PS C:\WINDOWS\system32> Get-ChildItem "C:\Scratch\KB5070773_extracted" -Filter "*.cab" | Format-Table Name,Length -AutoSize Name Length ---- ------ 139467dd-a40a-d66d-5921-e19864f89e1e_1.2509.1022.0_x64.msix.rif.cab 11042 14847cc3-88d4-0cbf-cfb7-1ab27f06eb15_1.2508.888.0_x64.msix.rif.cab 13332 286a7398-0eac-3629-7114-ea7fe87aeeb3_1.2509.1022.0_x64.msix.rif.cab 11561 2a0dfa69-2628-f2cd-4a78-f654af5e50c8_1.2509.1022.0_x64.msix.rif.cab 11795 2c14f2b4-8294-f78e-8592-0cdc988f364a_1.2509.1022.0_x64.msix.rif.cab 11248 30de3114-d1a7-aab6-a65f-ef5a746dbead_1.2509.1022.0_x64.msix.rif.cab 11004 3608320c-b0ef-35ca-215e-98625ea09023_1.2509.1022.0_x64.msix.rif.cab 11042 3b280eb3-0240-ab9f-ffbb-15a3b17483f5_1.7.817.0_x64.msix.rif.cab 10865 4927b7e4-795f-1dda-92d7-143a9ca854c1_1.2509.1022.0_x64.msix.rif.cab 11050 4a312b26-b2bc-9c4f-697e-bd37bd38c298_1.2509.1022.0_x64.msix.rif.cab 11815 4a8123a9-5fd0-fc08-15a0-3889604df3d5_1.2509.1022.0_x64.msix.rif.cab 12070 500aef3f-e14c-4095-8256-cb0ac3f371f1_1.2509.1022.0_x64.msix.rif.cab 11067 51645a2a-725b-fadc-49a9-9db46e4563ec_1.2506.707.0_x64.msix.rif.cab 11595 5a4c95f6-4267-042e-5211-148ada7530cc_1.2509.1022.0_x64.msix.rif.cab 11887 5b3627bf-566c-6719-0cf2-6b1795d93aa9_1.2508.888.0_x64.msix.rif.cab 13197 61e42671-4c6d-a52a-2c7d-f786f5b2bc9c_1.2509.1022.0_x64.msix.rif.cab 11410 6645a2ea-5804-a115-f379-7e4b27132a00_1.2509.1022.0_x64.msix.rif.cab 11407 6df9d3c2-cfda-e165-ece9-b88cf6d23797_1.2509.1022.0_x64.msix.rif.cab 11062 6f5ba4de-b4b6-9253-aa28-c1a99434c514_1.2509.1022.0_x64.msix.rif.cab 11061 7333d900-4d25-2b09-990f-9537c9fca549_1.2509.1022.0_x64.msix.rif.cab 11768 7b0d9694-6b7d-9587-48b3-59b76c09c7b4_1.2509.1022.0_x64.msix.rif.cab 12264 7f26acc0-d169-1844-1b15-f330069e4df7_1.7.817.0_x64.msix.rif.cab 10839 81054e32-601c-a517-c313-c9dea0eb6d6d_1.2509.1022.0_x64.msix.rif.cab 12426 87ce00be-9888-c3a1-f1c5-9e045a886c66_1.2508.888.0_x64.msix.rif.cab 12772 87e37cc0-3e5e-ff32-fd8e-c47978064684_1.2509.1022.0_x64.msix.rif.cab 12424 87e95fc4-b66e-9f82-9a41-114531352494_1.2509.1022.0_x64.msix.rif.cab 11158 8bc0a1ab-339d-f7ac-373e-8d4007d1a53c_1.7.817.0_x64.msix.rif.cab 10870 91c85e29-7596-a250-23da-d10c968374e4_1.2509.1022.0_x64.msix.rif.cab 11779 9959e792-3fa2-a9b6-db4b-607e9c36dec2_1.2509.1022.0_x64.msix.rif.cab 11033 998f3e45-8cce-d02e-3d25-5fb4709afb3f_1.2509.1022.0_x64.msix.rif.cab 11579 99c8c976-ccf8-753b-683d-07c62b9e7e6c_1.2509.1022.0_x64.msix.rif.cab 12252 9fd35909-0e0b-702d-3552-7ae5e4d7ab39_1.2509.1022.0_x64.msix.rif.cab 11580 a21d731f-299f-19d9-6ea2-53d0ed10823c_1.2508.879.0_x64.msix.rif.cab 11056 a3ac1fea-be48-4f71-cb90-e7ba8f1b8f55_1.2509.1022.0_x64.msix.rif.cab 11409 a4f674ab-fdca-58e2-cbff-a461ff265c0b_1.2509.1022.0_x64.msix.rif.cab 11063 a7d5832f-17ea-735d-fc9c-3558b64b909c_1.2509.1022.0_x64.msix.rif.cab 11048 a90ba0b9-af5d-2c57-0325-da4ba5e0b40c_1.2509.1022.0_x64.msix.rif.cab 13647 b4fb10e5-8f5f-b754-64b1-9404039cce68_1.2509.1022.0_x64.msix.rif.cab 11047 b5e13ce4-b08c-d623-a4ac-166e3b56f26d_1.2509.1022.0_x64.msix.rif.cab 11045 bc8dfc28-22bf-7bba-001d-1bd953401d71_1.2509.1022.0_x64.msix.rif.cab 11774 c15eb352-5ea9-1f86-c2cf-c672f144f202_1.2509.1022.0_x64.msix.rif.cab 11077 c3ea969e-3d1d-004e-18b6-fa25dc6e5ab0_1.2509.1022.0_x64.msix.rif.cab 11709 c6a3c941-80b2-c959-d4bc-c79499d29816_1.2509.1022.0_x64.msix.rif.cab 11006 cbafa2f6-4e6d-ea39-3e34-6b8c0964d650_1.2509.1022.0_x64.msix.rif.cab 12052 d0252b71-ca68-c4d7-a0ad-935df1374e18_1.2509.1022.0_x64.msix.rif.cab 12269 d07a6f2a-64c5-5352-d1a3-25ff9292f67d_1.2509.1022.0_x64.msix.rif.cab 11704 d8933cd4-e2bf-d7b8-caa9-0929c94e2de8_1.2509.1022.0_x64.msix.rif.cab 12226 d9ec8c5a-39f0-144f-b1e2-88e8ee21aca3_1.2509.1022.0_x64.msix.rif.cab 11508 DesktopDeployment.cab 10926664 DesktopDeployment_X86.cab 9511842 e0ea85e9-6cbb-36ba-6f68-ea14911e974c_1.2509.1022.0_x64.msix.rif.cab 11772 e1bf6ecf-0076-7bc0-97bb-3259c2d5641a_1.2509.1022.0_x64.msix.rif.cab 12444 e28da4dd-c4ea-371a-b8fa-3ac749d1bedd_1.2509.1022.0_x64.msix.rif.cab 12273 ef4ea2cb-0a7f-e531-1d14-4a70b505f6a5_1.2509.1022.0_x64.msix.rif.cab 11084 f52168cd-52b2-2288-570e-45769bc982a6_1.2509.1022.0_x64.msix.rif.cab 12086 f816f1f5-7777-a502-79ff-82dd65bba2fb_1.2509.1022.0_x64.msix.rif.cab 13803 ff21267a-ccf0-b2e1-57e5-3acd786f0b8d_1.7.817.0_x64.msix.rif.cab 10883 ff43562a-1c67-b38a-6aad-93f7cd5881b2_1.2508.888.0_x64.msix.rif.cab 10978 onepackage.AggregatedMetadata.cab 78927 SSU-26100.6893-x64.cab 19839041 wsusscan.cab 305697 PS C:\WINDOWS\system32>
 

Nice — you’ve already got the right CABs extracted. Next step is to apply the two CABs from the extracted folder, reboot, then verify. Run these exact commands from an elevated PowerShell / Admin Command Prompt (one at a time). Keep Kaspersky paused / Controlled Folder Access OFF while you run them.
1) Apply the metadata CAB
DISM /Online /Add-Package /PackagePath:"C:\Scratch\KB5070773_extracted\onepackage.AggregatedMetadata.cab"
2) Apply the deployment CAB
DISM /Online /Add-Package /PackagePath:"C:\Scratch\KB5070773_extracted\DesktopDeployment.cab"
3) Reboot to let the servicing commit
Restart-Computer
4) Verify whether KB5070773 is recorded
dism /Online /Get-Packages | findstr /I "KB5070773"
If a line for KB5070773 appears — success. Re-enable Kaspersky and you’re done.
If either DISM command errors or KB5070773 still does not appear, collect these small diagnostic files (run as Administrator) and attach them here so I can read the exact failure lines and give the single next fix:
Select-String -Path "$env:windir\Logs\DISM\dism.log" -Pattern '0x800f0991','Error','Failed' -CaseSensitive:$false -Context 3,8 | Out-File "$env:USERPROFILE\Desktop\dism_err_excerpt.txt" -Encoding ascii
dism /Online /Get-Packages | Out-File "$env:USERPROFILE\Desktop\Packages_full.txt" -Encoding ascii
Select-String -Path "$env:windir\Logs\CBS\CBS.log" -Pattern 'KB5070773','0x800f0991','error' -CaseSensitive:$false -Context 3,8 | Out-File "$env:USERPROFILE\Desktop\CBS_excerpt.txt" -Encoding ascii
Attach those three .txt files and I’ll parse them and tell you the single next action (most likely a specific CAB to apply or — if necessary — an in‑place repair).
Would you like me to wait now while you run the two DISM commands and reboot? I’ll stand by for the verification output.
 

You must log in or register to reply here.
Back
Top