Prev: Intercepting and blocking registry access
Next: AQ Test "RunFirstRun" for MultimediaControllers
From: Chris on 15 Jun 2010 11:30
On Jun 14, 9:52 am, "Michael Reim"
<nospammichaelDOTr...(a)REMOVENOSPAMANDCAPShelmut-fischer.denospam>
wrote:

> But I don't think that this will work if the user takes the hardware first
> way and lets the system search for a driver on disk.

Well, you're probably right. Can't you just delete the INF's from C:
\windows\inf by hand then?
From: eagersh on 15 Jun 2010 13:48
On Jun 15, 9:30 am, Chris <chris.aselt...(a)gmail.com> wrote:
> On Jun 14, 9:52 am, "Michael Reim"
> <nospammichaelDOTr...(a)REMOVENOSPAMANDCAPShelmut-fischer.denospam>
> wrote:
>
> > But I don't think that this will work if the user takes the hardware first
> > way and lets the system search for a driver on disk.
>
> Well, you're probably right.  Can't you just delete the INF's from C:
> \windows\inf by hand then?

If he targeting Windows 7 it could not help. He needs to remove all
entries in \DriverStore directory which is not accessible for
deleting.
He should do uninstall/scan/uninstall in Device Manager until all
entries of driver in \DriverStore would be removed.

Igor Sharovar
First  |  Prev  | 
Pages: 1 2
Prev: Intercepting and blocking registry access
Next: AQ Test "RunFirstRun" for MultimediaControllers