The drivers for the ports are rejected by Win10 pro at the moment and switching to tet mode is a nogo at work.
Any chance you can sign the drivers properly? (Otherwise please consider remove the Full win10 compatibility claim)
I am the signer for Windows 10 and as you can see from the screenshots from this link it is working fine under Windows 10 Enterprise x64. I have also test the driver on Windows 10 x64 15.x build and on WIndows 10 Pro and have not encountered any outstanding issue other than what is stated on the known issues.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I think I found the issue. According to Windows Driver Signing Policy "Starting with Windows 10, version 1607, Windows will not load any new kernel-mode drivers which are not signed by the Dev Portal."
There are exceptions though, If your PC was upgraded from an earlier release of Windows to Windows 10, version 1607 the driver should work but for fresh install of Windows 10, version 1607 or later you will have to turn off the Secure Boot from BIOS since the last exception is not applicable as the driver was signed after July 29th 2015.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Can you sign the latest version in bug #33 (I have the bugfix mentioned there)? I tried self-signing it myself(using various methods), but Windows 10 x64 doesn't seem to like it (only when running with driver signing signature enforcing disabled, which needs to be done on every boot of Windows 10 x64).
It's a x64-specific bug issue in the source code that's causing detection issues using the documented method from the source code example.
There's still another weird bug that shows when wiring the OUT1/OUT2 which I didn't figure out though (unstable or non responding behaviour driving them to a single output pin instead of two pins simultaneously (for example OUT1->DSR&CTS works, but OUT1->RI or OUT1->CD fails completely (never raises) or is unstable(seemingly randomly responding or not responding to the output being set on OUT1/OUT2 at all, staying low at the CD input))).
Last edit: superfury1 2022-08-27
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
sadly, as described by CyberCircuits in the message just above yours, changes to Microsofts signing policies mean no new signings can happen apart from by MS themselves. So we are stuck either with the Test Mode hassle, or an old version of com0com from times before the policy change (see my message from September 2021 below, obviously that version is before your bugfix for #33).
A weird thought: you wrote that the 32-bit version doesn't expose the bug. So maybe you could try force-installing the 32-bit version on your 64-bit machine and crossing all fingers, maybe it works? I have uploaded the really old, but signed, and because of being old Windows-accepted, 32-bit-only installer here: http://radio.jsh.de/com0com_x32.zip
Please write back here if that worked, if not I'll delete that ZIP so as not to trick others into installing something that's actually useless.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Tried installing it (confirming to install it when it complains about x64 arch of my device).
It started spouting weird errors when installing.
Then, running setupc.exe, it also spouted errors and didn't work at all (couldn't even add the device).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
OK, I feared that would happen. I did, in fact, just try it on a spare laptop of mine as well. I also saw error messages during install and after install even setupc was missing. I then unpacked the setup.exe (it is basically a ZIP with an installer-stub, so for example 7zip can unpack it) and copied the missing files into the installation folder. Then I right clicked on each of the INF-files and chose "Install". And then I tried running setupg again. It worked, and I was successfully able to create a CNC-port pair, but I was not successful installing a "COM-class" port. So... maybe you only need a CNC-pair, in that case maybe you can follow the above description. If you need a COM-port (a virtual one nonetheless), I fear there's nothing I can do. Good luck!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks Ionut. Can you send me the screenshot of winver output please? I will try to replicate and possible re-sign the drivers with a different certificate.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Please note it is not advisable to Enable Test Mode due to security implications on your system. However if you are a developer and really need to use this software you can use the workaround as suggested on the link above.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello, what does it take to have com0com signed via DevPortal? I've some hardware emulators that have com0com integrated and it's sad to switch to another solution just because of some policy. Turning off secure boot is no-go on computers w/BitLocker
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
So installing version 2.2 on a system with Windows 10 greater than 1607 works?
If not, there are thousands of people that depend on this. I would be willing to foot the bill for the cost of getting it signed.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Yes, works for me even with Bitlocker in work environment. I’m not sure about every configuration but mine works ok. Be sure to delete version 3.0 first
So installing version 2.2 on a system with Windows 10 greater than 1607 works?
If not, there are thousands of people that depend on this. I would be willing to foot the bill for the cost of getting it signed.
Status: open
Group: v1.0 (example)
Created: Thu Oct 18, 2018 07:29 AM UTC by Jes
Last Updated: Thu Feb 25, 2021 01:52 PM UTC
Owner: nobody
The drivers for the ports are rejected by Win10 pro at the moment and switching to tet mode is a nogo at work.
Any chance you can sign the drivers properly? (Otherwise please consider remove the Full win10 compatibility claim)
I use com0com in a teaching environment and have run into this problem.
Depending on the version of win10 (home/pro/education and version number) that particular students have and whether it s a clean install or upgraded v3.0 of com0com may or may not work.
v2.2 signed is working fine.
Using test mode etc for v3.0 not really a workable solution in our case.
Any news on getting the signing issue with v3.0 resolved?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi folks, I think(!) I can provide com0com 3.0 as a signed version of the installer including the setup-GUI. I made it in 2013 using separately signed versions of the 32- and 64-bit versions that I found back in 2012, and then forgot about it until I received feedback from a user who said she couldn't install on the newest Win10 build. Reading here above that Win10 build 1607 might have changed procedures, I just now tried running my installer on a laptop that has certainly never seen com0com before, and it ran without problems. I checked back with the user and found she had a different problem, which we also solved. So... you are all very welcome to try this version of com0com - I promise it's legitimate: http://radio.jsh.de/com0com.zip
👍
4
❤️
1
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi!
I need to install the emulator on Windows 10, version 20h2. But Windows does not recognize it.
Would you have any suggestions?
On older versions of Windows 10 it works normally
Regards
+1
+1
I am the signer for Windows 10 and as you can see from the screenshots from this link it is working fine under Windows 10 Enterprise x64. I have also test the driver on Windows 10 x64 15.x build and on WIndows 10 Pro and have not encountered any outstanding issue other than what is stated on the known issues.
Hello, as you can see in the attachment, it won't work on Win10 Enterprise, 10.0.16299. Do you need any info about my system?
I think I found the issue. According to Windows Driver Signing Policy "Starting with Windows 10, version 1607, Windows will not load any new kernel-mode drivers which are not signed by the Dev Portal."
There are exceptions though, If your PC was upgraded from an earlier release of Windows to Windows 10, version 1607 the driver should work but for fresh install of Windows 10, version 1607 or later you will have to turn off the Secure Boot from BIOS since the last exception is not applicable as the driver was signed after July 29th 2015.
Can you sign the latest version in bug #33 (I have the bugfix mentioned there)? I tried self-signing it myself(using various methods), but Windows 10 x64 doesn't seem to like it (only when running with driver signing signature enforcing disabled, which needs to be done on every boot of Windows 10 x64).
It's a x64-specific bug issue in the source code that's causing detection issues using the documented method from the source code example.
There's still another weird bug that shows when wiring the OUT1/OUT2 which I didn't figure out though (unstable or non responding behaviour driving them to a single output pin instead of two pins simultaneously (for example OUT1->DSR&CTS works, but OUT1->RI or OUT1->CD fails completely (never raises) or is unstable(seemingly randomly responding or not responding to the output being set on OUT1/OUT2 at all, staying low at the CD input))).
Last edit: superfury1 2022-08-27
Hi Superfury,
sadly, as described by CyberCircuits in the message just above yours, changes to Microsofts signing policies mean no new signings can happen apart from by MS themselves. So we are stuck either with the Test Mode hassle, or an old version of com0com from times before the policy change (see my message from September 2021 below, obviously that version is before your bugfix for #33).
A weird thought: you wrote that the 32-bit version doesn't expose the bug. So maybe you could try force-installing the 32-bit version on your 64-bit machine and crossing all fingers, maybe it works? I have uploaded the really old, but signed, and because of being old Windows-accepted, 32-bit-only installer here: http://radio.jsh.de/com0com_x32.zip
Please write back here if that worked, if not I'll delete that ZIP so as not to trick others into installing something that's actually useless.
Tried installing it (confirming to install it when it complains about x64 arch of my device).
It started spouting weird errors when installing.
Then, running setupc.exe, it also spouted errors and didn't work at all (couldn't even add the device).
OK, I feared that would happen. I did, in fact, just try it on a spare laptop of mine as well. I also saw error messages during install and after install even setupc was missing. I then unpacked the setup.exe (it is basically a ZIP with an installer-stub, so for example 7zip can unpack it) and copied the missing files into the installation folder. Then I right clicked on each of the INF-files and chose "Install". And then I tried running setupg again. It worked, and I was successfully able to create a CNC-port pair, but I was not successful installing a "COM-class" port. So... maybe you only need a CNC-pair, in that case maybe you can follow the above description. If you need a COM-port (a virtual one nonetheless), I fear there's nothing I can do. Good luck!
Thanks Ionut. Can you send me the screenshot of winver output please? I will try to replicate and possible re-sign the drivers with a different certificate.
Hello again, here you have it. If you need any info, don't ezitate. :)
Last edit: Jark 2019-02-04
Any news? :)
Unfortunately there were policy changes since the release of Windows 10, version 1607.
Please have a look here for workaround: https://sourceforge.net/projects/signed-drivers/files/com0com/
Please note it is not advisable to Enable Test Mode due to security implications on your system. However if you are a developer and really need to use this software you can use the workaround as suggested on the link above.
Hi There,
Is there any idea when this problem will have a solution?
Are someone working on this?
Obs.: turn off secure boot is not a good solution.
Thanks,
Hello, what does it take to have com0com signed via DevPortal? I've some hardware emulators that have com0com integrated and it's sad to switch to another solution just because of some policy. Turning off secure boot is no-go on computers w/BitLocker
For the meantime, i've solved the issue by using signed x64 version 2.2 of com0com which works just fine
So installing version 2.2 on a system with Windows 10 greater than 1607 works?
If not, there are thousands of people that depend on this. I would be willing to foot the bill for the cost of getting it signed.
Yes, works for me even with Bitlocker in work environment. I’m not sure about every configuration but mine works ok. Be sure to delete version 3.0 first
Related
Bugs: #32
I use com0com in a teaching environment and have run into this problem.
Depending on the version of win10 (home/pro/education and version number) that particular students have and whether it s a clean install or upgraded v3.0 of com0com may or may not work.
v2.2 signed is working fine.
Using test mode etc for v3.0 not really a workable solution in our case.
Any news on getting the signing issue with v3.0 resolved?
Hi folks, I think(!) I can provide com0com 3.0 as a signed version of the installer including the setup-GUI. I made it in 2013 using separately signed versions of the 32- and 64-bit versions that I found back in 2012, and then forgot about it until I received feedback from a user who said she couldn't install on the newest Win10 build. Reading here above that Win10 build 1607 might have changed procedures, I just now tried running my installer on a laptop that has certainly never seen com0com before, and it ran without problems. I checked back with the user and found she had a different problem, which we also solved. So... you are all very welcome to try this version of com0com - I promise it's legitimate:
http://radio.jsh.de/com0com.zip
Hi Simon, today I stumbled upon this issue, tried your setup package and it worked great.
You posted your fix just in time to save me!
Thank you!
Hi Simon,
Your setup package worked for me - I installed it on Windows Server 2019.
Thanks!
Hi Simon,
7 years later, you are still saving my day! It worked great for me.
Thanks!
Hi Simon - Life Saver,
Years went by, it still works.
Thank you!
Hi!
I need to install the emulator on Windows 10, version 20h2. But Windows does not recognize it.
Would you have any suggestions?
On older versions of Windows 10 it works normally
Regards