CODEWITHSUNDEEP
windows-servicesdevice-driver
9b42f4
9b42f4

Reputation: 13

service created but not started

I am trying to run a driver I created as a service. I managed to create a service out of the driver (using "sc.exe create ..."): The service now appears in the registry (under HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/services/mydriver). However the service cannot be started! When I use net start [myservice], I get the following output:

error 1275: This driver has been blocked from loading

One thing looked suspicious to me: The entry in the registry for my driver: The value of "ImagePath" was "\??[correct path]". I manually removed the "\??\" so that the correct path was left. However it did not solve the problem, instead I got an other error message (Error 123: The filename, directory name, or volume label syntax is incorrect).

By searching on the internet, I found out that this error 1275 indicates that a key in the registry is missing or corrupted. This makes sense as I modified it manually, so the value of "ImagePath" is probably corrupted. However I don't see anything wrong with the value I entered:

"C:\ledrivertest\driver1\bin\hello.sys"

Is there some kind of special syntax for the path of a driver binary which I don't know about?

I use Windows 7.

Thanks in advance

Upvotes: 1

Views: 1876

Answers (1)

David Heffernan
David Heffernan

Reputation: 613352

Since you are running on a 64 bit system, and you haven't signed the driver, the most likely explanation for error 1275 is that Windows blocked the driver due to it being unsigned.

Upvotes: 1

Related Questions