CP210x Driver v10.1.1 issue with Windows 10, build 1803
05/122/2018 | 01:57 PM
Hi All,
We've recently become aware of an issue with a new update to Windows 10 and our CP210x VCP "Universal" Driver for Windows 10, driver version v10.1.1. When attempting to install the driver, an error is given by Windows that states "A service installation section in this INF is invalid." This occurs because Windows has changed drive INF requirements slightly, and our current driver's INF file does not meet these requirements.
We currently are working to fix this issue, although due to testing and recertification requirements, we do not expect the fixed driver to be available until mid-June.
A work-around exists currently, but it involves manually editing the .INF file for the driver. This causes another issue - the driver is no longer signed in this case, so the driver must be forced to install, and Windows will show a warning that the driver is unsigned.
Once these changes are made, attempt to re-install the driver. A warning will be shown that the driver is unsigned, but you can ignore this for now. If you do not receive a warning issue, or if Windows refuses to install the unsigned driver (you may get an error about the hash being invalid), you can disable driver signing enforcement by following these instructions: https://www.maketecheasier.com/install-unsigned-drivers-windows10/
Alternatively, rolling back to a previous build of Windows also resolves the issue.
VCP Drivers
Discussion Forums
Interface
Unanswered
Thanks a lot for having so quickly published a workaround. Rolling back to previous version of Windows is so time-consuming and worrying. I do appreciate follow-up by client-centric companies like yours.
2
PLEASE!!! There is another issue!
Using the .NET serial port class (.NET 4.0) will fail on a port.Open(comport, 115200); You driver reports that the maximum baud rate is 23800.
Tom
1
I have the same issue like Tom said.
Using a Terminal program, I can choose any supported baud rate I want, but on my .NET application, Visual throws an exception that I have exceeded the maximum baud rate.
0
As far as i know there is a bug in the universal driver. We have plan to give a new version of driver but unfortunately I don't know when Silabs would put that new driver to their website. I send a separate email to discuss this with you.
-------------------------
Visual throws an exception that I have exceeded the maximum baud rate.
I have WIN10 machines (clients) that have received the update. I was able to follow the workaround for the driver issue while testing in my PC, but for the .NET COM PORT problem was not.
Is there any workaround for this?
Thank You
0
I am not sure if your issue is same as the one that Silabs has addressed. I would suggest you create an ticket in our salesforce system and I could give you a test driver, if the test driver could fix your issue, yes we have a solution for it.
Denver
0
Thanks, this workaround solved the installation block on a new computer (Win10/1803) to use a CP2012 USB adapter. Several other computers which had the driver installed prior to their 1803 update continue to work properly, so clearly this is just an installation issue. My students use these adapters, and hopefully you can get updated drivers out soon. Will you update this page and send out email notifications when you do?
0
This is not an installation issue unless the INF file is incorrect. Here is more information: This concerns Amateur radios with built in CP210x USB devices.
Both Icom and Yaesu radios use the CP210x USB UART drivers. Both Icom and Yaesu supply version 6.xx drivers. These work correctly. However I have run into a number of cases in the last few weeks where Windows update has replaced these with your CP210x Universal Windows Drivers. There is a bug in those version 10,x drivers. A simple Port.Open() where the baud rate is greater than 19200 fails saying the maximum supported baud rate is 23800. This happens in Microsoft .NET serial port class. Other software NOT written using .NET works correctly.
This must be fixed!
0
Silabs release a new version of driver, you could try if your issue fixed with this driver:
Was using 10.1.1.
Due to upgrade to Windows 10 1803, 10.1.1 stopped working, therefore installed 10.1.2.
While the new driver installs and works, I am getting serial monitor garbage at the beginning... then all is ok.
Tested at both 115200 and 9600.
Tested with both NodeMCU 1.0 (cp2102) and Feather Huzzah esp8266 (cp2104).
0
Hello All: Is there an update on when the update to the CP210X driver will be released that will fix the Windows 10 INF file issue? I have several machines with this issue. A mid June date was indicated.
thank you
0
Followup from a month ago: I just restored a Windows 10 computer (clean installation) and downloaded all the latest v1803 updates through the 2018-06 Cumulative Update. I plugged in my 2102 adapter and it self-installed, no manual driver download necessary. Looks like Microsoft got this one right. What a difference a month makes. I was hoping to give you some go/no-go feedback about your updated driver but that didn't happen.
0
hi @Erco,
do you mind tell me the vid/pid of your CP210x product?
0
hi @delu Sorry for the delay. My chip came from China so I can't vouch for its authenticity, but I get:
Related: I installed the same adapter on another computer with the 1803 update and the July update, and I had to manually install your new driver, which worked fine.
0
Hello Delu: Do you have an update on the release of the updated driver to fix the Windows 10 build 1803 invalid INF file issue?
CP210x Driver v10.1.1 issue with Windows 10, build 1803
Hi All,
We've recently become aware of an issue with a new update to Windows 10 and our CP210x VCP "Universal" Driver for Windows 10, driver version v10.1.1. When attempting to install the driver, an error is given by Windows that states "A service installation section in this INF is invalid." This occurs because Windows has changed drive INF requirements slightly, and our current driver's INF file does not meet these requirements.
We currently are working to fix this issue, although due to testing and recertification requirements, we do not expect the fixed driver to be available until mid-June.
A work-around exists currently, but it involves manually editing the .INF file for the driver. This causes another issue - the driver is no longer signed in this case, so the driver must be forced to install, and Windows will show a warning that the driver is unsigned.
Firstly, the work-around is as follows:
Download the Windows 10 Universal driver from here: https://www.silabs.com/products/development-tools/software/usb-to-uart-bridge-vcp-drivers
Edit the .inf file with this driver, performing the following modifications:
On or around line 118, change/edit
from this:
to this:
And on or around line 160, change/edit
from this:
to this:
I.e. replace every 13 in the file with 12.
Once these changes are made, attempt to re-install the driver. A warning will be shown that the driver is unsigned, but you can ignore this for now. If you do not receive a warning issue, or if Windows refuses to install the unsigned driver (you may get an error about the hash being invalid), you can disable driver signing enforcement by following these instructions: https://www.maketecheasier.com/install-unsigned-drivers-windows10/
Alternatively, rolling back to a previous build of Windows also resolves the issue.
PLEASE!!! There is another issue!
Using the .NET serial port class (.NET 4.0) will fail on a port.Open(comport, 115200); You driver reports that the maximum baud rate is 23800.
Tom
I have the same issue like Tom said.
Using a Terminal program, I can choose any supported baud rate I want, but on my .NET application, Visual throws an exception that I have exceeded the maximum baud rate.
As far as i know there is a bug in the universal driver. We have plan to give a new version of driver but unfortunately I don't know when Silabs would put that new driver to their website. I send a separate email to discuss this with you.
-------------------------
Visual throws an exception that I have exceeded the maximum baud rate.
-----------------------------
Check Tom's another post.
https://www.silabs.com/community/interface/forum.topic.html/cannot_connect_tocp-d8gJ
Hello @delu
Is there any workaround for the baudrate issue?
I have WIN10 machines (clients) that have received the update. I was able to follow the workaround for the driver issue while testing in my PC, but for the .NET COM PORT problem was not.
Is there any workaround for this?
Thank You
I am not sure if your issue is same as the one that Silabs has addressed. I would suggest you create an ticket in our salesforce system and I could give you a test driver, if the test driver could fix your issue, yes we have a solution for it.
Denver
This is not an installation issue unless the INF file is incorrect. Here is more information: This concerns Amateur radios with built in CP210x USB devices.
Both Icom and Yaesu radios use the CP210x USB UART drivers. Both Icom and Yaesu supply version 6.xx drivers. These work correctly. However I have run into a number of cases in the last few weeks where Windows update has replaced these with your CP210x Universal Windows Drivers. There is a bug in those version 10,x drivers. A simple Port.Open() where the baud rate is greater than 19200 fails saying the maximum supported baud rate is 23800. This happens in Microsoft .NET serial port class. Other software NOT written using .NET works correctly.
This must be fixed!
Silabs release a new version of driver, you could try if your issue fixed with this driver:
https://www.silabs.com/products/development-tools/software/usb-to-uart-bridge-vcp-drivers
Was using 10.1.1.
Due to upgrade to Windows 10 1803, 10.1.1 stopped working, therefore installed 10.1.2.
While the new driver installs and works, I am getting serial monitor garbage at the beginning... then all is ok.
Tested at both 115200 and 9600.
Tested with both NodeMCU 1.0 (cp2102) and Feather Huzzah esp8266 (cp2104).
Hello All: Is there an update on when the update to the CP210X driver will be released that will fix the Windows 10 INF file issue? I have several machines with this issue. A mid June date was indicated.
thank you
hi @Erco,
do you mind tell me the vid/pid of your CP210x product?
hi @delu Sorry for the delay. My chip came from China so I can't vouch for its authenticity, but I get:
USB\VID_10C4&PID_EA60&REV_0100
USB\VID_10C4&PID_EA60
Related: I installed the same adapter on another computer with the 1803 update and the July update, and I had to manually install your new driver, which worked fine.
Hello Delu: Do you have an update on the release of the updated driver to fix the Windows 10 build 1803 invalid INF file issue?
thank you