The device itself and the cable work because I've tested them on a Linux notebook and work as intended. When I connect the watch to my PC using Windows 10, I hear the disconnect and connect sound repeatedly, and the watch switches constantly from MTP device to Amazfit Pace on device manager. How can I fix this?
Amazfit Pace constantly disconnects and connects from Windows 10 using USB cable.
- Thread starter Mwen Davo
- Start date
Update or rollback driver.
Check MS Event Viewer for error messages in the time index when the disconnects happen.
Check MS Event Viewer for error messages in the time index when the disconnects happen.
Hello, on my Stratos this issue is due to the fact that the watch is not well fitted in the charging cradle ( i lost some parts in the watch that make the watch a bit loose in the charging device).
Despite the watch saying it is charging it is not and it is nowhere to be seen in the file explorer. Only if i exercise some pressure on the watch then i see it in file explorer.
As you say that it works fine in Linux your issue might be different but it might be worth trying to put some more pressure on the watch when it is in the charging device.
Regards
Despite the watch saying it is charging it is not and it is nowhere to be seen in the file explorer. Only if i exercise some pressure on the watch then i see it in file explorer.
As you say that it works fine in Linux your issue might be different but it might be worth trying to put some more pressure on the watch when it is in the charging device.
Regards
You might be right. After applying some pressure on the back of the cradle, it seems like it managed to stay connected and not disconnect and connect repeatedly. I think the issue lies on the connection. Will try cleaning the charging sockets on the watch.
No luck, it's still doing the same. Linux works though, I can create files folders without it disconnecting.
Event viewer keeps repeating these:
- Information 26-Jan-23 8:51:39 PM WPD-ClassInstaller 24578 Driver Post-Install Configuration:
- Drivers were successfully installed for device USB\VID_18D1&PID_4EE2&REV_????&MI_00.
- Information 26-Jan-23 8:51:39 PM WPD-ClassInstaller 24577 Driver Post-Install Configuration
- Media player and imaging program compatibility layers were successfully registered for device USB\VID_18D1&PID_4EE2&REV_????&MI_00. Layer bits 0x00000003 were requested, layer bits 0x00000003 were registered.
- Information 26-Jan-23 8:51:38 PM WPD-ClassInstaller 24576 Driver Installation
- Autoplay was successfully registered for device USB\VID_18D1&PID_4EE2&REV_????&MI_00.
- Information 26-Jan-23 8:51:38 PM UserPnp 20003 (7005)
- Driver Management has concluded the process to add Service WinUsb for Device Instance ID USB\VID_18D1&PID_4EE2&MI_00\7&C6C9EED&0&0000 with the following status: 0.
- Information 26-Jan-23 8:51:38 PM UserPnp 20003 (7005)
- Driver Management has concluded the process to add Service WUDFWpdMtp for Device Instance ID USB\VID_18D1&PID_4EE2&MI_00\7&C6C9EED&0&0000 with the following status: 0.
- Information 26-Jan-23 8:51:38 PM DriverFrameworks-UserMode 10100 Installation or update of device drivers.
- The driver package installation has succeeded.
- Information 26-Jan-23 8:51:38 PM DriverFrameworks-UserMode 10002 Installation or update of device drivers.
- The UMDF service WpdMtpDriver (CLSID {aaae762b-a6a2-4c45-b5d8-9a83afb6bb70}) was upgraded. It requires framework version 2.31.0 or higher.
- Information 26-Jan-23 8:51:38 PM DriverFrameworks-UserMode 10000 Installation or update of device drivers.
- A driver package which uses user-mode driver framework version 2.31.0 is being installed on device USB\VID_18D1&PID_4EE2&MI_00\7&C6C9EED&0&0000.
It's not "spamming"; it's logging.
- The UMDF service WpdMtpDriver (CLSID {aaae762b-a6a2-4c45-b5d8-9a83afb6bb70}) was upgraded. It requires framework version 2.31.0 or higher.
Can you verify it's loaded on your PC?
Check all Event Viewer sections/messages in the relevant time index. Play with it...
Due to personal matters I had to switch to Windows 11, but unfortunately the problem still persists. The logs are the same as they were on Windows 10.
I used to use the old Process Viewer to track things down. Don't think that tool works on newer versions but there's probably a similar one.
Play with it... do Google searches. 99.9% of the time that how I resolve issues.
I recently bought Amazfit Pace and had problem connecting it to PC. At first I was certain it was drivers problem, and/or Windows 11 problem. So I went to my parents home and tried there on Win 10 laptop. To my surprise had no luck either. So I ask my father to find a bag of old micro USB cables and out of 4 (counting the one I use previously) smartwatch didn't react at all or was shown in device menager as unknown device. On 5 cable my Pace was recognized by Windows and AMAZFIT Tool. Just like that! So I took that one home and on my regular PC it works as well - soo IMHO Amazfit Pace is apparently very picky about cables
I'm using the cable that came with the watch, but I'll try with various Micro USB cables that I have laying around.
Similar threads
- Locked
