Logitech MX Master 3 losing connectivity

PS C:\WINDOWS\system32> systeminfo | findstr /B /C:"OS Name" /C:"OS Version" /C:"System Type"
OS Name: Microsoft Windows 11 Pro Insider Preview
OS Version: 10.0.26200 N/A Build 26200
System Type: x64-based PC
PS C:\WINDOWS\system32>

These files haven't been created:

• CBS_SR.txt
• CBS_0x800f0991.txt
• dism_tail.txt

Thanks — good call uninstalling Acronis (that removes the service interference). Next we’ll get the exact OS info, re‑create the small CBS/DISM extracts that weren’t produced earlier, and I’ll fetch the correct KB5070773 package for your machine so you can install it manually. I’ll keep this short and give exact copy‑paste commands to run (all in an elevated PowerShell). After you run them paste the outputs or attach the three small files and I’ll tell you the single next action.
Step A — confirm OS edition/build (I need this to pick the exact KB)
Run this (Admin PowerShell) and paste the whole output here:
systeminfo | findstr /B /C:"OS Name" /C:"OS Version" /C:"System Type"
Step B — recreate the three diagnostic files (they weren’t created earlier)
Run these (Admin PowerShell). They’re safe and will put three small files on your Desktop:

create readable Windows Update log (you already created one, but repeat to be sure)​

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

extract CBS [SR] lines and any 0x800f0991 hits (fixed path)​

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 DISM log​

Get-Content "$env:windir\Logs\DISM\dism.log" -Tail 200 | Out-File "$env:USERPROFILE\Desktop\dism_tail.txt"
Step C — (optional) re‑try the Update cache reset now that Acronis is gone
If you want to try the cache reset again before manual install, run this block (Admin):
net stop wuauserv
net stop bits
net stop cryptsvc
net stop trustedinstaller
if (Test-Path "$env:windir\SoftwareDistribution") { Rename-Item "$env:windir\SoftwareDistribution" "SoftwareDistribution.old" -ErrorAction SilentlyContinue }
if (Test-Path "$env:windir\System32\catroot2") { Rename-Item "$env:windir\System32\catroot2" "catroot2.old" -ErrorAction SilentlyContinue }
net start wuauserv
net start bits
net start cryptsvc
net start trustedinstaller
Then try Settings → Windows Update → Check for updates. If that still fails, proceed to Step D.
Step D — paste the systeminfo output and attach the three Desktop files
Attach these files (from your Desktop) or paste their contents here:

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

And paste the systeminfo output from Step A.
What I’ll do as soon as you send those

• I’ll fetch the exact KB5070773 package from the Microsoft Update Catalog for your SKU and give the one command to install it (.msu via wusa or .cab via DISM) and the exact reboot step. Manual install often succeeds where Windows Update fails. If the manual install still fails, I’ll parse the CBS and DISM snippets and give the single next action (either a DISM with a local source or an in‑place repair). The manual‑install recommendation is the standard next step when WU fails repeatedly.

If you prefer to skip the logs and go straight to the manual package now

• paste the systeminfo output and I’ll immediately grab the KB package link and the exact install command for you.

If anything errors while you run those commands, paste the error text and I’ll interpret it.

Thanks — you’ve done the heavy lifting (SFC and DISM RestoreHealth succeeded and you removed Acronis). KB5070773 still failing with 0x800f0991 is common right now; the fastest reliable path is to download the exact KB package for your build and install it manually. Below are safe, exact steps (copy/paste) plus fallbacks if the manual install fails. I’ll keep it concise and concrete.
Important facts

• KB5070773 is the October 2025 out‑of‑band Cumulative Update for Windows 11 that addresses WinRE USB input issues (applies to builds 26200.6901 and 26100.6901). The catalog entry title you want is:
  "2025‑10 Cumulative Update for Windows 11, version 25H2 for x64‑based Systems (KB5070773) (26200.6901)".

Step A — Prepare (you already did most of this)

• You ran sfc /scannow and DISM /RestoreHealth (both completed successfully). Good.
• You uninstalled Acronis — that eliminates the earlier service conflict. Keep the system as-is for the next step.

Step B — Run component cleanup (safe; frees WinSxS and may help)
Run in an elevated PowerShell / Admin CMD:
DISM /Online /Cleanup-Image /StartComponentCleanup
Wait for it to finish.
Step C — Download the correct KB5070773 package
1) Go to the Microsoft Update Catalog and search for exactly:
2025-10 Cumulative Update for Windows 11, version 25H2 for x64-based Systems (KB5070773) (26200.6901)
(Or search just KB5070773 and choose the item that matches 26200.6901 and x64). 2) Download the x64 package (.msu) for build 26200.6901 to a folder (e.g. C:\Downloads). The catalog filename will look like the KB5070773 MSU for x64 and be ~3.9 GB.
If you want I can fetch the exact catalog link for you — tell me to "Get the KB link" and I’ll paste the catalog page result (you can then click the Download link).
Step D — Install the downloaded .msu manually (exact command)
After the download completes (assume file path is C:\Downloads\windows11-kb5070773-x64.msu — replace with the real filename), run in an elevated CMD/PowerShell:
wusa "C:\Downloads\windows11-kb5070773-x64.msu" /quiet /norestart

• This runs the installer. When it finishes, reboot to complete the install:
  Restart-Computer

Step E — If the manual install fails with an error
1) Capture logs immediately (copy/paste these exact commands in an elevated PowerShell). These write small files to your Desktop that I’ll parse:

readable Windows Update log (you already have this; OK if it’s WindowsUpdate.txt)​

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

extract CBS SR lines and any occurrences of the KB error​

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"

tail of DISM log​

Get-Content "$env:windir\Logs\DISM\dism.log" -Tail 200 | Out-File "$env:USERPROFILE\Desktop\dism_tail.txt"
Attach those Desktop files here (or paste key error lines) and I’ll parse them and give the single next action.
2) If CBS or DISM indicate missing payloads and manual .msu still fails, the reliable fix is an in‑place repair (keeps files/apps):

• Download the latest Windows 11 ISO or use the Windows 11 Installation Assistant from Microsoft, then run “Upgrade this PC now” and choose “Keep personal files and apps.” This will repair the component store and complete any pending servicing — it requires a reboot and can take 30–60+ minutes. I can walk you through that when you’re ready.

Step F — If install succeeds and you reboot

• Check Update history to confirm KB5070773 installed.
• Test your mouse in Windows. If it still drops, pair the MX Master 3 to Bluetooth and test 30–60 minutes. If Bluetooth is stable while Unifying was flaky, that confirms the Unifying receiver/radio placement was the issue (and your plan to use Bolt gear is sensible).

Step G — If you’d like me to fetch the direct catalog download link now

• Paste the output of this command (you already did earlier — good):
  systeminfo | findstr /B /C:"OS Name" /C:"OS Version" /C:"System Type"
  (Your output was: Microsoft Windows 11 Pro Insider Preview / 10.0.26200 Build 26200 / x64.
• I will fetch the matching KB5070773 x64 catalog entry and paste the Download page link for you to click. (You already gave the systeminfo — if you want me to get that link, say “Get the KB link” now and I’ll fetch it.

If manual install still fails after the steps above

• Attach WindowsUpdate.log, CBS_SR.txt, CBS_0x800f0991.txt and dism_tail.txt and I’ll parse them and give the one exact remediation (e.g., a DISM restore using a local install.wim source, or the in‑place repair instructions).

One last practical tip about the mouse while you do this

• Keep using the spare Unifying receiver on the UGreen passive USB‑2.0 extension as your temporary working config. If KB5070773 installs and the mouse still misbehaves, we’ll proceed to the Bluetooth test you planned and then the small Windows captures for the exact 19:00 drop.

Would you like me to:

• A) Fetch the Microsoft Update Catalog download link for KB5070773 (I already have your systeminfo), or
• B) Wait while you manually download and run the .msu and then help if it fails (you can attach the logs)?

Say A or B and I’ll take the next step immediately.

Update still failed after executing:
PS C:\WINDOWS\system32> systeminfo | findstr /B /C:"OS Name" /C:"OS Version" /C:"System Type"
OS Name: Microsoft Windows 11 Pro Insider Preview
OS Version: 10.0.26200 N/A Build 26200 System Type: x64-based PC 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.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
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251012.020031.530.1.etl

100.00%

Output
----------------
DumpFile: C:\Users\rupes\AppData\Local\Temp\WindowsUpdateLog\wuetl.XML.tmp.8a6a982e-5bde-4c1c-b032-3e8c465c0cca.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.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
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251014.013235.364.4.etl

100.00%

Output
----------------
DumpFile: C:\Users\rupes\AppData\Local\Temp\WindowsUpdateLog\wuetl.XML.tmp.8a6a982e-5bde-4c1c-b032-3e8c465c0cca.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.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
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251014.013235.364.14.etl

100.00%

Output
----------------
DumpFile: C:\Users\rupes\AppData\Local\Temp\WindowsUpdateLog\wuetl.XML.tmp.8a6a982e-5bde-4c1c-b032-3e8c465c0cca.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.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
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251016.231602.094.4.etl

100.00%

Output
----------------
DumpFile: C:\Users\rupes\AppData\Local\Temp\WindowsUpdateLog\wuetl.XML.tmp.8a6a982e-5bde-4c1c-b032-3e8c465c0cca.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.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
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251017.103515.110.1.etl

100.00%

Output
----------------
DumpFile: C:\Users\rupes\AppData\Local\Temp\WindowsUpdateLog\wuetl.XML.tmp.8a6a982e-5bde-4c1c-b032-3e8c465c0cca.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.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
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251018.064929.527.1.etl

100.00%

Output
----------------
DumpFile: C:\Users\rupes\AppData\Local\Temp\WindowsUpdateLog\wuetl.XML.tmp.8a6a982e-5bde-4c1c-b032-3e8c465c0cca.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.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
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251020.034848.447.1.etl

100.00%

Output
----------------
DumpFile: C:\Users\rupes\AppData\Local\Temp\WindowsUpdateLog\wuetl.XML.tmp.8a6a982e-5bde-4c1c-b032-3e8c465c0cca.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.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
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251021.161604.861.2.etl

100.00%

Output
----------------
DumpFile: C:\Users\rupes\AppData\Local\Temp\WindowsUpdateLog\wuetl.XML.tmp.8a6a982e-5bde-4c1c-b032-3e8c465c0cca.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.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
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251022.040349.610.1.etl

100.00%

Output
----------------
DumpFile: C:\Users\rupes\AppData\Local\Temp\WindowsUpdateLog\wuetl.XML.tmp.8a6a982e-5bde-4c1c-b032-3e8c465c0cca.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.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
C:\WINDOWS\logs\WindowsUpdate\WindowsUpdate.20251022.204612.211.1.etl

100.00%

Output
----------------
DumpFile: C:\Users\rupes\AppData\Local\Temp\WindowsUpdateLog\wuetl.XML.tmp.8a6a982e-5bde-4c1c-b032-3e8c465c0cca.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.2.etl

100.00%

Output
----------------
DumpFile: C:\Users\rupes\AppData\Local\Temp\WindowsUpdateLog\wuetl.XML.tmp.8a6a982e-5bde-4c1c-b032-3e8c465c0cca.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> Select-String -Path "$env:windir\Logs\CBS\CBS.log" -Pattern '\[SR\]' | Out-File "$env:USERPROFILE\Desktop\CBS_SR.txt"
PS C:\WINDOWS\system32> Select-String -Path "$env:windir\Logs\CBS\CBS.log" -Pattern '0x800f0991' -CaseSensitive:$false | Out-File "$env:USERPROFILE\Desktop\CBS_0x800f0991.txt"
PS C:\WINDOWS\system32> Get-Content "$env:windir\Logs\DISM\dism.log" -Tail 200 | Out-File "$env:USERPROFILE\Desktop\dism_tail.txt"
PS C:\WINDOWS\system32> net stop wuauserv
The Windows Update service is not started.

More help is available by typing NET HELPMSG 3521.

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 Cryptographic Services service is stopping..
The Cryptographic Services service was stopped successfully.

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>
PS C:\WINDOWS\system32> if (Test-Path "$env:windir\SoftwareDistribution") { Rename-Item "$env:windir\SoftwareDistribution" "SoftwareDistribution.old" -ErrorAction SilentlyContinue }
PS C:\WINDOWS\system32> if (Test-Path "$env:windir\System32\catroot2") { Rename-Item "$env:windir\System32\catroot2" "catroot2.old" -ErrorAction SilentlyContinue }
PS C:\WINDOWS\system32>
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 Cryptographic Services service is starting.
The Cryptographic Services service was started successfully.

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>

The following files were empty to so didn't upload:

CBS_0x800f0991.txt
CBS_SR.txt

Thanks — good info. Two important points first, then exactly what I recommend and the exact commands to run (or actions to take) next.
Two key facts we must be clear about

• You’re running Windows 11 Pro Insider Preview, Build 26200 (x64). That matters because servicing for Insider builds can behave differently from the public production channel — a release KB (KB5070773) sometimes won’t apply cleanly to Insider builds or the servicing stack can be out of sequence. You showed that system info earlier: “Microsoft Windows 11 Pro Insider Preview … Build 26200.”
• You already ran the right repairs (SFC and DISM RestoreHealth completed successfully) and produced a WindowsUpdate.log and a DISM tail; the CBS extracts you tried produced no hits for 0x800f0991 (they were empty) — that implies the update failure didn’t leave an obvious 0x800f0991 trace in CBS or the SR lines we searched, so we need the next‑best remediation.

Short recommendation (one line)
Because the KB still fails after SFC/DISM and Acronis removal, the most reliable next step is a manual installation of the matching KB (from the Microsoft Update Catalog) — and if that fails, perform an in‑place repair (Windows 11 setup / “Upgrade this PC now”) which reliably fixes servicing issues. I’ll give both safe options and the exact commands.
Option A — Manual download & install of KB5070773 (try this first)
Why: manual .msu (or .cab) often succeeds where WU fails. You’re on build 26200 so you want the KB package for 26200.6901 (x64).
1) Download the matching package

• Go to Microsoft Update Catalog and download the package titled “2025‑10 Cumulative Update for Windows 11, version 25H2 for x64‑based Systems (KB5070773) (26200.6901)”. (If you want, I’ll fetch the direct catalog link for you — say “Get the KB link” and I’ll paste it.

2) Install the package (exact command)

• After download (assume file path C:\Downloads\windows11-kb5070773.msu — replace with the real filename), run an elevated command:

wusa "C:\Downloads\<real_filename>.msu" /quiet /norestart

• When it finishes, reboot to complete the installation:
  Restart-Computer

If that succeeds, test your mouse. If the KB still fails with an error on manual install, capture the logs in step 4 below and attach them; I’ll parse the exact failure lines.
Option B — In‑place repair (most reliable if manual install fails)
Why: this repairs the entire servicing stack/components without wiping your files or apps and almost always resolves stubborn update errors.
High‑level steps (safe; back up important files first)
1) Download a matching Windows 11 installer / ISO. Because you’re on Insider Preview you should download the matching Insider ISO if possible (or use the latest Windows 11 ISO from Microsoft if you prefer to move back to the public build).
2) Mount the ISO (File Explorer: right‑click → Mount) or in PowerShell:
Mount-DiskImage -ImagePath "C:\Downloads\Win11.iso"
3) Run the installer from the mounted drive (replace D: with the drive letter of the mounted ISO):
Start-Process -FilePath "D:\setup.exe" -ArgumentList "/auto upgrade" -Wait

• In the GUI choose “Keep personal files and apps” when prompted. Follow on‑screen steps and reboot when prompted. This process can take 30–60+ minutes.

Option C — If you prefer I fetch the KB5070773 Catalog link now
Tell me “Get the KB link” and I’ll fetch the Microsoft Update Catalog entry (I already have your systeminfo / build). I will paste the direct catalog Download page and the exact filename to download — you can then run the wusa command above.
If you want me to diagnose the failure from logs instead
You already created WindowsUpdate.log and a DISM tail; CBS_SR/CBS_0x800f0991 were empty. If you still want me to parse them I’ll need the actual Desktop files attached (WindowsUpdate.txt/WINDOWSUPDATE.log and dism_tail.txt). If you attach them I will immediately scan for the exact installer error lines and tell you the single corrective action (for example: install a specific servicing stack update (SSU), use a specific DISM /RestoreHealth with a local image source, or proceed to in‑place repair). The file creation steps you ran are the correct ones; attach those files and I’ll parse them now.
Extra checks / safety commands you can run now (optional, quick)

• Check pending servicing file (if present):
  if (Test-Path C:\Windows\WinSxS\pending.xml) { Get-Content C:\Windows\WinSxS\pending.xml } else { "NO_PENDING_XML" }
• Confirm the Service Stack Update / recent packages installed (optional; I can parse output if you paste it):
  DISM /Online /Get-Packages | findstr /I "ServicingStack"

What I recommend you do next (pick one)

• If you’re comfortable: have me fetch the KB5070773 catalog link now (I’ll paste it), you download the .msu and run the exact wusa command above. If that fails, attach WindowsUpdate.log + dism_tail.txt and I’ll parse them and then we’ll do an in‑place upgrade. — OR —
• If you prefer to skip manual KB and move to the surefire repair: do the in‑place repair (mount ISO / run setup.exe and choose “Keep personal files and apps”). I’ll walk you step‑by‑step while you do it.

Which do you want right now?

• “Get the KB link” (I’ll fetch the Catalog entry and give the download filename + wusa command), or
• “Do in‑place repair” (I’ll give the step‑by‑step ISO / setup instructions and exactly what to select), or
• “Parse logs” (attach WindowsUpdate.txt and dism_tail.txt and I’ll read the exact failure lines and give one specific action).

Note: earlier guidance and commands I gave for collecting logs and for retrying Update are in the files I referenced — you followed those steps correctly. If you want me to fetch the catalog link now I already have your OS details (Windows 11 Pro Insider Preview Build 26200), so say “Get the KB link” and I’ll paste the download link and the one-line install command.

There are two .msu files available to download.
Which one?

Choose the KB5070773 .msu (the file name that contains "kb5070773") — that's the update you want. In your screenshot the second link is the correct one (the filename contains "kb5070773").
Exact steps (copy/paste; run in an elevated PowerShell / Command Prompt)
1) Download the KB5070773 .msu you clicked from the Microsoft Update Catalog into a folder, e.g. C:\Downloads.
2) Install it (run as Administrator). Replace <filename> with the real downloaded filename (including .msu):
wusa "C:\Downloads\<filename>.msu" /quiet /norestart
Notes:

• /quiet installs silently; /norestart prevents an immediate reboot so you can finish anything else first.
• After wusa finishes, reboot to complete the update:

Restart-Computer
3) Verify installation
After reboot, check Update history or run:
Get-HotFix | Where-Object { $_.HotFixID -eq 'KB5070773' }

or​

dism /online /get-packages | findstr /I "KB5070773"
If the KB is listed, installation succeeded.
4) If the manual install fails again — collect the diagnostic logs immediately and attach them (copy/paste these in an elevated PowerShell):

readable Windows Update log​

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

extract CBS SR lines and any occurrences of the error code​

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"

tail of DISM log​

Get-Content "$env:windir\Logs\DISM\dism.log" -Tail 200 | Out-File "$env:USERPROFILE\Desktop\dism_tail.txt"
Attach WindowsUpdate.log, CBS_SR.txt, CBS_0x800f0991.txt and dism_tail.txt and I’ll parse them and tell you the single next action.
5) If manual .msu still won’t install

• Next reliable option is an in‑place repair (Windows 11 Installation Assistant or ISO “Upgrade this PC now” → Keep personal files and apps). I can walk you through that step‑by‑step — it’s the most certain way to fix servicing/component store issues.

6) After a successful install + reboot

• Test the MX Master 3 in Windows. If the mouse still disconnects, pair it over Bluetooth and test for 30–60 minutes. If a drop occurs, run the two decisive captures (do NOT reboot) and attach them:

$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' -or $_.Message -match 'USB|usb|hub|reset|removed|disconnect|device|xhci|ehci' } | Select TimeCreated,ProviderName,Id,LevelDisplayName,Message | Out-File "$env:USERPROFILE\Desktop\USB_Events_Last60min.txt"
Attach those and I’ll parse immediately and give the one exact fix.
If you want, paste the exact filename of the KB5070773 .msu you downloaded and I’ll give you the precise wusa command line ready to paste.

Get the KB link

Good — you found the Catalog download dialog. Use the KB5070773 file (the one whose filename contains "kb5070773"). In your screenshot that is the second link — that’s the correct package for the out‑of‑band 2025‑10 release (26200.6901) for x64.
I’ll make this dead‑simple and safe — exact steps to download, install, and what to do if it still fails.
1) Catalog search page (one click)

• Open this Catalog search page and click the Download for the KB5070773 entry (choose the x64 package for build 26200.6901):
  
  http://[url]https://www.catalog.update.microsoft.com/Search.aspx?q=KB5070773

2) Which .msu to pick

• On the Download dialog choose the file whose name contains kb5070773 (not the kb5043… name). In your screenshot that is the second link. The file will be the KB5070773 x64 .msu.

3) Download location

• Save it to a short path you can type easily, for example:
  C:\Downloads\KB5070773.msu
  (or let your browser save to Downloads and note the exact filename).

4) Install the package (exact command — run as Administrator)

• Open an elevated PowerShell or Command Prompt and run this (replace the path/filename with the file you downloaded):

wusa "C:\Downloads\KB5070773.msu" /quiet /norestart

• Wait for the command to finish. It will install the package but will not force a reboot because of /norestart.

5) Reboot to complete the install

• After the installer finishes, reboot to finalize the update:

Restart-Computer
6) Verify the install

• After reboot, check Update history or run:

Get-HotFix | Where-Object { $_.HotFixID -eq 'KB5070773' }
or
dism /online /get-packages | findstr /I "KB5070773"
If it’s listed, the manual install succeeded.
7) If manual install fails again (what to do next)

• If wusa fails with an error, capture and attach these files (run these exact commands in Admin PowerShell) and paste them here or upload the files — I will parse and give the one next action:

Get-WindowsUpdateLog -LogPath "$env:USERPROFILE\Desktop\WindowsUpdate.log"
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"
Get-Content "$env:windir\Logs\DISM\dism.log" -Tail 200 | Out-File "$env:USERPROFILE\Desktop\dism_tail.txt"

• Attach WindowsUpdate.log, CBS_SR.txt, CBS_0x800f0991.txt, dism_tail.txt and I’ll parse the exact errors and tell you the single corrective step (for example: apply a specific servicing stack update, use a DISM source, or do an in‑place repair).

8) If manual install keeps failing (reliable fallback)

• Do an in‑place repair (Windows 11 Setup / “Upgrade this PC now” using an ISO or Installation Assistant) and choose “Keep personal files and apps.” This is the most reliable fix for stubborn servicing errors; I’ll guide you step‑by‑step if you want to do this (it requires a reboot and takes 30–60 minutes).

Would you like me to:

• (A) paste the exact one‑line wusa command ready for you to copy/paste after you confirm the downloaded filename, or
• (B) fetch the direct Catalog download link for the KB5070773 .msu you picked (I’ll paste it here so you can click it), or
• (C) proceed to the in‑place repair instructions now?

If you want (A) — paste the exact filename that your browser saved (from Downloads folder) and I’ll give the exact wusa command line ready to paste. If you want (B) say “Paste the Catalog link” and I’ll paste the direct catalog download URL for the file you should click.

PS C:\> wusa "c:\windows11.0-kb5043080-x64_953449672073f8fb99badb4cc6d5d7849b9c83e8.msu" /quiet /norestart
PS C:\>

How do I know when wusa has finished?

Good question — wusa can return you to the prompt before everything is obviously visible, so here are fast, reliable ways to tell whether the installer is still running and whether the update actually installed. Pick whichever is easiest.
1) Quick: check whether wusa is still running
Run this in an elevated PowerShell — if it returns nothing, the installer process has exited:
Get-Process -Name wusa -ErrorAction SilentlyContinue
If you prefer an automatic wait loop (it prints when finished):
while (Get-Process -Name wusa -ErrorAction SilentlyContinue) { Start-Sleep -Seconds 5 }
Write-Host "wusa finished"
2) Check whether the package is already installed (recommended)
Use DISM to list installed packages and search for the KB ID you expect (replace KB5070773 with the KB you wanted):
dism /Online /Get-Packages | findstr /I "KB5070773"
Or, since your filename shows KB5043080, check that too:
dism /Online /Get-Packages | findstr /I "KB5043080"
If the package is listed, the installer completed its job (a reboot may still be required to finish final steps).
3) Check Windows Update / HotFix listing
These can also show the installed KB:
Get-HotFix | Where-Object { $_.HotFixID -match 'KB5070773|KB5043080' }
Note: Get-HotFix doesn’t always list every cumulative update, so DISM is more reliable.
4) Check for pending reboot (if wusa used /norestart)
If the installer completed but hasn’t applied final steps, Windows may require a reboot. Check for a pending reboot entry:
Test-Path 'C:\Windows\WinSxS\pending.xml' ; # returns True if a pending XML exists
Or check the registry key (returns 0 if not present):
reg query "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\RebootRequired" /s
If you see a pending reboot, reboot to complete the install:
Restart-Computer
5) Check Windows Update log for install events (if you need details)
You already created WindowsUpdate.log; you can open it or search for the KB name:
Select-String -Path "$env:USERPROFILE\Desktop\WindowsUpdate.log" -Pattern "KB5070773","KB5043080","Install","error"
6) If you started wusa and it finished but the wrong KB was installed
I noticed you ran wusa with the file named kb5043080 (c:\windows11.0-kb5043080-.... If your goal was KB5070773 (the out‑of‑band Oct 2025 fix), check with DISM (step 2). If KB5070773 is not installed, download the correct KB5070773 .msu from the Microsoft Update Catalog and run wusa on that file (or I can fetch the exact catalog link for you).
7) If wusa appears to hang (rare)

• Look at the WindowsUpdate.log or check the Windows Modules Installer (TrustedInstaller) CPU activity in Task Manager; if it’s doing work then the install is still processing. If it hung for a very long time (30+ minutes with no disk/CPU IO from TrustedInstaller), you can stop it, collect logs, and retry manually.

Summary — the actionable short checklist you can run now

1. See if wusa is still running:
   Get-Process -Name wusa -ErrorAction SilentlyContinue
2. If not running, confirm the KB is installed:
   dism /Online /Get-Packages | findstr /I "KB5070773"
   dism /Online /Get-Packages | findstr /I "KB5043080"
3. If neither KB is listed, and wusa finished but nothing installed — download the correct KB5070773 .msu and run:
   wusa "C:\Downloads\<KB5070773_filename>.msu" /quiet /norestart
   (then Restart-Computer when you're ready)

If you’d like I can:

• Check for you which KB is installed now if you paste the output of the DISM command, or
• Fetch and paste the exact Microsoft Update Catalog link for KB5070773 so you can download and retry.

Which do you want me to do now — check whether the KB is installed (paste the DISM output), or get the KB5070773 catalog link for you to download?

PS C:\> wusa "c:\windows11.0-kb5043080-x64_953449672073f8fb99badb4cc6d5d7849b9c83e8.msu" /quiet /norestart
PS C:\> Get-Process -Name wusa -ErrorAction SilentlyContinue

Handles NPM(K) PM(K) WS(K) CPU(s) Id SI ProcessName
------- ------ ----- ----- ------ -- -- -----------
263 14 2680 16196 1.56 9664 3 wusa


PS C:\> while (Get-Process -Name wusa -ErrorAction SilentlyContinue) { Start-Sleep -Seconds 5 }
PS C:\> Write-Host "wusa finished"
wusa finished
PS C:\>
PS C:\>
PS C:\> dism /Online /Get-Packages | findstr /I "KB5070773"
PS C:\> dism /Online /Get-Packages | findstr /I "KB5043080"
PS C:\> Get-HotFix | Where-Object { $_.HotFixID -match 'KB5070773|KB5043080' }
PS C:\> Test-Path 'C:\Windows\WinSxS\pending.xml' ; # returns True if a pending XML exists
False
PS C:\> reg query "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\RebootRequired" /s
ERROR: The system was unable to find the specified registry key or value.
PS C:\>

Get the KB5070773 catalog link

PS C:\> wusa "windows11.0-kb5070773-x64_b235da912270f84b761402e9511000a4f500b4ac.msu" /quiet /norestart
PS C:\> Get-Process -Name wusa -ErrorAction SilentlyContinue

Handles NPM(K) PM(K) WS(K) CPU(s) Id SI ProcessName
------- ------ ----- ----- ------ -- -- -----------
225 11 4232 12784 3.66 608 3 wusa


PS C:\> Write-Host "wusa finished"
wusa finished
PS C:\> dism /Online /Get-Packages | findstr /I "KB5070773"
PS C:\> dism /Online /Get-Packages | findstr /I "KB5043080"
PS C:\> Get-HotFix | Where-Object { $_.HotFixID -match 'KB5070773|KB5043080' }
PS C:\> Test-Path 'C:\Windows\WinSxS\pending.xml' ; # returns True if a pending XML exists
False
PS C:\> reg query "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\RebootRequired" /s
ERROR: The system was unable to find the specified registry key or value.
PS C:\>

I don't understand when I executed:

PS C:\> Write-Host "wusa finished"

wusa finished

appeared instantly

PS C:\> Get-Process -Name wusa -ErrorAction SilentlyContinue

Handles NPM(K) PM(K) WS(K) CPU(s) Id SI ProcessName
------- ------ ----- ----- ------ -- -- -----------
237 14 3028 16808 9.52 608 3 wusa


PS C:\>

PS C:\WINDOWS\system32> Get-Process -Name wusa -ErrorAction SilentlyContinue

Handles NPM(K) PM(K) WS(K) CPU(s) Id SI ProcessName
------- ------ ----- ----- ------ -- -- -----------
239 14 3108 16936 9.52 608 3 wusa


PS C:\WINDOWS\system32> while (Get-Process -Name wusa -ErrorAction SilentlyContinue) { Start-Sleep -Seconds 5 }
>> Write-Host "wusa finished"

I think wusa is still running.

PS C:\WINDOWS\system32> while (Get-Process -Name wusa -ErrorAction SilentlyContinue) { Start-Sleep -Seconds 5 }
>> Write-Host "wusa finished"
wusa finished
PS C:\WINDOWS\system32> dism /Online /Get-Packages | findstr /I "KB5070773"
PS C:\WINDOWS\system32> dism /Online /Get-Packages | findstr /I "KB5043080"
PS C:\WINDOWS\system32> Get-HotFix | Where-Object { $_.HotFixID -match 'KB5070773|KB5043080' }
PS C:\WINDOWS\system32> Test-Path 'C:\Windows\WinSxS\pending.xml' ; # returns True if a pending XML exists
False
PS C:\WINDOWS\system32> reg query "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\RebootRequired" /s
ERROR: The system was unable to find the specified registry key or value.
PS C:\WINDOWS\system32>

wusa finished but nothing installed

I tried again but its not installed:

PS C:\WINDOWS\system32> Get-Process -Name wusa -ErrorAction SilentlyContinue

Handles NPM(K) PM(K) WS(K) CPU(s) Id SI ProcessName
------- ------ ----- ----- ------ -- -- -----------
239 14 2956 16692 9.22 21128 1 wusa


PS C:\WINDOWS\system32> Get-Process -Name wusa -ErrorAction SilentlyContinue
PS C:\WINDOWS\system32> Get-Process -Name wusa -ErrorAction SilentlyContinue
PS C:\WINDOWS\system32> dism /Online /Get-Packages | findstr /I "KB5070773"
PS C:\WINDOWS\system32> dism /Online /Get-Packages | findstr /I "KB5043080"
PS C:\WINDOWS\system32>

Also the WindowsUpdate.log hasn't been modified since 21:36