I am using the 64-bit version of com0com and I am having trouble. I'd like to debug this, but I can not find any free serial port monitor software, like portmon that works with a 64-bit OS. Does anyone know of any? Frequently Asked Questions. 1) My SDRPlay is not found. I need a SIGNED version of com0com for my 64 bit version of Windows. If you download an unsigned.

• Com0com Windows 10

Minor VirtualVP update and signed 64 bit virtual serial driver Weather Software VP Tools (Virtual VP, VP Live, and VP Tools) minor VirtualVP update and signed 64 bit virtual serial driver (3/7) jayhoehn: I am not familiar with using the USB connection with Vantage Pro. I'm not sure how VVP would connect. Maybe someone else can help. I did find out that VSP Manager is not available any longer. Your only other option is to purchase a virtual port driver.

The problem is that microsoft has decided to charge a lot of money to license 64 bit drivers. Here is a link where you can buy one if you want. Hope that helps. Jay Choupie: thank you Jay for your help I bought windows and I don't want to give money for these drivers. Excepted to Tinplate;) Bushman: has the old versions of VSP tinplate: For a while, there was a free virtual serial port driver that was signed. But the author of that driver had to pull it from availability because of a license issue with a third party component utilized in the driver. With that gone, there were no free signed drivers.

To address this issue, I have obtained the certificate necessary to do the signing process, and am donating this service to the com0com open source virtual serial port project. The author of that software has added me as a developer on that project, and I'm working with him to provide signed 64-bit versions. He will put together the next release containing the signed drivers, but I have a version that can be used to beta test. So if a couple people that are already using com0com on 64 bits using windows test mode can email me at support at softwx.com, I will send you the signed version to try out.

I'd like you to take windows out of test mode, test that the driver no longer works in normal windows, then update the driver with files I will send you, then test that the updated driver works. This test will only work if you already have com0com installed, as I don't have a whole installer package built. I only have the new signed driver, catalog, and inf file. Steve tinplate: Ok, I now have the full install for the signed 64 bit version of com0com. So if there are a couple people that didn't want to the the windows test mode thing, aren't using another virtual serial port driver, and want to beta test the signed 64-bit version of com0com, send an email to support at softwx.com Steve Navigation 0 #.

Hello, I use a device driver for my application. This driver file has to be renamed because of which its signature becomes invalid. And hence the driver file and the catalog file need to be digitally-signed again in order to install in a 64 bit OS. I went through the whole process of creating a catalog file using inf2cat then signing the catalog file and driver file using signtool and a digital certificate obtained from Verisign. The signatures have also been verified. I then created a driver package with all the required files for installation including the signed files.

Enabled the test-signing option and rebooted my machine. Running the installation for the driver (using.inf files) worked without any error but there are errors in the device manager that 'Windows cannot verify the digital signatures for the drivers.' Please let me know what I need to do in order to resolve this issue.

Do I have to sign both.cat and.sys files? Thanks, Saritha. Based on your information you are asking your questions in the wrong place. Has links about signed drivers, but you may need to go to MSDN for more assistance. You're not really asking a simple Windows 7 compatibility question. You're asking how to get your modified driver accepted and that would be a question better addressed in a programming and/or development forum. Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question.

This can be beneficial to other community members reading the thread. The verification certificates are placed in the file by the publisher of the driver, noy by Microsoft.

You can try to obtain another copy of the file or you can contact the publisher of the driver. Windows is merely pointing out that it cannot verify the dudgital signature.

You need to go to the Microsoft webpage about digital signatures as this is a forum for Windows 7 and not a programming forum. Has several links to Driver Digital Signatures. Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

I've come to this forum as a last resort because the driver publishers tell me that they have nothing to do with the digital signatures. If the digital signatures are invalid then the signtool should tell me so. When I verify the signatures using signtool, there are no errors.

Also, when I check the properties of the.cat and.sys files, it says that the driver signature is OK. When I install the drivers, the logs say that the drivers are signed and the installation completes without any errors. It's only when I check the device manager that I see the error mentioned above. Could you please help me in this regard or point me in the right direction. I've read a lot of documentation but found no answers to my problem. We use Jungo's WinDriver in order to connect to our instrument. The instrument is a Rheometer.

Jungo provides signed drivers to us. But we rename the driver file with our instrument's name.

We do this because a number of applications use Jungo's Windriver and it may so happen that in our systems or our customer's systems installing our software might overwrite an already existing Windriver file or installing any other application that uses Windriver might overwrite our application's driver file. In order to prevent this overwrite, we rename Windriver's driver file.

Doing so, its signature is invalid. And hence the driver file and the catalog file need to be digitally-signed again in order to install in a 64 bit OS.

Based on your information you are asking your questions in the wrong place. Has links about signed drivers, but you may need to go to MSDN for more assistance. You're not really asking a simple Windows 7 compatibility question. You're asking how to get your modified driver accepted and that would be a question better addressed in a programming and/or development forum.

Com0com Windows 10

Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.