Hi All,
I use to install the driver using inf file manually.And till now I use to delete the oem.inf and pnf files from the inf folder to uninstall the driver. And whenever I try to install a new driver I delete/uninsatall the old inf and pnf file.
And in my old uninstallations( by deleting inf and pnf files ) I didnt modify or delete any registry settings.
In this case do I want to remove any settings from registry ( for ex: devnode )?
You shouldn’t delete the old INF and PNF files yourself. Call SetupUninstallOEMInf instead:
http://msdn.microsoft.com/en-us/library/aa377446(v=vs.85).aspx
Tim Green
Senior Development Engineer
DisplayLink (UK) Limited
Registered in England No. 04811048
-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@gmail.com
Sent: 24 July 2012 05:54
To: Windows System Software Devs Interest List
Subject: [ntdev] Registry settings after oem and inf delete?
Hi All,
I use to install the driver using inf file manually.And till now I use to delete the oem.inf and pnf files from the inf folder to uninstall the driver. And whenever I try to install a new driver I delete/uninsatall the old inf and pnf file.
And in my old uninstallations( by deleting inf and pnf files ) I didnt modify or delete any registry settings.
In this case do I want to remove any settings from registry ( for ex: devnode )?
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 for your reply. Yes, I am planning to use this API
“SetupUninstallOEMInf” , but my doubt here is, apart from deleting the pnf
and inf files, is there anything else I want to delete from the registry (
for example devnode ).
On Tue, Jul 24, 2012 at 1:22 PM, Tim Green wrote:
> You shouldn’t delete the old INF and PNF files yourself. Call
> SetupUninstallOEMInf instead:
> http://msdn.microsoft.com/en-us/library/aa377446(v=vs.85).aspx
>
>
> Tim Green
> Senior Development Engineer
> DisplayLink (UK) Limited
> Registered in England No. 04811048
>
> -----Original Message-----
> From: xxxxx@lists.osr.com [mailto:
> xxxxx@lists.osr.com] On Behalf Of xxxxx@gmail.com
> Sent: 24 July 2012 05:54
> To: Windows System Software Devs Interest List
> Subject: [ntdev] Registry settings after oem and inf delete?
>
> Hi All,
> I use to install the driver using inf file manually.And till now I use to
> delete the oem.inf and pnf files from the inf folder to uninstall the
> driver. And whenever I try to install a new driver I delete/uninsatall the
> old inf and pnf file.
>
> And in my old uninstallations( by deleting inf and pnf files ) I didnt
> modify or delete any registry settings.
>
> In this case do I want to remove any settings from registry ( for ex:
> devnode )?
>
>
> —
> 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
>
You should look at the Driver Install Framework API’s and not even use
the SetupUninstallOEMInf.
Don Burn
Windows Filesystem and Driver Consulting
Website: http://www.windrvr.com
Blog: http://msmvps.com/blogs/WinDrvr
“Sethuraman R” wrote in message
news:xxxxx@ntdev:
> Thanks for your reply. Yes, I am planning to use this API
> “SetupUninstallOEMInf” , but my doubt here is, apart from deleting the pnf
> and inf files, is there anything else I want to delete from the registry (
> for example devnode ).
>
> On Tue, Jul 24, 2012 at 1:22 PM, Tim Green wrote:
>
> > You shouldn’t delete the old INF and PNF files yourself. Call
> > SetupUninstallOEMInf instead:
> > http://msdn.microsoft.com/en-us/library/aa377446(v=vs.85).aspx
> >
> >
> > Tim Green
> > Senior Development Engineer
> > DisplayLink (UK) Limited
> > Registered in England No. 04811048
> >
> > -----Original Message-----
> > From: xxxxx@lists.osr.com [mailto:
> > xxxxx@lists.osr.com] On Behalf Of xxxxx@gmail.com
> > Sent: 24 July 2012 05:54
> > To: Windows System Software Devs Interest List
> > Subject: [ntdev] Registry settings after oem and inf delete?
> >
> > Hi All,
> > I use to install the driver using inf file manually.And till now I use to
> > delete the oem.inf and pnf files from the inf folder to uninstall the
> > driver. And whenever I try to install a new driver I delete/uninsatall the
> > old inf and pnf file.
> >
> > And in my old uninstallations( by deleting inf and pnf files ) I didnt
> > modify or delete any registry settings.
> >
> > In this case do I want to remove any settings from registry ( for ex:
> > devnode )?
> >
> >
> > —
> > 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
> >
Sethuraman R wrote:
Thanks for your reply. Yes, I am planning to use this API
“SetupUninstallOEMInf” , but my doubt here is, apart from deleting the
pnf and inf files, is there anything else I want to delete from the
registry ( for example devnode ).
We can’t answer that, because we don’t know what you’re trying to do.
The word “uninstall” has many different meanings. Remember that
Microsoft basically recommends you do nothing at all – leave all the
files and the registry settings alone.
So, why are you trying to uninstall? What’s the purpose? There are
traces of your driver left in the registry, in the Services key, the
Enum key, and the Control key. Also, in most cases, your entire driver
package will remain in the driver store.
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.
>
So, why are you trying to uninstall? What’s the purpose? There are
traces of your driver left in the registry, in the Services key, the
Enum key, and the Control key. Also, in most cases, your entire driver
package will remain in the driver store.
Till now, the driver has been manually installed using inf file from new
hardware wizard.And there was no PNP installation earlier. Now, we have
implemented the software first PNP installation using dpinst.exe and
completely changed the inf for our device,
If i uninstall my new PNP driver package, there may be a chance that our
previous driver gets loaded from inf directory, which should be avoided in
my case.
I hope u can adivice me now.
On Tue, Jul 24, 2012 at 9:45 PM, Tim Roberts wrote:
> Sethuraman R wrote:
> > Thanks for your reply. Yes, I am planning to use this API
> > “SetupUninstallOEMInf” , but my doubt here is, apart from deleting the
> > pnf and inf files, is there anything else I want to delete from the
> > registry ( for example devnode ).
>
> We can’t answer that, because we don’t know what you’re trying to do.
> The word “uninstall” has many different meanings. Remember that
> Microsoft basically recommends you do nothing at all – leave all the
> files and the registry settings alone.
>
> So, why are you trying to uninstall? What’s the purpose? There are
>> traces of your driver left in the registry, in the Services key, the
>> Enum key, and the Control key. Also, in most cases, your entire driver
>> package will remain in the driver store.
>>
>
> –
> Tim Roberts, xxxxx@probo.com
> Providenza & Boekelheide, Inc.
>
>
> —
> 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
>
Sethuraman R wrote:
So, why are you trying to uninstall? What’s the purpose? There
are traces of your driver left in the registry, in the Services
key, the
Enum key, and the Control key. Also, in most cases, your entire
driver package will remain in the driver store.Till now, the driver has been manually installed using inf file from
new hardware wizard.And there was no PNP installation earlier. Now, we
have implemented the software first PNP installation using dpinst.exe
and completely changed the inf for our device,
If i uninstall my new PNP driver package, there may be a chance that
our previous driver gets loaded from inf directory, which should be
avoided in my case.
That’s not really something your installer can handle. You’re saying
you have driver N installed, then you install driver N+1 using dpinst,
then you uninstall driver N+1, and want to make sure it doesn’t fall
back to driver N?
The only way to do that is to have something (co-installer, maybe?) that
runs during your installation of driver N+1 that intentionally wipes out
any traces of the old driver. You can’t do that with an INF file.
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.
>
and want to make sure it doesn’t fall back to driver N?
You are right.
However, here, I am automating the driver installation process by writing a
C code, in which I invoke the dpinst.exe to install the driver package.
So in my case ,before calling the dpinst.exe in my program, I can delete
the old oemxx.inf files using “”,
I hope am in the right pathAm i in the right path? Or Do i need to do
anything else (like deleting the registry or x or Y)?
On Wed, Jul 25, 2012 at 10:00 PM, Tim Roberts wrote:
> Sethuraman R wrote:
> >
> > So, why are you trying to uninstall? What’s the purpose? There
> > are traces of your driver left in the registry, in the Services
> > key, the
> > Enum key, and the Control key. Also, in most cases, your entire
> > driver package will remain in the driver store.
> >
> >
> > Till now, the driver has been manually installed using inf file from
> > new hardware wizard.And there was no PNP installation earlier. Now, we
> > have implemented the software first PNP installation using dpinst.exe
> > and completely changed the inf for our device,
> > If i uninstall my new PNP driver package, there may be a chance that
> > our previous driver gets loaded from inf directory, which should be
> > avoided in my case.
>
> That’s not really something your installer can handle. You’re saying
> you have driver N installed, then you install driver N+1 using dpinst,
> then you uninstall driver N+1, and want to make sure it doesn’t fall
> back to driver N?
>
> The only way to do that is to have something (co-installer, maybe?) that
> runs during your installation of driver N+1 that intentionally wipes out
> any traces of the old driver. You can’t do that with an INF file.
>
> –
> Tim Roberts, xxxxx@probo.com
> Providenza & Boekelheide, Inc.
>
>
> —
> 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
>
Sethuraman R wrote:
and want to make sure it doesn’t fall back to driver N?
You are right.
However, here, I am automating the driver installation process by
writing a C code, in which I invoke the dpinst.exe to install the
driver package. So in my case ,before calling the dpinst.exe in my
program, I can delete the old oemxx.inf files using “”,
I hope am in the right pathAm i in the right path? Or Do i need to do
anything else (like deleting the registry or x or Y)?
It’s difficult for us to know this, in part because we don’t know
details about how the old driver was installed. If the new driver has a
different service name, you’ll want to delete the Services entry in the
registry (which you can do with the Service Manager APIs). You
shouldn’t have to worry about the Enum entry, if you are updating the
same device to a new driver.
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.
>
It’s difficult for us to know this, in part because we don’t know
details about how the old driver was installed.
Device Manager -> update driver -> select the inf file from local drive,
this is the how the old drivers were installed.
If the new driver has a different service name, you’ll want to delete the
Services entry in the registry (which you can do with the Service Manager
APIs).
Can you please explain me a bit more on “service name”.?
What about OEM uninstallation with “SetupUninstallOEMInf”?
Thanks…
On Thu, Jul 26, 2012 at 9:41 PM, Tim Roberts wrote:
> Sethuraman R wrote:
> >
> > and want to make sure it doesn’t fall back to driver N?
> >
> > You are right.
> > However, here, I am automating the driver installation process by
> > writing a C code, in which I invoke the dpinst.exe to install the
> > driver package. So in my case ,before calling the dpinst.exe in my
> > program, I can delete the old oemxx.inf files using “”,
> > I hope am in the right pathAm i in the right path? Or Do i need to do
> > anything else (like deleting the registry or x or Y)?
>
> It’s difficult for us to know this, in part because we don’t know
> details about how the old driver was installed. If the new driver has a
> different service name, you’ll want to delete the Services entry in the
> registry (which you can do with the Service Manager APIs). You
> shouldn’t have to worry about the Enum entry, if you are updating the
> same device to a new driver.
>
> –
> Tim Roberts, xxxxx@probo.com
> Providenza & Boekelheide, Inc.
>
>
> —
> 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
>
Sethuraman R wrote:
If the new driver has a different service name, you’ll want to
delete the Services entry in the registry (which you can do with
the Service Manager APIs).Can you please explain me a bit more on “service name”.?
Drivers in Windows are never referred to by their file name. Instead,
drivers are always referred to by their Service name. That name is
looked up in the registry (in HKLM\System\CurrentControlSet\Services),
and that key includes the file name and the other parameters. In your
INF file, you have this line:
AddService = xyz, 2, Driver.Services.Section
The “xyz” is the service name. That’s how your driver is known. If you
ever need to install a filter driver, it is the service name that you
add to the UpperFilters or LowerFilters key.
If your new driver has a different service name, you’ll probably want to
delete the old service.
What about OEM uninstallation with “SetupUninstallOEMInf”?
What about it? That deletes the files, including the oemxx.inf file. I
don’t remember whether that deletes the service entry.
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.
Hi Tim,
Thanks for explaining about servicename in detail.
The below is the NT.Services section of my old and new INF file.
From Old INF file :
AddService=usbser, 0x00000002, Devicename.SERVICEINST
New INF file :
AddService = usbser, 0x00000000, LowerFilter_Service_Inst
Do I want to do any thing in this case?
On Thu, Jul 26, 2012 at 11:14 PM, Tim Roberts wrote:
> Sethuraman R wrote:
> >
> >
> >
> > If the new driver has a different service name, you’ll want to
> > delete the Services entry in the registry (which you can do with
> > the Service Manager APIs).
> >
> >
> > Can you please explain me a bit more on “service name”.?
>
> Drivers in Windows are never referred to by their file name. Instead,
> drivers are always referred to by their Service name. That name is
> looked up in the registry (in HKLM\System\CurrentControlSet\Services),
> and that key includes the file name and the other parameters. In your
> INF file, you have this line:
>
> AddService = xyz, 2, Driver.Services.Section
>
> The “xyz” is the service name. That’s how your driver is known. If you
> ever need to install a filter driver, it is the service name that you
> add to the UpperFilters or LowerFilters key.
>
> If your new driver has a different service name, you’ll probably want to
> delete the old service.
>
>
> > What about OEM uninstallation with “SetupUninstallOEMInf”?
>
> What about it? That deletes the files, including the oemxx.inf file. I
> don’t remember whether that deletes the service entry.
>
> –
> Tim Roberts, xxxxx@probo.com
> Providenza & Boekelheide, Inc.
>
>
> —
> 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
>
Sethuraman R wrote:
Thanks for explaining about servicename in detail.
The below is the NT.Services section of my old and new INF file.
From Old INF file :
AddService=usbser, 0x00000002, Devicename.SERVICEINSTNew INF file :
AddService = usbser, 0x00000000, LowerFilter_Service_InstDo I want to do any thing in this case?
There’s still no way for us to answer this. You are replacing the
existing service with your new service. This has a couple of problems
in itself. (1) The system will not allow you to do this if the old
driver is loaded. You can’t replace a live service entry. (2) If you
have any existing devices that refer to this service, they’re now going
to be confused, because they will try to load your driver, which is now
a filter instead of a full driver.
I don’t know, I’m lost as to what you are trying to do. You just need
to test what you have and make sure it does what you want.
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.
Hi Tim,
The old method, we used for installing the driver is non plug-n-play
method. And now using “dpinst.exe”, to install the driver, and now our new
driver is working fine as a plug-n-play device.
Now I have to avoid driver roll back to the old inf, if any, when i
uninstall the new driver package.
Is it possible to answer now for the above roll back issue?
On Mon, Jul 30, 2012 at 10:56 PM, Tim Roberts wrote:
> Sethuraman R wrote:
> >
> > Thanks for explaining about servicename in detail.
> >
> > The below is the NT.Services section of my old and new INF file.
> >
> > From Old INF file :
> > AddService=usbser, 0x00000002, Devicename.SERVICEINST
> >
> > New INF file :
> > AddService = usbser, 0x00000000, LowerFilter_Service_Inst
> >
> > Do I want to do any thing in this case?
>
> There’s still no way for us to answer this. You are replacing the
> existing service with your new service. This has a couple of problems
> in itself. (1) The system will not allow you to do this if the old
> driver is loaded. You can’t replace a live service entry. (2) If you
> have any existing devices that refer to this service, they’re now going
> to be confused, because they will try to load your driver, which is now
> a filter instead of a full driver.
>
> I don’t know, I’m lost as to what you are trying to do. You just need
> to test what you have and make sure it does what you want.
>
> –
> Tim Roberts, xxxxx@probo.com
> Providenza & Boekelheide, Inc.
>
>
> —
> 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
>
Sethuraman R wrote:
The old method, we used for installing the driver is non plug-n-play
method. And now using “dpinst.exe”, to install the driver, and now our
new driver is working fine as a plug-n-play device.Now I have to avoid driver roll back to the old inf, if any, when i
uninstall the new driver package.Is it possible to answer now for the above roll back issue?
What do you expect the system to do in that case? Leave the device
unrecognized?
If you go trolling through the \windows\inf\oem##.inf files looking for
yours, then delete that file and the associated .pnf file, then the
system should not be able to load the old driver.
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.
Thanks for all your replies.
What do you expect the system to do in that case? Leave the device
unrecognized?
I could really understand the basic behavior of widnows’ default design.
However, as i am trying to install a new driver, in a need not to roll back
to my old driver. I have written few other utilites, which will be
corrupted if my old driver loaded back.
If you go trolling through the \windows\inf\oem##.inf files looking for
yours, then delete that file and the associated .pnf file, then the
system should not be able to load the old driver.
To uninstall the old oem##.inf/pnf, i follow the below steps:
You cannot delete the package if there are devnodes using it.
–
Maxim S. Shatskih
Windows DDK MVP
xxxxx@storagecraft.com
http://www.storagecraft.com
“Sethuraman R” wrote in message news:xxxxx@ntdev…
Thanks for all your replies.
What do you expect the system to do in that case? Leave the device
unrecognized?
I could really understand the basic behavior of widnows’ default design.
However, as i am trying to install a new driver, in a need not to roll back to my old driver. I have written few other utilites, which will be corrupted if my old driver loaded back.
If you go trolling through the \windows\inf\oem##.inf files looking for
yours, then delete that file and the associated .pnf file, then the
system should not be able to load the old driver.
To uninstall the old oem##.inf/pnf, i follow the below steps:
Using SetupDiEnumDeviceInfo and SetupDiGetDeviceRegistryProperty to match my hardware ID
SetupDiOpenDevRegKey and RegQueryValueEx to read the corresponding InfPath
Call SetupUninstallOEMInf to uninstall the inf and pnf.
Now,I am able to retreive around 5 INF paths matched with my h/w id following the steps 1 & 2.One INF contains driver for other device?. However the registry maps with H/W id.
Does windows reallocate the OEM.inf to other device?
Previously,I used to remove the OEM INF/PNF files, without deleting registry entry.
Am I doing anything wrong here?Please advice…
On Wed, Aug 1, 2012 at 9:26 PM, Tim Roberts wrote:
Sethuraman R wrote:
>
> The old method, we used for installing the driver is non plug-n-play
> method. And now using “dpinst.exe”, to install the driver, and now our
> new driver is working fine as a plug-n-play device.
>
> Now I have to avoid driver roll back to the old inf, if any, when i
> uninstall the new driver package.
>
> Is it possible to answer now for the above roll back issue?
What do you expect the system to do in that case? Leave the device
unrecognized?
If you go trolling through the \windows\inf\oem##.inf files looking for
yours, then delete that file and the associated .pnf file, then the
system should not be able to load the old driver.
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.
—
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
Sethuraman R wrote:
Thanks for all your replies.
What do you expect the system to do in that case? Leave the device
unrecognized?I could really understand the basic behavior of widnows’ default
design.
However, as i am trying to install a new driver, in a need not to roll
back to my old driver. I have written few other utilites, which will
be corrupted if my old driver loaded back.
But you need to think about genuine user scenarios here. Are your
driver and your application installed together? If so, then running the
uninstaller should remove both of them, so the application can no longer
run. If a stubborn user deletes your driver by hand without deleting
the application, then it is his own fault if the application doesn’t
work. He gets the result he deserves.
Can’t your application tell whether it is talking to the old driver or
the new driver?
Now,I am able to retreive around 5 INF paths matched with my h/w id
following the steps 1 & 2.One INF contains driver for other device?.
However the registry maps with H/W id.
Does windows reallocate the OEM.inf to other device?
Yes. When you add a new INF, Windows looks for the lowest number that
is not in use. So, if you delete oem4.inf, the next device to be loaded
will go to oem4.inf.
Am I doing anything wrong here?Please advice…
I think you are worrying about situations that you do not need to worry
about.
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.