New
#1
getting disconnect sound, followed by one or more reconnect sounds
I run an ASUS laptop, Win10 Pro 20H2 build 19042.746, see my specs for computer details. At random and more or less one to a dozen times an hour, the laptop will give a disconnect sound, followed by one or two connect sounds. (These are the sounds I get when I unplug or plug in a USB device.) But I'm not connecting or disconnecting anything at all, it happens when I'm not touching the computer.
If I'm typing, often whatever I'm typing into stops getting the input. This is at worst inconvenient and leads to typos. I have to wiggle the mouse or hit enter to return to being able to type where I was.
Worse is: when I'm running my observatory and have several well designed commercial packages working together to control three separate hardware devices, they stop working together, sometimes get disconnected from each other, and I lose control of where the telescope is pointing.
How do I find out what is disconnecting and reconnecting, so I can disable it? I've tried event viewer as suggested elsewhere, but it seems to only record errors, warnings, and "information" and don't have timestamps that relate to the random behavior. I'm optimistically (and ignorantly) thinking there should be a log of (or a way to log) every single time something connects to something else in the computer (software AND hardware). I looked at device manager, and what I see is when I connect the same device again, the only events noted there are associated with days or years old information, related to the first time recently I connected it.
My work laptop, which is heavily managed by my employer, also has started doing this. It is a Dell Inspiron and has been getting worse, especially it seems when I'm connected to the internet but NOT connected to the VPN.
When I run the ASUS laptop in Safe mode with network, The Problem Stops (with the observatory coming disconnected) But I don't know if the sounds stop because audio is disabled in safe mode. but running in safe mode is not a long-term option for the observatory because the observatory needs alot of services, I think.