Prev: Replacing signed drivers during development
Next: WdfUsbTargetDeviceGetInterface fails
From: Tai-hua Liang Tai-hua on 19 Jan 2010 21:37
Greetings,

We're trying to update our mouse filter driver to a newer revision inside
OOBE(audit mode in W7). It seems the updated driver is properly loaded after
rebooting to OOBE; however, if we switch back to normal mode, OS only selects
the old driver.

Is there any way to force the !audit mode OS to load the new driver updated
in OOBE?

Thanks.
From: Mike [MSFT] on 20 Jan 2010 18:30
What's the difference between rebooting to OOBE and switching back to normal
mode? It's not clear from that description what you mean. What process are
you using to update the filter driver? Unless there is a sysprep generalize
happening after your update it should not revert back, assuming it was
properly updated.

-Mike

"Tai-hua Liang" <Tai-hua Liang(a)discussions.microsoft.com> wrote in message
news:C66AC213-1CB6-4FAE-B48D-A4B7E7D5D1C6(a)microsoft.com...
> Greetings,
>
> We're trying to update our mouse filter driver to a newer revision inside
> OOBE(audit mode in W7). It seems the updated driver is properly loaded
> after
> rebooting to OOBE; however, if we switch back to normal mode, OS only
> selects
> the old driver.
>
> Is there any way to force the !audit mode OS to load the new driver
> updated
> in OOBE?
>
> Thanks.

 | 
Pages: 1
Prev: Replacing signed drivers during development
Next: WdfUsbTargetDeviceGetInterface fails