Great — here’s a concise, ready‑to‑run “migration script” you can follow when your Bolt gear arrives. It covers pre‑migration prep, the exact pairing & firmware/update steps, how to restore settings, verification, and a short troubleshooting checklist (with the exact PowerShell captures to run if anything goes wrong).
Do this in order. I assume Windows 10/11 on the PC you’ll use as primary.
Before you start (prep, 5–10 min)
1) Create a System Restore point (just in case):
- Search → Create a restore point → Create.
2) Install Logitech software
- Install Logi Options+ (the app that handles Bolt and the device settings). Sign in to your Logitech account if you want cloud backup. (If you prefer the older apps for specific models, install as needed later.)
3) Backup any existing device settings (if you used Logi Options+ previously)
- Open Logi Options+ → Sign‑in → ensure Device Backup / cloud sync is enabled. Wait for settings to sync.
4) Note current power settings (we used these earlier) — ensure selective suspend is off:
- In elevated CMD or PowerShell run:
powercfg -setacvalueindex SCHEME_CURRENT SUB_USB USBSELECTSUSPEND 0
powercfg -setdcvalueindex SCHEME_CURRENT SUB_USB USBSELECTSUSPEND 0
powercfg -S SCHEME_CURRENT
Migration / pairing steps (on the day you get Bolt gear)
A. First device (keyboard K650 or whichever you want as primary)
1) Plug the Bolt receiver into a rear, motherboard USB2 port. If you have a short passive extension (UGreen), use it for best radio position.
2) Launch Logi Options+ → click “Add Device” or the Bolt pairing action.
3) Choose “Logi Bolt receiver” option, follow on‑screen steps (press pairing buttons on the receiver/mouse/keyboard as prompted). Wait for the app to confirm the new device is paired.
4) Repeat for the other device (mouse). You can pair multiple Bolt devices to the same Bolt receiver (check the app count).
B. Firmware & Options
1) In Logi Options+ select each device and check “Firmware” / “Check for Update” — update firmware if available.
2) If you used cloud backup earlier, restore the backup in Options+:
- Options+ → Devices → Settings → Restore from cloud (if available).
- If no cloud backup, reconfigure buttons/flows in Options+ manually.
C. Verify behavior
1) Test basic functions: cursor movement, left/right/middle buttons, side buttons, wheel, keyboard keys.
2) Walk test: move mouse around for 10–30 minutes; look for stutters/drops.
3) If using Flow (multi‑PC clipboard), test that switching works.
If you want a temporary fallback
- Keep your old Unifying receiver + UGreen available (do NOT have Bolt and Unifying receivers both in the same port if you don’t need to) — they are not compatible but can both be present in different ports if needed.
Post‑migration verification & housekeeping
1) Confirm the new Bolt devices appear in Device Manager:
- Run in PowerShell: Get-PnpDevice -PresentOnly | Where-Object { $_.InstanceId -match 'VID_046D|VID_0A5C' } | Format-List FriendlyName,InstanceId,Status
2) Confirm firmware versions in Logi Options+ and keep a note (screenshot).
3) Remove old pairings (optional)
- Use Logitech Unifying Utility to unpair old Unifying devices if you no longer need them (don’t unpair until you’ve confirmed Bolt devices work).
Troubleshooting (decisive captures — run these immediately after any drop)
If you see a drop or disconnect, do NOT reboot. Run these in an elevated PowerShell and attach the two resulting files (or paste their contents here) — they are the minimal evidence I need to tell you the single correct fix.
1) Device list (shows whether Windows still sees receiver / device):
$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) System events (USB / kernel events around the drop):
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_Last10min.txt"
Attach those two files and I will:
- If events show “usb … disconnect” or xhci_hcd resets → tell you the exact chipset/USB driver or BIOS update to install (I’ll give a single download and the exact install step).
- If the receiver stays present but the device stops responding → instruct to swap receiver / test Bluetooth / instruct replacement or replacement receiver purchase.
Tips & best practices for Bolt
- Put the Bolt receiver on a rear motherboard USB2 port or on a short passive extension positioned on the desk — good RF geometry still matters.
- Keep selective suspend off for USB root hubs and Logitech devices in Device Manager (we already disabled earlier).
- Ensure Windows chipset drivers and BIOS are up to date if you see hub/controller resets.
Quick script you can save for the migration day (copy/paste)
- Save this as migrate_to_bolt.txt for a checklist:
1) Install Logi Options+ and sign in.
2) Plug Bolt receiver into rear USB2 (use UGreen if available).
3) Options+ → Add Device → Bolt → follow pairing steps for keyboard then mouse.
4) Options+ → Check Firmware → Update if available.
5) Options+ → Restore backup (if present).
6) Test for 15–30 minutes. If drop occurs, run the two PowerShell captures above and attach the files.
If you want I can also:
- Produce a one‑page printout you can follow while doing the migration step‑by‑step on the day (copyable checklist), or
- Prepare a short fallback purchase list (one Bolt receiver + inexpensive K650 + MX Master 3S or 4 suggestions) — but you said no checklist needed.
Would you like the small one‑page printable checklist now, or do you want me to stand by and parse any capture files if a drop occurs after you migrate?
) [Start-Process], ParameterBindingException
