Weird behavior: Driver trying to access registry?

Hello all,
I have a legacy driver that is being loaded. The driver needs to search the
registry for certain keys so it could grab certain values. When the driver
is loaded with OSR Driver Loader when the machine is already loaded up, the
driver is able to grab the keys successfully. If I have the driver loaded
when the machine is booting by installing the driver, I get error 0xc0000034
(object name not found). Is it possible I am loading before the registry
has time to initalize? Is that why it does not work when my driver is
loading? Also, is there a way around this?

Thanks
J

Maybe it would help if you provided a little less information - NOT!!! Keys for drivers are available even for boot start drivers. My suspicion is that you think there is a user logged in during boot and trying to read a key from there or some software hive, neither of which are present during boot. Did you read the page in the WDK titled “Overview of Registry Keys”?

“Jonathon” wrote in message news:xxxxx@ntdev…
Hello all,

I have a legacy driver that is being loaded. The driver needs to search the registry for certain keys so it could grab certain values. When the driver is loaded with OSR Driver Loader when the machine is already loaded up, the driver is able to grab the keys successfully. If I have the driver loaded when the machine is booting by installing the driver, I get error 0xc0000034 (object name not found). Is it possible I am loading before the registry has time to initalize? Is that why it does not work when my driver is loading? Also, is there a way around this?

Thanks
J

What key path is not found? Something under HKLM\software ? If so, the software key is loaded very late in boot and there is no notification you can register for that tells you when it is loaded.

d

Sent from my phone with no t9, all spilling mistakes are not intentional.


From: Jonathon
Sent: Thursday, May 14, 2009 9:17 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] Weird behavior: Driver trying to access registry?

Hello all,

I have a legacy driver that is being loaded. The driver needs to search the registry for certain keys so it could grab certain values. When the driver is loaded with OSR Driver Loader when the machine is already loaded up, the driver is able to grab the keys successfully. If I have the driver loaded when the machine is booting by installing the driver, I get error 0xc0000034 (object name not found). Is it possible I am loading before the registry has time to initalize? Is that why it does not work when my driver is loading? Also, is there a way around this?

Thanks
J
— NTDEV is sponsored by OSR For our schedule of WDF, WDM, debugging and other seminars visit: http://www.osr.com/seminars To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

Thanks guys for the reply. Yeah, I am trying to access
“\Registry\Machine\Software.…” So I guess the software key is not loaded
yet :frowning: Are there ways around this? It’s really important that I get this
information from the key.
David, would you happen to have the link to that page? I tried googling it
and I couldn’t find it.

thanks

J

On Thu, May 14, 2009 at 9:53 PM, Doron Holan wrote:

> What key path is not found? Something under HKLM\software ? If so, the
> software key is loaded very late in boot and there is no notification you
> can register for that tells you when it is loaded.
>
> d
>
> Sent from my phone with no t9, all spilling mistakes are not intentional.
>
> ------------------------------
> From: Jonathon
> Sent: Thursday, May 14, 2009 9:17 PM
> To: Windows System Software Devs Interest List
> Subject: [ntdev] Weird behavior: Driver trying to access registry?
>
> Hello all,
> I have a legacy driver that is being loaded. The driver needs to search
> the registry for certain keys so it could grab certain values. When the
> driver is loaded with OSR Driver Loader when the machine is already loaded
> up, the driver is able to grab the keys successfully. If I have the driver
> loaded when the machine is booting by installing the driver, I get error
> 0xc0000034 (object name not found). Is it possible I am loading before the
> registry has time to initalize? Is that why it does not work when my driver
> is loading? Also, is there a way around this?
>
> Thanks
> J
> — NTDEV is sponsored by OSR For our schedule of WDF, WDM, debugging and
> other seminars visit: http://www.osr.com/seminars To unsubscribe, visit
> the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>

Right. This key isn’t available at boot time.

The best you can do is wait for the system to start, and access the data then. Or, have the driver access the registry data during shutdown and cache the data in its own device key (for example) which is accessible during boot.

Peter
OSR

If you need to retrieve registry data at boot start time, then you really should store it under your driver parameters key.

  • S

From: Jonathon
Sent: Friday, May 15, 2009 06:14
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] Weird behavior: Driver trying to access registry?

Thanks guys for the reply. Yeah, I am trying to access “\Registry\Machine\Software.…” So I guess the software key is not loaded yet :frowning: Are there ways around this? It’s really important that I get this information from the key.

David, would you happen to have the link to that page? I tried googling it and I couldn’t find it.

thanks

J

On Thu, May 14, 2009 at 9:53 PM, Doron Holan > wrote:
What key path is not found? Something under HKLM\software ? If so, the software key is loaded very late in boot and there is no notification you can register for that tells you when it is loaded.

d

Sent from my phone with no t9, all spilling mistakes are not intentional.

________________________________
From: Jonathon >
Sent: Thursday, May 14, 2009 9:17 PM
To: Windows System Software Devs Interest List >
Subject: [ntdev] Weird behavior: Driver trying to access registry?

Hello all,

I have a legacy driver that is being loaded. The driver needs to search the registry for certain keys so it could grab certain values. When the driver is loaded with OSR Driver Loader when the machine is already loaded up, the driver is able to grab the keys successfully. If I have the driver loaded when the machine is booting by installing the driver, I get error 0xc0000034 (object name not found). Is it possible I am loading before the registry has time to initalize? Is that why it does not work when my driver is loading? Also, is there a way around this?

Thanks
J
— NTDEV is sponsored by OSR For our schedule of WDF, WDM, debugging and other seminars visit: http://www.osr.com/seminars To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer


NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

— NTDEV is sponsored by OSR For our schedule of WDF, WDM, debugging and other seminars visit: http://www.osr.com/seminars To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer