0

This is a chronological continuation of this question. I have simplified my board so it runs well with the DDK version of BulkUSB on 32bit versions of XP and Vista, but I'm not able to install it on Vista 64.(built with amd64 fre) I've been able to make windows recognize the files it needs to install, using both BulkUSB and USBSamp, but once installed it says 

Windows cannot load the device driver for this hardware.
The driver may be corrupted or missing. (Code 39)

In problem code property in the details, it says 27. When I install it for the first time, it complains about the driver not being digitally signed, and I've tried running:

bcdedit.exe -set loadoptions DDISABLE_INTEGRITY_CHECKS

As there are placed that mention it should make windows run unsigned drivers, but it doesn't help.

If anyone has an insight about this, any help will be appreciated.

Thank you,

Surd.

Edit another part of the deal it took me a long time to find that isn't anywhere in the questions or answers: When unintalling a driver, you either need to check "remove driver" in the device manager or use pnputil -d oem##.inf to remove the driver, otherwise the new drivers won't be used.

Community
  • 1
  • 1
SurDin
  • 3,281
  • 4
  • 26
  • 28

2 Answers2

3

Even after changing the bcedit options, it is impossible to load unsigned drivers under Windows Vista/7 64 bit. You need to make test-signing for the driver. I solved this problem following instructions from "Kernel-Mode Code Signing Walkthrough" document which can be downloaded from the Microsoft site: http://www.microsoft.com/whdc/driver/install/drvsign/kmcs-walkthrough.mspx

Unsigned drivers cannot be loaded by Vista/7 64 bit in any case. Test-signied drivers can be loaded after changing bcedit options. Release-signed drivers are loaded without restrictions, but with warning message. You can make test-signing yourself, following this document instructions. For release-signing, it is necessary to buy a code-signing certificate.

The final (and optional) step is passing the tests from the Windows Logo Kit (WLK). This allows to remove the warning message shown during driver installation.

Alex F
  • 42,307
  • 41
  • 144
  • 212
  • Works like a charm, darling! Although, the walk-through did hint me in on the possibility of running an unsigned driver for debug purposes, by using "Disable Driver Signature Enforcement" in the F8 Boot menu. – SurDin Aug 24 '10 at 07:34
  • Yes, I remember also that unsigned driver can be loaded if remote debugger is active. – Alex F Aug 24 '10 at 07:39
1

I am getting this error message on windows 10: 'Windows cannot load the device driver for this hardware. The driver may be corrupted or missing. (Code 39)'. After following https://www.tenforums.com/tutorials/104025-turn-off-core-isolation-memory-integrity-windows-10-a.html this, the issue is solved for me.

Xiaoqiong
  • 11
  • 1
  • 1
    A link to a solution is welcome, but please ensure your answer is useful without it: [add context around the link](https://meta.stackexchange.com/questions/8231/are-answers-that-just-contain-links-elsewhere-really-good-answers/8259#8259) so your fellow users will have some idea what it is and why it’s there, then quote the most relevant part of the page you're linking to in case the target page is unavailable. [Answers that are little more than a link may be deleted.](https://stackoverflow.com/help/deleted-answers) – Dwhitz May 07 '19 at 07:27