When I used to debug on Windows XP and wanted to change a driver, I just copied the new driver into Windows\system32\drivers, replacing the old driver. And restarted the machine.
When I try to do this with Windows 7, the operating system replaces the new driver with a copy of the old one. I see a copy of the old driver in Windows\system32\DriverStore\FileRepository<drivername>. When I try to copy my new driver into the \FileRepository directory, the system does not allow me to do this, even though I am logged in as administrator.
When I used to debug on Windows XP and wanted to change a driver, I just
copied the new driver into Windows\system32\drivers, replacing the old
driver. And restarted the machine.
When I try to do this with Windows 7, the operating system replaces the new
driver with a copy of the old one. I see a copy of the old driver in
Windows\system32\DriverStore\FileRepository<drivername>. When I try to copy my new driver into the \FileRepository directory, the system does not allow me to do this, even though I am logged in as administrator.
Tim, that’s what I don’t want to do. Since it involves rebuilding the installer (this take a long time, and is involved). And also uninstalling/reinstalling. On XP, I just replaced the driver in ‘drivers’ and that was that.
You can use the pnputil system command to remove your old driver from the driver store before you use the new one. It’s not perfect (e.g., you have to know what oem* name got used when your driver installed before, and if you’re installed several times you have to remove them one at a time), but it works. Pnputil -? For the usual short form help.
Sketch
Pnputil -e <== gives you a list of all the third party drivers installed and their oem inf names
Pnputil -d oem19.inf <== deletes oem19.inf package from the store.
You might be able to wrest ownership of the file eventually, since you are an administrator.
When I used to debug on Windows XP and wanted to change a driver, I just copied the new driver into Windows\system32\drivers, replacing the old driver. And restarted the machine.
When I try to do this with Windows 7, the operating system replaces the new driver with a copy of the old one. I see a copy of the old driver in Windows\system32\DriverStore\FileRepository<drivername>. When I try to copy my new driver into the \FileRepository directory, the system does not allow me to do this, even though I am logged in as administrator.
For testing purposes I just attach windbg and use .kdfiles to
overwrite the old with the new. Works great, plus it is sticky.
of course it doesn’t work at all for boot drivers, as far as I can
tell, others swear it does, but they have awesomer hacking powers than
I do.
Mark Roddy
On Thu, Oct 21, 2010 at 4:51 PM, wrote: > Tim, that’s what I don’t want to do. Since it involves rebuilding the installer (this take a long time, and is involved). And also uninstalling/reinstalling. On XP, I just replaced the driver in ‘drivers’ and that was that. > > — > 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 >