here is window 11 driver
please find the window 11 driver in attachment.
window 11 driver
Please find the window 11 driver at attachment.
So the thing is, I have two devices connected via USB to my windows 11 computer. The two devices use COM10 port because in device manager I only got one "USB serial device" available and is set to COM10. So, the devices are a Turing Smart Screen and an UPS from Salicru. Each one of the devices have a specific software to manage them. Because the devices are detected with the same COM port, I can only use one software at a time. So, the thing I need to know is if with hub4com and com0com it's possible...
Windows Update solved the issue for me on both Windows 10 and 11. Under Windows Update > Advanced options > Toggle on "Receive updates for other Microsoft Products". After toggling on, check for Windows update again.
I am running windows 10 64 bit. Is Com0com used only for software defined radios? If not, I am wanting to have a virtual port directed back to a physical comport. My example will be ito have USB serial port3 to connect with virtual port 10. Can you provide the steps? Thanks
Hi, This error is typical when the driver is not signed and Windows does not allow its installation. Make sure to use the signed driver, which you can find on SourceForge. Have a look at the screenshot. To check whether the driver you're using is signed, right-click the com0com.sys file, go to Properties, and under the Digital Signatures tab, check that there is an entry under Embedded Signatures. In some versions of Windows, the Digital Signatures tab doesn't appear at all — which means the driver...
Hi, This error is typical when the driver is not signed and Windows does not allow its installation. Make sure to use the signed driver, which you can find on SourceForge. Have a look at the screenshot. To check whether the driver you're using is signed, right-click the .sys file, go to Properties, and under the Digital Signatures tab, check that there is an entry under Embedded Signatures. In some versions of Windows, the Digital Signatures tab doesn't appear at all — which means the driver is not...
Hi, This error is typical when the driver is not signed and Windows does not allow its installation. Make sure to use the signed driver, which you can find on SourceForge. Have a look at the screenshot. To check whether the driver you're using is signed, right-click the .sys file, go to Properties, and under the Digital Signatures tab, check that there is an entry under Embedded Signatures. In some versions of Windows, the Digital Signatures tab doesn't appear at all — which means the driver is not...
Hi, This error is typical when the driver is not signed and Windows does not allow its installation. Make sure to use the signed driver, which you can find on SourceForge. Have a look at the screenshot. To check whether the driver you're using is signed, right-click the .sys file, go to Properties, and under the Digital Signatures tab, check that there is an entry under Embedded Signatures. In some versions of Windows, the Digital Signatures tab doesn't appear at all — which means the driver is not...
Hi, This error is typical when the driver is not signed and Windows does not allow its installation. Make sure to use the signed driver, which you can find on SourceForge. Have a look at the screeshot. To check whether the driver you're using is signed, right-click the .sys file, go to Properties, and under the Digital Signatures tab, check that there is an entry under Embedded Signatures. In some versions of Windows, the Digital Signatures tab doesn't appear at all — which means the driver is not...
Hello com0com Developers and Users, Following questions here https://stackoverflow.com/q/79545926/4999991, here https://sourceforge.net/p/com0com/code/, and here https://superuser.com/q/1889354/588662, I'm seeking assistance with installing the com0com virtual serial port driver on my Windows 10 system. I am encountering the "Code 52" error (Windows cannot verify the digital signature) for the com0com devices, preventing the driver from loading. My Environment: Operating System: Windows 10 (Latest...
Additional Troubleshooting Performed: Extracted the certificate from the signed com0com.sys driver and manually added it to both the "Trusted Publishers" and "Root" certificate stores in Windows. Copied the com0com.cat catalog file to the Windows catalog directory (CatRoot). Modified the driver signing policy in the registry. Found that despite all these attempts, Windows still rejects the driver with error 577: "Windows cannot verify the digital signature for this file." The ports are successfully...
Issues with com0com driver installation on Windows 10 with Secure Boot enabled
This is a good point... has anybody succeeded with it?
This is a good point... anybody suceeded with it?
Is this bugfix applied in the latest code? It's just modifying the sizeof(PULONG) to become sizeof(ULONG) on the RtlCopyMemory call for the C0CE_SIGNATURE. Anyone?
That still doesn't answer his question. His question wasn't how to simulate a a random error in order to get the parity correction routine to detect the error. His question was how do you get a parity setting mismatch to actual behave correctly. For a parity setting mismatch to behave correctly, it would need to display ALL ERRORS when the parity is set to EVEN on one port, but ODD on the matching port. When I do that myself, it displays NO ERRORS. This has NOTHING to do with random noise on the...
Such accurate simulation would be useful for testing serial port software under a variety of port setting mismatches, to see what would happen in these real situations. This would allow such tests to be run on a computer without a real serial port, in order to test the behavior of such software (that may at times have wrong settings by accident), so that you can map out its behavior, knowledge that would then be useful when that same software is later run on a computer with real serial ports. Some...
I have installed version 2.2.2.0 and configured the ports as COM3 and COM4. They appear in the com0com section of device manager. However programs like Teraterm don't know that the ports exist. Should the virtual ports also appear in the "Ports" section of device manager? They are not shown there. How do I fix this problem?
I just installed the 2.2.2.0 version. The 52-error is gone, and now it works :)
I just installed the 2.2.2.0 version. The 52-error is gone
Yes, I'm facing the same problem. From reading other posts, this issue has been a real pain over the years... Let's hope an updated signing will come soon
Dear developer team, I am using this project in win10 correctly but in Win11 not working giving the Code 52 message. What should I do for this message? Is there any plan for driver sing for Win 11? Thanks in advance.
I use com0com to set up a pair, COM4 and COM5, just using all the default settings. I wrote a small program to open COM4 and send a binary string. The program successfully opens COM4 and I do not get any errors sending my string. I use PowerShell to open COM5 and ask it to read what comes through. However, nothing comes through. It is my understanding that com0com is used to pass from virtual COM4 to virtual COM5 (in this case), so anything sent to COM4 is received by COM5. Am I misunderstanding...
I've been trying to create a vitual port using com0com. All I get is COM#, and I cannot get an assigned number when I select "use Ports class". I think on my initial download and install I tried to execute setup multiple times. I had some firewall issues and a Microsoft NET download to install. When I finally got com0com to launch, I had six or seven virtual port pairs. I deleted them all. Then I selected "Add Pair" and followed the pdf instructions I was using. But each time I try to add a virtual...
Hello Simon. I have tried the 3.0.0 solution signed by you mentioned in post #c463. Im running w11 23H2 up to date and the device drivers show the same error as before. Have you got any updates? Best regards, Dennis.
Hi Gavin, yes, v.2.2.2 did not have the support for the "Ports" device-class, that only came with 3.0. However I am not sure why you recommend using the older 2.2.2 when there is a "known-good" way of getting com0com 3.0 with Secure Boot active and all. Just see my post #c463 above, I promise it works, Ilast installed com0com on Windows 11 23H2 in January. Best regards!
I installed version 2.2.2.0 on Windows 11 without turning off Secure Boot as per the post by "Oliver Heggelbacher". It works! although N.B. the driver ports won't appear under the "Ports" heading in Device Manager. If you can live with that and the older version then I would encourage giving it a try..
Great job, I really appreciate the effort. 🤘
I have been documenting and archiving the multiple different various approaches that have been reported to work in various circumstances at the link below. Obviously, not all approaches might work for everyone, so some trial and error might be needed in order to determine what might work best. * https://github.com/BrickBot/Archive/releases/tag/com0com
I figured it out. The Secure Boot feature in the BIOS was turned on. The other 2 PC's I have which use com-0-com had Secure Boot disabled. As soon as I disabled it on this PC, com-0-com started working fine.
I can install the latest version, 3.0.0.0-i386-and-x64-signed with no install errors. I can open com-0-com and setup new virtual ports, no errors. But in Windows Device Manager I get the following error on all the ports I setup: "Windows cannot verify the digital signature for the drivers required for this device. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source. (Code 52)". This in on...
hub4com doesn´t work windows 10
hub4com doesn´t work windows 10
Hi I want to check use port class (tick) from command prompt through command ""setupc.exe" INSTALL 0 PortName=COM1,EmuBR=yes PortName=COM10,EMUBR=yes" ?Can you please provide the command because I see EMUOVVERRun, HiddenMode etc for all other except use port class
Hi I want to check use port class (tick) from command prompt through command ""setupc.exe" INSTALL 0 PortName=COM1,EmuBR=yes PortName=COM10,EMUBR=yes" ?
Hello, I'm experiencing an issue with hub4com where it doesn't obey the baud rate configuration when opening the PC's port. I've set the baud rate to 115200, but when the port is actually opened, it runs at 921600. Due to this discrepancy, I'm unable to communicate with an external device. Here is a snippet of the command line arguments/configurations that I used: D:\Downloads\hub4com>hub4com --baud=115200 --route=all:all //./COM16 //./C1 //./C2 //./COM16 Open("//./COM16", baud=921600, data=8, parity=no,...
Hi Simon, thanks for the message, great. Sad, that the project is abandoned. Your signature must be from one of the cross certificates still valid: https://learn.microsoft.com/en-us/windows-hardware/drivers/install/cross-certificates-for-kernel-mode-code-signing Before, the list was very long. Now, most certificates expired. Greetings from Naumburg (Saale), Harald
Hi all, Next to the possible update solution Jean mentions, I'd like to gently nudge you to have a look at this post: https://sourceforge.net/p/com0com/bugs/32/#c463 There is a signed version of 3.0.0 that works because it was built pre-Win10-build1607, therefore the signing cert is accepted even on Windows11 to this day. Try it, I honestly think it will work for y'all.
Hi Harald, I'm very glad the good old 3.0 package still works for you. Thanks also to the reference to the signing tutorial. It amazes me to this day that the old package I made back in 2013 still works. It was assembled from separate x32 and x64 packages I found floating around the 'net, that were I believe signed in 2012 by Christos Nikolaou. Sadly, I think the original author of com0com has gone inactive, and therefore there's nobody able to update the download sources in this SourceForge project....
Friendly nudge to have a look at this post: https://sourceforge.net/p/com0com/bugs/32/#c463 There is a signed version of 3.0.0 that works because it was built pre-Win10-build1607, therefore the signing cert is accepted even on Windows11 to this day. Try it, I honestly think it will work for y'all.
Dear Team, thank you for the great software ! I can confirm, that on my WIndows 10 64 bit box: The version in the download does not work The version in the post above by Simon Harston - 2021-09-16 works It would be great to have this version in the official distribution, so people don't stumble over the issue. I personally liked this tutorial about driver signing: https://www.davidegrayson.com/signing/ The issue is, that Microsoft has expired most cross certificates. My company has recently purchased...
Hi Sorry for the stupid question. I use a W7 Desktop as an replacement for an new Pc who got broken. I also use a USB GNSS Receiver who use Port 5. I install both Software one for the Port Splitter and the Hub. I cant get the Hub running to split the GNSS Data from Port 5 to other Virtual Ports. Can someone pls tell me what Variables I need to use? Thanks
Hello, The company I represent wants to use this tool for commercial use, in a simulator which would be provided to their customers. Therefore, I need to have the exact text of the GPL license. Does anyone have it or know where I can find it?! Best regards, M.
Check this answer: https://sourceforge.net/p/com0com/bugs/32/#c463 This works on my Windows 10 21H2.
Hello Regilmar, it's not clear which version of com0com you are using - v.2.2.2 or v.3.0, 32bit or 64bit, signed or unsigned, official version from sourceforge or my "old-therefore-works-even-with-non-Microsoft-signature"-version (see post https://sourceforge.net/p/com0com/bugs/32/#c463). If you can possibly provide more details, maybe also a screenshot of the properties-dialog for the devices showing errors, that might help us find a solution. Cheers!
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
Hi Simon - Life Saver, Years went by, it still works. Thank you!
Should com0com virtual com ports be displayable in Windows 10 Device Manager? If so, how can I make that happen? I've created several pairs that work fine, but are not displayed in "Ports" under Device Manager.
OK. I just noticed the attached list of com0coms in my Device Manager. Questions: What are the differences between the items that say: com0com - bus for serial port pair emulator (8 of these) com0com - bus for serial port pair emulator 1 (COM1 <-> COM2) (3 of these). com0com -serial port emulator (a ton of these)
Should com0com virtual com ports be displayable in Windows 10 Device Manager? If so, how can I make that happen? I've created several pairs that work fine, but are not displayed in Device Manager.
I have a desktop PC program called Faction that connects via COM port to a microcontroller. The microcontroller is on COM1. I have written my own program called 'Spy' that works as a man in the middle. My Spy program connects to COM1 and reads data from it, and it forwards this data on to Virtual COM2. Then I get the 'Faction' program to connect to Virtual COM3. My Spy program is working perfectly: There doesn't seem to be any data loss, and there doesn't seem to be any corruption. But, when the...
Hi. I am trying to virtually pair two ports and read data. I am using terminal to do this. I have created two ports as given below. I write to the COM13 and trying to read data from COM14. But writing is working fine but I couldn't open port COM14 to read data. Can you please help me with this issue? CNCA1 PortName=COM13,EmuBR=yes,EmuOverrun=yes CNCB1 PortName=COM14,EmuBR=yes,EmuOverrun=yes
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...
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).
I ran into the same problem today. The link that Oliver posted (based on Markus' suggestion) worked for me.
We ran into the same issue recently. As mentioned by Markus above, v2.2.2.0 works for us. I tested and confirmed that the com0com V2.2.2.0 x64 signed installer can be installed and used on up-to-date Windows 10 and Windows 11.
We ran into the same issue recently. As mentioned by Markus above, v2.2.2.0 works for us. I tested and confirmed that the com0com V2.2.2.0 x64 signed installer from @vfrolov can be installed and used on up-to-date Windows 10 and Windows 11.
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...
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...
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...
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...
Can anyone create a proper signed version with this bugfix? It's kind of a hassle to have to keep booting into safe mode every time I want to test or use the OUT1/OUT2 extended functionality, because that requires the detection to work (which requires the above bugfix on 64-bit builds (32-bit builds work fine tho, but my OS is 64-bit Windows 10, which doesn't allow it with secure boot etc.)).
OUT1/OUT2 custom output is unstable or not driving at all
Hello I am looking for ARM64 version of Null modem for Win 10/11. Thanks for any help
Hi Alex Bondarenko, do you, by any chance, have the patch you said you'd post? I'm facing the same situation, having to support a protocol that uses the parity bit as 9th bit.
I've managed to confirm the bugfix working as it should (with the proper result when using the bottom RtlCopyMemory patch (replacing "+ sizeof(PULONG)" with " + sizeof(ULONG)")) when using badly/unsigned drivers compiled from the latest source code on sourceforge (3.0.0). Although I can't load said drivers without driver signing protection disabled in Windows 10 x64 because I can't get it to sign the drivers properly for Windows to accept it as a valid driver to load (even when setting my own signature...
IOCTL_SERIAL_GET_MODEM_CONTROL signature bug
I want to see the state of the DSR pin from 2 programs. For this I create two virtual Port Pairs CNCA1 - CNCB1 and CNCA2 - CNCB2 and connect with hub4com the actual COM-Port I am interested in with these pairs. hub4com --route=All:All \.\COM2 \.\CNCA1 \.\CNCA2 this seems to work, but the problem is, that the pin I am interested in does not send but receives. I see there is an invert option, does this only invert the current status of DSR, or does it send this state to the other coms DTR. I think...
Hi, I've just been experimenting with Hub4Com on Windows 11. I'm trying to take streaming input from a physical device and direct it to multiple apps at the same time. For the sake of discussion let's say the physical port is COM1. I have a some virtual port pairs set up with com0com (COM99<-->CNCB0 and COM98<-->CNCB1), and I've been using the following command line: > .\hub4com --baud=115200 \\.\COM1 \\.\CNCB0 \\.\CNCB1 I can open COM99 and get data, and then I can open COM98 and get data. But if...
I\m try to enable "emulate baudrate" an enable "buffer overrun", bot no luck
Hi all, a found a possible bug in v3.0.0.0 version of com0com. I was created a pair COM59 COM60/ Open COM60 in Putty terminal, and COM60 in my test program: #include "stdafx.h" #include <Windows.h> DWORD WINAPI ThFu(void *p) { HANDLE h = (HANDLE)p; DWORD dw; char buf[2]; buf[0]='z'; while(1) { Sleep(2000); WriteFile(h,buf,1,&dw,NULL); printf("w\n"); } } int _tmain(int argc, _TCHAR* argv[]) { HANDLE hf[3]; COMMTIMEOUTS ts; DWORD dw; COMMCONFIG cc; char buf[128]; buf[0]='r'; hf[2]= CreateFile("\\\\.\\COM59",GENERIC_READ|GENERIC_WRITE...
Try com0com from PETE’S BLOG (https://pete.akeo.ie/) => http://files.akeo.ie/blog/com0com.7z [1] [1] https://damn99.com/en/2021-03-13-com0com/
I've used com0com for a couple years but now I am having to reinstall all my software after a SSD upgrade when my hard drive croaked. Use com0com with SDRPlay Uno software. It works after starting the computer with Uno and another software (Black Cat WeFax) but if I then listen to radio frequencies and go back to WeFax it doesn't work. I went back a version that had the signed certificate but same issue. Any solutions or input on what to try and resolve. Prior to my crash it was always available...
Hi, I am trying to connect software to a virtual 56k modem on my computer. The virtual modem is connected to a remote machine which contains a 56k modem operating on a M2M data SIM card. I don't see any instructions on how to setup virtual ports so would appreciate any help. P.S. The software supplied with the remote machine only allows connection through Com Ports 1 - 4.
I get this same error when installing on Windows 11. Is there a signed com0com for Windows 11 available? Any suggestions if using Windows 11?
Hi Simon, 7 years later, you are still saving my day! It worked great for me. Thanks!
It uses the following packets: 0xFF with the next byte being break(bit 2)/DTR(bit 1)/RTS(bit 0) That one is sent when the connection is made with the TCP server/client, from both sides, to initialize their respective signals from the modem control and line control registers. It's also sent when those lines on the senders side change (by updating those registers). When receiving "0xFF, 0xFF", the other side is literally sending the 0xFF byte. In all other cases, it's a normally sent byte over the...
Dosbox's Nullmodem
No one has an idea? Can I provide more information that would be helpful?
Hi, I use com0com, hub4com and tcp2com to read/write data from/to 2 applications with a real serial port. my problem is when i send a tcp request, the first feedback that i have is the request itself. I think this problem come from the hub4com configuration, all data to COM1 are send back to both virtual port (and send back to the sender). is there a way to disable COM port to send back the request to it's sending port ? thanks My hub4com command : hub4com --baud=9600 --octs=off --bi-route=0:All...
We have a strange phenomenon with this great software. We are using it to make the COM ports on the server available on another host. The problem is that the first time we start hub4com on the client, the connection is not working. But when we start it again (without doing anything on the server) on the client, it is working fine. Of course, we made sure that the server is running well earlier than the client. So, on the server we run hub4com like this, to make COM100 available via TCP on port 10100:...
We have a strange phenomenon with this great software. We are using it to make the COM ports on the server available on another host. The problem is that the first time we start hub4com on the client, the connection is not working. But when we start it again (without doing anything on the server) on the client, it is working fine. Of course, we made sure that the server is running well earlier than the client. So, on the server we run hub4com like this, to make COM100 available via TCP on port 10100:...
We have a strange phenomenon with this great software. We are using it to make the COM ports on the server available on another host. The problem is that the first time we start hub4com on the client, the connection is not working. But when we start it again (without doing anything on the server) on the client, it is working fine. Of course, we made sure that the server is running well earlier than the client. So, on the server we run hub4com like this, to make COM100 available via TCP on port 10100:...
This worked for me, only had to do it once. Thanks!
Go to Device Manager and find the driver under com0com. Open the properties and the Update tab. Click Update Driver; let it try searching (it won't find one on your computer); then let it search Windows Update for a current driver. This will install a new driver in addition to the old bad one. Delete the old bad one. You may need to repeat when you create new port pairs, but it will find the good driver on your PC now.
I found a listing on another page: hub4com usage: hub4com [options] <port0> [options] [<port1> ...]</port1></port0> Common options: --load=[<file>]</file>[,<begin>[,<end>]</end></begin>][:<prms>]</prms> - load arguments (one argument per line) between <begin> and <end> lines from a file <file> (use standard input if empty) and insert them into the command line. The syntax of <prms> is <prm1>[,<prm2>...]</prm2>, where <prmn> will replace %%n%% in the arguments. Do loading since begining if <begin>...
After fighting installation issues related to outdated driver signature, I finally got com0com to work by ignoring the error messages during installation and clicking "continue". Then I found the (bad) device in Device manager (under com0com) and updated it from Windows Update to get the more recent driver from Microsoft. This added another device without the warning triangle. I then deleted the old bad device. I had to do this a couple more times as I added more pairs, but now I could do it by looking...
After fighting installation issues, I finally got com0com to work by ignoring the error messages during installation and clicking "continue". Then I found the (bad) device in Device manager (under com0com) and updated it from Windows Update to get the more recent driver from Microsoft. This added another device without the warning triangle. I then deleted the old bad device. I had to do this a couple more times as I added more pairs, but now I could do it by looking for it on my computer. After that...
I came across this page (actually 3) that was a big help in understanding how to make this work. http://www.rei-labs.net/connecting-multiple-virtual-serial-ports-together/ I was able to get a couple instances of RealTerm to talk to each other, which is a start. Now to figure out Hub4com......
Can someone please produce a text document of the Help file produced when you run hub4cmo without arguments? i can't get any redirection commands to work with it, and it is difficult to work from it onscreen. Thanks, Neil Preston Lee's Summit MO "Never confuse motion with action" - Benjamin Franklin
I am using hub4com as a telnet server redirected to a com port. When I send a BREAK in the telnet client, hub4com reponds with a "unknown code 243". How do I get hub4com to redirect the BREAK to the com port?
Hi! i have a problem with hub4com and Mindeo barcode scanner (cs2290) Initial data local sys - win10, remote - ws2016 local com-port : - COM9 ( scanner mode : Virtual COM port ) local IP 10.8.2.2 (openVPN) hub4com server with cmd line "com2tcp-rfc2217 COM9 7000" or "com2tcp COM9 7000 " (nvm) remote port created by com0com: CNCB10--->COM10 hub4com client with cmd line "com2tcp-rfc2217 \.\CNCB10 10.8.2.2 7000" connection successful!!! what's happening i am using Serial Lab (software) to listen on remote...
Hi Simon, Your setup package worked for me - I installed it on Windows Server 2019. Thanks!
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 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,...
I have 3.0.0 version and the changes in comport.inf doesn't works, any else could resolve this problem?