- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello all,
Our device is using the Cypress ARM Cortex-M3 (CY8c5866LTI-LP022, PSoC5800). It stores data which is sent to the client using USB.
For this, we install the Cypress USB UART driver (https://www.cypress.com/documentation/software-and-drivers/microsoft-certified-usb-uart-driver ) on the PC.
All works splendid, however...
On some of the windows 10 computers, the driver disappears after an update.
The fix is simple: Right click the Unknown device -> update drivers -> automatically search for drivers -> done.
All is working again... however:
Why does this happen? and what can I do about it so it won't happen again / or is solved automatically/programatically.
Best regards,
JB
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Please try Microsoft's USB serial driver.
USB serial driver (Usbser.sys) - Windows drivers | Microsoft Docs
The INF file usbser.inf is located in the folder C:\Windows\INF on my Windows 10 PC.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
I think you need to contact Microsoft for this issue.
There are similar queries which as follows where certain drivers were missing after Windows 10 update:
Driver Missing after Windows Update - Microsoft Community
Missing drivers after Windows 10 update - Microsoft Community
Thanks,
Ankita
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Please try Microsoft's USB serial driver.
USB serial driver (Usbser.sys) - Windows drivers | Microsoft Docs
The INF file usbser.inf is located in the folder C:\Windows\INF on my Windows 10 PC.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thank you for your answer. It seems that if I select the windows driver, no USB to UART shows up on the device manager, however, all works perfectly fine!
What I do find weird, is that the default windows driver is not (always) automatically detected as compatible driver.