After a recent update to windows, the signed version of com0com is no longer working. The error showing in the device manager is as follows:
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)
Is there an update to the signed installation?
Thanks,
Kevin Gregory
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Just had the same problem on Windows 7 (64bit) after installing windows update KB3033929.
Uninstalling the update got the driver working again. http://support.microsoft.com/kb/3033929
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
We have the same problem on several computers with Windows 7 (64 bit). Disabling driver signature verification does not help.
The only way in which it all works is to Disable the verification and install unsigned version of the com0com.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm having this issue right now. I was troubleshooting a completely different issue, so I uninstalled and reinstalled com0com. Now none of my previously working ports are working and I have the same Code 52 as stated above. My computer did update some things also recently, but windows won't let me revert.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Possible Solution
Win10: Install driver 3.0, in device manager driver is marked as invalid.
Now double click on driver and perform update of driver, searching windows update. On windows update install optional driver. After Update driver signature shall be ok.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
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.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
After a recent update to windows, the signed version of com0com is no longer working. The error showing in the device manager is as follows:
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)
Is there an update to the signed installation?
Thanks,
Kevin Gregory
What Windows you use?
Win7 ultimate 64bit
I can't reproduce the problem.
installed Win7 enterprise 64bit (evaluation copy)
installed com0com-2.2.2.0-x64-fre-signed.zip
tested com0com - OK
done complete Windows Update
tested com0com - OK
uninstalled com0com
installed com0com-2.2.2.0-x64-fre-signed.zip
tested com0com - OK
Just had the same problem on Windows 7 (64bit) after installing windows update KB3033929.
Uninstalling the update got the driver working again.
http://support.microsoft.com/kb/3033929
We have the same problem on several computers with Windows 7 (64 bit). Disabling driver signature verification does not help.
The only way in which it all works is to Disable the verification and install unsigned version of the com0com.
Same issue, same configuration - Windows 7 64 bit.
Vyacheslav, any updates from you?
I'm having this issue right now. I was troubleshooting a completely different issue, so I uninstalled and reinstalled com0com. Now none of my previously working ports are working and I have the same Code 52 as stated above. My computer did update some things also recently, but windows won't let me revert.
Possible Solution
Win10: Install driver 3.0, in device manager driver is marked as invalid.
Now double click on driver and perform update of driver, searching windows update. On windows update install optional driver. After Update driver signature shall be ok.
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.