Logitech MX Master 3 losing connectivity

[Distorted Vision]

I am running Windows 11.

The PC is assigned to 1 of 3 in the Easy-Switch. When it loses connectivity the '1' light is no longer lit. Issue is only resolved by powering off the mouse and powering back on.

I have tried:

Charging the mouse overnight
Moved the Logitech Unifying Receiver to different USB ports
Checked for new firmware and updates for Logi Options+

 

[Distorted Vision]

PS C:\WINDOWS\system32> powercfg -setacvalueindex 381b4222-f694-41f0-9685-ff5bb260df2e 2a737441-1930-4402-8d77-b2bebba308a3 48e6b7a6-50f5-4782-a5d4-53bb8f07e226 0
PS C:\WINDOWS\system32> powercfg -setdcvalueindex 381b4222-f694-41f0-9685-ff5bb260df2e 2a737441-1930-4402-8d77-b2bebba308a3 48e6b7a6-50f5-4782-a5d4-53bb8f07e226 0
PS C:\WINDOWS\system32> powercfg -S 381b4222-f694-41f0-9685-ff5bb260df2e
PS C:\WINDOWS\system32> powercfg -q 381b4222-f694-41f0-9685-ff5bb260df2e | findstr /i "48e6b7a6"
Power Setting GUID: 48e6b7a6-50f5-4782-a5d4-53bb8f07e226 (USB selective suspend setting)
PS C:\WINDOWS\system32> powercfg -q 381b4222-f694-41f0-9685-ff5bb260df2e
Power Scheme GUID: 381b4222-f694-41f0-9685-ff5bb260df2e (Balanced)
GUID Alias: SCHEME_BALANCED
Subgroup GUID: 0012ee47-9041-4b5d-9b77-535fba8b1442 (Hard disk)
GUID Alias: SUB_DISK
Power Setting GUID: 6738e2c4-e8a5-4a42-b16a-e040e769756e (Turn off hard disk after)
GUID Alias: DISKIDLE
Minimum Possible Setting: 0x00000000
Maximum Possible Setting: 0xffffffff
Possible Settings increment: 0x00000001
Possible Settings units: Seconds
Current AC Power Setting Index: 0x000004b0
Current DC Power Setting Index: 0x00000258

Subgroup GUID: 02f815b5-a5cf-4c84-bf20-649d1f75d3d8 (Internet Explorer)
Power Setting GUID: 4c793e7d-a264-42e1-87d3-7a0d2f523ccd (JavaScript Timer Frequency)
Possible Setting Index: 000
Possible Setting Friendly Name: Maximum Power Savings
Possible Setting Index: 001
Possible Setting Friendly Name: Maximum Performance
Current AC Power Setting Index: 0x00000001
Current DC Power Setting Index: 0x00000000

Subgroup GUID: 0d7dbae2-4294-402a-ba8e-26777e8488cd (Desktop background settings)
Power Setting GUID: 309dce9b-bef4-4119-9921-a851fb12f0f4 (Slide show)
Possible Setting Index: 000
Possible Setting Friendly Name: Available
Possible Setting Index: 001
Possible Setting Friendly Name: Paused
Current AC Power Setting Index: 0x00000000
Current DC Power Setting Index: 0x00000001

Subgroup GUID: 19cbb8fa-5279-450e-9fac-8a3d5fedd0c1 (Wireless Adapter Settings)
Power Setting GUID: 12bbebe6-58d6-4636-95bb-3217ef867c1a (Power Saving Mode)
Possible Setting Index: 000
Possible Setting Friendly Name: Maximum Performance
Possible Setting Index: 001
Possible Setting Friendly Name: Low Power Saving
Possible Setting Index: 002
Possible Setting Friendly Name: Medium Power Saving
Possible Setting Index: 003
Possible Setting Friendly Name: Maximum Power Saving
Current AC Power Setting Index: 0x00000000
Current DC Power Setting Index: 0x00000002

Subgroup GUID: 238c9fa8-0aad-41ed-83f4-97be242c8f20 (Sleep)
GUID Alias: SUB_SLEEP
Power Setting GUID: 29f6c1db-86da-48c5-9fdb-f2b67b1f44da (Sleep after)
GUID Alias: STANDBYIDLE
Minimum Possible Setting: 0x00000000
Maximum Possible Setting: 0xffffffff
Possible Settings increment: 0x00000001
Possible Settings units: Seconds
Current AC Power Setting Index: 0x00000000
Current DC Power Setting Index: 0x00000258

Power Setting GUID: 94ac6d29-73ce-41a6-809f-6363ba21b47e (Allow hybrid sleep)
GUID Alias: HYBRIDSLEEP
Possible Setting Index: 000
Possible Setting Friendly Name: Off
Possible Setting Index: 001
Possible Setting Friendly Name: On
Current AC Power Setting Index: 0x00000001
Current DC Power Setting Index: 0x00000001

Power Setting GUID: 9d7815a6-7ee4-497e-8888-515a05f02364 (Hibernate after)
GUID Alias: HIBERNATEIDLE
Minimum Possible Setting: 0x00000000
Maximum Possible Setting: 0xffffffff
Possible Settings increment: 0x00000001
Possible Settings units: Seconds
Current AC Power Setting Index: 0x00000000
Current DC Power Setting Index: 0x00000000

Power Setting GUID: bd3b718a-0680-4d9d-8ab2-e1d2b4ac806d (Allow wake timers)
GUID Alias: RTCWAKE
Possible Setting Index: 000
Possible Setting Friendly Name: Disable
Possible Setting Index: 001
Possible Setting Friendly Name: Enable
Possible Setting Index: 002
Possible Setting Friendly Name: Important Wake Timers Only
Current AC Power Setting Index: 0x00000001
Current DC Power Setting Index: 0x00000001

Subgroup GUID: 2a737441-1930-4402-8d77-b2bebba308a3 (USB settings)
Power Setting GUID: 48e6b7a6-50f5-4782-a5d4-53bb8f07e226 (USB selective suspend setting)
Possible Setting Index: 000
Possible Setting Friendly Name: Disabled
Possible Setting Index: 001
Possible Setting Friendly Name: Enabled
Current AC Power Setting Index: 0x00000000
Current DC Power Setting Index: 0x00000000

Subgroup GUID: 4f971e89-eebd-4455-a8de-9e59040e7347 (Power buttons and lid)
GUID Alias: SUB_BUTTONS
Power Setting GUID: a7066653-8d6c-40a8-910e-a1f54b84c7e5 (Start menu power button)
GUID Alias: UIBUTTON_ACTION
Possible Setting Index: 000
Possible Setting Friendly Name: Sleep
Possible Setting Index: 001
Possible Setting Friendly Name: Hibernate
Possible Setting Index: 002
Possible Setting Friendly Name: Shut down
Current AC Power Setting Index: 0x00000000
Current DC Power Setting Index: 0x00000000

Subgroup GUID: 501a4d13-42af-4429-9fd1-a8218c268e20 (PCI Express)
GUID Alias: SUB_PCIEXPRESS
Power Setting GUID: ee12f906-d277-404b-b6da-e5fa1a576df5 (Link State Power Management)
GUID Alias: ASPM
Possible Setting Index: 000
Possible Setting Friendly Name: Off
Possible Setting Index: 001
Possible Setting Friendly Name: Moderate power savings
Possible Setting Index: 002
Possible Setting Friendly Name: Maximum power savings
Current AC Power Setting Index: 0x00000000
Current DC Power Setting Index: 0x00000002

Subgroup GUID: 54533251-82be-4824-96c1-47b60b740d00 (Processor power management)
GUID Alias: SUB_PROCESSOR
Power Setting GUID: 893dee8e-2bef-41e0-89c6-b55d0929964c (Minimum processor state)
GUID Alias: PROCTHROTTLEMIN
Minimum Possible Setting: 0x00000000
Maximum Possible Setting: 0x00000064
Possible Settings increment: 0x00000001
Possible Settings units: %
Current AC Power Setting Index: 0x00000005
Current DC Power Setting Index: 0x00000005

Power Setting GUID: bc5038f7-23e0-4960-96da-33abaf5935ec (Maximum processor state)
GUID Alias: PROCTHROTTLEMAX
Minimum Possible Setting: 0x00000000
Maximum Possible Setting: 0x00000064
Possible Settings increment: 0x00000001
Possible Settings units: %
Current AC Power Setting Index: 0x00000064
Current DC Power Setting Index: 0x00000064

Subgroup GUID: 7516b95f-f776-4464-8c53-06167f40cc99 (Display)
GUID Alias: SUB_VIDEO
Power Setting GUID: 3c0bc021-c8a8-4e07-a973-6b14cbcb2b7e (Turn off display after)
GUID Alias: VIDEOIDLE
Minimum Possible Setting: 0x00000000
Maximum Possible Setting: 0xffffffff
Possible Settings increment: 0x00000001
Possible Settings units: Seconds
Current AC Power Setting Index: 0x00000000
Current DC Power Setting Index: 0x000000b4

Power Setting GUID: aded5e82-b909-4619-9949-f5d71dac0bcb (Display brightness)
GUID Alias: VIDEONORMALLEVEL
Minimum Possible Setting: 0x00000000
Maximum Possible Setting: 0x00000064
Possible Settings increment: 0x00000001
Possible Settings units: %
Current AC Power Setting Index: 0x0000004b
Current DC Power Setting Index: 0x0000004b

Power Setting GUID: f1fbfde2-a960-4165-9f88-50667911ce96 (Dimmed display brightness)
Minimum Possible Setting: 0x00000000
Maximum Possible Setting: 0x00000064
Possible Settings increment: 0x00000001
Possible Settings units: %
Current AC Power Setting Index: 0x00000032
Current DC Power Setting Index: 0x00000032

Power Setting GUID: fbd9aa66-9553-4097-ba44-ed6e9d65eab8 (Enable adaptive brightness)
GUID Alias: ADAPTBRIGHT
Possible Setting Index: 000
Possible Setting Friendly Name: Off
Possible Setting Index: 001
Possible Setting Friendly Name: On
Current AC Power Setting Index: 0x00000000
Current DC Power Setting Index: 0x00000000

Subgroup GUID: 9596fb26-9850-41fd-ac3e-f7c3c00afd4b (Multimedia settings)
Power Setting GUID: 03680956-93bc-4294-bba6-4e0f09bb717f (When sharing media)
Possible Setting Index: 000
Possible Setting Friendly Name: Allow the computer to sleep
Possible Setting Index: 001
Possible Setting Friendly Name: Prevent idling to sleep
Possible Setting Index: 002
Possible Setting Friendly Name: Allow the computer to enter Away Mode
Current AC Power Setting Index: 0x00000001
Current DC Power Setting Index: 0x00000000

Power Setting GUID: 10778347-1370-4ee0-8bbd-33bdacaade49 (Video playback quality bias)
Possible Setting Index: 000
Possible Setting Friendly Name: Video playback power-saving bias
Possible Setting Index: 001
Possible Setting Friendly Name: Video playback performance bias
Current AC Power Setting Index: 0x00000001
Current DC Power Setting Index: 0x00000000

Power Setting GUID: 34c7b99f-9a6d-4b3c-8dc7-b6693b78cef4 (When playing video)
Possible Setting Index: 000
Possible Setting Friendly Name: Optimize video quality
Possible Setting Index: 001
Possible Setting Friendly Name: Balanced
Possible Setting Index: 002
Possible Setting Friendly Name: Optimize power savings
Current AC Power Setting Index: 0x00000000
Current DC Power Setting Index: 0x00000001

Subgroup GUID: e73a048d-bf27-4f12-9731-8b2076e8891f (Battery)
GUID Alias: SUB_BATTERY
Power Setting GUID: 5dbb7c9f-38e9-40d2-9749-4f8a0e9f640f (Critical battery notification)
GUID Alias: BATFLAGSCRIT
Possible Setting Index: 000
Possible Setting Friendly Name: Off
Possible Setting Index: 001
Possible Setting Friendly Name: On
Current AC Power Setting Index: 0x00000001
Current DC Power Setting Index: 0x00000001

Power Setting GUID: 637ea02f-bbcb-4015-8e2c-a1c7b9c0b546 (Critical battery action)
GUID Alias: BATACTIONCRIT
Possible Setting Index: 000
Possible Setting Friendly Name: Do nothing
Possible Setting Index: 001
Possible Setting Friendly Name: Sleep
Possible Setting Index: 002
Possible Setting Friendly Name: Hibernate
Possible Setting Index: 003
Possible Setting Friendly Name: Shut down
Current AC Power Setting Index: 0x00000002
Current DC Power Setting Index: 0x00000002

Power Setting GUID: 8183ba9a-e910-48da-8769-14ae6dc1170a (Low battery level)
GUID Alias: BATLEVELLOW
Minimum Possible Setting: 0x00000000
Maximum Possible Setting: 0x00000064
Possible Settings increment: 0x00000001
Possible Settings units: %
Current AC Power Setting Index: 0x0000000a
Current DC Power Setting Index: 0x0000000a

Power Setting GUID: 9a66d8d7-4ff7-4ef9-b5a2-5a326ca2a469 (Critical battery level)
GUID Alias: BATLEVELCRIT
Minimum Possible Setting: 0x00000000
Maximum Possible Setting: 0x00000064
Possible Settings increment: 0x00000001
Possible Settings units: %
Current AC Power Setting Index: 0x00000005
Current DC Power Setting Index: 0x00000005

Power Setting GUID: bcded951-187b-4d05-bccc-f7e51960c258 (Low battery notification)
GUID Alias: BATFLAGSLOW
Possible Setting Index: 000
Possible Setting Friendly Name: Off
Possible Setting Index: 001
Possible Setting Friendly Name: On
Current AC Power Setting Index: 0x00000001
Current DC Power Setting Index: 0x00000001

Power Setting GUID: d8742dcb-3e6a-4b3c-b3fe-374623cdcf06 (Low battery action)
GUID Alias: BATACTIONLOW
Possible Setting Index: 000
Possible Setting Friendly Name: Do nothing
Possible Setting Index: 001
Possible Setting Friendly Name: Sleep
Possible Setting Index: 002
Possible Setting Friendly Name: Hibernate
Possible Setting Index: 003
Possible Setting Friendly Name: Shut down
Current AC Power Setting Index: 0x00000000
Current DC Power Setting Index: 0x00000000

Power Setting GUID: f3c5027d-cd16-4930-aa6b-90db844a8f00 (Reserve battery level)
Minimum Possible Setting: 0x00000000
Maximum Possible Setting: 0x00000064
Possible Settings increment: 0x00000001
Possible Settings units: %
Current AC Power Setting Index: 0x00000007
Current DC Power Setting Index: 0x00000007

PS C:\WINDOWS\system32>

 

[ChatGPT]

Thanks — good work so far. You’ve successfully changed the USB selective suspend setting (verify showed Current AC/DC = 0). That rules out Windows power plan suspending the USB port. Next we focus on the remaining host/RF causes and capture the diagnostic logs if the mouse drops again.
Short summary of state

• Mouse + receiver were stable on another PC for 1 hour → mouse/receiver hardware & firmware very likely OK.
• You reproduced drops on your main PC → problem is host/USB/hub/placement or local RF environment at that PC.
• USB selective suspend is now disabled for your active power scheme (so power plan suspension is not the cause).

What to do next (priority order)
1) Confirm Device Manager power settings (manual)

• Open Device Manager → View → Show hidden devices.
• Under Universal Serial Bus controllers: for each USB Root Hub / Generic USB Hub → Properties → Power Management → uncheck “Allow the computer to turn off this device to save power.”
• Under Human Interface Devices and Mice and other pointing devices: find Logitech/Unifying HID entries → Properties → Power Management → uncheck same box.
• Reboot.

2) Use a desk extension for the Unifying receiver (practical fix)

• Order a passive USB 2.0 A‑male → A‑female extension (1–1.5 m is fine). Use “USB 2.0” and “passive/shielded” in the listing — do NOT buy an “active repeater” unless you need >5m.
• Plug the extension into a rear motherboard USB2 port and place the receiver on the desk ~20–50 cm from the mouse (not next to the metal mouse mat). This is the most likely permanent fix.

3) Avoid USB3 hubs or noisy hubs for the receiver

• Don’t put the Unifying receiver into the Anker USB3 hub or into a hub that has high‑speed/active devices on it. Put it on a rear port (or extension to a rear port).

4) Update host drivers / BIOS

• Download and install the latest chipset/USB drivers from your motherboard vendor and update the system BIOS/UEFI to the latest stable version. Reboot and test.

5) If the mouse drops again — capture logs immediately
Right after the next drop (do not reboot), run these exact commands in an elevated PowerShell (copy/paste). They capture device state and relevant System events for the last 10 minutes:
Run as Administrator — copy/paste these three lines:
$start=(Get-Date).AddMinutes(-10)
Get-PnpDevice -PresentOnly | Where-Object { $_.InstanceId -match 'VID_046D|VID0A5C' } | Format-List FriendlyName,InstanceId,Status
Get-WinEvent -FilterHashtable @{LogName='System'; StartTime=$start} | Where-Object { $.Message -match 'USB|usb|Kernel-PnP|USBHUB|UsbHub|Usb' } | Select-Object TimeCreated, ProviderName, Id, LevelDisplayName, Message | Format-List

• Paste the full output here. I’ll look specifically for Kernel‑PnP/USB messages showing “device removed”, “port reset”, “controller reset”, or any VID/PID referenced (e.g. VID_046D&PID_C52B). Those lines tell us whether Windows reset the port or the mouse radio session died.

If you prefer files (so you can attach them), run this script (Admin PowerShell) immediately after the drop — it writes three text files to your Desktop:
$start=(Get-Date).AddMinutes(-10)
Get-PnpDevice -PresentOnly | Where-Object { $_.InstanceId -match 'VID_046D|VID_0A5C' } | Format-List FriendlyName,InstanceId,Status | Out-File "$env:USERPROFILE\Desktop\Mouse_Device_Info.txt"
Get-PnpDevice -PresentOnly -Class USB | Format-List FriendlyName,InstanceId,Status | Out-File "$env:USERPROFILE\Desktop\All_USBDevices.txt"
Get-WinEvent -FilterHashtable @{LogName='System'; StartTime=$start} | Where-Object { $.Message -match 'USB|usb|Kernel-PnP|USBHUB|UsbHub|Usb' } | Select TimeCreated, ProviderName, Id, LevelDisplayName, Message | Out-File "$env:USERPROFILE\Desktop\USB_Events_Last10min.txt"
Attach those files here or paste their contents.
6) Short troubleshooting you can do now

• Temporarily unpair the K800 keyboard from the same receiver (or move keyboard to another receiver) for a few hours to rule out multi‑device interactions.
• Try Bluetooth channel for the mouse as a fallback while you test.

When to consider RMA

• If the mouse + receiver fail on another PC consistently (not the case so far), then RMA the problematic unit (mouse or receiver depending which fails on the other PC).
• If the capture logs show no host USB resets and only a radio/session drop for the mouse (and the keyboard is unaffected), Logitech support will likely request RMA (since the mouse is dropping its radio channel).

If you want I can:

• Give a one‑click command to capture logs (I provided the script above).
• Walk you through updating chipset drivers/BIOS for your motherboard if you paste the motherboard model.
• Recommend specific passive USB 2.0 extension cables (1–1.5 m) to order.

Next step for you now
1) Do the Device Manager power management checks and reboot.
2) If you can, order a passive USB 2.0 extension (1–1.5 m) and plan to test with the receiver on that extension.
3) If a drop occurs again, run the log capture commands above and paste the output here — I’ll parse it and tell you exactly whether to update BIOS/drivers, move to a different root hub, or RMA.
Tell me which of the three follow‑ups you want help with: Device Manager steps, finding the right extension cable, or capturing/parsing the event logs.

 

[Distorted Vision]

You requested in post #18:

• Also double‑check these Device Manager power options:
  • Device Manager → View → Devices by connection (or View → Show hidden devices) → Under Universal Serial Bus controllers, open each USB Root Hub / Generic USB Hub → Power Management → uncheck “Allow the computer to turn off this device to save power”.
  • Under Human Interface Devices and Mice and other pointing devices, find Logitech/Unifying entries → Power Management → uncheck the same

There are no Universal Serial Bus controllers in this view:

Only in View → Devices by type

 

[ChatGPT]

Thanks — that screenshot helps. You were right: the USB controllers are not visible at the top level in the "Devices by connection" tree until you expand the correct parent nodes. Here's exactly how to find them and change the power‑management setting, plus a PowerShell alternative if you prefer command line.
A. Using Device Manager (recommended)

1. Open Device Manager (Win + X → Device Manager).
2. In Device Manager choose View → Devices by connection.
3. Expand the top node (your computer name). Then expand these nodes in order until you see the USB controllers:
   • ACPI x64‑based PC (or similar)
   • Microsoft Device Association Root Enumerator / PCI bus entries / Host Controller entries
   • Look for entries named like "Intel USB 3.0 eXtensible Host Controller", "USB Root Hub (USB 3.0)", "Generic USB Hub", "USB Root Hub (USB 2.0)".
     Tip: The controllers are often under a PCI Express Root or under a motherboard chipset node — keep expanding child nodes until you find "Universal Serial Bus controllers" items.
4. When you find a "USB Root Hub" or "Generic USB Hub" entry:
   • Right‑click → Properties → Power Management tab.
   • Uncheck "Allow the computer to turn off this device to save power".
   • Click OK.
5. Repeat for every USB Root Hub / Generic USB Hub you see.
6. Now expand "Human Interface Devices" (and "Mice and other pointing devices") in the main Device Manager (View → Devices by type) and for any Logitech / HID entries:
   • Right‑click → Properties → Power Management → uncheck "Allow the computer to turn off this device to save power".
7. Reboot the PC.

If you don't see the Power Management tab for a particular entry that’s normal for some drivers — just do the hub/root entries and the HID/mouse entries that do show it.
B. Quick PowerShell listing (to confirm what you have)
Run an elevated PowerShell (Run as Administrator) and paste the output here if you want me to point to the exact item to expand:
Get-PnpDevice -PresentOnly | Where-Object { $.Class -match 'USB|HID' -or $.FriendlyName -match 'Root Hub|Hub|USB' } | Format-Table -AutoSize FriendlyName,InstanceId,Class,Status
This will list the USB/HID devices present and their InstanceId so you can match them in Device Manager (Device Details → Instance Path).
C. If you still can't find the root hubs

• Paste the output of the PowerShell command above and I’ll mark exactly which entry to expand and which Properties dialog to open.
• Or attach a screenshot of Device Manager with "Devices by connection" fully expanded to the bottom (I can point to the exact node).

D. Next steps after changing settings

• Reboot, put the Unifying receiver back where you normally use it (or on the rear port), and test.
• If you still see drops, run the event‑capture commands I posted earlier right after the next drop and paste the output.

If you want I can give a one‑line command to open Device Manager to the USB controllers, or walk you step‑by‑step while you expand the tree — tell me which you prefer.

 

[Distorted Vision]

I checked every Generic USB Hub entry and in Power Management. Allow the computer to turn off this device to save power is unchecked in all of them.

 

[ChatGPT]

Thanks — good work checking the USB hub power‑management settings. Since those are already unchecked, we can rule out Windows turning off the hubs as the cause. Next steps are focused on isolating host vs RF and collecting logs if the mouse drops again.
Short plan (pick one to do next)

• Quick practical fix: order a passive USB 2.0 extension (1–1.5 m) and put the Unifying receiver on the desk plugged into that extension (rear motherboard port → extension → receiver). This often fixes these symptoms permanently.
• Host/drivers fix: update your motherboard chipset/USB drivers and BIOS. (I can walk you through this if you post the exact motherboard model; I noticed Gigabyte Z68AP‑D3 in your screenshot — confirm that if you want guidance.
• Capture logs: if the mouse drops again, run the small script below (Admin PowerShell) immediately afterwards and attach the generated text files. I’ll parse them and tell you the exact next action.

Why I recommend those:

• Receiver proximity/USB3 interference is the most common cause (desk extension is the usual, simple fix).
• If the problem is host side, chipset/USB driver or BIOS updates often fix intermittent resets.
• If neither solves it, the logs will show whether Windows performed a USB/hub reset (host issue) or the mouse simply lost its radio session (device/firmware issue → RMA).

Exact script to run immediately after the next drop

• Run PowerShell as Administrator and copy/paste the block below exactly. It writes three text files to your Desktop that you can attach here.

$start = (Get-Date).AddMinutes(-10)
Get-PnpDevice -PresentOnly | Where-Object { $_.InstanceId -match 'VID_046D|VID_0A5C' } | Format-List FriendlyName,InstanceId,Status | Out-File "$env:USERPROFILE\Desktop\Mouse_Device_Info.txt"
Get-PnpDevice -PresentOnly -Class USB | Format-List FriendlyName,InstanceId,Status | Out-File "$env:USERPROFILE\Desktop\All_USBDevices.txt"
Get-WinEvent -FilterHashtable @{LogName='System'; StartTime=$start} | Where-Object { $.Message -match 'USB|usb|Kernel-PnP|USBHUB|UsbHub|Usb' } | Select-Object TimeCreated, ProviderName, Id, LevelDisplayName, Message | Out-File "$env:USERPROFILE\Desktop\USB_Events_Last10min.txt"
Notes:

• Run that as soon as you see the drop (do not reboot). The files will be on your Desktop.
• If you prefer not to create files, you can instead run these two quick commands (Admin PowerShell) and paste their output here:
  Get-PnpDevice -PresentOnly | Where-Object { $_.InstanceId -match 'VID_046D|VID0A5C' } | Format-List FriendlyName,InstanceId,Status
  $start=(Get-Date).AddMinutes(-10); Get-WinEvent -FilterHashtable @{LogName='System'; StartTime=$start} | Where-Object { $.Message -match 'USB|usb|Kernel-PnP|USBHUB|UsbHub|Usb' } | Select TimeCreated, ProviderName, Id, LevelDisplayName, Message | Format-List

Other quick diagnostics to run now or while you wait for the extension:

• Temporarily unpair the K800 from the same receiver (or move it to another receiver) and use the mouse alone for several hours. If the mouse becomes stable, that suggests multi‑device interaction on the receiver.
• Try Bluetooth channel for the mouse as a temporary workaround and to see if connectivity is stable via BT.
• If you want me to check drivers/BIOS, confirm your motherboard model (I saw “Gigabyte Z68AP‑D3” in your screenshot — is that the correct board?. If yes, I’ll give exact download links and step‑by‑step.

What I need from you after the next drop

• Attach the three Desktop files the script creates (Mouse_Device_Info.txt, All_USB_Devices.txt, USB_Events_Last10min.txt) or paste the outputs from the two quick commands above.
• Tell me which USB port/hub the receiver was using when the drop occurred (rear motherboard, front panel, Belkin hub, Anker hub).

If you want, I can:

• Recommend a few passive USB 2.0 extension cables to order.
• Walk you through updating chipset/USB drivers and BIOS for your Gigabyte board.
• Parse the logs the moment you paste them.

Which of these should we do next — order the extension, update drivers/BIOS (I can guide), or wait and capture logs on the next drop?

 

[Distorted Vision]

I had a disconnect and ran the script with all the Powershell commands but there were errors:

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> cd \
PS C:\> .\Mouse.ps1


FriendlyName : HID-compliant system controller
InstanceId : HID\VID_046D&PID_C548&MI_01&COL03\9&2741F85C&0&0002
Status : OK

FriendlyName : USB Input Device
InstanceId : USB\VID_0A5C&PID_4502\8&80E368A&0&1
Status : OK

FriendlyName : HID-compliant vendor-defined device
InstanceId : HID\VID_046D&PID_C52B&MI_02&COL01\8&2038E687&0&0000
Status : OK

FriendlyName : HID-compliant mouse
InstanceId : HID\VID_0A5C&PID_4503&COL01\9&2D1D4BEB&0&0000
Status : OK

FriendlyName : HID-compliant device
InstanceId : HID\VID_046D&PID_C548&MI_01&COL04\9&2741F85C&0&0003
Status : OK

FriendlyName : Logitech USB Input Device
InstanceId : USB\VID_046D&PID_C548&MI_00\8&11508CCC&0&0000
Status : OK

FriendlyName : Logitech USB Input Device
InstanceId : USB\VID_046D&PID_C52B&MI_00\7&2FFDA91A&0&0000
Status : OK

FriendlyName : USB Composite Device
InstanceId : USB\VID_046D&PID_C548\7&203B8509&0&3
Status : OK

FriendlyName : Generic USB Hub
InstanceId : USB\VID_0A5C&PID_4500\7&2E45F226&0&5
Status : OK

FriendlyName : USB Input Device
InstanceId : USB\VID_0A5C&PID_4503\8&80E368A&0&2
Status : OK

FriendlyName : HID-compliant vendor-defined device
InstanceId : HID\VID_046D&PID_C52B&MI_02&COL02\8&2038E687&0&0001
Status : OK

FriendlyName : HID Keyboard Device
InstanceId : HID\VID_046D&PID_C52B&MI_00\8&20E309E7&0&0000
Status : OK

FriendlyName : HID-compliant consumer control device
InstanceId : HID\VID_0A5C&PID_4503&COL02\9&2D1D4BEB&0&0001
Status : OK

FriendlyName : USB Input Device
InstanceId : USB\VID_046D&PID_C548&MI_01\8&11508CCC&0&0001
Status : OK

FriendlyName : USB Input Device
InstanceId : USB\VID_046D&PID_C52B&MI_01\7&2FFDA91A&0&0001
Status : OK

FriendlyName : HID-compliant touch pad
InstanceId : HID\VID_046D&PID_C548&MI_03\9&19D9F812&0&0000
Status : OK

FriendlyName : HID-compliant vendor-defined device
InstanceId : HID\VID_046D&PID_C52B&MI_02&COL03\8&2038E687&0&0002
Status : OK

FriendlyName : HID-compliant mouse
InstanceId : HID\VID_046D&PID_C548&MI_01&COL01\9&2741F85C&0&0000
Status : OK

FriendlyName : HID Keyboard Device
InstanceId : HID\VID_046D&PID_C548&MI_00\9&36ABA9A&0&0000
Status : OK

FriendlyName : USB Input Device
InstanceId : USB\VID_046D&PID_C548&MI_02\8&11508CCC&0&0002
Status : OK

FriendlyName : USB Input Device
InstanceId : USB\VID_046D&PID_C52B&MI_02\7&2FFDA91A&0&0002
Status : OK

FriendlyName : HID-compliant consumer control device
InstanceId : HID\VID_046D&PID_C548&MI_01&COL02\9&2741F85C&0&0001
Status : OK

FriendlyName : HID-compliant vendor-defined device
InstanceId : HID\VID_046D&PID_C548&MI_02&COL02\9&2166BCD&0&0001
Status : OK

FriendlyName : HID-compliant vendor-defined device
InstanceId : HID\VID_046D&PID_C548&MI_02&COL01\9&2166BCD&0&0000
Status : OK

FriendlyName : HID-compliant vendor-defined device
InstanceId : HID\VID_046D&PID_C52B&MI_01&COL04\8&8755A42&0&0003
Status : OK

FriendlyName : USB Input Device
InstanceId : USB\VID_046D&PID_C548&MI_03\8&11508CCC&0&0003
Status : OK

FriendlyName : HID-compliant system controller
InstanceId : HID\VID_046D&PID_C52B&MI_01&COL03\8&8755A42&0&0002
Status : OK

FriendlyName : USB Composite Device
InstanceId : USB\VID_046D&PID_C52B\6&3AE11B61&0&3
Status : OK

FriendlyName : HID-compliant consumer control device
InstanceId : HID\VID_046D&PID_C52B&MI_01&COL02\8&8755A42&0&0001
Status : OK

FriendlyName : HID-compliant mouse
InstanceId : HID\VID_046D&PID_C52B&MI_01&COL01\8&8755A42&0&0000
Status : OK





FriendlyName : Generic USB Hub
InstanceId : USB\VID_8087&PID_0024\5&2CF571C4&0&1
Status : OK

FriendlyName : VIA Rev 5 or later USB Universal Host Controller
InstanceId : PCI\VEN_1106&DEV_3038&SUBSYS_30381106&REV_61\5&25DA5584&0&0000E3
Status : OK

FriendlyName : Intel(R) 6 Series/C200 Series Chipset Family USB Enhanced Host Controller - 1C2D
InstanceId : PCI\VEN_8086&DEV_1C2D&SUBSYS_50061458&REV_05\3&13C0B0C5&0&D0
Status : OK

FriendlyName : Generic USB Hub
InstanceId : USB\VID_2109&PID_2812\7&203B8509&0&4
Status : OK

FriendlyName : Etron USB 3.0 eXtensible Host Controller - 1.0 (Microsoft)
InstanceId : PCI\VEN_1B6F&DEV_7023&SUBSYS_50071458&REV_01\4&36E9BF94&0&00E1
Status : OK

FriendlyName : VIA USB Enhanced Host Controller
InstanceId : PCI\VEN_1106&DEV_3104&SUBSYS_31041106&REV_63\5&25DA5584&0&0200E3
Status : OK

FriendlyName : DYMO LabelWriter 5XL
InstanceId : USB\VID_0922&PID_002A\06131032883000
Status : OK

FriendlyName : USB Composite Device
InstanceId : USB\VID_046D&PID_C548\7&203B8509&0&3
Status : OK

FriendlyName : Generic USB Hub
InstanceId : USB\VID_0A5C&PID_4500\7&2E45F226&0&5
Status : OK

FriendlyName : Intel(R) 6 Series/C200 Series Chipset Family USB Enhanced Host Controller - 1C26
InstanceId : PCI\VEN_8086&DEV_1C26&SUBSYS_50061458&REV_05\3&13C0B0C5&0&E8
Status : OK

FriendlyName : DYMO LabelWriter 450 Twin Turbo
InstanceId : USB\VID_0922&PID_0022\12052518413680
Status : OK

FriendlyName : Generic USB Hub
InstanceId : USB\VID_050D&PID_0237\6&3AE11B61&0&4
Status : OK

FriendlyName : USB Root Hub
InstanceId : USB\ROOT_HUB\6&B6CB339&0
Status : OK

FriendlyName : USB Root Hub
InstanceId : USB\ROOT_HUB20\4&2F7D0B00&0
Status : OK

FriendlyName : VIA Rev 5 or later USB Universal Host Controller
InstanceId : PCI\VEN_1106&DEV_3038&SUBSYS_30381106&REV_61\5&25DA5584&0&0100E3
Status : OK

FriendlyName : USB Root Hub
InstanceId : USB\ROOT_HUB20\4&34898846&0
Status : OK

FriendlyName : USB Mass Storage Device
InstanceId : USB\VID_1058&PID_2621\575831324133355034385254
Status : OK

FriendlyName : USB Composite Device
InstanceId : USB\VID_0922&PID_1002\22430731072014
Status : OK

FriendlyName : USB Root Hub
InstanceId : USB\ROOT_HUB\6&2850901C&0
Status : OK

FriendlyName : USB Mass Storage Device
InstanceId : USB\VID_0922&PID_1002&MI_01\7&EAC329A&0&0001
Status : OK

FriendlyName : DYMO LabelManager PnP
InstanceId : USB\VID_0922&PID_1002&MI_00\7&EAC329A&0&0000
Status : OK

FriendlyName : DAEMON Tools Lite Virtual USB Bus
InstanceId : ROOT\USB\0000
Status : OK

FriendlyName : USB Root Hub
InstanceId : USB\ROOT_HUB20\6&12393495&0
Status : OK

FriendlyName : Generic USB Hub
InstanceId : USB\VID_8087&PID_0024\5&90E832B&0&1
Status : OK

FriendlyName : Generic USB Hub
InstanceId : USB\VID_2109&PID_2812\6&3AE11B61&0&5
Status : OK

FriendlyName : USB Composite Device
InstanceId : USB\VID_046D&PID_C52B\6&3AE11B61&0&3
Status : OK

FriendlyName : USB Root Hub (USB 3.0)
InstanceId : USB\ROOT_HUB30\5&99F7FE2&0&0
Status : OK





FriendlyName : Generic USB Hub
InstanceId : USB\VID_8087&PID_0024\5&2CF571C4&0&1
Status : OK

FriendlyName : VIA Rev 5 or later USB Universal Host Controller
InstanceId : PCI\VEN_1106&DEV_3038&SUBSYS_30381106&REV_61\5&25DA5584&0&0000E3
Status : OK

FriendlyName : Intel(R) 6 Series/C200 Series Chipset Family USB Enhanced Host Controller - 1C2D
InstanceId : PCI\VEN_8086&DEV_1C2D&SUBSYS_50061458&REV_05\3&13C0B0C5&0&D0
Status : OK

FriendlyName : Generic USB Hub
InstanceId : USB\VID_2109&PID_2812\7&203B8509&0&4
Status : OK

FriendlyName : Etron USB 3.0 eXtensible Host Controller - 1.0 (Microsoft)
InstanceId : PCI\VEN_1B6F&DEV_7023&SUBSYS_50071458&REV_01\4&36E9BF94&0&00E1
Status : OK

FriendlyName : VIA USB Enhanced Host Controller
InstanceId : PCI\VEN_1106&DEV_3104&SUBSYS_31041106&REV_63\5&25DA5584&0&0200E3
Status : OK

FriendlyName : DYMO LabelWriter 5XL
InstanceId : USB\VID_0922&PID_002A\06131032883000
Status : OK

FriendlyName : USB Composite Device
InstanceId : USB\VID_046D&PID_C548\7&203B8509&0&3
Status : OK

FriendlyName : Generic USB Hub
InstanceId : USB\VID_0A5C&PID_4500\7&2E45F226&0&5
Status : OK

FriendlyName : Intel(R) 6 Series/C200 Series Chipset Family USB Enhanced Host Controller - 1C26
InstanceId : PCI\VEN_8086&DEV_1C26&SUBSYS_50061458&REV_05\3&13C0B0C5&0&E8
Status : OK

FriendlyName : DYMO LabelWriter 450 Twin Turbo
InstanceId : USB\VID_0922&PID_0022\12052518413680
Status : OK

FriendlyName : Generic USB Hub
InstanceId : USB\VID_050D&PID_0237\6&3AE11B61&0&4
Status : OK

FriendlyName : USB Root Hub
InstanceId : USB\ROOT_HUB\6&B6CB339&0
Status : OK

FriendlyName : USB Root Hub
InstanceId : USB\ROOT_HUB20\4&2F7D0B00&0
Status : OK

FriendlyName : VIA Rev 5 or later USB Universal Host Controller
InstanceId : PCI\VEN_1106&DEV_3038&SUBSYS_30381106&REV_61\5&25DA5584&0&0100E3
Status : OK

FriendlyName : USB Root Hub
InstanceId : USB\ROOT_HUB20\4&34898846&0
Status : OK

FriendlyName : USB Mass Storage Device
InstanceId : USB\VID_1058&PID_2621\575831324133355034385254
Status : OK

FriendlyName : USB Composite Device
InstanceId : USB\VID_0922&PID_1002\22430731072014
Status : OK

FriendlyName : USB Root Hub
InstanceId : USB\ROOT_HUB\6&2850901C&0
Status : OK

FriendlyName : USB Mass Storage Device
InstanceId : USB\VID_0922&PID_1002&MI_01\7&EAC329A&0&0001
Status : OK

FriendlyName : DYMO LabelManager PnP
InstanceId : USB\VID_0922&PID_1002&MI_00\7&EAC329A&0&0000
Status : OK

FriendlyName : DAEMON Tools Lite Virtual USB Bus
InstanceId : ROOT\USB\0000
Status : OK

FriendlyName : USB Root Hub
InstanceId : USB\ROOT_HUB20\6&12393495&0
Status : OK

FriendlyName : Generic USB Hub
InstanceId : USB\VID_8087&PID_0024\5&90E832B&0&1
Status : OK

FriendlyName : Generic USB Hub
InstanceId : USB\VID_2109&PID_2812\6&3AE11B61&0&5
Status : OK

FriendlyName : USB Composite Device
InstanceId : USB\VID_046D&PID_C52B\6&3AE11B61&0&3
Status : OK

FriendlyName : USB Root Hub (USB 3.0)
InstanceId : USB\ROOT_HUB30\5&99F7FE2&0&0
Status : OK



Get-WinEvent : A null value was encountered in the StartTime hash table key. Null values are not permitted.
At C:\Mouse.ps1:4 char:1
+ Get-WinEvent -FilterHashtable @{LogName='System'; StartTime=$start} |
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidArgument: (StartTime:String) [Get-WinEvent], Exception
+ FullyQualifiedErrorId : NullNotAllowedInHashtable,Microsoft.PowerShell.Commands.GetWinEventCommand

$.Message : The term '$.Message' 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 C:\Mouse.ps1:11 char:86
+ ... ogName='System'; StartTime=$start} | Where-Object { $.Message -match ...
+ ~~~~~~~~~
+ CategoryInfo : ObjectNotFound: ($.Message:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

$.Message : The term '$.Message' 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 C:\Mouse.ps1:11 char:86
+ ... ogName='System'; StartTime=$start} | Where-Object { $.Message -match ...
+ ~~~~~~~~~
+ CategoryInfo : ObjectNotFound: ($.Message:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

$.Message : The term '$.Message' 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 C:\Mouse.ps1:11 char:86
+ ... ogName='System'; StartTime=$start} | Where-Object { $.Message -match ...
+ ~~~~~~~~~
+ CategoryInfo : ObjectNotFound: ($.Message:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

$.Message : The term '$.Message' 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 C:\Mouse.ps1:11 char:86
+ ... ogName='System'; StartTime=$start} | Where-Object { $.Message -match ...
+ ~~~~~~~~~
+ CategoryInfo : ObjectNotFound: ($.Message:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

$.Message : The term '$.Message' 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 C:\Mouse.ps1:11 char:86
+ ... ogName='System'; StartTime=$start} | Where-Object { $.Message -match ...
+ ~~~~~~~~~
+ CategoryInfo : ObjectNotFound: ($.Message:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

$.Message : The term '$.Message' 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 C:\Mouse.ps1:11 char:86
+ ... ogName='System'; StartTime=$start} | Where-Object { $.Message -match ...
+ ~~~~~~~~~
+ CategoryInfo : ObjectNotFound: ($.Message:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

$.Message : The term '$.Message' 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 C:\Mouse.ps1:11 char:86
+ ... ogName='System'; StartTime=$start} | Where-Object { $.Message -match ...
+ ~~~~~~~~~
+ CategoryInfo : ObjectNotFound: ($.Message:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

$.Message : The term '$.Message' 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 C:\Mouse.ps1:11 char:86
+ ... ogName='System'; StartTime=$start} | Where-Object { $.Message -match ...
+ ~~~~~~~~~
+ CategoryInfo : ObjectNotFound: ($.Message:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

$.Message : The term '$.Message' 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 C:\Mouse.ps1:11 char:86
+ ... ogName='System'; StartTime=$start} | Where-Object { $.Message -match ...
+ ~~~~~~~~~
+ CategoryInfo : ObjectNotFound: ($.Message:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

$.Message : The term '$.Message' 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 C:\Mouse.ps1:11 char:86
+ ... ogName='System'; StartTime=$start} | Where-Object { $.Message -match ...
+ ~~~~~~~~~
+ CategoryInfo : ObjectNotFound: ($.Message:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

$.Message : The term '$.Message' 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 C:\Mouse.ps1:11 char:86
+ ... ogName='System'; StartTime=$start} | Where-Object { $.Message -match ...
+ ~~~~~~~~~
+ CategoryInfo : ObjectNotFound: ($.Message:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

$.Message : The term '$.Message' 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 C:\Mouse.ps1:11 char:86
+ ... ogName='System'; StartTime=$start} | Where-Object { $.Message -match ...
+ ~~~~~~~~~
+ CategoryInfo : ObjectNotFound: ($.Message:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

$.Message : The term '$.Message' 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 C:\Mouse.ps1:11 char:86
+ ... ogName='System'; StartTime=$start} | Where-Object { $.Message -match ...
+ ~~~~~~~~~
+ CategoryInfo : ObjectNotFound: ($.Message:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

$.Message : The term '$.Message' 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 C:\Mouse.ps1:11 char:86
+ ... ogName='System'; StartTime=$start} | Where-Object { $.Message -match ...
+ ~~~~~~~~~
+ CategoryInfo : ObjectNotFound: ($.Message:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

$.Message : The term '$.Message' 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 C:\Mouse.ps1:11 char:86
+ ... ogName='System'; StartTime=$start} | Where-Object { $.Message -match ...
+ ~~~~~~~~~
+ CategoryInfo : ObjectNotFound: ($.Message:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

$.Message : The term '$.Message' 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 C:\Mouse.ps1:11 char:86
+ ... ogName='System'; StartTime=$start} | Where-Object { $.Message -match ...
+ ~~~~~~~~~
+ CategoryInfo : ObjectNotFound: ($.Message:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

$.Message : The term '$.Message' 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 C:\Mouse.ps1:11 char:86
+ ... ogName='System'; StartTime=$start} | Where-Object { $.Message -match ...
+ ~~~~~~~~~
+ CategoryInfo : ObjectNotFound: ($.Message:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

PS C:\>

I have attached the 3 files created on the desktop.

 

[Distorted Vision]

USB_Events_Last10min.txt is empty so would not attach.

 

[ChatGPT]

Thanks — that output is useful. Summary first, then exact next steps you can run right now.
Quick findings from the device list you posted

• The Unifying receiver and Logitech devices are present and showing OK. I can see the Unifying vendor/device IDs in your output: USB\VID_0A5C&PID_4503 and a Generic USB Hub entry USB\VID_0A5C&PID_4500 — so Windows is seeing the receiver and the mouse at the USB layer. (This matches the list you pasted above.
• The Get-WinEvent portion failed in your script because $start was null / not set in the script scope, so the event log extraction did not run. That’s why you got the “A null value was encountered in the StartTime hash table key” error. We need to run a corrected one‑liner interactively so $start exists in the same session.

What this means

• Because the receiver and mouse are present and OK in Device Manager, but the mouse still drops while the keyboard on the same receiver stays connected, the problem is most likely:
  1) RF/session problem between the mouse and receiver (interference or pairing/session glitch), or
  2) receiver sharing a noisy USB host/hub or an intermittent host reset — we need the system event log to know which.

Two immediate, high‑value actions
A — Reproduce the drop, then run the corrected capture commands interactively (copy/paste)
1) Wait until the mouse drops (don’t reboot). Open PowerShell as Administrator and paste these three lines exactly (they set $start in the same session and capture the data). Paste the outputs here or attach the files.
$start = (Get-Date).AddMinutes(-10)
Get-PnpDevice -PresentOnly | Where-Object { $_.InstanceId -match 'VID_046D|VID_0A5C' } | Format-List FriendlyName,InstanceId,Status
Get-WinEvent -FilterHashtable @{LogName='System'; StartTime=$start} | Where-Object { $.ProviderName -match 'Kernel-PnP|USBHUB3|USB' -or $.Message -match 'USB|usb|hub|reset|removed' } | Select-Object TimeCreated, ProviderName, Id, LevelDisplayName, Message | Format-List
Notes:

• Run these interactively (not inside a saved .ps1) so $start is defined and used in the same session.
• If you prefer files (easier to attach), run this instead (single block):

$start=(Get-Date).AddMinutes(-10)
Get-PnpDevice -PresentOnly | Where-Object { $_.InstanceId -match 'VID_046D|VID_0A5C' } | Format-List FriendlyName,InstanceId,Status | Out-File "$env:USERPROFILE\Desktop\Mouse_DeviceInfo.txt"
Get-WinEvent -FilterHashtable @{LogName='System'; StartTime=$start} | Where-Object { $.ProviderName -match 'Kernel-PnP|USBHUB3|USB' -or $_.Message -match 'USB|usb|hub|reset|removed' } | Select TimeCreated, ProviderName, Id, LevelDisplayName, Message | Out-File "$env:USERPROFILE\Desktop\USB_Events_Last10min.txt"
B — Short practical test you can do now

• Re‑pair the mouse (clean rebind) to the Unifying receiver:
  1) Close Logi Options+/Unifying Software.
  2) Run Logitech Unifying Utility (or Logi Options+ → Add device).
  3) Remove/unpair the mouse (if present) then re‑pair it on the channel you use (select channel on mouse, power off → on, run pairing).
  4) After pairing, update firmware in Logi Options+ if offered.
• Immediately test for several hours.

If re‑pairing doesn’t fix it, most likely you’ll benefit from a desk extension (see below) or the event log will show hub resets.
How to find which root hub / host controller the receiver is on (useful if we need to move it)

• Copy the InstanceId you saw for the Unifying device (for example USB\VID_0A5C&PID_4503\8&80E368A&0&2 from your output).
• In Device Manager choose View → Devices by connection. Action → Find… and paste the InstanceId (or the long string) — Device Manager will jump to that device in the physical tree and show which USB Root Hub / host controller it is attached to. Move the receiver to a rear port on a different host controller (or to a USB2 port) if it’s sharing that hub with a noisy/high‑power device.

Practical workaround (very often the permanent fix)

• Get a short passive USB 2.0 extension (1–1.5 m). Plug the extension into a rear motherboard USB2 port and rest the Unifying receiver on the desk ~20–50 cm from the mouse (away from the metal mouse pad). That removes interference and solves >80% of these problems.

If the event log shows a port/hub reset

• We’ll update chipset/USB drivers and BIOS (I can provide direct links & step‑by‑step if you paste the motherboard model or run: Get-CimInstance -ClassName Win32_BaseBoard | Format-List Manufacturer,Product,Version).

Next actions for you (pick one)
1) If you can reproduce the drop now — run the corrected capture commands above interactively and paste the full output (or attach the two Desktop files). I’ll parse them and tell you exactly whether Windows reset a port or the mouse simply lost its radio session.
2) If you want a quick test: re‑pair the mouse + update firmware in Logi Options+, then test. Report whether the drops stop.
3) If you prefer to try the almost‑certain fix: order a passive USB 2.0 extension and test with the receiver on the desk.
If you paste the outputs from the two interactive commands above (or attach the produced USB_Events file), I’ll read the event messages and give the single next remedial step (move to a different host controller, update BIOS/drivers, or RMA).

 

[ChatGPT]

Thanks — I got the outputs you pasted and the two files you created (Mouse_Device_Info and All_USB_Devices). Good troubleshooting so far.
What those files show

• The Unifying receiver and the mouse are present and enumerating — I can see the Logitech/Unifying entries (VID_0A5C and VID_046D devices) and a Generic USB Hub for the Unifying receiver on the system. The device list you pasted includes the Unifying hub entry USB\VID_0A5C&PID_4500\… and the Unifying input device USB\VID_0A5C&PID_4503\… so the receiver is attached and Windows currently "sees" it as OK.
• The Get‑WinEvent step in your script failed, which is why USB_Events_Last10min.txt was empty; the error shows the StartTime value was null and the script attempted to use $.Message incorrectly in a Where-Object filter (PowerShell treated “$.” as a command). Because of that we don’t yet have the System event lines that would prove whether Windows reset the USB port/hub or whether the mouse radio lost the session.

Bottom line from what we have now

• Because the receiver enumerates and your keyboard (on the same receiver) does not drop while the mouse does, this points more to a radio/pairing or mouse‑side issue (or a flaky pairing) than to an obvious USB host controller failure. But we still need the System event log lines captured immediately after a drop to be sure.

Next actions — exactly what to run and why
Please run these commands manually (NOT inside a saved script) immediately after the next dropout — open PowerShell as Administrator (right‑click → Run as administrator) and copy/paste these two blocks, one after the other. Doing them manually avoids the scoping/variable issues you hit.
1) Capture the Unifying/Logitech devices (paste the output here)
Copy/paste this single line and press Enter:
Get-PnpDevice -PresentOnly | Where-Object { $_.InstanceId -match 'VID_046D|VID_0A5C' } | Format-List FriendlyName,InstanceId,Status
2) Capture System USB/Kernel events from the last 10 minutes (paste the output here)
Copy/paste this single line and press Enter (this sets $start and runs the query in the same command — avoids the null StartTime error):
$start=(Get-Date).AddMinutes(-10); Get-WinEvent -FilterHashtable @{LogName='System'; StartTime=$start} | Where-Object { $_.Message -match 'USB|usb|Kernel-PnP|USBHUB|UsbHub|Usb' } | Select-Object TimeCreated, ProviderName, Id, LevelDisplayName, Message | Format-List
Important: run both commands immediately (within a minute) after the drop, and paste the full outputs here. If the System output is long, paste the entries with timestamps that match the moment the device dropped (I only need the events +/- 1 minute around the drop).
If you prefer the files on Desktop (so you can attach)
Run these two lines (Admin PowerShell) immediately after the drop — they write files to your Desktop:
$start=(Get-Date).AddMinutes(-10)
Get-PnpDevice -PresentOnly | Where-Object { $_.InstanceId -match 'VID_046D|VID_0A5C' } | Format-List FriendlyName,InstanceId,Status | Out-File "$env:USERPROFILE\Desktop\Mouse_DeviceInfo.txt"
Get-WinEvent -FilterHashtable @{LogName='System'; StartTime=$start} | Where-Object { $.Message -match 'USB|usb|Kernel-PnP|USBHUB|UsbHub|Usb' } | Select-Object TimeCreated, ProviderName, Id, LevelDisplayName, Message | Out-File "$env:USERPROFILE\Desktop\USB_Events_Last10min.txt"
If you run the file version, attach both files here. (Do NOT reboot the PC before running these — reboot clears the immediate event context.
Quick troubleshooting steps you can do now (while you wait for the next drop)

• Re‑pair the mouse to the Unifying receiver (clean rebind):
  1. Quit Options+.
  2. Run the Unifying utility (or Options+ pairing) → Remove/unpair the mouse from that receiver.
  3. Reboot the PC.
  4. Pair the mouse again to the receiver on channel 1.
     This clears a stale/corrupted pairing which often causes “needs power‑cycle” behavior.
• If you haven’t already, temporarily unpair the keyboard from the same receiver (or move the keyboard to a different receiver) and use the mouse alone for several hours. If the mouse stabilizes, that suggests a multi‑device interaction issue.
• When you can, get a passive USB‑2.0 extension (1.0–1.5 m) and use it to place the Unifying receiver on your desk ~20–50 cm from the mouse (plug extension into a rear motherboard USB2 port). This fixes RF/USB3 interference in most cases. If you want a recommendation I’ll list a couple of good keywords and examples.

If the logs show host USB resets vs. radio disconnect

• If the System events show USB hub/port resets, controller errors, or “device removed” at the same timestamps as the mouse drop, we focus on chipset/USB drivers and BIOS updates and moving the receiver to a different physical root hub. I’ll give exact steps and drivers if you paste your motherboard model or the output of:
  Get-CimInstance -ClassName Win32_BaseBoard | Format-List Manufacturer,Product,Version,SerialNumber
• If the System events show no USB resets and only the mouse disappears from the HID list or you see no matching USB port errors, that points to a device/radio/pairing problem — re‑pair/RMA the mouse (Logitech support will want the logs and your test results).

What I can do immediately when you paste the outputs

• Parse the Get-PnpDevice output to identify exact Instance IDs and the hub the receiver is on.
• Read System event lines and tell you whether Windows reset the port/hub or not, and the specific driver or controller involved.
• Give the single next action (move receiver, BIOS/chipset update, re‑pair, or RMA) — I’ll give only the one-most-likely fix.

Ready when you are
Run the two manual commands immediately after the next drop and paste the outputs here (or attach the two Desktop files if you used the Out-File version). I’ll parse them and return the single next action.

 

[Distorted Vision]

I checked Gigabyte's website and the last chipset drivers installed were in 2015 and were for Windows 10.
Furthermore I have the latest BIOS version:

https://www.gigabyte.com/Motherboard/GA-Z68AP-D3-rev-10/support#support-dl

 

[ChatGPT]

Thanks — that CPU‑Z screenshot and the Gigabyte support check are very helpful.
Short summary of what that means

• Your board (Gigabyte GA‑Z68AP‑D3, Ivy Bridge / Intel 6 Series) is quite old. Gigabyte’s latest INF/chipset/USB packages for that board were published for Windows 10 (and last updated years ago) and your BIOS is already the latest the vendor supplies.
• That means there may not be modern vendor USB drivers specifically targeted for Windows 11 — Windows will usually use built‑in Microsoft drivers for these controllers. Because of the age, the practical fixes (receiver placement / host choice) are the highest yield and lowest risk; driver/BIOS work is still possible but may not add much beyond the fixes below.

What I recommend next (priority order — one action at a time)
1) First and best practical fix — get a passive USB 2.0 extension (1.0–1.5 m)

• Buy a shielded passive USB 2.0 A‑male → A‑female extension cable (1–1.5 m). Keywords to search: “USB 2.0 A male to A female extension cable 1m shielded passive”. Avoid “USB 3.0” or “active repeater” in the product name.
• Plug the extension into a rear motherboard USB2 port and rest the Unifying receiver on the desk ~20–50 cm from the mouse (away from metal mouse pad). This removes RF attenuation and USB3 interference and solves these Logitech drops in the majority of cases.
• If you want, tell me the country and I’ll suggest two widely available product names to search.

2) Map the receiver to the physical host controller and, if needed, move it to a different rear port

• Run this in an elevated PowerShell to show which controller the Unifying device is on:
  Copy/paste (Admin PowerShell):
  Get-CimInstance Win32USBControllerDevice |
  ForEach-Object {
  $ctrl = ($.Antecedent -split '"')[1]; $dev = ($_.Dependent -split '"')[1];
  $ctrlName = (Get-CimInstance Win32USBController | Where-Object { $.DeviceID -eq $ctrl }).Name;
  [PSCustomObject]@{Device=$dev; Controller=$ctrl; ControllerName=$ctrlName}
  } |
  Where-Object { $_.Device -match 'VID_0A5C|VID_046D' } |
  Format-Table -AutoSize
• Note the ControllerName for your Unifying device. In Device Manager (View → Devices by connection) use Action → Find and paste the Device Instance string (from your earlier Get‑PnpDevice output) to jump straight to the node and see which physical root hub it’s attached to.
• If it’s on the same controller/hub as a high‑power device (external HDD, webcam, front panel card reader), move the receiver to a different rear USB2 port on a different controller if available.

3) If you want to try drivers (optional / lower priority)

• Because Gigabyte only lists older drivers, you can:
  • Reinstall the chipset/INF package from Gigabyte’s support page for the Z68AP‑D3 (Windows 10 package). Run the installer as Administrator and, if needed, use Compatibility Mode for Windows 8/10. Reboot after install.
  • Install the Etron USB3 driver packaged on Gigabyte’s site (that’s the driver for the Etron USB3 controller you have). That can fix USB3 noise issues that leak into 2.4 GHz.
• I can prepare exact download filenames and step‑by‑step if you tell me you want to try this. Note: be cautious — don’t flash BIOS (you already have latest) unless vendor instructs otherwise.

4) If the issue continues after the extension / port move / re‑pair

• Capture the System event log at the moment of the next drop so we can see whether Windows reset the port (host side) or no port reset is recorded (device/radio side). Use these interactive commands immediately after a drop (Admin PowerShell — paste the output here):
  1) Show Logitech devices:
  Get-PnpDevice -PresentOnly | Where-Object { $_.InstanceId -match 'VID_046D|VID_0A5C' } | Format-List FriendlyName,InstanceId,Status
  2) Show recent USB/kernel events:
  $start=(Get-Date).AddMinutes(-10); Get-WinEvent -FilterHashtable @{LogName='System'; StartTime=$start} |
  Where-Object { $_.Message -match 'USB|usb|hub|reset|removed|Kernel-PnP|USBHUB3' } |
  Select-Object TimeCreated, ProviderName, Id, LevelDisplayName, Message |
  Format-List
• Paste the outputs and I will read them and tell you the exact next action (update specific driver, move receiver to X root hub, or RMA the mouse).

Practical notes & safety

• Don’t plug the Unifying receiver into USB3 hubs next to high‑speed devices on the desk. USB3 radios and certain powered hubs commonly create interference. The extension is the low‑cost, risk‑free first step.
• Re‑pairing the mouse (Unifying utility / Options+) is quick and harmless — do that now if you haven’t recently.
• Because the board is old and vendor drivers are old, Windows’ own built‑in drivers may be the most stable option. If driver installs look risky, prefer the physical fixes first.

If you want I’ll:

• Give two specific product names/keywords to buy a passive USB 2.0 extension (no links).
• Walk you through the Device Manager mapping steps to identify which exact rear port is on which controller (paste the output of the mapping command above and I’ll point).
• Prepare exact Gigabyte driver filenames and installation steps (if you want to try the vendor drivers).

Which of the three do you want now:
A) Shopping keywords & recommended cable specs for the USB extension,
B) I’ll walk you step‑by‑step to locate the receiver in Device Manager and move it to a different root hub, or
C) I’ll give the exact Gigabyte driver files and step‑by‑step install instructions for your board?

 

[Distorted Vision]

I got a disconnect.

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-PnpDevice -PresentOnly | Where-Object { $_.InstanceId -match 'VID_046D|VID_0A5C' } | Format-List FriendlyName,InstanceId,Status


FriendlyName : HID-compliant system controller
InstanceId : HID\VID_046D&PID_C548&MI_01&COL03\9&2741F85C&0&0002
Status : OK

FriendlyName : USB Input Device
InstanceId : USB\VID_0A5C&PID_4502\8&80E368A&0&1
Status : OK

FriendlyName : HID-compliant vendor-defined device
InstanceId : HID\VID_046D&PID_C52B&MI_02&COL01\8&2038E687&0&0000
Status : OK

FriendlyName : HID-compliant mouse
InstanceId : HID\VID_0A5C&PID_4503&COL01\9&2D1D4BEB&0&0000
Status : OK

FriendlyName : HID-compliant device
InstanceId : HID\VID_046D&PID_C548&MI_01&COL04\9&2741F85C&0&0003
Status : OK

FriendlyName : Logitech USB Input Device
InstanceId : USB\VID_046D&PID_C548&MI_00\8&11508CCC&0&0000
Status : OK

FriendlyName : Logitech USB Input Device
InstanceId : USB\VID_046D&PID_C52B&MI_00\7&2FFDA91A&0&0000
Status : OK

FriendlyName : USB Composite Device
InstanceId : USB\VID_046D&PID_C548\7&203B8509&0&3
Status : OK

FriendlyName : Generic USB Hub
InstanceId : USB\VID_0A5C&PID_4500\7&2E45F226&0&5
Status : OK

FriendlyName : USB Input Device
InstanceId : USB\VID_0A5C&PID_4503\8&80E368A&0&2
Status : OK

FriendlyName : HID-compliant vendor-defined device
InstanceId : HID\VID_046D&PID_C52B&MI_02&COL02\8&2038E687&0&0001
Status : OK

FriendlyName : HID Keyboard Device
InstanceId : HID\VID_046D&PID_C52B&MI_00\8&20E309E7&0&0000
Status : OK

FriendlyName : HID-compliant consumer control device
InstanceId : HID\VID_0A5C&PID_4503&COL02\9&2D1D4BEB&0&0001
Status : OK

FriendlyName : USB Input Device
InstanceId : USB\VID_046D&PID_C548&MI_01\8&11508CCC&0&0001
Status : OK

FriendlyName : USB Input Device
InstanceId : USB\VID_046D&PID_C52B&MI_01\7&2FFDA91A&0&0001
Status : OK

FriendlyName : HID-compliant touch pad
InstanceId : HID\VID_046D&PID_C548&MI_03\9&19D9F812&0&0000
Status : OK

FriendlyName : HID-compliant vendor-defined device
InstanceId : HID\VID_046D&PID_C52B&MI_02&COL03\8&2038E687&0&0002
Status : OK

FriendlyName : HID-compliant mouse
InstanceId : HID\VID_046D&PID_C548&MI_01&COL01\9&2741F85C&0&0000
Status : OK

FriendlyName : HID Keyboard Device
InstanceId : HID\VID_046D&PID_C548&MI_00\9&36ABA9A&0&0000
Status : OK

FriendlyName : USB Input Device
InstanceId : USB\VID_046D&PID_C548&MI_02\8&11508CCC&0&0002
Status : OK

FriendlyName : USB Input Device
InstanceId : USB\VID_046D&PID_C52B&MI_02\7&2FFDA91A&0&0002
Status : OK

FriendlyName : HID-compliant consumer control device
InstanceId : HID\VID_046D&PID_C548&MI_01&COL02\9&2741F85C&0&0001
Status : OK

FriendlyName : HID-compliant vendor-defined device
InstanceId : HID\VID_046D&PID_C548&MI_02&COL02\9&2166BCD&0&0001
Status : OK

FriendlyName : HID-compliant vendor-defined device
InstanceId : HID\VID_046D&PID_C548&MI_02&COL01\9&2166BCD&0&0000
Status : OK

FriendlyName : HID-compliant vendor-defined device
InstanceId : HID\VID_046D&PID_C52B&MI_01&COL04\8&8755A42&0&0003
Status : OK

FriendlyName : USB Input Device
InstanceId : USB\VID_046D&PID_C548&MI_03\8&11508CCC&0&0003
Status : OK

FriendlyName : HID-compliant system controller
InstanceId : HID\VID_046D&PID_C52B&MI_01&COL03\8&8755A42&0&0002
Status : OK

FriendlyName : USB Composite Device
InstanceId : USB\VID_046D&PID_C52B\6&3AE11B61&0&3
Status : OK

FriendlyName : HID-compliant consumer control device
InstanceId : HID\VID_046D&PID_C52B&MI_01&COL02\8&8755A42&0&0001
Status : OK

FriendlyName : HID-compliant mouse
InstanceId : HID\VID_046D&PID_C52B&MI_01&COL01\8&8755A42&0&0000
Status : OK



PS C:\WINDOWS\system32> $start=(Get-Date).AddMinutes(-10); Get-WinEvent -FilterHashtable @{LogName='System'; StartTime=$start} | Where-Object { $_.Message -match 'USB|usb|Kernel-PnP|USBHUB|UsbHub|Usb' } | Select-Object TimeCreated, ProviderName, Id, LevelDisplayName, Message | Format-List
PS C:\WINDOWS\system32> $start=(Get-Date).AddMinutes(-10)
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\Mouse_DeviceInfo.txt"
PS C:\WINDOWS\system32> Get-WinEvent -FilterHashtable @{LogName='System'; StartTime=$start} | Where-Object { $.Message -match 'USB|usb|Kernel-PnP|USBHUB|UsbHub|Usb' } | Select-Object TimeCreated, ProviderName, Id, LevelDisplayName, Message | Out-File "$env:USERPROFILE\Desktop\USB_Events_Last10min.txt"
$.Message : The term '$.Message' 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:1 char:86
+ ... ogName='System'; StartTime=$start} | Where-Object { $.Message -match ...
+ ~~~~~~~~~
+ CategoryInfo : ObjectNotFound: ($.Message:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

PS C:\WINDOWS\system32>

 

[ChatGPT]

Thanks — the errors you saw came from two small issues in the script you ran:

• The Get-WinEvent call failed earlier because $start was not defined in the same PowerShell session when Get-WinEvent ran. You must set $start and then call Get-WinEvent in the same interactive session (not from a saved .ps1 that has scoping issues).
• The other error (many occurrences of “$.Message : The term '$.Message' is not recognized…”) is simply a typo: in PowerShell the pipeline variable is $ (underscore), not $. So use $.Message (not $.Message).

Below are corrected, copy/paste‑ready commands you should run immediately after the next drop. Do them interactively in an elevated PowerShell (right‑click PowerShell → Run as administrator) so $start is defined and used in the same session.
1) Quick interactive capture (paste output here)
Paste these two lines into an Admin PowerShell prompt, one after the other, right after the drop:
$start = (Get-Date).AddMinutes(-10)
Get-PnpDevice -PresentOnly | Where-Object { $_.InstanceId -match 'VID_046D|VID_0A5C' } | Format-List FriendlyName,InstanceId,Status
Then paste this one line (it will show kernel/USB events from the last 10 minutes):
$start=(Get-Date).AddMinutes(-10); 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' } | Select-Object TimeCreated, ProviderName, Id, LevelDisplayName, Message | Format-List
2) If you prefer files to attach (recommended)
Paste this block (Admin PowerShell) immediately after the drop. It writes 2 files to your Desktop:
$start=(Get-Date).AddMinutes(-10)
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' } | Select-Object TimeCreated, ProviderName, Id, LevelDisplayName, Message | Out-File "$env:USERPROFILE\Desktop\USB_Events_Last10min.txt"
Notes / tips

• Run these commands interactively (copy/paste) after the drop — do NOT run them from a saved .ps1 unless you know $start is set in the same scope.
• Don’t reboot before running these commands: reboots clear the events you need.
• If the USB_Events_Last10min.txt file contains no events, try increasing the AddMinutes window (e.g. AddMinutes(-30) and re-run immediately after the next drop; or open Event Viewer GUI and look for events at the exact timestamp.

If you get output or files, attach the USB_Events_Last10min.txt and Mouse_DeviceInfo.txt (or paste the command outputs here). I’ll parse them and tell you exactly whether Windows reset the port / controller or whether the mouse lost its radio connection (and the single next action to take).
Troubleshooting guidance depending on what we find

• If you see Kernel‑PnP / USB controller reset / “device removed” entries at the drop time → host/controller/driver issue. Next step: move receiver to a different rear root hub (or use the USB 2.0 extension), then update chipset/USB drivers. I’ll give exact driver links if you want.
• If you see no hub/port resets and the mouse simply stops sending input (no USB errors) → radio/pairing problem on the mouse; try re‑pairing and placing the receiver on an extension; if that fails, Logitech RMA likely.

If you want, I can also give the exact Event Viewer GUI steps to filter System log entries for Kernel‑PnP / USB at a specific timestamp — say so and I’ll paste those steps.
Run the capture (interactive) after the next drop and paste or attach the results — I’ll parse immediately and tell you the single most likely fix.

 

[Distorted Vision]

I'm not sure if this outside of your scope because this is a Windows forum but as diagnostic step I was wondering if I could try and run a portable Slax and see if there are disconnects in Linux to eliminate whether RF interference is the cause.

 

[ChatGPT]

Yes — that’s a great diagnostic. Booting a Linux live USB (Slax or any other distro) and using the mouse there will help separate Windows/driver/host problems from RF/pairing/mouse hardware problems.
Below I give a short plan + exact, copy/paste commands you can run from a Linux live environment so you can reproduce the test and capture useful logs to paste here.
Summary plan

• Create a bootable Slax (or Ubuntu) USB and boot the PC from it.
• Use the Unifying receiver in the same physical USB port you normally use (or the rear port you tested). Use the same mouse usage you normally do until it drops.
• While using, capture kernel/USB messages and input events. If the mouse drops in Linux too, that points to RF/pairing or mouse/receiver hardware. If it stays stable under Linux, the issue is almost certainly Windows/driver/host related.

Making a live USB (Slax or Ubuntu)

• Slax: download Slax ISO from slax.org. On Windows use Rufus (or BalenaEtcher) to write the ISO to a USB stick. Pick MBR/BIOS+UEFI or GPT+UEFI depending on your PC (Rufus will help).
• Ubuntu (recommended if you want apt & tools like solaar easily): download Ubuntu Desktop ISO and write with Rufus/BalenaEtcher. Ubuntu live gives easier package install and solaar (Logitech Unifying manager).
• Boot from the USB (enter BIOS/boot menu, choose USB). Select “Try Ubuntu” or run Slax live. No install required.

What to test in the live session
1) Use the mouse normally and watch for a drop (use the same desk position / hub/port).
2) Capture USB/kernel messages and input events (run these in a terminal immediately before and during the test).
Commands to run in the live session (copy/paste)

• Open a terminal and start the kernel message monitor (writes to files so you can attach them later):
  sudo sh -c 'dmesg -wH > /tmp/dmesg_live.log' & echo $! > /tmp/dmesg_pid.txt
• Also capture system journal (Ubuntu only; Slax may not have systemd journal):
  sudo journalctl -f > /tmp/journal_live.log & echo $! > /tmp/journal_pid.txt
• List USB devices (to locate the receiver / mouse):
  lsusb
• Show USB tree (helps see which root hub):
  lsusb -t
• List input devices:
  cat /proc/bus/input/devices
  or
  xinput --list
• Live monitor input events (find the event node from the previous step, then):
  sudo apt-get update && sudo apt-get install -y evtest # Ubuntu only, skip if not available
  sudo evtest /dev/input/eventN # replace eventN with the correct node for the mouse
  Or use xinput test (if xinput shows the device id):
  xinput --list # find id
  xinput test <id> # shows button/motion events to terminal

How to capture a short timestamped USB log around the drop (recommended)

• Run these in the live terminal before you start using the mouse:
  START=$(date --iso-8601=seconds)
  sudo dmesg -wH > /tmp/dmesg_live.log & echo $! > /tmp/dmesg_pid.txt
  

  then use the mouse until it drops...​

  Immediately after drop, stop the live capture processes:​

  sudo kill $(cat /tmp/dmesg_pid.txt) # stops dmesg capture
  

  Save a copy to Desktop (or /tmp)​

  cp /tmp/dmesglive.log ~/"dmesg${START}.txt"
  

  If you used journalctl:​

  sudo kill $(cat /tmp/journal_pid.txt)
  cp /tmp/journallive.log ~/"journal${START}.txt"
  

  Collect lsusb output:​

  lsusb -v > ~/"lsusb_${START}.txt"
  

  Collect input device info:​

  cat /proc/bus/input/devices > ~/"inputdev_${START}.txt"
  

  Compress the files if you want:​

  tar -czf ~/mouse_linuxlogs${START}.tgz ~/dmesg${START}.txt ~/lsusb${START}.txt ~/inputdev_${START}.txt

What to look for in the logs

• dmesg / journal: lines that mention “usb X‑Y: USB disconnect”, “device descriptor read/failed”, “reset high-speed USB device”, “xhci_hcd”, “ehci_hcd”, or hub/controller errors. If you see these at the exact time the mouse dropped, that indicates the host/port is resetting the device.
• If you see nothing in dmesg/journal but evtest/xinput shows no more events, that points to the mouse radio losing connection (device side / RF / pairing).
• lsusb before/after drop: if the receiver disappears from lsusb at drop time, that’s a USB enumeration issue. If it stays present but input stops, that’s a radio/session problem.

If you prefer Solaar (Unifying manager) — useful on Ubuntu

• On Ubuntu live: sudo apt update && sudo apt install solaar
• Run solaar to show battery/firmware and device pairing details. It can show the Unifying receiver and attached devices and sometimes re-pair or display connection state.

Notes / tips

• Use the same physical port you tested on Windows so you replicate the same host/hub environment. If you have a rear motherboard port, use that.
• If you have no extension, try both: test with receiver at rear port and with it temporarily in the desk hub to mimic previous conditions.
• If the mouse drops in Linux too, that strongly implicates mouse RF/pairing or local RF interference (or very rarely a flaky receiver that happens across OSes).
• If Linux is stable but Windows still drops, the issue is Windows drivers/power management/host controller in Windows (we’ll pursue chipset/driver fixes).
• If you want, I can provide the exact Rufus settings for Slax or Ubuntu (MBR/UEFI), or recommend a small Ubuntu ISO for best tooling.

If you run this test, please attach or paste:

• the dmesg output (the saved file from just after the drop),
• the lsusb output,
• the evtest/xinput snippet showing lack of events (if used),
• and tell me which USB port/hub the receiver was in during the test.

Want me to:

• give step‑by‑step Rufus settings for writing Slax or Ubuntu to USB? or
• recommend a quick Ubuntu Live ISO instead (because solaar & apt make diagnosis easier)?

Which would you prefer?

 

[Distorted Vision]

I got a disconnect:

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> $start=(Get-Date).AddMinutes(-10)
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.txt"
PS C:\WINDOWS\system32> 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' } | Select-Object TimeCreated, ProviderName, Id, LevelDisplayName, Message | Out-File "$env:USERPROFILE\Desktop\USB_Events_Last10min.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:1 char:86
+ ... e='System'; StartTime=$start} | Where-Object { $.ProviderName -match ...
+ ~~~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: ($.ProviderName:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

PS C:\WINDOWS\system32> $start = (Get-Date).AddMinutes(-10)
PS C:\WINDOWS\system32> Get-PnpDevice -PresentOnly | Where-Object { $_.InstanceId -match 'VID_046D|VID_0A5C' } | Format-List FriendlyName,InstanceId,Status


FriendlyName : HID-compliant system controller
InstanceId : HID\VID_046D&PID_C548&MI_01&COL03\9&2741F85C&0&0002
Status : OK

FriendlyName : USB Input Device
InstanceId : USB\VID_0A5C&PID_4502\8&80E368A&0&1
Status : OK

FriendlyName : HID-compliant vendor-defined device
InstanceId : HID\VID_046D&PID_C52B&MI_02&COL01\8&2038E687&0&0000
Status : OK

FriendlyName : HID-compliant mouse
InstanceId : HID\VID_0A5C&PID_4503&COL01\9&2D1D4BEB&0&0000
Status : OK

FriendlyName : HID-compliant device
InstanceId : HID\VID_046D&PID_C548&MI_01&COL04\9&2741F85C&0&0003
Status : OK

FriendlyName : Logitech USB Input Device
InstanceId : USB\VID_046D&PID_C548&MI_00\8&11508CCC&0&0000
Status : OK

FriendlyName : Logitech USB Input Device
InstanceId : USB\VID_046D&PID_C52B&MI_00\7&2FFDA91A&0&0000
Status : OK

FriendlyName : USB Composite Device
InstanceId : USB\VID_046D&PID_C548\7&203B8509&0&3
Status : OK

FriendlyName : Generic USB Hub
InstanceId : USB\VID_0A5C&PID_4500\7&2E45F226&0&5
Status : OK

FriendlyName : USB Input Device
InstanceId : USB\VID_0A5C&PID_4503\8&80E368A&0&2
Status : OK

FriendlyName : HID-compliant vendor-defined device
InstanceId : HID\VID_046D&PID_C52B&MI_02&COL02\8&2038E687&0&0001
Status : OK

FriendlyName : HID Keyboard Device
InstanceId : HID\VID_046D&PID_C52B&MI_00\8&20E309E7&0&0000
Status : OK

FriendlyName : HID-compliant consumer control device
InstanceId : HID\VID_0A5C&PID_4503&COL02\9&2D1D4BEB&0&0001
Status : OK

FriendlyName : USB Input Device
InstanceId : USB\VID_046D&PID_C548&MI_01\8&11508CCC&0&0001
Status : OK

FriendlyName : USB Input Device
InstanceId : USB\VID_046D&PID_C52B&MI_01\7&2FFDA91A&0&0001
Status : OK

FriendlyName : HID-compliant touch pad
InstanceId : HID\VID_046D&PID_C548&MI_03\9&19D9F812&0&0000
Status : OK

FriendlyName : HID-compliant vendor-defined device
InstanceId : HID\VID_046D&PID_C52B&MI_02&COL03\8&2038E687&0&0002
Status : OK

FriendlyName : HID-compliant mouse
InstanceId : HID\VID_046D&PID_C548&MI_01&COL01\9&2741F85C&0&0000
Status : OK

FriendlyName : HID Keyboard Device
InstanceId : HID\VID_046D&PID_C548&MI_00\9&36ABA9A&0&0000
Status : OK

FriendlyName : USB Input Device
InstanceId : USB\VID_046D&PID_C548&MI_02\8&11508CCC&0&0002
Status : OK

FriendlyName : USB Input Device
InstanceId : USB\VID_046D&PID_C52B&MI_02\7&2FFDA91A&0&0002
Status : OK

FriendlyName : HID-compliant consumer control device
InstanceId : HID\VID_046D&PID_C548&MI_01&COL02\9&2741F85C&0&0001
Status : OK

FriendlyName : HID-compliant vendor-defined device
InstanceId : HID\VID_046D&PID_C548&MI_02&COL02\9&2166BCD&0&0001
Status : OK

FriendlyName : HID-compliant vendor-defined device
InstanceId : HID\VID_046D&PID_C548&MI_02&COL01\9&2166BCD&0&0000
Status : OK

FriendlyName : HID-compliant vendor-defined device
InstanceId : HID\VID_046D&PID_C52B&MI_01&COL04\8&8755A42&0&0003
Status : OK

FriendlyName : USB Input Device
InstanceId : USB\VID_046D&PID_C548&MI_03\8&11508CCC&0&0003
Status : OK

FriendlyName : HID-compliant system controller
InstanceId : HID\VID_046D&PID_C52B&MI_01&COL03\8&8755A42&0&0002
Status : OK

FriendlyName : USB Composite Device
InstanceId : USB\VID_046D&PID_C52B\6&3AE11B61&0&3
Status : OK

FriendlyName : HID-compliant consumer control device
InstanceId : HID\VID_046D&PID_C52B&MI_01&COL02\8&8755A42&0&0001
Status : OK

FriendlyName : HID-compliant mouse
InstanceId : HID\VID_046D&PID_C52B&MI_01&COL01\8&8755A42&0&0000
Status : OK



PS C:\WINDOWS\system32> $start=(Get-Date).AddMinutes(-10); 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' } | Select-Object TimeCreated, ProviderName, Id, LevelDisplayName, Message | Format-List
$.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:1 char:121
+ ... e='System'; StartTime=$start} | Where-Object { $.ProviderName -match ...
+ ~~~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: ($.ProviderName:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

PS C:\WINDOWS\system32>

 

[ChatGPT]

Thanks — the error you saw is just a typo in the Where-Object scriptblock (you used $.ProviderName instead of $_.ProviderName). Run these corrected commands (copy/paste) in an elevated PowerShell window right after a disconnect; they will create two files on your Desktop:
1) Open PowerShell as Administrator, then set your time window (example = last 10 minutes) and save the device info:
$start = (Get-Date).AddMinutes(-10)
Get-PnpDevice -PresentOnly |
Where-Object { $_.InstanceId -match 'VID_046D|VID_0A5C' } |
Format-List FriendlyName,InstanceId,Status |
Out-File "$env:USERPROFILE\Desktop\MouseDeviceInfo.txt"
2) Capture System events that mention USB / hub / disconnect within that time window:
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|enumerate|fail') } |
Select-Object TimeCreated, ProviderName, Id, LevelDisplayName, Message |
Out-File "$env:USERPROFILE\Desktop\USB_Events_Last10min.txt"
Notes and troubleshooting

• Make sure you define $start in the same PowerShell session immediately before running the Get-WinEvent command. If $start is missing you get the “null StartTime” error.
• If you want a wider window use AddMinutes(-30) or AddHours(-1).
• If Get-WinEvent doesn’t return anything (or errors) try the legacy fallback:
  Get-EventLog -LogName System -After $start |
  Where-Object { $_.Message -match 'USB|usb|reset|disconnect|removed|hub|enumerate|fail' } |
  Select TimeGenerated, Source, EventID, EntryType, Message |
  Out-File "$env:USERPROFILE\Desktop\USB_Events_GetEventLog.txt"
• If you prefer a GUI realtime capture, NirSoft’s USBLogView (portable) is handy to monitor USB connect/disconnect activity.

When you’ve run the corrected commands and reproduced a disconnect, attach the two files (MouseDeviceInfo.txt and USB_Events_Last10min.txt). Paste any suspicious event lines here and I’ll help interpret them and recommend the next steps.

 

[Distorted Vision]

@ChatGPT I will have to return to troubleshooting this issue tomorrow. It's late and I need to go to bed!

 

[ChatGPT]

No problem — rest up. Quick recap and a ready-to-run set of commands for when you return tomorrow.
Short status summary (where we left off)

• Mouse (Logitech Unifying) intermittently drops; Easy‑Switch light goes out for channel 1. Keyboard on same receiver stays OK.
• You tested on a second PC (no drops), moved the receiver to a rear USB 2.0 port (temporary), and disabled USB selective suspend via powercfg (you ran the GUID-based commands successfully).
• Device Manager power settings were checked (root hub / generic hubs: "Allow the computer to turn off this device to save power" already unchecked).
• Script you ran failed because of a typo: $. vs $_. so the event capture file was empty.
• Chipset drivers are old (Gigabyte board, last Windows 10 drivers from 2015); BIOS is current.
• Next diagnostic step is to capture device list + System USB events immediately after a disconnect.

When you’re back, open PowerShell as Administrator and paste this (copy/paste-ready). It sets the time window (last 10 minutes) and writes two files to your Desktop:

start = last 10 minutes​

$start = (Get-Date).AddMinutes(-10)

save mouse/unifying device info​

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

save system USB-related events from the timeframe​

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|enumerate|fail') } |
Select-Object TimeCreated, ProviderName, Id, LevelDisplayName, Message |
Out-File "$env:USERPROFILE\Desktop\USB_Events_Last10min.txt"
If Get-WinEvent fails / returns nothing, run this fallback:
Get-EventLog -LogName System -After $start |
Where-Object { $_.Message -match 'USB|usb|reset|disconnect|removed|hub|enumerate|fail' } |
Select TimeGenerated, Source, EventID, EntryType, Message |
Out-File "$env:USERPROFILE\Desktop\USB_Events_GetEventLog.txt"
What to attach when you return

• MouseDeviceInfo.txt
• USB_Events_Last10min.txt (or USB_Events_GetEventLog.txt)
• Note exact time(s) of disconnect(s) if you can (or approximate), and which USB port/hub the receiver was in at the time.

Optional extra tests you mentioned

• Booting a Linux live USB (Slax or other) to check whether the mouse drops under Linux is a good way to rule in/out Windows driver/power issues vs RF/receiver hardware — worth doing when convenient.

When you’re back tomorrow paste the files or the relevant event lines and I’ll analyze them and recommend next steps. Sleep well!