Logitech MX Master 3 losing connectivity

[Distorted Vision]

I want to finish the chat session with Logitech first. Then run test with Bluetooth.

 

[ChatGPT]

Perfect — sensible plan. Here’s a short, exact checklist you can follow after you finish the Logitech livechat. It covers (A) finishing the chat safely, (B) reboot & verify KB5070773 applied, (C) Bluetooth pairing for the MX Master 3 and how to test it, and (D) what to capture if any drop happens so I can parse the logs for you.
A — End the Logitech chat first (don’t reboot during the chat)

• Finish the livechat with Logitech. Don’t reboot until the chat ends (as you said).

B — After chat: reboot to complete KB5070773 install

1. Reboot the PC to let KB5070773 finish installing. (This update normally requires a reboot.)
2. After reboot, confirm the update installed:
   • Settings → Windows Update → Update history → look for “KB5070773” (or check the build number).
   • If you prefer PowerShell, run (Admin):
     Get-HotFix | Where-Object { $_.HotFixID -like 'KB5070773' }
   • If it’s listed, OK — proceed to Bluetooth test.

C — Pair MX Master 3 to Bluetooth (exact pairing steps)

1. On the mouse: pick a Bluetooth channel via Easy-Switch (choose an unused channel). To enter pairing mode: press and hold the Easy‑Switch channel button until the LED blinks rapidly (about 3 seconds). That puts the mouse into Bluetooth pairing mode.
2. On Windows: Settings → Bluetooth & devices → Add device → Bluetooth → select “Logitech MX Master 3” (or “MX Master 3” / device name shown) and complete pairing.
3. Confirm Options+: open Logi Options+ (if installed) — it may show the device and allow firmware checks (note: Bolt pairing is separate; Bluetooth pairing will be listed in Windows and in some Logi apps).

D — Bluetooth test procedure (what to do, for how long)

• Use the mouse over Bluetooth for 30–60 minutes with normal use (scroll, click, use side buttons).
• Note any disconnects and the wall‑clock time (HH:MM:SS). If a temporary jitter occurs that auto‑recovers, note it; if it becomes a permanent disconnect, note the time exactly and do the captures below.

E — If a drop happens (what to capture — immediate, decisive, do NOT reboot)
Run these two PowerShell commands immediately (elevated Admin). They produce two small files on your Desktop that I will parse and act on:
$start = (Get-Date).AddMinutes(-60)
Get-PnpDevice -PresentOnly | Where-Object { $_.InstanceId -match 'VID_046D|VID_0A5C' } | Format-List FriendlyName,InstanceId,Status | Out-File "$env:USERPROFILE\Desktop\MouseDeviceInfo.txt"
Get-WinEvent -FilterHashtable @{LogName='System'; StartTime=$start} | Where-Object { $.ProviderName -match 'Kernel-PnP|USBHUB3|USB' -or $.Message -match 'USB|usb|hub|reset|removed|disconnect|device|xhci|ehci' } | Select-Object TimeCreated,ProviderName,Id,LevelDisplayName,Message | Out-File "$env:USERPROFILE\Desktop\USB_Events_Last60min.txt"

• Attach both files here and tell me the wall‑clock time of the drop. I will:
  • If event log shows controller/hub/xhci resets → give the one driver/BIOS update to install.
  • If receiver stayed present and only device retries / “device doesn’t respond” appear → advise to use Bluetooth (good), swap receivers, or replace the mouse (I’ll draft the next message or RMA text).

F — If Bluetooth is stable

• If the MX Master 3 is solid over Bluetooth, that strongly indicates the Unifying link or receiver (placement/antenna/receiver revision) was the problem — that validates keeping the spare receiver + UGreen as your interim setup until you purchase Bolt gear on Black Friday.

G — If Bluetooth also fails

• If the mouse fails over Bluetooth too, the mouse hardware is likely at fault. Attach the two files above (post‑drop) and I’ll confirm and give one clear next action (recommend replacement model and migration steps or the RMA text, if you still want it).

H — Optional: stop USB monitor before reboot / after test

• If you have the usb_monitor running and you’re about to reboot to complete KB install, stop it first (Admin PowerShell):
  Stop-Process -Id (Get-Content "$env:USERPROFILE\Desktop\usb_monitor.pid") -Force; Remove-Item "$env:USERPROFILE\Desktop\usb_monitor.pid" -ErrorAction SilentlyContinue

Summary (one line)

• Finish Logitech chat → reboot to complete KB5070773 → pair MX Master 3 via Bluetooth → test for 30–60 minutes → if a drop occurs, run the two PowerShell captures and attach the two desktop files; I’ll parse and give the single next action.

I’ll wait here while you finish the chat — tell me when you’re ready and I’ll stand by to parse the logs or walk you through the Bluetooth pairing step if you want live guidance.

 

[Distorted Vision]

The update failed at 27% with Install error - 0x800f0991

 

[ChatGPT]

Good — that plan (finish Logitech chat, then run the Bluetooth test) makes sense. Below is a short, practical checklist you can follow now and immediately after the chat, plus the exact commands I want you to run if any more drops happen (so I can parse the logs and give the single next action). I’ll also include the safe non‑reboot steps you can run now if Logitech asks you to try fixes while in chat.
Quick context reminder (why we care)

• Your Unifying software and Slax captures already showed repeated “Device doesn’t respond” messages and temporary reconnects, and the receiver often stayed enumerated while the mouse channel failed — that points strongly to a per‑device radio/session issue rather than a full USB controller crash. I’ll re‑confirm after you finish the chat and after the Bluetooth test.

Plan — what to do now and after the chat
1) While you’re still in the Logitech livechat

• Do NOT reboot until the chat finishes (you said this).
• You may run the non‑reboot health/cleanup steps below if Logitech asks you to try fixes now (they don’t require a reboot). They often help Windows Update retries.

Non‑reboot safe steps you can run now (if needed)
Run these in an elevated PowerShell / Administrator Command Prompt (one block at a time; each finishes before the next):
A — Run SFC (checks system files)
sfc /scannow
B — Run DISM checks (does not force reboot)
DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
If ScanHealth reports corruption, you can run:
DISM /Online /Cleanup-Image /RestoreHealth
(If RestoreHealth needs files and fails, we’ll get a manual source after your chat — don’t reboot now.)
C — Reset Windows Update cache (stops/starts services; no reboot)
net stop wuauserv
net stop bits
net stop cryptsvc
net stop trustedinstaller
ren "%windir%\SoftwareDistribution" SoftwareDistribution.old
ren "%windir%\System32\catroot2" catroot2.old
net start wuauserv
net start bits
net start cryptsvc
net start trustedinstaller
What to expect: these are safe. If they fix the broken update components, Windows Update may retry automatically. If KB5070773 still fails, we’ll collect logs after the chat.
2) Finish the Logitech livechat (do not reboot during it) — when you finish, come back here and:
A — Reboot to complete update installs

• Reboot once chat is over so KB5070773 (and any pending updates) can finish applying. KB5070773 usually requires a reboot to finalize. If the update succeeds after the reboot, test the mouse in Windows for normal behaviour first.

B — Immediately pair and test the mouse over Bluetooth

• Steps:
  1. Put the MX Master 3 into a Bluetooth channel and pairing mode (hold the Easy‑Switch channel button until it blinks rapidly).
  2. Windows → Settings → Bluetooth & devices → Add device → Bluetooth → select the MX Master 3 and pair.
  3. Use the mouse for 30–60 minutes with normal actions (move, click, scroll, side buttons). Note and record wall‑clock time(s) of any temporary or permanent disconnect(s).

Why: Bluetooth isolates the radio link from Unifying — if Bluetooth is stable, the problem is the Unifying link/receiver/placement, not the mouse internals.
3) If a drop occurs after the chat (do NOT reboot) — the single decisive captures
Run these exact commands in an elevated PowerShell immediately after the next drop (copy/paste). They save two small files to your Desktop that you can attach here; I will parse and give the single next action:
$start = (Get-Date).AddMinutes(-60)
Get-PnpDevice -PresentOnly | Where-Object { $_.InstanceId -match 'VID_046D|VID0A5C' } | Format-List FriendlyName,InstanceId,Status | Out-File "$env:USERPROFILE\Desktop\MouseDeviceInfo.txt"
Get-WinEvent -FilterHashtable @{LogName='System'; StartTime=$start} | Where-Object { $.ProviderName -match 'Kernel-PnP|USBHUB3|USB|Microsoft-Windows-DriverFrameworks-UserMode' -or $_.Message -match 'USB|usb|hub|reset|removed|disconnect|device|xhci|ehci|HID' } | Select-Object TimeCreated,ProviderName,Id,LevelDisplayName,Message | Out-File "$env:USERPROFILE\Desktop\USB_Events_Last60min.txt"
Attach (paperclip) the two files: MouseDeviceInfo.txt and USB_Events_Last60min.txt and tell me the wall‑clock time of the drop(s). I will parse them immediately and tell you the single next action:

• If the event log shows hub/controller/xhci resets at the drop time → we update a single chipset/USB driver or BIOS (I’ll give the exact download link and steps).
• If the receiver stayed present and the events show only per‑device retries / “device doesn’t respond” → it’s a radio/session issue — try the spare receiver/Bluetooth or replace the mouse (I’ll recommend the single hardware action).

(You already captured earlier Windows and Slax evidence showing “device doesn’t respond” and no controller reset — that strongly suggested device/radio issues; these post‑drop Windows captures will confirm for the ~19:00 event.)
4) If KB5070773 still fails to install (0x800f0991) after the chat and before reboot

• If the update keeps failing with 0x800f0991, the usual non‑reboot remedies are SFC/DISM (above) and clearing SoftwareDistribution (above). If those don’t fix it, the manual install from the Microsoft Update Catalog or an in‑place repair (Windows 11 Installation Assistant) may be needed — both usually require a reboot and/or will be safe to run after your chat ends. If KB fails again after you reboot, capture these and attach them so I can diagnose:

A) WindowsUpdate log:
Get-WindowsUpdateLog -LogPath "$env:USERPROFILE\Desktop\WindowsUpdate.log"
B) CBS errors (extract SR lines + any 0x800f0991 lines):
findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log > "%USERPROFILE%\Desktop\CBS_SR.txt"
findstr /i "0x800f0991" "%windir%\Logs\CBS\CBS.log" > "%USERPROFILE%\Desktop\CBS_0x800f0991.txt"
Attach WindowsUpdate.log and the CBS extracts and I’ll tell you the single next step to get the update installed.
5) While you finish the chat — keep the USB monitor running

• You already had the monitor running; leave it running while you’re away so any events are captured. When you return stop it and attach USB_Monitor.log (it helps, but the Event log captures above are decisive). If you want the stop command to paste later:

Stop-Process -Id (Get-Content "$env:USERPROFILE\Desktop\usb_monitor.pid") -Force; Remove-Item "$env:USERPROFILE\Desktop\usb_monitor.pid" -ErrorAction SilentlyContinue
(We discussed the monitor and how to stop it earlier; the log will be useful if the drop recurs.)
Final short checklist (copy/paste)

• Finish Logitech chat (no reboot).
• After chat: reboot to complete KB5070773.
• Pair MX Master 3 to Bluetooth and test 30–60 minutes.
• If drop occurs: run the two capture commands above and attach the two Desktop files.
• If KB5070773 still fails post‑reboot: run WindowsUpdate/CBS log commands above and attach those logs.

I’ll wait here while you finish the livechat. After you reboot and run the Bluetooth test (or if a drop happens), attach the two small files (MouseDeviceInfo.txt + USB_Events_Last60min.txt) and I’ll parse immediately and give the single next action.

 

[Distorted Vision]

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

Install error - 0x800f0991

Walk me through what I need to do now.

 

[ChatGPT]

Okay — let’s fix 0x800f0991 step‑by‑step without rebooting. I’ll give you a short explanation, then the exact commands to run now (safe to run while you’re still in the Logitech chat). After each block I say what to expect and what to paste back if you want me to check results.
Short explanation (one line)

• 0x800f0991 means the update failed to apply because Windows couldn’t get/replace some component store payloads (common causes: corrupted component store, missing payloads for certain SKUs like “N”, or transient WU service problems). We’ll try repairs and reset WU cache without rebooting first, gather logs, and only reboot when you finish chat.

Run these in an elevated PowerShell / Admin Command Prompt. Do them in order.
1) Run the built‑in Windows Update troubleshooter (safe)
msdt.exe /id WindowsUpdateDiagnostic

• Follow prompts. If it finds/fixes anything, note the message it reports.

2) System File Checker (SFC) — checks system files
Run in an elevated command prompt:
sfc /scannow

• Wait until it finishes. If it reports “found corrupt files and repaired them”, paste that summary line. If it reports no integrity violations, move on.

3) DISM quick health checks (no reboot required)
Run these three commands (may take a few minutes):
DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth

• If ScanHealth reports corruption, run (this may download repair payloads from WU):
  DISM /Online /Cleanup-Image /RestoreHealth

Note: /RestoreHealth may take several minutes and may download files from Microsoft. If it fails and asks for a source, don’t worry — capture logs (see below) and I’ll guide you.
4) Reset Windows Update cache (stops/starts services; no reboot)
Run this whole block in an elevated prompt (copy/paste):
net stop wuauserv
net stop bits
net stop cryptsvc
net stop trustedinstaller
ren "%windir%\SoftwareDistribution" SoftwareDistribution.old
ren "%windir%\System32\catroot2" catroot2.old
net start wuauserv
net start bits
net start cryptsvc
net start trustedinstaller

• After this, try Settings → Windows Update → Check for updates. If it still fails, continue.

5) If you want to attempt a manual install now (download only; install later)

• I can fetch the Microsoft Update Catalog link for KB5070773 for your exact build/edition so you can download the .msu/.cab now and install after the chat (install usually requires reboot). Tell me your exact Windows edition/build (run command below and paste output) and I’ll fetch the exact package:
  systeminfo | findstr /B /C:"OS Name" /C:"OS Version" /C:"System Type"

6) Collect diagnostics (do this now — important)
If the update still fails, run these to produce logs I need to diagnose:
A) WindowsUpdate log (converts event trace to readable log):
Get-WindowsUpdateLog -LogPath "$env:USERPROFILE\Desktop\WindowsUpdate.log"

• Attach WindowsUpdate.log (from your Desktop).

B) Extract CBS error lines and any specific 0x800f0991 occurrences:
findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log > "%USERPROFILE%\Desktop\CBS_SR.txt"
findstr /i "0x800f0991" "%windir%\Logs\CBS\CBS.log" > "%USERPROFILE%\Desktop\CBS_0x800f0991.txt"

• Attach CBS_SR.txt and CBS_0x800f0991.txt (they’ll be small if matches exist).

C) If you already have WindowsUpdate error details in Settings → Update history, copy/paste the exact error text and KB id (you already have KB5070773 and 0x800f0991).
7) If DISM /RestoreHealth fails asking for a source (don’t do this until chat ends if you must keep session)

• You can mount a matching Windows ISO and use it as a source. Example (replace D: with the mounted ISO drive letter):
  DISM /Online /Cleanup-Image /RestoreHealth /Source:wim:\sources\install.wim:1 /LimitAccess
  (We’ll only do this after chat if needed — I’ll guide you to select the correct image index for your Windows edition.)

8) If all non‑reboot steps fail

• Two options after chat ends:
  A) Manual install of KB5070773 (.msu/.cab) from Microsoft Update Catalog (I can grab the link for you now). Installation usually requires reboot.
  B) In‑place upgrade / repair using Windows 11 Installation Assistant (keeps apps/files) — this also fixes component store problems. I can guide you when you’re ready.

What to paste/attach here now

• Results of sfc /scannow (summary).
• Results of DISM commands (ScanHealth / RestoreHealth output).
• If any of the commands produced errors, paste the error lines or attach the three log files from step 6 (WindowsUpdate.log, CBS_SR.txt, CBS_0x800f0991.txt) and I’ll parse them immediately.

If you want I can:

• Fetch the KB5070773 download link for your exact Windows SKU now (you’ll still wait to install until your chat ends), OR
• Walk you through running DISM /RestoreHealth now and interpreting output.

Which would you like me to do next?

• (A) Walk through SFC + DISM + Update cache reset now (I’ll wait for each command result), or
• (B) Grab the KB5070773 Download link for your exact SKU (tell me your OS name/version from systeminfo command above).

 

[Distorted Vision]

Windows Update troubleshooter didn't fix anything.

PS C:\WINDOWS\system32> msdt.exe /id WindowsUpdateDiagnostic
PS C:\WINDOWS\system32> sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.
PS C:\WINDOWS\system32> DISM /Online /Cleanup-Image /CheckHealth

Deployment Image Servicing and Management tool
Version: 10.0.26100.5582

Image Version: 10.0.26200.5670

The component store is repairable.
The operation completed successfully.
PS C:\WINDOWS\system32> DISM /Online /Cleanup-Image /ScanHealth

Deployment Image Servicing and Management tool
Version: 10.0.26100.5582

Image Version: 10.0.26200.5670

[==========================100.0%==========================] No component store corruption detected.
The operation completed successfully.
PS C:\WINDOWS\system32>
PS C:\WINDOWS\system32>

 

[Distorted Vision]

Chat has ended.

Windows Update Troubleshooter didn't find anything.

PS C:\WINDOWS\system32> msdt.exe /id WindowsUpdateDiagnostic
PS C:\WINDOWS\system32> sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.
PS C:\WINDOWS\system32> DISM /Online /Cleanup-Image /CheckHealth

Deployment Image Servicing and Management tool
Version: 10.0.26100.5582

Image Version: 10.0.26200.5670

The component store is repairable.
The operation completed successfully.
PS C:\WINDOWS\system32> DISM /Online /Cleanup-Image /ScanHealth

Deployment Image Servicing and Management tool
Version: 10.0.26100.5582

Image Version: 10.0.26200.5670

[==========================100.0%==========================] No component store corruption detected.
The operation completed successfully.
PS C:\WINDOWS\system32>
PS C:\WINDOWS\system32>

Trying to install the update again.

 

[ChatGPT]

Thanks — good work so far. Since the update failed at 27% with 0x800f0991, here’s a safe, ordered plan you can run now (no reboot required) to try to fix it, how to collect the logs if it still fails, and the single next actions after each outcome. I’ll keep it short and give exact copy‑paste commands for each step.
Quick summary of what 0x800f0991 means

• It indicates Windows Update couldn’t apply the package because the component store or payloads are inconsistent / missing (common on some SKUs and when the component store needs repair). KB5070773 is the Oct‑2025 out‑of‑band update for WinRE/USB input.

Do these steps in order (run each block in an elevated PowerShell / Admin Command Prompt). Wait for each command to finish before running the next. Don’t reboot while you’re still doing the non‑reboot steps.
1) (Already done) Quick verification you already ran

• You ran SFC and DISM ScanHealth; SFC reported no integrity violations and DISM ScanHealth reported no corruption. Good; we’ll still try RestoreHealth next. (You’re already on the right track.)

2) Run DISM RestoreHealth now (may download replacement files; no reboot)
Run exactly:
DISM /Online /Cleanup-Image /RestoreHealth

• Expect: this can take 5–30+ minutes. If it completes successfully it will report that it repaired the image or that no repair was needed.

3) Reset Windows Update cache & services (safe; no reboot)
Run this block exactly (stops WU services, renames caches, restarts services):
net stop wuauserv
net stop bits
net stop cryptsvc
net stop trustedinstaller
ren "%windir%\SoftwareDistribution" SoftwareDistribution.old
ren "%windir%\System32\catroot2" catroot2.old
net start wuauserv
net start bits
net start cryptsvc
net start trustedinstaller

• Then try Settings → Windows Update → Check for updates again.

4) If update still fails — collect the diagnostic logs (do this now)
Run these commands to create the readable logs I’ll need to diagnose the exact cause:
Get-WindowsUpdateLog -LogPath "$env:USERPROFILE\Desktop\WindowsUpdate.log"

extract Component-Based Servicing (CBS) SR lines and any occurrences of the error code​

findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log > "%USERPROFILE%\Desktop\CBS_SR.txt"
findstr /i "0x800f0991" "%windir%\Logs\CBS\CBS.log" > "%USERPROFILE%\Desktop\CBS_0x800f0991.txt"

copy recent System events (useful but optional)​

Get-WinEvent -FilterHashtable @{LogName='System'; StartTime=(Get-Date).AddHours(-6)} |
Where-Object { $.ProviderName -match 'WindowsUpdate|Kernel-PnP|USBHUB|USBHUB3|xHCI|ehci|TrustedInstaller' -or $.Message -match '0x800f0991|error|failed|reset|disconnect' } |
Select-Object TimeCreated,ProviderName,Id,LevelDisplayName,Message |
Out-File "$env:USERPROFILE\Desktop\System_USB_and_WU_events.txt"
Attach these three desktop files here:

• WindowsUpdate.log
• CBS_SR.txt
• CBS_0x800f0991.txt
  (Optionally System_USB_and_WU_events.txt) — I’ll parse them and tell you the single next step.

5) If you want to try a manual package install (recommended after logs if WU keeps failing)

• I can fetch the correct Microsoft Update Catalog package for KB5070773 for your exact SKU (Windows 11 25H2 x64 or 24H2 x64). Tell me which Windows edition you have (run this and paste the output):

systeminfo | findstr /B /C:"OS Name" /C:"OS Version"

• After you confirm the exact edition, I’ll give the exact Microsoft Update Catalog link and the exact command to install the .msu or .cab (wusa "C:\path\KB5070773.msu" /quiet /norestart or DISM /Online /Add-Package /PackagePath:"C:\path\KB5070773.cab"). Note: installing manually usually requires a reboot to finish — do that after your Logitech chat ends.

6) If manual .msu install fails or DISM/RestoreHealth cannot get files

• Option A (safe, if you can wait): do an in‑place repair / repair install with the Windows 11 Installation Assistant or an ISO (keeps apps/data). This normally fixes component store problems. I can walk you through this after you finish chat and are ready to reboot. Back up important files first.
• Option B: If your Windows is an “N” SKU you may need the Media Feature Pack for your build — let me know the OS Name/Version (step above) and I’ll confirm. Missing media components can cause 0x800f0991 on some updates.

7) If you prefer me to fetch the KB package link now
Tell me the output of:
systeminfo | findstr /B /C:"OS Name" /C:"OS Version" /C:"System Type"
and I’ll fetch the exact KB5070773 package link for your SKU so you can download it now and install later. (I won’t recommend installing requiring a reboot while you’re mid‑support chat, but you can download now and install after.)
8) What I’ll do with the logs

• I will parse WindowsUpdate.log and CBS_SR/CBS_0x800f0991.txt and look for the exact failure reason (missing payload, component store mismatch, or SKU/media issue). Then I’ll give one single instruction: either the direct .msu to install, the exact DISM command with a source, or “do in‑place repair” and I’ll give the exact Microsoft link & steps.

Quick practical note about your mouse issue

• KB5070773 targets WinRE/USB fixes; if the update succeeds and you still see the MX Master drops, we’ll continue with the Bluetooth isolate and the decisive captures I described earlier (Get‑PnpDevice + Get‑WinEvent) and I’ll tell you the one hardware or driver step next. Your Unifying logs already showed “Device doesn’t respond” (device‑side clues) so we may still find the mouse/receiver is root cause.

What do you want me to do now?

• A: I can walk you through running DISM /RestoreHealth and the Update cache reset step now (I’ll wait for outputs).
• B: Or I can fetch the KB5070773 Microsoft Update Catalog links for your exact Windows SKU right away — paste the systeminfo output and I’ll get the exact download links.

Which do you prefer?

 

[Distorted Vision]

Update failed.

PS C:\WINDOWS\system32> msdt.exe /id WindowsUpdateDiagnostic
PS C:\WINDOWS\system32> sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.
PS C:\WINDOWS\system32> DISM /Online /Cleanup-Image /CheckHealth

Deployment Image Servicing and Management tool
Version: 10.0.26100.5582

Image Version: 10.0.26200.5670

The component store is repairable.
The operation completed successfully.
PS C:\WINDOWS\system32> DISM /Online /Cleanup-Image /ScanHealth

Deployment Image Servicing and Management tool
Version: 10.0.26100.5582

Image Version: 10.0.26200.5670

[==========================100.0%==========================] No component store corruption detected.
The operation completed successfully.
PS C:\WINDOWS\system32>
PS C:\WINDOWS\system32> DISM /Online /Cleanup-Image /RestoreHealth

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> net stop wuauserv
The Windows Update service is stopping.
The Windows Update service was stopped successfully.

PS C:\WINDOWS\system32> net stop bits
The Background Intelligent Transfer Service service is not started.
More help is available by typing NET HELPMSG 3521. PS C:\WINDOWS\system32> net stop cryptsvc The following services are dependent on the Cryptographic Services service. Stopping the Cryptographic Services service will also stop these services.

Acronis Cyber Protection Service
Acronis Active Protection (TM) Service

Do you want to continue this operation? (Y/N) [N]: y
System error 5 has occurred.

Access is denied.

PS C:\WINDOWS\system32> net stop trustedinstaller
The Windows Modules Installer service is stopping.
The Windows Modules Installer service was stopped successfully.

PS C:\WINDOWS\system32> ren "%windir%\SoftwareDistribution" SoftwareDistribution.old
ren : Cannot rename because item at '%windir%\SoftwareDistribution' does not exist.
At line:1 char:1
+ ren "%windir%\SoftwareDistribution" SoftwareDistribution.old
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidOperation: ) [Rename-Item], PSInvalidOperationException
+ FullyQualifiedErrorId : InvalidOperation,Microsoft.PowerShell.Commands.RenameItemCommand

PS C:\WINDOWS\system32> ren "%windir%\System32\catroot2" catroot2.old
ren : Cannot rename because item at '%windir%\System32\catroot2' does not exist.
At line:1 char:1
+ ren "%windir%\System32\catroot2" catroot2.old
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidOperation: ) [Rename-Item], PSInvalidOperationException
+ FullyQualifiedErrorId : InvalidOperation,Microsoft.PowerShell.Commands.RenameItemCommand

PS C:\WINDOWS\system32> net start wuauserv
The Windows Update service is starting.
The Windows Update service was started successfully.

PS C:\WINDOWS\system32> net start bits
The Background Intelligent Transfer Service service is starting..
The Background Intelligent Transfer Service service was started successfully.

PS C:\WINDOWS\system32> net start cryptsvc
The requested service has already been started.

More help is available by typing NET HELPMSG 2182.

PS C:\WINDOWS\system32> net start trustedinstaller
The Windows Modules Installer service is starting.
The Windows Modules Installer service was started successfully.

PS C:\WINDOWS\system32> Get-WindowsUpdateLog -LogPath "$env:USERPROFILE\Desktop\WindowsUpdate.log"

Getting the list of all ETL files...

Please wait for all of conversions to complete...


================ Results from WULog_0 ================

Input
----------------
File(s):
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251011.130551.567.1.etl
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251011.132055.268.1.etl
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251011.141250.882.1.etl
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251011.191250.469.1.etl
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251011.191250.469.2.etl
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251011.191250.469.3.etl
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251011.191250.469.4.etl
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251011.195309.916.1.etl
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251011.205851.680.1.etl
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251011.215115.338.1.etl

100.00%

Output
----------------
DumpFile: C:\Users\rupes\AppData\Local\Temp\WindowsUpdateLog\wuetl.XML.tmp.758ded55-f4e5-4922-ac05-8d6985efa8d3.00000
Warning:
Some events do not match the schema.
Please rerun the command with -lr to get less restricted XML dump
The command completed successfully.

==================================================


================ Results from WULog_1 ================

Input
----------------
File(s):
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251012.020031.530.1.etl
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251012.021533.739.1.etl
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251012.032058.303.1.etl
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251012.075733.745.1.etl
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251012.105027.837.1.etl
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251012.151023.385.1.etl
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251012.151023.385.2.etl
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251014.013235.364.1.etl
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251014.013235.364.2.etl
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251014.013235.364.3.etl

100.00%

Output
----------------
DumpFile: C:\Users\rupes\AppData\Local\Temp\WindowsUpdateLog\wuetl.XML.tmp.758ded55-f4e5-4922-ac05-8d6985efa8d3.00001
Warning:
Some events do not match the schema.
Please rerun the command with -lr to get less restricted XML dump
The command completed successfully.

==================================================


================ Results from WULog_2 ================

Input
----------------
File(s):
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251014.013235.364.4.etl
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251014.013235.364.5.etl
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251014.013235.364.6.etl
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251014.013235.364.7.etl
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251014.013235.364.8.etl
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251014.013235.364.9.etl
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251014.013235.364.10.etl
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251014.013235.364.11.etl
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251014.013235.364.12.etl
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251014.013235.364.13.etl

100.00%

Output
----------------
DumpFile: C:\Users\rupes\AppData\Local\Temp\WindowsUpdateLog\wuetl.XML.tmp.758ded55-f4e5-4922-ac05-8d6985efa8d3.00002
Warning:
Some events do not match the schema.
Please rerun the command with -lr to get less restricted XML dump
The command completed successfully.

==================================================


================ Results from WULog_3 ================

Input
----------------
File(s):
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251014.013235.364.14.etl
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251014.013235.364.15.etl
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251014.013235.364.16.etl
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251014.013235.364.17.etl
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251016.083115.031.1.etl
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251016.083115.031.2.etl
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251016.083115.031.3.etl
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251016.231602.094.1.etl
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251016.231602.094.2.etl
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251016.231602.094.3.etl

100.00%

Output
----------------
DumpFile: C:\Users\rupes\AppData\Local\Temp\WindowsUpdateLog\wuetl.XML.tmp.758ded55-f4e5-4922-ac05-8d6985efa8d3.00003
Warning:
Some events do not match the schema.
Please rerun the command with -lr to get less restricted XML dump
The command completed successfully.

==================================================


================ Results from WULog_4 ================

Input
----------------
File(s):
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251016.231602.094.4.etl
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251016.231602.094.5.etl
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251016.231602.094.6.etl
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251016.231602.094.7.etl
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251017.012726.981.1.etl
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251017.020522.747.1.etl
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251017.021814.571.1.etl
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251017.040412.641.1.etl
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251017.095804.092.1.etl
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251017.102056.246.1.etl

100.00%

Output
----------------
DumpFile: C:\Users\rupes\AppData\Local\Temp\WindowsUpdateLog\wuetl.XML.tmp.758ded55-f4e5-4922-ac05-8d6985efa8d3.00004
Warning:
Some events do not match the schema.
Please rerun the command with -lr to get less restricted XML dump
The command completed successfully.

==================================================


================ Results from WULog_5 ================

Input
----------------
File(s):
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251017.103515.110.1.etl
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251017.164938.872.1.etl
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251017.164938.872.2.etl
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251018.061621.640.1.etl
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251018.061621.640.2.etl
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251018.061621.640.3.etl
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251018.061621.640.4.etl
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251018.061621.640.5.etl
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251018.061621.640.6.etl
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251018.061621.640.7.etl

100.00%

Output
----------------
DumpFile: C:\Users\rupes\AppData\Local\Temp\WindowsUpdateLog\wuetl.XML.tmp.758ded55-f4e5-4922-ac05-8d6985efa8d3.00005
Warning:
Some events do not match the schema.
Please rerun the command with -lr to get less restricted XML dump
The command completed successfully.

==================================================


================ Results from WULog_6 ================

Input
----------------
File(s):
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251018.064929.527.1.etl
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251018.064929.527.2.etl
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251019.084743.136.1.etl
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251019.084743.136.2.etl
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251019.084743.136.3.etl
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251019.124222.627.1.etl
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251019.125732.477.1.etl
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251020.012027.987.1.etl
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251020.013102.628.1.etl
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251020.023241.384.1.etl

100.00%

Output
----------------
DumpFile: C:\Users\rupes\AppData\Local\Temp\WindowsUpdateLog\wuetl.XML.tmp.758ded55-f4e5-4922-ac05-8d6985efa8d3.00006
Warning:
Some events do not match the schema.
Please rerun the command with -lr to get less restricted XML dump
The command completed successfully.

==================================================


================ Results from WULog_7 ================

Input
----------------
File(s):
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251020.034848.447.1.etl
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251020.184341.395.1.etl
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251020.184341.395.2.etl
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251020.184341.395.3.etl
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251021.014559.001.1.etl
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251021.014559.001.2.etl
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251021.133418.343.1.etl
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251021.134920.964.1.etl
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251021.151259.807.1.etl
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251021.161604.861.1.etl

100.00%

Output
----------------
DumpFile: C:\Users\rupes\AppData\Local\Temp\WindowsUpdateLog\wuetl.XML.tmp.758ded55-f4e5-4922-ac05-8d6985efa8d3.00007
Warning:
Some events do not match the schema.
Please rerun the command with -lr to get less restricted XML dump
The command completed successfully.

==================================================


================ Results from WULog_8 ================

Input
----------------
File(s):
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251021.161604.861.2.etl
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251021.161604.861.3.etl
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251021.161604.861.4.etl
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251021.161604.861.5.etl
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251021.161604.861.6.etl
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251021.161604.861.7.etl
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251021.220758.658.1.etl
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251021.220758.658.2.etl
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251022.002540.990.1.etl
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251022.031417.095.1.etl

100.00%

Output
----------------
DumpFile: C:\Users\rupes\AppData\Local\Temp\WindowsUpdateLog\wuetl.XML.tmp.758ded55-f4e5-4922-ac05-8d6985efa8d3.00008
Warning:
Some events do not match the schema.
Please rerun the command with -lr to get less restricted XML dump
The command completed successfully.

==================================================


================ Results from WULog_9 ================

Input
----------------
File(s):
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251022.040349.610.1.etl
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251022.044406.542.1.etl
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251022.044406.542.2.etl
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251022.115112.874.1.etl
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251022.131301.691.1.etl
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251022.165143.453.1.etl
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251022.165143.453.2.etl
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251022.181043.475.1.etl
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251022.192023.122.1.etl
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251022.202435.988.1.etl

100.00%

Output
----------------
DumpFile: C:\Users\rupes\AppData\Local\Temp\WindowsUpdateLog\wuetl.XML.tmp.758ded55-f4e5-4922-ac05-8d6985efa8d3.00009
Warning:
Some events do not match the schema.
Please rerun the command with -lr to get less restricted XML dump
The command completed successfully.

==================================================


================ Results from WULog_10 ================

Input
----------------
File(s):
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251022.204612.211.1.etl
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251022.204612.211.2.etl

100.00%

Output
----------------
DumpFile: C:\Users\rupes\AppData\Local\Temp\WindowsUpdateLog\wuetl.XML.tmp.758ded55-f4e5-4922-ac05-8d6985efa8d3.00010
Warning:
Some events do not match the schema.
Please rerun the command with -lr to get less restricted XML dump
The command completed successfully.

==================================================


WindowsUpdate.log written to C:\Users\rupes\Desktop\WindowsUpdate.log

PS C:\WINDOWS\system32> findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log > "%USERPROFILE%\Desktop\CBS_SR.txt"
out-file : Could not find a part of the path 'C:\WINDOWS\system32\%USERPROFILE%\Desktop\CBS_SR.txt'.
At line:1 char:1
+ findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log > "%USERPROFILE%\Desktop\ ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : OpenError: ) [Out-File], DirectoryNotFoundException
+ FullyQualifiedErrorId : FileOpenFailure,Microsoft.PowerShell.Commands.OutFileCommand

PS C:\WINDOWS\system32> findstr /i "0x800f0991" "%windir%\Logs\CBS\CBS.log" > "%USERPROFILE%\Desktop\CBS_0x800f0
>> findstr /i "0x800f0991" "%windir%\Logs\CBS\CBS.log" > "%USERPROFILE%\Desktop\CBS_0x800f0991.txt"
>> Select-Object TimeCreated,ProviderName,Id,LevelDisplayName,Message |
>> Out-File "$env:USERPROFILE\Desktop\System_USB_and_WU_events.txt"
>>
Files:

• CBS_SR.txt
• CBS_0x800f0991.txt

were not created.

I renameed WindowsUpdate.log to WindowsUpdate.txt as it won't allow me to upload .log files.

 

[ChatGPT]

Thanks — you’ve done the key repairs (SFC and DISM RestoreHealth completed) which are good. Since KB5070773 still fails with 0x800f0991, here’s a clear, ordered plan (exact commands to copy/paste) to finish this safely and get the update installed — plus what to capture and the single next action depending on the outcome.
Short summary of what we know

• KB5070773 is the October 2025 out‑of‑band servicing fix for Windows 11 (addresses WinRE / USB input regressions). Many machines hit install errors such as 0x800f0991; community/coverage confirms this was widespread after the recent rollouts.

Immediate goal

• Get KB5070773 installed (or confirm a specific reason it cannot be installed) and reboot to complete the package so we can re‑test your mouse behaviour.

Do these steps in order. I include exact commands and what to expect. You can run them now — you said chat finished, so a reboot is OK at the end when I ask you to.
1) Make sure third‑party services won’t block servicing (Acronis showed up earlier)
Why: The Net Stop cryptsvc earlier failed because Cryptographic Services had dependent Acronis services. Those services can interfere with servicing. Disable them temporarily.
Run these as Administrator (PowerShell):

stop and disable Acronis services temporarily (if present)​

Get-Service -Name "Acronis*" -ErrorAction SilentlyContinue | ForEach-Object { Stop-Service -Id $.Id -Force -ErrorAction SilentlyContinue; Set-Service -Id $.Id -StartupType Disabled }
If you don’t have Acronis, the command will do nothing. If prompted by UAC, accept. After update finishes you can re-enable Acronis services with:

re-enable Acronis services​

Get-Service -Name "Acronis*" -ErrorAction SilentlyContinue | ForEach-Object { Set-Service -Id $.Id -StartupType Automatic; Start-Service -Id $.Id -ErrorAction SilentlyContinue }
2) Run component store cleanup and analyze (helps with servicing)
Run as Administrator:

cleanup unused components and packages​

DISM /Online /Cleanup-Image /StartComponentCleanup

optional: more thorough analyze (gives a report)​

DISM /Online /Cleanup-Image /AnalyzeComponentStore
What to expect: StartComponentCleanup is safe and usually quick. It reduces the WinSxS footprint and can unblock some installs.
3) Try manual install of KB5070773 (download + wusa) — recommended next
We need to download the correct package from Microsoft Update Catalog for your exact Windows SKU. First, tell me your OS details (run and paste):
systeminfo | findstr /B /C:"OS Name" /C:"OS Version" /C:"System Type"
When you paste that back I will give the exact Microsoft Update Catalog link for the correct .msu (or .cab) and the exact install command (wusa or DISM). Manual install often bypasses Windows Update server-side issues.
If you want to proceed immediately without me fetching the link, general command after downloading the .msu to C:\Downloads:

install MSU (requires admin; will likely prompt for reboot)​

wusa "C:\Downloads\windows11.0-kb5070773-x64.msu" /quiet /norestart
Or for a .cab:
DISM /Online /Add-Package /PackagePath:"C:\Downloads\KB5070773.cab"
4) If manual install fails: capture specific logs (I’ll parse them)
Run these now (Admin PowerShell). You already produced WindowsUpdate.log — keep that. Also produce these small targeted files:

make readable WindowsUpdate log (if not already)​

Get-WindowsUpdateLog -LogPath "$env:USERPROFILE\Desktop\WindowsUpdate.log"

extract SR lines from CBS and any 0x800f0991 hits​

findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log > "%USERPROFILE%\Desktop\CBS_SR.txt"
findstr /i "0x800f0991" "%windir%\Logs\CBS\CBS.log" > "%USERPROFILE%\Desktop\CBS_0x800f0991.txt"

also copy last 200 lines of DISM log (if used)​

Get-Content C:\Windows\Logs\DISM\dism.log -Tail 200 | Out-File "$env:USERPROFILE\Desktop\dism_tail.txt"
Attach those Desktop files here (WindowsUpdate.log, CBS_SR.txt, CBS_0x800f0991.txt, dism_tail.txt). I will parse them and tell you one exact remediation.
5) If logs don’t reveal a simple fix: in‑place repair (single reliable fix)
If manual install and DISM fixes fail, the reliable next step is an in‑place repair (keeps apps and files). It essentially re‑installs Windows servicing components and will resolve stubborn 0x800f0991 errors.

• Download the Windows 11 Installation Assistant from Microsoft or a matching ISO, run it, choose “Upgrade this PC now” and “Keep personal files and apps.” Follow prompts. This requires a reboot and can take 30–60 minutes. Back up anything unsaved.

I’ll walk you through this if you want; it’s generally effective when servicing is stuck.
6) Extra checks (only if the above still fails)

• Check EFI/System partition size (0x800f0922 usually, but worth checking):
  Get-Partition | Format-Table -AutoSize
  Get-Volume | Format-Table -AutoSize
  If the EFI/System partition is tiny (e.g. ~100MB), consider enlarging it (I can walk you through safely) — but do this only if logs indicate boot files could not be updated.
• Check for pending.xml:
  Test-Path C:\Windows\WinSxS\pending.xml && Get-Content C:\Windows\WinSxS\pending.xml | Out-File "$env:USERPROFILE\Desktop\pending_preview.txt" || "NO_PENDING_XML" | Out-File "$env:USERPROFILE\Desktop\pending_preview.txt"

7) After you get KB5070773 installed & reboot

• Reboot and then test your mouse. If issues persist, pair the MX Master 3 over Bluetooth and run the 60‑minute test; if a drop occurs, run the short, decisive capture I gave earlier and attach files (MouseDeviceInfo + USB_Events_Last60min). I’ll parse and give a single action (driver/BIOS update vs replace receiver/mouse). The earlier evidence we parsed pointed to device/radio issues (Unifying “Device doesn't respond”) rather than host resets.

What I’ll do for you next

• If you want, paste the systeminfo output now and I’ll immediately fetch the correct KB5070773 package link from the Microsoft Update Catalog and give the exact download + install command.
• Or run the DISM /StartComponentCleanup and manual install attempt yourself and then attach WindowsUpdate.log / CBS excerpts and I’ll parse them.

Recommended immediate option

• Paste the systeminfo output (OS Name / OS Version / System Type) and I’ll fetch the exact KB5070773 download link and the install command so you can try the manual install now (then reboot). That’s the highest‑chance next step.

If you prefer I can also:

• Walk you through the in‑place repair (step‑by‑step) if the manual install fails — it’s a reliable last resort.

Which do you want me to do now — fetch the KB download link for your exact SKU (paste systeminfo output) or run another targeted command for you to try first?

 

[Distorted Vision]

Issue with Acronis:

PS C:\WINDOWS\system32> Get-Service -Name "Acronis*" -ErrorAction SilentlyContinue | ForEach-Object { Stop-Service -Id $.Id -Force -ErrorAction SilentlyContinue; Set-Service -Id $.Id -StartupType Disabled }
Stop-Service : A parameter cannot be found that matches parameter name 'Id'.
At line:1 char:92
+ ... orAction SilentlyContinue | ForEach-Object { Stop-Service -Id $.Id -F ...
+ ~~~
+ CategoryInfo : InvalidArgument: ) [Stop-Service], ParameterBindingException
+ FullyQualifiedErrorId : NamedParameterNotFound,Microsoft.PowerShell.Commands.StopServiceCommand

Set-Service : A parameter cannot be found that matches parameter name 'Id'.
At line:1 char:151
+ ... Id $.Id -Force -ErrorAction SilentlyContinue; Set-Service -Id $.Id -S ...
+ ~~~
+ CategoryInfo : InvalidArgument: ) [Set-Service], ParameterBindingException
+ FullyQualifiedErrorId : NamedParameterNotFound,Microsoft.PowerShell.Commands.SetServiceCommand

Stop-Service : A parameter cannot be found that matches parameter name 'Id'.
At line:1 char:92
+ ... orAction SilentlyContinue | ForEach-Object { Stop-Service -Id $.Id -F ...
+ ~~~
+ CategoryInfo : InvalidArgument: ) [Stop-Service], ParameterBindingException
+ FullyQualifiedErrorId : NamedParameterNotFound,Microsoft.PowerShell.Commands.StopServiceCommand

Set-Service : A parameter cannot be found that matches parameter name 'Id'.
At line:1 char:151
+ ... Id $.Id -Force -ErrorAction SilentlyContinue; Set-Service -Id $.Id -S ...
+ ~~~
+ CategoryInfo : InvalidArgument: ) [Set-Service], ParameterBindingException
+ FullyQualifiedErrorId : NamedParameterNotFound,Microsoft.PowerShell.Commands.SetServiceCommand

PS C:\WINDOWS\system32> Get-Service -Name "Acronis*" -ErrorAction SilentlyContinue | ForEach-Object { Set-Service -Id $.Id -StartupType Automatic; Start-Service -Id $.Id -ErrorAction SilentlyContinue }
Set-Service : A parameter cannot be found that matches parameter name 'Id'.
At line:1 char:91
+ ... rorAction SilentlyContinue | ForEach-Object { Set-Service -Id $.Id -S ...
+ ~~~
+ CategoryInfo : InvalidArgument: ) [Set-Service], ParameterBindingException
+ FullyQualifiedErrorId : NamedParameterNotFound,Microsoft.PowerShell.Commands.SetServiceCommand

Start-Service : A parameter cannot be found that matches parameter name 'Id'.
At line:1 char:138
+ ... et-Service -Id $.Id -StartupType Automatic; Start-Service -Id $.Id -E ...
+ ~~~
+ CategoryInfo : InvalidArgument: ) [Start-Service], ParameterBindingException
+ FullyQualifiedErrorId : NamedParameterNotFound,Microsoft.PowerShell.Commands.StartServiceCommand

Set-Service : A parameter cannot be found that matches parameter name 'Id'.
At line:1 char:91
+ ... rorAction SilentlyContinue | ForEach-Object { Set-Service -Id $.Id -S ...
+ ~~~
+ CategoryInfo : InvalidArgument: ) [Set-Service], ParameterBindingException
+ FullyQualifiedErrorId : NamedParameterNotFound,Microsoft.PowerShell.Commands.SetServiceCommand

Start-Service : A parameter cannot be found that matches parameter name 'Id'.
At line:1 char:138
+ ... et-Service -Id $.Id -StartupType Automatic; Start-Service -Id $.Id -E ...
+ ~~~
+ CategoryInfo : InvalidArgument: ) [Start-Service], ParameterBindingException
+ FullyQualifiedErrorId : NamedParameterNotFound,Microsoft.PowerShell.Commands.StartServiceCommand

PS C:\WINDOWS\system32>

 

[ChatGPT]

Thanks — that error is just because those cmdlets don’t use an -Id parameter. Use the service Name (or the service objects’ Name property). Follow these exact steps (copy/paste) — they’ll safely stop & disable Acronis services, run the component cleanup, then we’ll get your OS details so I can fetch the correct KB5070773 package for a manual install.
Do these in an elevated PowerShell (Run as Administrator). I’ll wait for your outputs for the last command.
1) List Acronis services so you can see what’s present
Get-Service -Name 'Acronis*' | Select-Object Name, DisplayName, Status
2) Stop and disable Acronis services (safe)
Get-Service -Name 'Acronis*' -ErrorAction SilentlyContinue |
ForEach-Object {
Write-Host "Stopping & disabling service: $($.Name)"
Stop-Service -Name $.Name -Force -ErrorAction SilentlyContinue
Set-Service -Name $_.Name -StartupType Disabled -ErrorAction SilentlyContinue
}
3) Confirm they are stopped/disabled
Get-Service -Name 'Acronis*' -ErrorAction SilentlyContinue | Select-Object Name, Status, StartType
(When you’re ready to re‑enable them later, use the commands at the end of this reply.)
4) Run component store cleanup (safe)
DISM /Online /Cleanup-Image /StartComponentCleanup
(Wait for it to finish; this is quick and safe.)
5) Try Windows Update again (GUI) — if it still fails, do the manual steps below. If it fails again, proceed to step 6.
6) If the update still fails — get your exact Windows edition/build (I need this to fetch the correct KB package)
Run and paste the output of this exact command:
systeminfo | findstr /B /C:"OS Name" /C:"OS Version" /C:"System Type"
Paste that output here and I’ll fetch the correct KB5070773 download link for your exact SKU and give you the exact manual install command (and whether it will be .msu or .cab).
7) If you want to re‑enable Acronis services later (once update done)
Get-Service -Name 'Acronis*' -ErrorAction SilentlyContinue |
ForEach-Object {
Set-Service -Name $.Name -StartupType Automatic -ErrorAction SilentlyContinue
Start-Service -Name $.Name -ErrorAction SilentlyContinue
Write-Host "Enabled & started: $($_.Name)"
}
Notes and safety

• We disabled Acronis only temporarily because its services were blocking cryptsvc stop earlier; re‑enable when you’re done.
• If SoftwareDistribution or catroot2 renames earlier failed because the folders didn’t exist, we’ll check existence before trying to rename — I can show those commands if you want to retry the cache reset after stopping services.
• After you paste systeminfo I’ll fetch the correct KB and give the exact manual install command so you can install & reboot at your convenience.

Paste the output of the systeminfo command and I’ll get the right KB download link and the install command for you.

 

[Distorted Vision]

Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.

Install the latest PowerShell for new features and improvements! Installing PowerShell on Windows - PowerShell

PS C:\WINDOWS\system32> Get-Service -Name 'Acronis*' | Select-Object Name, DisplayName, Status

Name DisplayName Status
---- ----------- ------
AcronisActiveProtectionService Acronis Active Protection (TM) Service Running
AcronisCyberProtectionService Acronis Cyber Protection Service Running


PS C:\WINDOWS\system32> Get-Service -Name 'Acronis*' -ErrorAction SilentlyContinue |
>> ForEach-Object {
>> Write-Host "Stopping & disabling service: $($.Name)"
>> Stop-Service -Name $.Name -Force -ErrorAction SilentlyContinue
>> Set-Service -Name $_.Name -StartupType Disabled -ErrorAction SilentlyContinue
>> }
$.Name : The term '$.Name' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct
and try again.
At line:3 char:45
+ Write-Host "Stopping & disabling service: $($.Name)"
+ ~~~~~~
+ CategoryInfo : ObjectNotFound: ($.Name:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

Stopping & disabling service:
$.Name : The term '$.Name' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct
and try again.
At line:3 char:45
+ Write-Host "Stopping & disabling service: $($.Name)"
+ ~~~~~~
+ CategoryInfo : ObjectNotFound: ($.Name:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

Stopping & disabling service:
PS C:\WINDOWS\system32> Get-Service -Name 'Acronis*' -ErrorAction SilentlyContinue | Select-Object Name, Status, StartType

Name Status StartType
---- ------ ---------
AcronisActiveProtectionService Running Automatic
AcronisCyberProtectionService Running Automatic


PS C:\WINDOWS\system32>

 

[ChatGPT]

Thanks — the problem was just the PowerShell variable syntax in the ForEach-Object block. Use $_ (the current pipeline object) inside $() when you want to expand it inside a string. Below are the corrected commands and a safe sequence to stop Acronis services, reset the Update cache (only if those folders exist), retry Update, and next steps to get KB5070773 manually if needed.
Do these in an elevated PowerShell (Run as Administrator). I’ll wait while you run each group and paste the results if anything errors.
1) Stop & disable Acronis services (corrected)
Copy & paste this block exactly:
Get-Service -Name 'Acronis*' -ErrorAction SilentlyContinue |
ForEach-Object {
Write-Host "Stopping & disabling service: $($.Name)"
Stop-Service -Name $.Name -Force -ErrorAction SilentlyContinue
Set-Service -Name $_.Name -StartupType Disabled -ErrorAction SilentlyContinue
}
Check they stopped/are disabled:
Get-Service -Name 'Acronis*' -ErrorAction SilentlyContinue | Select-Object Name, Status, StartType
If Stop-Service reports Access Denied, ensure the PowerShell session is elevated. If Acronis still resists, exit the Acronis UI (tray icon) and try again; if that still fails we can stop the Acronis processes with:
Stop-Process -Name Acronis* -Force -ErrorAction SilentlyContinue
(Use this only if needed; it kills their processes.)
2) Rename Update caches only if they exist (safe)
Some earlier rename attempts failed because the folders didn’t exist. Run this block — it checks first:
if (Test-Path "$env:windir\SoftwareDistribution") {
Rename-Item "$env:windir\SoftwareDistribution" "SoftwareDistribution.old" -ErrorAction SilentlyContinue
Write-Host "SoftwareDistribution renamed"
} else { Write-Host "SoftwareDistribution folder not found" }
if (Test-Path "$env:windir\System32\catroot2") {
Rename-Item "$env:windir\System32\catroot2" "catroot2.old" -ErrorAction SilentlyContinue
Write-Host "catroot2 renamed"
} else { Write-Host "catroot2 folder not found" }
3) Restart update services
Run:
net start wuauserv
net start bits
net start cryptsvc
net start trustedinstaller
Then try Check for updates in Settings → Windows Update.
4) If Windows Update still fails (0x800f0991), collect the logs I need
Run these to create the log files on your Desktop (you’ve already made WindowsUpdate.log — keep it). Run them now:
Get-WindowsUpdateLog -LogPath "$env:USERPROFILE\Desktop\WindowsUpdate.log"
findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log > "$env:USERPROFILE\Desktop\CBS_SR.txt"
findstr /i "0x800f0991" "%windir%\Logs\CBS\CBS.log" > "$env:USERPROFILE\Desktop\CBS_0x800f0991.txt"
Get-Content C:\Windows\Logs\DISM\dism.log -Tail 200 | Out-File "$env:USERPROFILE\Desktop\dism_tail.txt"
Attach those files (or paste any error lines) and I’ll parse them and recommend the single next action.
5) If you want to try manual install of KB5070773 now (I can fetch the correct package)
I need your exact OS/edition to give the right Microsoft Update Catalog link. Run and paste the output of:
systeminfo | findstr /B /C:"OS Name" /C:"OS Version" /C:"System Type"
When you paste that, I’ll pull the KB5070773 catalog entry for your SKU and give the exact download and install command (wusa for .msu or DISM for .cab). Note: installing the .msu will typically require a reboot to finish.
6) Re‑enable Acronis services afterwards (when you’re done)
To restore Acronis to automatic and restart them, run:
Get-Service -Name 'Acronis*' -ErrorAction SilentlyContinue |
ForEach-Object {
Set-Service -Name $.Name -StartupType Automatic -ErrorAction SilentlyContinue
Start-Service -Name $.Name -ErrorAction SilentlyContinue
Write-Host "Enabled & started: $($_.Name)"
}
7) If Acronis prevents stopping or the update still fails

• If Acronis keeps blocking cryptsvc or other actions even after stopping services, you can either:
  • Exit its UI and retry the Stop/Disable block, or
  • Temporarily uninstall Acronis (if you’re comfortable) and reinstall later — I can give exact commands if needed.

Next step for me

• Paste the systeminfo output (OS Name / OS Version / System Type) and let me fetch the exact KB5070773 download link and the command to install it.
• Or attach the three log files (WindowsUpdate.log, CBS_SR.txt, CBS_0x800f0991.txt) if you prefer I diagnose from those first.

Which do you want me to do next — fetch the KB package link for your exact OS, or parse the logs you’ll produce?

 

[Distorted Vision]

PS C:\WINDOWS\system32> Get-Service -Name 'Acronis*' -ErrorAction SilentlyContinue |
>> ForEach-Object {
>> Write-Host "Stopping & disabling service: $($.Name)"
>> Stop-Service -Name $.Name -Force -ErrorAction SilentlyContinue
>> Set-Service -Name $_.Name -StartupType Disabled -ErrorAction SilentlyContinue
>> }
$.Name : The term '$.Name' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct
and try again.
At line:3 char:45
+ Write-Host "Stopping & disabling service: $($.Name)"
+ ~~~~~~
+ CategoryInfo : ObjectNotFound: ($.Name:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

Stopping & disabling service:
$.Name : The term '$.Name' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct
and try again.
At line:3 char:45
+ Write-Host "Stopping & disabling service: $($.Name)"
+ ~~~~~~
+ CategoryInfo : ObjectNotFound: ($.Name:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

Stopping & disabling service:
PS C:\WINDOWS\system32> Get-Service -Name 'Acronis*' -ErrorAction SilentlyContinue | Select-Object Name, Status, StartType

Name Status StartType
---- ------ ---------
AcronisActiveProtectionService Running Automatic
AcronisCyberProtectionService Running Automatic


PS C:\WINDOWS\system32>

 

[ChatGPT]

Thanks — got it. The error you hit was from using the wrong variable syntax inside the ForEach‑Object block. Use $ (not $.) and, if embedding in a string, use $($.Name). Below are the exact, tested commands to:

• stop & disable Acronis services correctly,
• safely rename the Windows Update caches only if they exist,
• re‑start Update services,
• collect the CBS / WindowsUpdate / DISM snippets I need if the update still fails,
• get your OS info so I can fetch the correct KB5070773 package for manual install,
• and re‑enable Acronis later.

Run these in an elevated PowerShell (Run as Administrator). Copy‑paste each block and wait for it to finish.
1) Stop & disable Acronis services (corrected)
Get-Service -Name 'Acronis*' -ErrorAction SilentlyContinue |
ForEach-Object {
Write-Host "Stopping & disabling service: $($.Name)"
Stop-Service -Name $.Name -Force -ErrorAction SilentlyContinue
Set-Service -Name $_.Name -StartupType Disabled -ErrorAction SilentlyContinue
}
Check status:
Get-Service -Name 'Acronis*' -ErrorAction SilentlyContinue | Select-Object Name, Status, StartType
If Stop‑Service fails due to stubborn processes, run (only if needed):
Stop-Process -Name "Acronis*" -Force -ErrorAction SilentlyContinue
2) Rename Windows Update caches only if they exist (safe)
if (Test-Path "$env:windir\SoftwareDistribution") {
Rename-Item "$env:windir\SoftwareDistribution" "$env:windir\SoftwareDistribution.old" -ErrorAction SilentlyContinue
Write-Host "Renamed SoftwareDistribution"
} else { Write-Host "SoftwareDistribution not found" }
if (Test-Path "$env:windir\System32\catroot2") {
Rename-Item "$env:windir\System32\catroot2" "$env:windir\System32\catroot2.old" -ErrorAction SilentlyContinue
Write-Host "Renamed catroot2"
} else { Write-Host "catroot2 not found" }
3) Restart Windows Update services
net start wuauserv
net start bits
net start cryptsvc
net start trustedinstaller
Then try Settings → Windows Update → Check for updates. If it still fails, continue.
4) If the update still fails: collect the logs I need (these create small files on your Desktop)

readable Windows Update log​

Get-WindowsUpdateLog -LogPath "$env:USERPROFILE\Desktop\WindowsUpdate.log"

extract CBS [SR] lines and any occurrences of 0x800f0991​

Select-String -Path "$env:windir\Logs\CBS\CBS.log" -Pattern '[SR]' | Out-File "$env:USERPROFILE\Desktop\CBS_SR.txt"
Select-String -Path "$env:windir\Logs\CBS\CBS.log" -Pattern '0x800f0991' -CaseSensitive:$false | Out-File "$env:USERPROFILE\Desktop\CBS_0x800f0991.txt"

last lines of DISM log​

Get-Content "$env:windir\Logs\DISM\dism.log" -Tail 200 | Out-File "$env:USERPROFILE\Desktop\dism_tail.txt"
Attach these Desktop files (WindowsUpdate.log, CBS_SR.txt, CBS_0x800f0991.txt, dism_tail.txt) and I’ll parse them and tell you the precise remediation.
5) Give me your exact OS edition/build so I can fetch the KB5070773 package
Run and paste the output here:
systeminfo | findstr /B /C:"OS Name" /C:"OS Version" /C:"System Type"
When you paste that, I’ll fetch the correct Microsoft Update Catalog package for KB5070773 for your SKU and give the exact manual install command (wusa for .msu or DISM for .cab). Manual install usually requires a reboot to complete.
6) Re‑enable Acronis services later (when you’re ready)
To restore Acronis once the update is done:
Get-Service -Name 'Acronis*' -ErrorAction SilentlyContinue |
ForEach-Object {
Set-Service -Name $.Name -StartupType Automatic -ErrorAction SilentlyContinue
Start-Service -Name $.Name -ErrorAction SilentlyContinue
Write-Host "Enabled & started: $($_.Name)"
}
7) If the manual .msu install fails or DISM/RestoreHealth can’t fix

• Next reliable step is an in‑place repair (Windows 11 Installation Assistant or ISO “Upgrade this PC now” — keeps apps/files). I’ll walk you through that if needed.

Recap / what I need from you now

• Run the corrected Acronis stop/disable block above (if you haven’t already).
• If Windows Update still fails, run step 4 to produce the log files and attach them.
• Or run the systeminfo command and paste the output so I can fetch the exact KB5070773 download link for your machine.

Paste the systeminfo output now (or attach the log files) and I’ll take it from there.

 

[Distorted Vision]

Sorry I already went ahead and uninstalled Acronis True Image.

 

[ChatGPT]

Thanks — you’ve done the important repairs (SFC + DISM RestoreHealth completed) and you produced the WindowsUpdate log. Because KB5070773 still fails with 0x800f0991, the next reliable step is a targeted manual install of the correct package for your exact Windows SKU — I’ll fetch that for you. First I need two small things from you, then I’ll give the exact download + install command.
What I need you to do now (one short command — paste the output)
1) Tell me your exact OS edition/build so I can fetch the correct KB package:
Run this in an elevated PowerShell (copy/paste) and paste the output here:
systeminfo | findstr /B /C:"OS Name" /C:"OS Version" /C:"System Type"
Why: KB packages are specific to OS edition and build. You mentioned 25H2 earlier, but I must confirm the exact edition/build string before picking the correct .msu/.cab.
While I wait for that, two safe prep / diagnostic steps you can run (optional but useful)

• If you want to re‑create the CBS/SRU extracts (you attempted earlier but had a path issue), run these exact commands in an elevated PowerShell. They are safe and will create small files on your Desktop so I can parse the precise failure traces:

create readable Windows Update log (you already created this earlier; keep the file)​

Get-WindowsUpdateLog -LogPath "$env:USERPROFILE\Desktop\WindowsUpdate.log"

extract SR lines from CBS and any 0x800f0991 occurrences​

Select-String -Path "$env:windir\Logs\CBS\CBS.log" -Pattern '[SR]' | Out-File "$env:USERPROFILE\Desktop\CBS_SR.txt"
Select-String -Path "$env:windir\Logs\CBS\CBS.log" -Pattern '0x800f0991' -CaseSensitive:$false | Out-File "$env:USERPROFILE\Desktop\CBS_0x800f0991.txt"

save the last 200 lines of the DISM log (if present)​

Get-Content "$env:windir\Logs\DISM\dism.log" -Tail 200 | Out-File "$env:USERPROFILE\Desktop\dism_tail.txt"
Attach those files if you want me to inspect them now. You wrote WindowsUpdate.log to Desktop earlier, so we already have that step done.
What I will do as soon as you paste the systeminfo output

• I will fetch the exact Microsoft Update Catalog entry for KB5070773 that matches your Windows edition and give the exact single command you should run to install it (wusa for .msu or DISM for .cab), plus the safe reboot step. Manual install typically succeeds where Windows Update loops fail and it’s the next best step.

If the manual install succeeds

• Reboot to complete the install, then test your MX Master mouse. If it still drops, pair it to Bluetooth and test (we’ll isolate device vs receiver). If a drop occurs post‑reboot, run the “decisive captures” (Get‑PnpDevice + Get‑WinEvent) I provided earlier and attach the two files; I’ll parse immediately and give the single next action.

If the manual install fails (or you prefer not to try it)

• I’ll parse the CBS / WindowsUpdate logs you attach and give the one next action: either a specific DISM /RestoreHealth with a local source (I’ll give the exact install.wim path & command), or an in‑place repair (Installation Assistant) with step‑by‑step instructions.

Recap — exactly what to paste now

• Paste the output of:
  systeminfo | findstr /B /C:"OS Name" /C:"OS Version" /C:"System Type"

Also attach (optional) the Desktop files if you already created them:

• WindowsUpdate.log (you renamed earlier — that’s fine)
• CBS_SR.txt
• CBS_0x800f0991.txt
• dism_tail.txt

I’ll fetch the correct KB download and give the single-line install command immediately after you paste the systeminfo output.