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)
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!
👍
1
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
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 a globalsign certificate. Globalsign still promisses on its web-site, that drivers may be signed. But this is not the case ;-).
Thank you,
Harald
👍
1
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
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. I fear the only way to "spread the word" about the working 3.0 package is by messages in this forum.
Best regards from Darmstadt to you over there just a bit further in the East :)
Simon
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
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.
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!
Check this answer:
https://sourceforge.net/p/com0com/bugs/32/#c463
This works on my Windows 10 21H2.
Dear Team,
thank you for the great software !
I can confirm, that on my WIndows 10 64 bit box:
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 a globalsign certificate. Globalsign still promisses on its web-site, that drivers may be signed. But this is not the case ;-).
Thank you,
Harald
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. I fear the only way to "spread the word" about the working 3.0 package is by messages in this forum.
Best regards from Darmstadt to you over there just a bit further in the East :)
Simon
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
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.
Great job, I really appreciate the effort. 🤘