Logitech MX Master 3 losing connectivity

Draft RMA Message
I have some jobs to do for the next 1-2 hours
Leave the USB Monitor script running and see if there are any drop outs
Then we'll do the Bluetooth test
If no drops then I propose I use the Logi branded Unifying receiver temporarily until I purchase the Bolt gear on Black Friday.

I feel the temporary finishing line is in sight.

Below is a ready‑to‑copy RMA/support message you can paste into Logitech’s support form or email. I wrote it to be concise, factual, and to include the exact diagnostic evidence Logitech will want. I also list the files to attach and a short checklist of follow‑ups they may request.
Subject
Request for service/replacement — MX Master 3 (intermittent Unifying link failure)
Message
Hello Logitech Support,
I’m reporting an intermittent connectivity fault with my MX Master 3 (USB Unifying). I’ve performed systematic tests and captured logs; the fault consistently appears as the mouse channel failing while the Unifying receiver remains enumerated. Because this has required a mouse power‑cycle to recover and is reproducible, I’m requesting repair or replacement guidance.
Device details

• Product: MX Master 3
• Serial: 4082‑F0‑B8‑D2‑89
• Firmware: 019.001.00015 (reported by Logi Options+)
• Bootloader: BL.9500.013

Unifying receiver (original)

• Model: Unifying Receiver (046d:c52b)
• Serial: F19493C9
• Receiver firmware: 024.001.00023

Other devices mentioned

• Logitech K800 keyboard — ModelId 0x32010, FW 022.001.00019 — remained connected on the same receiver throughout tests.

Summary of problem

• Symptom: MX Master 3 intermittently stops responding over the Unifying link and sometimes only recovers after a mouse power‑cycle. When the issue occurs the Unifying receiver remains present to the OS; the receiver does not disappear from the USB bus.
• Observed behaviour: multiple short automatic reconnects were seen during Linux live (Slax) tests; later a permanent disconnect occurred that required power‑cycling the mouse to recover. The Unifying software logs show repeated “Device doesn’t respond” entries after pairing. Moving the receiver to a short passive USB‑2.0 extension (UGreen) in a rear motherboard USB2 port eliminated permanent disconnects in my tests (this suggests RF/placement or per‑device endpoint issues).
• Times/dates of notable events (local time): testing and logs captured on 22‑Oct‑2025; example log messages at ~12:08 and several “Device doesn’t respond” entries recorded (see attached logs).

What I tested

• Linux live (Slax) capture of kernel/lsusb and mouse input (tarball created).
• Windows testing with Logi Options+, unpair/re‑pair flows, and USB/System event captures.
• Moved receiver to a passive USB‑2.0 extension on a rear USB2 port (UGreen) — this stopped the permanent disconnects during subsequent testing.
• Paired both MX Master 3 and K800 using Unifying Utility and also tested spare receivers.

Why I believe the mouse (or its interaction) is faulty

• The receiver remains enumerated in lsusb / Device Manager while the mouse channel fails (per‑device resets rather than controller resets), and the Unifying logs show “Device doesn't respond” after pairing. These symptoms point to a per‑device radio/session problem rather than a motherboard USB controller failure.

What I want from Logitech

• Please advise whether this device is covered for repair or replacement. If out‑of‑warranty, please advise paid repair/repair options or a discount replacement program.
• If you require additional logs, I can attach or re‑capture specific files and timestamps. Please let me know which items you want first.

Attachments included
(Please confirm these files will upload correctly; I can re‑send any requested file.)

• Unifying System Report (from Unifying Software) — includes firmware and pairing events.
• Slax capture tarball (mouselinuxlogs_win_20251022_025516.tgz) — contains dmesg, lsusb before/after, and mouse event dump.
• USB_Monitor.log — continuous USB/System event log captured during one interval.
• MouseDeviceInfo.txt — Windows Get‑PnpDevice output showing devices present.
• USB_Events_Last60min.txt (or USB_Events_Last300min.txt) — Windows System events filtered for USB/hub/reset messages.
• Screenshots of Logi Options+ device pages showing firmware versions.

Contact & practical details

• Preferred contact email: [your email]
• I can provide the purchase receipt if required (this device is out of warranty, so I’m primarily seeking repair/paid options or replacement discounts).

Notes for support

• Important symptom to note: the K800 keyboard on the same receiver remained connected while the MX Master 3 channel required a power‑cycle. This difference is important diagnostic evidence (device‑specific channel failure).
• I can reproduce the issue and provide timestamps if needed; I can also re‑run captures live if you need a remote/real‑time diagnostic.

Thank you for your help — please let me know the next steps and what I should attach or re‑capture.
Best regards,
[Your name]
[Contact email / phone if required]
——
If you’d like, I’ll:

• Attach the above as plain text and format it for Logitech’s support form (they often have a web form with fields).
• Or I can shorten it to a 2–3 line summary for their chat/quick form and keep the rest as the log list. Which format would you prefer?

Also: I’ll keep the USB monitor running for the next few hours and we’ll do the Bluetooth test when you’re back, as planned. If the monitor captures a drop I’ll parse the logs immediately and advise the single next action.

Do both:

1. Attach the above as plain text and format it for Logitech’s support form
2. Shorten it to a 2–3 line summary for their chat/quick form

Done — I prepared both versions for you. You can copy‑paste these directly into Logitech’s support form and chat.
1) Full support form / email text (copy‑paste into the form’s “Description” or email body)
Subject: MX Master 3 intermittent Unifying link failure — request repair/replacement
Hello Logitech Support,
I’m reporting an intermittent connectivity fault with my MX Master 3 (Unifying). I’ve run systematic tests and collected logs; the behaviour consistently shows the mouse channel failing while the Unifying receiver remains enumerated. Because the mouse sometimes only recovers after a power‑cycle, I’m requesting repair/replacement guidance or paid repair options.
Device details

• Product: MX Master 3
• Serial: 4082‑F0‑B8‑D2‑89
• Firmware: 019.001.00015
• Bootloader: BL.9500.013

Unifying receiver (original)

• Model: Unifying Receiver (046d:c52b)
• Serial: F19493C9
• Receiver firmware: 024.001.00023

Summary of fault and tests

• Symptom: MX Master 3 intermittently stops responding over the Unifying link; recovery sometimes required a mouse power‑cycle. The Unifying receiver remained visible to the OS (did not disappear).
• Reproduced behaviour: transient auto‑reconnects during Linux live tests; one permanent Linux disconnect requiring power‑cycle. Unifying logs include repeated “Device doesn’t respond” entries after pairing.
• Mitigation tried: moving the receiver to a short passive USB‑2.0 extension (UGreen) into a rear motherboard USB2 port prevented permanent disconnects (strongly suggests RF/placement or per‑device endpoint issue). I also unpaired/re‑paired devices and tested with a spare Unifying receiver.

Files attached
(Please confirm you received these; I can re‑send if needed.)

• Unifying System Report (from Unifying Software) — includes firmware and pairing events.
• Slax capture tarball: mouselinuxlogs_win_20251022_025516.tgz — contains dmesg, lsusb before/after, and mouse event dump.
• USB_Monitor.log — USB/System event log captured during tests.
• MouseDeviceInfo.txt — Get‑PnpDevice output showing devices present.
• USB_Events_Last60min.txt (or USB_Events_Last300min.txt) — filtered Windows System events for USB/hub/reset messages.
• Screenshots of Logi Options+ showing firmware versions.

What I’m requesting

• Please advise whether repair or replacement is available (device is out of warranty). If OOW, please advise paid repair or replacement/discount options. If you need additional logs or a specific capture, tell me which files you want and I will provide them immediately.

Key diagnostic detail to note

• The K800 keyboard on the same Unifying receiver remained connected while the MX Master 3’s channel failed — the receiver stayed on the bus but the mouse endpoint stopped responding. (This suggests a per‑device radio/session failure rather than a motherboard USB controller crash.)

Contact & practical info

• Preferred contact: [your name] — [your email / phone]
• I can re‑run captures live or provide timestamps if you want remote diagnostics.

Thank you — please advise next steps.
Best regards,
[Your name]
2) Short 2–3 line summary for chat / quick form
MX Master 3 (SN 4082‑F0‑B8‑D2‑89, FW 019.001.00015) intermittently loses its Unifying link and sometimes only recovers after a mouse power‑cycle. The Unifying receiver (046d:c52b, SN F19493C9) remains enumerated; Unifying logs show repeated “Device doesn’t respond” entries. I’ve attached system/USB logs and a Slax capture; please advise repair/replacement or paid repair options (device is out of warranty).
Attachments to include (exact filenames to upload)

• Unifying_System_Report.txt (or whatever the Unifying app saved)
• mouselinuxlogs_win_20251022_025516.tgz
• USB_Monitor.log
• MouseDeviceInfo.txt
• USB_Events_Last60min.txt (or USB_Events_Last300min.txt)
• Screenshots (Logi Options+ firmware pages)

If you’d like I can also:

• Convert the long form above into a one‑line subject + bullet list tailored for Logitech’s web form fields (Product / Serial / Description / Attachments) — say “Format for web form” and I’ll do that.
• Or I can paste the shortened chat message again formatted with line breaks for their chat box.

Would you like the “web form field” version next (fields prefilled), or are these two ready to go?

Paste the shortened chat message again formatted with line breaks for their chat box

MX Master 3 (SN 4082‑F0‑B8‑D2‑89, FW 019.001.00015) intermittently loses its Unifying link and sometimes only recovers after a mouse power‑cycle.
The Unifying receiver (046d:c52b, SN F19493C9) remains enumerated while the mouse stops responding; Unifying logs show repeated “Device doesn’t respond” entries.
I’ve attached system/USB logs and a Slax capture — please advise repair/replacement or paid repair options (device is out of warranty).

There has been a permanent drop at around 19:00-19:01.
There were several temporary drops before then.

Sorry to hear the permanent drop happened — let’s capture the exact logs for the 19:00–19:01 window so I can be definitive (host/controller reset vs mouse/receiver radio/session). Do these steps now — they’re quick and will give me the decisive evidence.
Immediate (do this first)
1) If the mouse is still disconnected: power‑cycle the mouse (switch off → wait 5s → on) to restore control so you can run commands. Note the exact wall time if it drops again.
2) Capture the Windows logs for the 19:00–19:01 event (copy‑paste these exact commands into an elevated PowerShell — Run as Administrator). These create two small files on your Desktop that you can attach here.

Set a precise time window around the drop​

$start = Get-Date "2025-10-22 19:00:00"

Save current device list (shows whether receiver/device is still present)​

Get-PnpDevice -PresentOnly | Where-Object { $_.InstanceId -match 'VID_046D|VID_0A5C' } |
Format-List FriendlyName,InstanceId,Status | Out-File "$env:USERPROFILE\Desktop\MouseDeviceInfo_postdrop.txt"

Save System events (USB/hub/controller) for the drop window (+/− 5 minutes)​

Get-WinEvent -FilterHashtable @{LogName='System'; StartTime=$start; EndTime=($start).AddMinutes(5)} |
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_1900-1905.txt"
If the exact drop time is approximate and you want a wider window, use AddMinutes(-30) or run:
$start = (Get-Date).AddMinutes(-120) # last 2 hours
Get-WinEvent ... Out-File "$env:USERPROFILE\Desktop\USB_Events_Last120min.txt"
3) Stop the USB monitor (if still running) — one line (paste into elevated PowerShell):
Stop-Process -Id (Get-Content "$env:USERPROFILE\Desktop\usb_monitor.pid") -Force -ErrorAction SilentlyContinue; Remove-Item "$env:USERPROFILE\Desktop\usb_monitor.pid" -ErrorAction SilentlyContinue
4) Attach files (paperclip) to your next reply

• MouseDeviceInfo_postdrop.txt (from step 2)
• USB_Events_1900-1905.txt (or USB_Events_Last120min.txt if you used larger window)
• USB_Monitor.log (the background monitor log — if you left it running; attach the file even if small)

What I will do as soon as you attach them

• I will extract the exact event lines with timestamps that decide host vs device: any “usb … disconnect”, “reset high‑speed USB device”, xhci_hcd / ehci_hcd port resets (host/controller) or only per‑device retries / “device doesn’t respond” entries while the receiver stays present (device/radio/session). Then I’ll tell you one exact next action (update a specific driver/BIOS or replace the receiver/mouse). This is the same decisive test we’ve been using. (Earlier Unifying logs you shared already showed “Device doesn't respond” entries which pointed to a per‑device radio/session failure; these new Windows logs will confirm for the 19:00 event.)

While you run those captures (optional immediate mitigations)

• Keep the receiver on the UGreen passive USB‑2.0 extension in the rear USB2 port (leave it there while we test). That improved stability earlier and is the best temporary workaround.
• If you need immediate functionality and the mouse is dead on this PC, try the laptop Bolt/Bluetooth option you mentioned, or use the K800 + spare receiver as temporary keyboard.

If you prefer I can run the wider pull for you (last 5 hours)

• Tell me “capture last 5 hours” and I’ll give the one‑line StartTime value to paste instead of the 19:00 time so you don’t have to guess.

I’ll analyze the files the moment you attach them and give a single, actionable recommendation.

PS C:\WINDOWS\system32> $start = Get-Date "2025-10-22 19:00:00"
PS C:\WINDOWS\system32> Get-PnpDevice -PresentOnly | Where-Object { $_.InstanceId -match 'VID_046D|VID_0A5C' } |
>> Format-List FriendlyName,InstanceId,Status | Out-File "$env:USERPROFILE\Desktop\MouseDeviceInfo_postdrop.txt"
PS C:\WINDOWS\system32> Get-WinEvent -FilterHashtable @{LogName='System'; StartTime=$start; EndTime=($start).AddMinutes(5)} |
>> 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_1900-1905.txt"
Get-WinEvent : No events were found that match the specified selection criteria.
At line:1 char:1
+ Get-WinEvent -FilterHashtable @{LogName='System'; StartTime=$start; E ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: ) [Get-WinEvent], Exception
+ FullyQualifiedErrorId : NoMatchingEventsFound,Microsoft.PowerShell.Commands.GetWinEventCommand

PS C:\WINDOWS\system32> If the exact drop time is approximate and you want a wider window, use AddMinutes(-30) or run:
At line:1 char:3
+ If the exact drop time is approximate and you want a wider window, us ...
+ ~
Missing '(' after 'If' in if statement.
+ CategoryInfo : ParserError: ) [], ParentContainsErrorRecordException
+ FullyQualifiedErrorId : MissingOpenParenthesisInIfStatement

PS C:\WINDOWS\system32> $start = (Get-Date).AddMinutes(-120) # last 2 hours
PS C:\WINDOWS\system32> Get-WinEvent ... Out-File "$env:USERPROFILE\Desktop\USB_Events_Last120min.txt"
Get-WinEvent : A positional parameter cannot be found that accepts argument 'Out-File'.
At line:1 char:1
+ Get-WinEvent ... Out-File "$env:USERPROFILE\Desktop\USB_Events_Last12 ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidArgument: ) [Get-WinEvent], ParameterBindingException
+ FullyQualifiedErrorId : PositionalParameterNotFound,Microsoft.PowerShell.Commands.GetWinEventCommand

PS C:\WINDOWS\system32> 3) Stop the USB monitor (if still running) one line (paste into elevated PowerShell):
At line:1 char:2
+ 3) Stop the USB monitor (if still running) one line (paste into elev ...
+ ~
Unexpected token ')' in expression or statement.
+ CategoryInfo : ParserError: ) [], ParentContainsErrorRecordException
+ FullyQualifiedErrorId : UnexpectedToken

PS C:\WINDOWS\system32> Stop-Process -Id (Get-Content "$env:USERPROFILE\Desktop\usb_monitor.pid") -Force -ErrorAction SilentlyContinue; Remove-Item "$env:USERPROFILE\Desktop\usb_monitor.pid" -ErrorAction SilentlyContinue
PS C:\WINDOWS\system32>

Thanks — that output (Get-WinEvent returned nothing for the tight 19:00→19:05 window) is useful information. It simply means Windows didn’t record any System events that matched that exact filter/time window — not that nothing happened. We still need to collect a broader set of evidence for the 19:00–19:01 permanent drop so I can be definitive.
Two short points first

• Your Unifying report already showed “Device doesn’t respond” entries earlier — that strongly suggested a per‑device radio/session failure rather than a full USB controller crash. I’ll confirm whether that same pattern holds for the 19:00 drop.
• The Get-WinEvent call can return “No events” when the filter is too narrow (provider/message patterns didn’t match) or when the event types you need are in a different provider/channel. So we’ll run broader captures now.

Do this now (exact copy/paste — elevated PowerShell)
1) Capture a broad System window that covers the drop (wider window so we don’t miss it):
$start = Get-Date "2025-10-22 17:30:00" # change start if you want an earlier window
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_wide_1730-2000.txt"
2) Dump the current Logitech/Unifying device list (post‑drop device state):
Get-PnpDevice -PresentOnly | Where-Object { $_.InstanceId -match 'VID_046D|VID_0A5C' } | Format-List FriendlyName,InstanceId,Status | Out-File "$env:USERPROFILE\Desktop\MouseDeviceInfo_postdrop.txt"
3) Also save the last 500 System‑level events (raw) in case something odd is stored under other providers:
Get-WinEvent -MaxEvents 500 -LogName System | Select-Object TimeCreated, ProviderName, Id, LevelDisplayName, Message | Out-File "$env:USERPROFILE\Desktop\System_Last500.txt"
4) Stop the monitor (if still running) and attach the monitor log
Stop-Process -Id (Get-Content "$env:USERPROFILE\Desktop\usb_monitor.pid") -Force -ErrorAction SilentlyContinue
Remove-Item "$env:USERPROFILE\Desktop\usb_monitor.pid" -ErrorAction SilentlyContinue

Then attach the file:​

C:\Users\<you>\Desktop\USB_Monitor.log​

What I need you to attach here after running the above

• USB_Events_wide_1730-2000.txt
• MouseDeviceInfo_postdrop.txt
• System_Last500.txt
• USB_Monitor.log (if you left it running; attach it even if small)

Why these three are decisive

• If the System event file contains lines like “usb x‑y: USB disconnect”, “reset high‑speed USB device”, or xhci_hcd/ehci_hcd port reset at ~19:00 → that’s a host/controller reset and we’ll update a specific chipset/USB driver or BIOS (I’ll give the exact download and steps).
• If the Windows files show the receiver remains present (MouseDeviceInfo_postdrop will show Status: OK or not) and the System events only show per‑device retries or no hub/controller resets, that points to a device/radio/session failure (mouse ↔ receiver). In that case we’ll try the spare receiver, Bluetooth test, or (if tests indicate the mouse itself is faulty) replace the mouse. (Your earlier Unifying log already showed device‑doesn’t‑respond messages; these new Windows files will confirm the same pattern around 19:00.)

If the files are large or the event query finishes slowly

• It’s normal for the wide System scan to take a few seconds. If Get‑WinEvent returns a lot of data, attach the files rather than pasting into the chat.

If you prefer a single command that saves everything in one go (alternative)
Run this block (Admin PowerShell). It writes the same files and is a one‑shot capture for the last few hours:
$start = (Get-Date).AddHours(-6)
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 TimeCreated,ProviderName,Id,LevelDisplayName,Message | Out-File "$env:USERPROFILE\Desktop\USB_EventsLast6hrs.txt"
Get-PnpDevice -PresentOnly | Where-Object { $.InstanceId -match 'VID_046D|VID_0A5C' } | Format-List FriendlyName,InstanceId,Status | Out-File "$env:USERPROFILE\Desktop\MouseDeviceInfo_postdrop.txt"
Get-WinEvent -MaxEvents 500 -LogName System | Select TimeCreated,ProviderName,Id,LevelDisplayName,Message | Out-File "$env:USERPROFILE\Desktop\System_Last500.txt"
When you’ve attached the files

• I’ll extract the exact lines at ~19:00–19:01 and tell you the single next action (one command/one download or “swap receiver/test Bluetooth/replace mouse”) — no long lists, just the one thing to do next.

One small practical note while you run these

• If the mouse is currently disconnected and you need to run the commands: power‑cycle the mouse to restore input first (or run the commands from another machine remotely). Do not reboot until you’ve saved the Windows events — reboot clears them.

I’ll wait for the three files and will parse them immediately when you attach them.

PS C:\WINDOWS\system32> $start = Get-Date "2025-10-22 17:30:00"
PS C:\WINDOWS\system32> 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_wide_1730-2000.txt"
$.ProviderName : The term '$.ProviderName' 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:2 char:16
+ Where-Object { $.ProviderName -match 'Kernel-PnP|USBHUB3|USB|Microsof ...
+ ~~~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: ($.ProviderName:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

$.ProviderName : The term '$.ProviderName' 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:2 char:16
+ Where-Object { $.ProviderName -match 'Kernel-PnP|USBHUB3|USB|Microsof ...
+ ~~~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: ($.ProviderName:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

$.ProviderName : The term '$.ProviderName' 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:2 char:16
+ Where-Object { $.ProviderName -match 'Kernel-PnP|USBHUB3|USB|Microsof ...
+ ~~~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: ($.ProviderName:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

$.ProviderName : The term '$.ProviderName' 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:2 char:16
+ Where-Object { $.ProviderName -match 'Kernel-PnP|USBHUB3|USB|Microsof ...
+ ~~~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: ($.ProviderName:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

$.ProviderName : The term '$.ProviderName' 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:2 char:16
+ Where-Object { $.ProviderName -match 'Kernel-PnP|USBHUB3|USB|Microsof ...
+ ~~~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: ($.ProviderName:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

$.ProviderName : The term '$.ProviderName' 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:2 char:16
+ Where-Object { $.ProviderName -match 'Kernel-PnP|USBHUB3|USB|Microsof ...
+ ~~~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: ($.ProviderName:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

PS C:\WINDOWS\system32> Get-PnpDevice -PresentOnly | Where-Object { $_.InstanceId -match 'VID_046D|VID_0A5C' } | Format-List FriendlyName,InstanceId,Status | Out-File "$env:USERPROFILE\Desktop\MouseDeviceInfo_postdrop.txt"
PS C:\WINDOWS\system32> Get-WinEvent -MaxEvents 500 -LogName System | Select-Object TimeCreated, ProviderName, Id, LevelDisplayName, Message | Out-File "$env:USERPROFILE\Desktop\System_Last500.txt"
PS C:\WINDOWS\system32> Stop-Process -Id (Get-Content "$env:USERPROFILE\Desktop\usb_monitor.pid") -Force -ErrorAction SilentlyContinue
>> Remove-Item "$env:USERPROFILE\Desktop\usb_monitor.pid" -ErrorAction SilentlyContinue
Get-Content : Cannot find path 'C:\Users\rupes\Desktop\usb_monitor.pid' because it does not exist.
At line:1 char:19
+ ... rocess -Id (Get-Content "$env:USERPROFILE\Desktop\usb_monitor.pid") - ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (C:\Users\rupes\Desktop\usb_monitor.pid:String) [Get-Content], ItemNotFoundException
+ FullyQualifiedErrorId : PathNotFound,Microsoft.PowerShell.Commands.GetContentCommand

Stop-Process : Cannot bind argument to parameter 'Id' because it is null.
At line:1 char:18
+ ... Process -Id (Get-Content "$env:USERPROFILE\Desktop\usb_monitor.pid") ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidData: ) [Stop-Process], ParameterBindingValidationException
+ FullyQualifiedErrorId : ParameterArgumentValidationErrorNullNotAllowed,Microsoft.PowerShell.Commands.StopProcessCommand

PS C:\WINDOWS\system32>

USB_Events_wide_1730-2000.txt is empty so didn't upload.

I'm in a livechat session with Logitech. They told me to check if there are any outstanding Windows Updates.

When I checked it said:

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

I found this article referring to this KB:

Thanks — good catch. KB5070773 is the out‑of‑band October 2025 update that fixes USB keyboard/mouse problems in the Windows Recovery Environment (WinRE). The install error 0x800f0991 means Windows Update failed to apply the package (commonly caused by a corrupted component store, missing payloads for certain SKUs, or other update component problems). I’ll give a short explanation, then an ordered set of practical troubleshooting steps you can try now (each step includes the exact commands to paste in an elevated prompt). I’ll also point out the logs to capture if a step still fails so I can help interpret the cause.
Short background

• KB5070773 was released as an out‑of‑band fix for Windows 11 24H2/25H2 to repair WinRE USB keyboard/mouse issues. Windows Update may download it automatically, but some systems report install errors (0x800f0991) when the update processing or component store is inconsistent.

What to try now — ordered, with exact commands
Run each step in order and test Windows Update (Check for updates) after the step that follows “Quick checks” and the cleanup steps.
A — Quick checks (do first)

• Reboot (if not just rebooted) and ensure you have 20–30 GB free on C:. Pending restarts can block installs.
• Temporarily disable any third‑party antivirus/security software and any disk encryption UI that might interfere.
• Make sure system has internet and the date/time are correct.

B — Run the Windows Update Troubleshooter (built‑in)

1. Settings → System → Troubleshoot → Other troubleshooters → Windows Update → Run.
   OR run in elevated PowerShell:
   msdt.exe /id WindowsUpdateDiagnostic

C — Clear Windows Update temporary files and reset update services
Open an elevated Command Prompt (Run as Administrator) and run these commands copy/paste as a block:
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 that, try Windows Update → Check for updates again.
D — Repair component store; run SFC and DISM
If resetting Update didn’t help, run System File Checker and DISM to repair corruption:
Run in elevated Command Prompt or PowerShell:
sfc /scannow
Wait until it finishes. Then run DISM:
DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth
If /RestoreHealth fails because it cannot obtain files, you can provide a local source (Windows ISO mounted as drive D: — replace D: with your letter):
DISM /Online /Cleanup-Image /RestoreHealth /Source:wim:\sources\install.wim:1 /LimitAccess
E — Manually download & install KB5070773 (if Windows Update still fails)

1. Go to the Microsoft Update Catalog and download the appropriate package for your exact OS build/edition (x64, 24H2/25H2). Then run the .msu or .cab installer as Administrator. (If you want I can find the Catalog entry for KB5070773 for you.)
2. If it’s an .msu, run:
   wusa "C:\Path\to\windows10.0-kb5070773-x64.msu" /quiet /norestart
3. If it’s a .cab, use DISM to add:
   DISM /Online /Add-Package /PackagePath:"C:\Path\to\KB5070773.cab"

F — If install still fails — capture logs to diagnose (attach them here)
If you hit the error again after trying the steps above, gather these files and attach them or paste relevant excerpts:
1) Windows Update log:

• In an elevated PowerShell:
  Get-WindowsUpdateLog -LogPath "$env:USERPROFILE\Desktop\WindowsUpdate.log"
  Attach WindowsUpdate.log.

2) CBS log (component store errors):

• Attach (or search for the recent errors and paste lines) from:
  C:\Windows\Logs\CBS\CBS.log
  You can extract error lines with:
  findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log > "%userprofile%\Desktop\CBS_SR.txt"
  findstr /i "error 0x800f0991" "%windir%\Logs\CBS\CBS.log" > "%userprofile%\Desktop\CBS_0x800f0991.txt"

3) The failure code + update history

• Settings → Windows Update → Update history screenshot or copy error code details.

G — Optional targeted fixes (if N edition or media features required)

• If you run an “N” edition of Windows, certain updates fail because Media Feature Pack is missing. Check your edition:
  systeminfo | findstr /B /C:"OS Name" /C:"OS Version"
  If N edition, install the Media Feature Pack for your exact build from Microsoft and retry. (0x800f0991 is often seen on N builds with missing media components.)

H — If none of that works — options

• Try manual install in Safe Mode with Networking (sometimes helps if a driver is blocking).
• As last resort, you can use the Windows 11 Installation Assistant / in-place upgrade repair (keeps files/apps), which will bring your system up to date and often resolves component store issues. Make sure to backup first.

What to tell Logitech in chat (if they ask)

• Mention you’re troubleshooting a Windows Update install error 0x800f0991 for KB5070773 — and that you will provide the WindowsUpdate and CBS logs if they still need more details. They asked you to check updates — that’s exactly right.

Caveats & safety

• If you run DISM with a local source, make sure the install.wim (or install.esd) matches the installed Windows edition and build. Using a mismatched image can fail.
• When using wusa/DISM installers, reboot when prompted. If a manual install succeeds but Windows Update still shows error, reboot and re-check update history.

If you want, I can:

• Walk you through each command interactively (I can paste exact commands to run and explain what to expect), or
• Fetch the Microsoft Update Catalog entry for KB5070773 and give the direct download links for the appropriate package (I’ll need to know whether your OS is Windows 11 25H2 or 24H2 and whether it’s x64 and whether it’s an “N” SKU).

Which do you want next?

• (A) I can walk you step‑by‑step through SFC/DISM and resetting Update components now; or
• (B) I can fetch the direct Microsoft Update Catalog download links for KB5070773 for your exact SKU so you can try a manual install.

Say which and I’ll proceed with the exact next commands/links.

I cannot reboot as it will disconnect the livechat session with Logitech.

What did you parse from the two files uploaded in #290 ?

Understood — don’t reboot while you’re in the Logitech live chat. Below are safe, exact commands you can run now (they do not require a reboot) to try to repair the Windows Update problem and to collect the logs Logitech or I’ll need. Run each command in an elevated PowerShell or elevated Command Prompt (right‑click → Run as administrator). After each block I say what to expect and what to paste back if you want me to read it.
Important: run these one block at a time and wait for each to finish.
1) Run the Windows Update troubleshooter (safe, no reboot)

• Opens the built‑in troubleshooter; follow the prompts (it may report fixes or say nothing).
  msdt.exe /id WindowsUpdateDiagnostic

2) Run System File Checker (SFC) — scans system files (no reboot required immediately)
sfc /scannow

• Wait for it to finish. If it reports “found corrupt files and repaired them” that’s useful. Paste the summary line here.

3) Check component store health with DISM (no reboot required)
DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth

• If ScanHealth reports corruption, run RestoreHealth (also does not force an immediate reboot):
  DISM /Online /Cleanup-Image /RestoreHealth
• Note: /RestoreHealth may download replacement files from Windows Update; it can take some minutes.

4) Reset Windows Update temporary files & services (stops services but does not require a reboot)
Open elevated Command Prompt and run this whole block (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

• This clears Update cache and restarts the services. After this, try Check for updates in Settings again (no reboot yet).

5) If Windows Update still shows the same error and you want the package now (manual download) — note this usually requires a reboot after install

• I can fetch the direct Microsoft Update Catalog link for KB5070773 that matches your Windows build/edition and give you the safe .msu/.cab to download; installing might require a reboot, so hold off until the chat ends if you must keep the session.

6) Collect the diagnostic logs (do this now and attach them to chat or paste here)
A) Create a readable Windows Update log:
Get-WindowsUpdateLog -LogPath "$env:USERPROFILE\Desktop\WindowsUpdate.log"

• Attach the resulting WindowsUpdate.log from your Desktop.

B) Extract recent CBS (component store) errors — creates a small file with only error lines:
findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log > "%USERPROFILE%\Desktop\CBS_SR.txt"
findstr /i "error 0x800f0991" "%windir%\Logs\CBS\CBS.log" > "%USERPROFILE%\Desktop\CBS_0x800f0991.txt"

• Attach CBS_SR.txt and CBS_0x800f0991.txt (they will be small if present).

C) Save Windows Update history error as screenshot or text — or copy the error code and include it (you already have 0x800f0991).
7) If you want to retry Update check (safe)

• After steps 2–4, check for updates:
  Start-Process ms-settings:windowsupdate

8) If all else fails and you must not reboot now

• If the manual install or DISM /RestoreHealth requires a restart to finish, postpone that reboot until your livechat ends. In that case attach the logs above and I’ll advise the single next step to run after you finish the chat.

What I’ll do after you paste the outputs or attach the logs

• I’ll read the WindowsUpdate.log and the CBS extracts and tell you:
  • if the component store is corrupted and /RestoreHealth needs a specific source, or
  • whether the error code is due to an SKU mismatch (e.g., N edition needing Media Feature Pack), or
  • recommend the single next action (manual .msu install link or in‑place repair) — short and exact.

If you want me to fetch the KB5070773 download links for your exact Windows SKU now, tell me:

• whether your PC is Windows 11 25H2 (you said 25H2 earlier) and
• whether your Windows SKU is “N” (Media Feature Pack missing) or standard (run this and paste the output):
  systeminfo | findstr /B /C:"OS Name" /C:"OS Version" /C:"System Type"

Which would you like next:
A) I walk you through SFC, DISM and Reset steps now (I’ll wait while you run them), or
B) I grab the Microsoft Update Catalog link for KB5070773 for your SKU so you can download it (but you’ll likely need to install and reboot when chat ends)?
Tell me which and I’ll give the exact next commands / links.

Its installing the update itself now without my intervention.

Short answer — what I parsed from those two files (MouseDeviceInfo and the Windows event extract) and what it means

• MouseDeviceInfo: Windows still sees the Logitech Unifying receiver and all the Logitech HID interfaces (the receiver and the mouse HID endpoints are listed and each shows Status: OK). This proves the dongle stayed enumerated on the USB bus.
• Windows System events (the filtered event extract you supplied): there are no hub/controller reset messages (no “usb … disconnect”, no “reset high‑speed USB device”, no xhci_hcd/ehci_hcd port‑reset entries) in that event extract around the times you reported. In short — Windows did not record a controller‑level USB reset.

My conclusion from those two facts

• This pattern (receiver still present + no controller/hub reset entries) points to a device‑side radio/session failure — i.e., the mouse’s Unifying channel stopped responding (or its endpoint flaked) while the receiver itself remained connected. That matches the “Device doesn’t respond” entries in the Unifying report and also matches your Slax captures. In plain language: the mouse ↔ receiver link dropped, not the PC’s USB controller.

Why that matters (one sentence)

• If it’s device/radio/session, replacing the receiver or using the UGreen extension (better placement/orientation) or using Bluetooth often fixes it; if it were a host/controller reset we’d instead update a chipset/USB driver or BIOS.

Immediate recommended next step (one action)

• Keep the spare Unifying receiver on the passive UGreen USB‑2.0 extension in a rear USB2 port (leave it there). That’s the highest‑ROI temporary fix — you already saw it stop permanent disconnects and it’s the right next thing to live‑test for 24–48 hours.

If the mouse drops again (what I need to be definitive)

• Run these two commands immediately (elevated PowerShell) and attach the two files they create. I’ll parse them and give the one exact remediation (driver/BIOS update vs replace hardware):

$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-Object TimeCreated,ProviderName,Id,LevelDisplayName,Message | Out-File "$env:USERPROFILE\Desktop\USB_Events_Last60min.txt"
What I can do next for you

• If you want, I’ll: (A) parse those two files the moment you attach them and give one exact remediation; or (B) help you run the Bluetooth and cross‑host tests you planned and interpret the results. Which do you want to do next?

Good — that’s promising. KB5070773 was the out‑of‑band patch Microsoft released specifically to fix USB keyboard/mouse failures in the Windows Recovery Environment (WinRE). Let the update finish installing and then follow the short checklist below — I’ll explain what to expect and exactly what to capture if the mouse still drops after the install and reboot.
Short summary of what KB5070773 does

• KB5070773 is Microsoft’s out‑of‑band cumulative that restores USB input in WinRE on affected Windows 11 24H2 / 25H2 builds. It’s delivered via Windows Update or the Microsoft Update Catalog and usually requires a reboot to complete.

What to do right now (while the update is installing / while you’re in the Logitech chat)
1) Let the update finish installing — do not interrupt it. The installer may download additional servicing pieces (SSU) automatically. That’s normal.
2) Do NOT reboot while you are mid‑chat with Logitech if that would disconnect support. Wait until the livechat ends, unless Logitech tells you they need you to reboot now. (If a forced reboot is required, save any work first.)
After the update has completed and the livechat ends (the safe order)
A — Reboot to finish installation

• Reboot once the installation is complete to allow the out‑of‑band package to finalize (this is required for the WinRE fix to take effect). KB5070773 typically needs a reboot to apply.

B — Quick checks after reboot

• Check Update history → confirm KB5070773 is listed (or check the OS build; the OOB builds are 26100.6901 for 24H2 and 26200.6901 for 25H2).
• Test the mouse in normal Windows use (move/click/scroll). If the device still disconnects, continue below.

If the mouse still shows disconnects after reboot (exact, decisive captures)
Do these immediately (do NOT reboot first). Run these in an elevated PowerShell (Run as Administrator) and attach the two small files it creates to the chat here — I’ll parse them and give the single next action.
1) Save current Logitech/Unifying device list:
$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"
2) Save filtered System events around the last hour:
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 (MouseDeviceInfo.txt and USB_Events_Last60min.txt) and I’ll extract the exact lines that tell us whether Windows reset the USB host/controller or only the mouse endpoint was failing.
Interpretation guide (what I’ll look for)

• Host/controller reset: you’ll see messages like “usb … disconnect”, “reset high‑speed USB device”, or xhci_hcd / EHCI hub reset entries at the drop time. That points to a port/controller problem and the fix will be to update one specific chipset/USB driver or BIOS (I’ll give the exact download + steps).
• Device/session failure: receiver stays present in MouseDeviceInfo.txt but the Unifying logs or system events show per‑device retries / “device doesn’t respond”. That points to a mouse↔receiver (radio or pairing) issue — we’ll try swapping the receiver, testing Bluetooth, or replace the faulty unit. (Your earlier Unifying log already showed “Device doesn’t respond” entries; that’s consistent with device/radio problems rather than WinRE issues.)

If Windows Update failed (error 0x800f0991) while installing

• Error 0x800f0991 can occur if the component store is inconsistent or payloads are missing; if the update failed and you want to pursue it while still in the chat, I can walk you through safe non‑reboot repair steps (SFC /scannow, DISM /RestoreHealth, resetting SoftwareDistribution) that do not require a reboot. If you prefer I can wait until the chat ends to do any steps requiring a restart.

Practical temporary plan while you wait for Black Friday (if KB5070773 doesn’t immediately fix everything)

• Keep using the spare Unifying receiver on the UGreen passive USB2 extension (your best interim fix).
• If the mouse remains flaky after the update and reboot, do the Bluetooth test (pair the MX to the Bluetooth dongle) and cross‑host test (try the same spare receiver + UGreen on another PC). Those isolates quickly indicate whether the mouse or receiver is at fault. I’ll interpret logs you attach from the decisive captures above and tell you the single next action (swap receiver, update a specific driver/BIOS, or replace the mouse).

If you like, I will:

• Wait while the update completes, or
• Walk you step‑by‑step through the non‑reboot repair steps (SFC/DISM/Update reset) now if the installer fails with an error (you said it’s installing now so probably not needed), or
• Parse the two Windows files immediately after you attach them if the drop recurs post‑reboot.

Tell me which you want right now:

• “Wait” — I’ll stand by while the install completes, or
• “Repair now” — I’ll walk you through the safe, non‑reboot repair steps so you can keep the Logitech livechat open.

Either way, great progress — KB5070773 is the correct update for WinRE USB issues, and we’ll confirm whether it also ends the MX Master disconnects after the reboot.