Re: KDMF Driver status Code 37 after Last Known configuration

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

this is an issue with the v1.5 coinstaller. the v1.7 coinstaller in the latest wdk fixes this issue

d

--
Please do not send e-mail directly to this alias. this alias is for
newsgroup purposes only.
This posting is provided "AS IS" with no warranties, and confers no rights.


"hammerli22" <hammerli22@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:DB5C9546-C08B-4C54-8579-BE231415BCEF@xxxxxxxxxxxxxxxx
Hello,

Does any know if this is expected behaviour ?

After loading my kmdf driver (which loaded succesfully) and some other
drivers (non-kdmf) I had to reboot the system. When the system came up, the
other driver
BSOD, so I rebooted to last know configuration and the system came up.
However, my kdmf driver shows up with a yellow bang and Code 37.
Reinstalling my kdmf driver continues returngin Code 37. A check of the
log files
show that the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Wdf\...
are missing. Restoring this directory (from a another computer) of course
did not help and I still got the mysterious Code 37. I suspect last know
configuration restored some other hklm\system\currentcontrolsetXX therefore
wiping out some information. Then only think i could do was reinstall the
O/S. Is this a bug or as expected with a kdmf driver ? Problem was on
computer running LongHorn.

thanks
Mel


.