T
TimmyJW
Guest
A customer is getting a Code 52 code signing error when trying to install our driver on a Windows 10 system. The same device works just fine for my Windows 10 system I know the driver is signed as I did it myself. I'm banging my head here to find an explanation but I can't find answers. Any suggestions on what to check or ideas to try?
Everything seems to go back to the same set of steps and none of them are helpful. Some refer to USB devices and this is not such a device. Others to reinstall the drive or get an update. There is no update since I wrote the driver and know it works just fine. I can't ask a customer to disable driver signature enforcement since that doesn't really identify a problem and I know the driver is signed. When the user installs the driver it shows a signature but when they complete the process it turns a code 52 anyway. All other posts on this topic seem to follow paths that don't apply to my situation. Thoughts/suggestions?
Continue reading...
Everything seems to go back to the same set of steps and none of them are helpful. Some refer to USB devices and this is not such a device. Others to reinstall the drive or get an update. There is no update since I wrote the driver and know it works just fine. I can't ask a customer to disable driver signature enforcement since that doesn't really identify a problem and I know the driver is signed. When the user installs the driver it shows a signature but when they complete the process it turns a code 52 anyway. All other posts on this topic seem to follow paths that don't apply to my situation. Thoughts/suggestions?
Continue reading...