updated driver in OOBE(audit mode) no longer selected in norma
in [Device Drivers]
|
Prev: GetJob inside Port Monitor returns different type of pMachineName
Next: NDIS Intermediate Driver Vista Issue
From: Tai-hua Liang on 20 Jan 2010 21:44 To update the driver, we did an 'uninstallation' from control panel and then re-ran setup.exe do install the new one. Does that mean a 'sysprep generalize' will revert all driver installation happened in OOBE? If that's the case, I guess that's the problem as we did use generalize to go back to !audit mode. "Mike [MSFT]" wrote: > 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.
From: Mike [MSFT] on 27 Jan 2010 15:25
Sysprep generalize will remove any machine specific configuration, including any device installs. -Mike "Tai-hua Liang" <TaihuaLiang(a)discussions.microsoft.com> wrote in message news:DA7AC162-EB1D-4005-8FEB-7F5A5F0D6C00(a)microsoft.com... > To update the driver, we did an 'uninstallation' from control panel and > then > re-ran setup.exe do install the new one. > > Does that mean a 'sysprep generalize' will revert all driver installation > happened in OOBE? If that's the case, I guess that's the problem as we > did > use generalize to go back to !audit mode. > > "Mike [MSFT]" wrote: >> 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. |