OP,

In addition to device and bufferSize, status, buffer and numBytesRead all need to be valid, too.

OP, if/as Device Manager is only showing the device in grey only when "show hidden devices" is selected, is the device even plugged in?  Or are you asking about software-first driver installs?

If/as you are on Windows 10, our VCP driver is distributed via Microsoft's Windows Update mechanism.  Therefore, in Device Manager, right-click the device select "Update driver" then select "Search automatically for updated driver software".  This will look on the Internet for the latest driver distributed for your CP210x devices (unless you've customized the device's VID and/or PID).

1) Can you please tell why installation files (.exe) are not being generated with VCP v10.1?

Microsoft is deprecating the use of DPInst.exe as a means of installing device drivers.  Specifically, they do not make available a DPInst.exe for ARM- or ARM64-architecture platforms.  As our VCP v10.1.x driver is a Universal driver its intended install platforms includes platforms that include ARM-based devices.  If/as DPInst is no longer offered by Microsoft for our redistribution on all of our supported platforms, we too are deprecating the .exe approach to installing the VCP driver.

2) In Custom USB Driver Installation Wizard, it is suggested to use VCP v10.1 for Windows 10. Is it good practice to use v6.7 for Windows10?

We recommend using v10.1 for your Windows 10.  v10.1 is a Universal driver. Windows versions prior to Windows 10 do not support the Universal model.

VCP v6.7 is a Desktop- (server-) targeted driver. It works on "Windows 7 and later" … which includes Windows 10.  We are no longer actively improving VCP v6.7, and consequently no longer releasing subsequent versions in this version line.  This broadly aligns with Microsoft's support of Windows 7, 8, 8.1 life-cycle.

Mike, can you attach the setupapi.dev.log log file from your computer, please?  Assuming you've installed Windows 10 to the default disk and location you'll find it under C:\Windows\INF\  It is a text file, it contains time-stamped log entries from Windows as it associates drivers with devices, from oldest to newest.  If you can attach it, tell us the VID/PID of your device (or, tell us it's the default if those are not changed), and the time at which you attempted the install.  Better, disconnect the device, re-connect it, take a note of the time you did that and look a the last entries in that file.  That's a good place to star to help us help you.

OP,

Can you send me Code.exe? Is that the process you run to create this system crash? And a description of how/what set up I need to repro?

If not, can you get me a MEMORY.DMP file?  (I have one or two from other infrequent reports of same 10D crash).

Not that it helps you, but I do already have this as an issue: dev Jira ticket# MCUSW-429.

Still issues here?

VCP v10.1.7 (and later as subsequent releases are released) is available from Windows Update.  (Go to Device Manager, select the device, select "update driver", select "search online").

Windows logs install-related activity -- including errors if they should occur -- in C:\Windows\INF\setupapi.dev.log. The timestamped log entries in that text file are usually the first level of self-support for install issues.

Definitive answer: Yes, CP210x Driver works with Windows 10, build 1809.

Build 1809 is also known as RS5, it came out in  Fall 2018.  Although not strictly necessary, we have a policy/goal to re-Certify the VCP driver against this twice-per-year Windows 10 Updates within one month of the release.  RS5 was released, pulled back, released, pulled back, so there was a bit of churn, but yes, VCP v10.1.5 (and subsequent releases) has been (oldname)"WHQL-Certified" on 1809.  RS6 should be released by Microsoft in "May", and we hope to follow that release by re-Certifying VCP on it shortly thereafter.

The VCP driver is released though Windows Update, so as we re-release it, you can get it there.