You’re very close — RestoreHealth and the SSU are in place (good progress). The next step is to install the two CABs we extracted. If DISM still reports “The system cannot find the file specified” (0x80070002) we’ll capture a tiny set of outputs and I’ll tell you the single corrective action. (Reference: your RestoreHealth success and earlier CAB‑open errors are in the logs you collected.
Do these exact commands (copy/paste each line) from an elevated PowerShell / Admin Command Prompt. Run them in order and wait for each to finish.
1) Reconfirm the two CAB filenames (one line — paste back the output)
Get-ChildItem "C:\Scratch\KB5070773_extracted" -Filter "*.cab" | Format-Table Name,Length -AutoSize
(You already ran this and saw DesktopDeployment.cab and onepackage.AggregatedMetadata.cab listed — confirm they still appear.
2) Try to add the two CABs (run one at a time). Save the full DISM output to small text files so we can inspect the exact error if it fails:
DISM /Online /Add-Package /PackagePath:"C:\Scratch\KB5070773_extracted\onepackage.AggregatedMetadata.cab" > "$env:USERPROFILE\Desktop\dism_onepkg_output.txt" 2>&1
DISM /Online /Add-Package /PackagePath:"C:\Scratch\KB5070773_extracted\DesktopDeployment.cab" > "$env:USERPROFILE\Desktop\dism_deploy_output.txt" 2>&1
3) Reboot to allow any servicing commits:
Restart-Computer
4) After reboot, verify whether KB5070773 is now recorded:
dism /Online /Get-Packages | findstr /I "KB5070773"
If KB5070773 appears — done. Re‑enable Kaspersky and Controlled Folder Access.
If either DISM /Add-Package fails or the KB is still not recorded, collect these small diagnostic outputs and attach them (or paste the contents). They’re small and will let me give the single exact remediation.
Collect and attach (run as Administrator):
A) The two DISM add outputs we wrote to Desktop already (paste the files):
- %USERPROFILE%\Desktop\dism_onepkg_output.txt
- %USERPROFILE%\Desktop\dism_deploy_output.txt
B) File integrity + permission checks for the two CABs (paste the three command outputs):
Get-FileHash -Algorithm SHA256 "C:\Scratch\KB5070773_extracted\onepackage.AggregatedMetadata.cab"
Get-FileHash -Algorithm SHA256 "C:\Scratch\KB5070773_extracted\DesktopDeployment.cab"
icacls "C:\Scratch\KB5070773_extracted\onepackage.AggregatedMetadata.cab" /T
icacls "C:\Scratch\KB5070773_extracted\DesktopDeployment.cab" /T
C) Small DISM/CBS excerpts (if DISM produced an error; these are the commands I’ll parse):
Select-String -Path "$env:windir\Logs\DISM\dism.log" -Pattern '0x800f0991','0x80070002','Error','Failed' -Context 3,6 | Out-File "$env:USERPROFILE\Desktop\dism_err_small.txt" -Encoding ascii
Select-String -Path "$env:windir\Logs\CBS\CBS.log" -Pattern 'KB5070773','0x800f0991','error' -Context 3,6 | Out-File "$env:USERPROFILE\Desktop\CBS_err_small.txt" -Encoding ascii
Attach these small files (dism_onepkg_output.txt, dism_deploy_output.txt, dism_err_small.txt, CBS_err_small.txt) and paste the two Get-FileHash + icacls outputs here. I’ll read them and give the single next command (most likely one of: re-run DISM pointing at a different CAB from the extracted set, re-run DISM with a local source image, or — only if necessary — recommend the in‑place repair).
Why these steps
- You already extracted the package and the SSU/RestoreHealth steps were the right prerequisites; now we need to let the LCU content install. If DISM can open and apply the two CABs the update usually commits. If DISM still reports file‑not‑found or access errors, the HASH/icacls output quickly reveals whether the CAB files are corrupted, locked, or have ACL problems (and I’ll tell you the one fix). The earlier CAB‑open errors you saw are consistent with that possibility.
Do you want me to wait while you run the two DISM /Add‑Package lines and collect the outputs, or do you prefer to attach the files you already generated? I’ll stand by and parse whatever you attach immediately.
avoids any weird long-path or path-parsing issues that sometimes cause DISM to be unable to open files.