Simon Harston

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!

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.

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!

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...

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...

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,...