Recent changes to 32: Win10 signed drivers request

#32 Win10 signed drivers request

2024-02-03T10:47:02.940000Z

Great job, I really appreciate the effort. 🤘

#32 Win10 signed drivers request

2024-02-02T03:24:20.761000Z

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

#32 Win10 signed drivers request

2023-09-15T09:45:44.751000Z

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

#32 Win10 signed drivers request

2023-09-15T08:17:43.147000Z

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

#32 Win10 signed drivers request

2023-09-15T07:26:44.440000Z

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

#32 Win10 signed drivers request

2023-04-07T13:15:05.053000Z

Check this answer:
https://sourceforge.net/p/com0com/bugs/32/#c463

This works on my Windows 10 21H2.

#32 Win10 signed drivers request

2023-04-07T12:12:20.530000Z

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!

#32 Win10 signed drivers request

2023-04-06T18:28:38.571000Z

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

#32 Win10 signed drivers request

2023-02-14T03:25:42.604000Z

Hi Simon - Life Saver,

Years went by, it still works.

Thank you!

#32 Win10 signed drivers request

2022-09-10T16:24:58.555000Z

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!