If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
How do I uninstall an INF file?
I right clicked an driver inf file and selected "install". It got
installed without any prompt, which is normal. Then, how do I *uninstall* it? The context menu do not provide an "uninstall" command, nor in control panel, nor in device manager, even "devmgr_show_nonpresent_devices=1" is set. -- Regards, Lu Wei IM: PGP: 0xA12FEF7592CCE1EA |
Ads |
#2
|
|||
|
|||
How do I uninstall an INF file?
On Wed, 15 Jul 2020 16:44:08 +0800, Lu Wei wrote:
I right clicked an driver inf file and selected "install". It got installed without any prompt, which is normal. Then, how do I *uninstall* it? The context menu do not provide an "uninstall" command, nor in control panel, nor in device manager, even "devmgr_show_nonpresent_devices=1" is set. That environment variable simply enables the possibility to display devices which are previously installed, but no longer exist/plugged. You still need to show hidden devices from the View menu of the Device Manager. Also FYI, INF file is basically just a software script. While usually it contains both installation and uninstallation tasks, both of the tasks are optional. An INF file may contain other task, but no installation and uninstallation task. e.g. reset some registry settings. So, it depends on the contents of the INF file. But for driver INF file, the driver is not normally installable via right-click-Install popup menu from the Windows Explorer - even if it doesn't display any error. In this case, the driver never did installed into the system. Most driver INF file can only be used from the "Add Hardware" control panel. But for driver INF file which actually installable via right-click-Install popup menu, the driver is usually for non PnP device. In Device manager, the device is placed under the "Non-Plug and Play Drivers" node which is hidden by default. |
#3
|
|||
|
|||
How do I uninstall an INF file?
On Thu, 16 Jul 2020 00:23:10 +0700, JJ wrote:
Also FYI, INF file is basically just a software script. While usually it contains both installation and uninstallation tasks, both of the tasks are optional. An INF file may contain other task, but no installation and uninstallation task. e.g. reset some registry settings. If the INF file actually have an uninstallation task, try executing the task from the Command Prompt like this. rundll32 setupapi,InstallHinfSection DefaultUninstall 132 driver.inf Double-quote the INF file if the file path has spaces. |
#4
|
|||
|
|||
How do I uninstall an INF file?
Lu Wei wrote:
I right clicked an driver inf file and selected "install". It got installed without any prompt, which is normal. Then, how do I *uninstall* it? The context menu do not provide an "uninstall" command, nor in control panel, nor in device manager, You mention the context menu, but then say there isn't one (or it does not have an Uninstall entry) for devices listed in Device Manager (devmgmt.msc). That's where I go: Device Manager (devmgmt.msc), right-click on a device, and select Uninstall Device from the context menu. https://images.pcworld.com/images/ar...er-5863510.png If you double-click on a device to see its properties (or double-click the device), the Driver tab should also have an Uninstall button. https://images.pcworld.com/images/ar...es-5863509.png You need to remove/disable the hardware device before the next hardware scan. So, don't do a hardware scan and get rid of the device before the next time you start Windows. even "devmgr_show_nonpresent_devices=1" is set. I think that just makes stick the "View - Show hidden devices" menu option in Device Manager. |
#5
|
|||
|
|||
How do I uninstall an INF file?
JJ wrote:
On Wed, 15 Jul 2020 16:44:08 +0800, Lu Wei wrote: I right clicked an driver inf file and selected "install". It got installed without any prompt, which is normal. Then, how do I *uninstall* it? The context menu do not provide an "uninstall" command, nor in control panel, nor in device manager, even "devmgr_show_nonpresent_devices=1" is set. That environment variable simply enables the possibility to display devices which are previously installed, but no longer exist/plugged. You still need to show hidden devices from the View menu of the Device Manager. Also FYI, INF file is basically just a software script. While usually it contains both installation and uninstallation tasks, both of the tasks are optional. An INF file may contain other task, but no installation and uninstallation task. e.g. reset some registry settings. So, it depends on the contents of the INF file. But for driver INF file, the driver is not normally installable via right-click-Install popup menu from the Windows Explorer - even if it doesn't display any error. In this case, the driver never did installed into the system. Most driver INF file can only be used from the "Add Hardware" control panel. But for driver INF file which actually installable via right-click-Install popup menu, the driver is usually for non PnP device. In Device manager, the device is placed under the "Non-Plug and Play Drivers" node which is hidden by default. How you manage this on a Promise 20378, is to install the "plain" INF, then if you want RAID, you install the "RAID" INF over top. And if you want to switch back, you install the "plain" INF again over top. The last one installed, is the driver set that's running at the time. Promise likes to make installs which only include an INF and no removal mechanism. And there's also no guarantee that such swashbuckling will end well. You could just end up with a giant mess without too much trouble. This mechanism is, of course, entirely unsatisfactory. And, unhygienic. And about as much fun as gutting a fish with a dull knife. The driver files themselves, would be stored in more than one folder, so that Windows File Protection can work. It would be a deception to think that "just deleting blah.sys" is the end of the story. You'd have to find all of the copies of blah.sys, and likely, while running Linux or something, for easy access to them. The INF files, there are two copies. There is "original.INF", but once installed, the OS renames the file to "OEM23.INF" and the INF files are numbered sequentially. The next file would be "OEM24.INF" if yet another one needed to be created. Since I don't know exactly what to do about this, I'll leave the answer right there. I can describe it's a mess, but maybe some third party tool will make removal more convenient. Historically, Windows hardly ever cleans up anything when you ask it. Uninstalling programs never gives a desired result. The cache with the MSI files in it never gets cleaned up. And so on. Just about anything you can think of, is ****ed up. At least WinSXS on the later OSes, got a minor and cursory cleanup, in response to IT people pounding on Microsoft to fix this. People who manage VMs complained that the bloat was making their VM images too large. ******* Device Manager (and devcon) have options to remove a driver, but I really wonder whether any cached copies are also removed so the thing cannot come back on the next reboot or whatever. Hmmm. https://docs.microsoft.com/en-us/win.../devcon-remove "This operation does not delete the device driver or any files installed for the device. After removing the device from the device tree, the files remain and the device is still represented internally as a nonpresent device that can be reenumerated." Dandy. Just dandy. Paul |
#6
|
|||
|
|||
How do I uninstall an INF file?
On 2020-7-16 1:30, JJ wrote:
... Yes, I've shown the hidden ones and it was not anywhere including non-PNP drivers. If the INF file actually have an uninstallation task, try executing the task from the Command Prompt like this. rundll32 setupapi,InstallHinfSection DefaultUninstall 132 driver.inf Double-quote the INF file if the file path has spaces. I tried the command and also tried replacing "DefaultUninstall" to "DefaultInstall". Both returns a dialogue window "Installation failed". So it turns out the driver did not get installed at all. The problem is the context menu installation do not return any results. I have also tried "Add printer wizard" (it's a network printer, and "add hardware from control panel" is only for connected hardware). It shows error like "the driver is not compatible with current version of Windows or is not applicable." I uploaded the file he https://paste.mozilla.org/fUECMyTN Is there any line saying it is not compatible with Windows XP? -- Regards, Lu Wei IM: PGP: 0xA12FEF7592CCE1EA |
#7
|
|||
|
|||
How do I uninstall an INF file?
Lu Wei wrote:
On 2020-7-16 1:30, JJ wrote: ... Yes, I've shown the hidden ones and it was not anywhere including non-PNP drivers. If the INF file actually have an uninstallation task, try executing the task from the Command Prompt like this. rundll32 setupapi,InstallHinfSection DefaultUninstall 132 driver.inf Double-quote the INF file if the file path has spaces. I tried the command and also tried replacing "DefaultUninstall" to "DefaultInstall". Both returns a dialogue window "Installation failed". So it turns out the driver did not get installed at all. The problem is the context menu installation do not return any results. I have also tried "Add printer wizard" (it's a network printer, and "add hardware from control panel" is only for connected hardware). It shows error like "the driver is not compatible with current version of Windows or is not applicable." I uploaded the file he https://paste.mozilla.org/fUECMyTN Is there any line saying it is not compatible with Windows XP? WinXP = setupapi.log and friends. There is a log file kept of hardware installation attempts. The log rolls over when it is too big, and it starts anew. There will be older versions of the file with a number appended so they have unique names. The entries should have a date stamp, to better enable correlation with user attempts to install stuff. Look for error messages. The driver itself could be a virtual print driver, or perhaps something to make a Dymo label-maker work. It doesn't bind to a hardware identifier like a normal driver. That's what I see in it. It also isn't doing a #include and executing a Microsoft INF. It's not a normal driver. Paul |
#8
|
|||
|
|||
How do I uninstall an INF file?
On Thu, 16 Jul 2020 09:04:13 +0800, Lu Wei wrote:
I uploaded the file he https://paste.mozilla.org/fUECMyTN Is there any line saying it is not compatible with Windows XP? That's not an INF file for your printer. It's the NTPRINT.INF file, which is for Core Printer drivers, or base drivers for printer devices. NTPRINT.INF is part of Windows 2003 (NT5.2; newer than XP) and later. And "Core Printer" is a driver model for printer which is available only in Vista and later. So, you'll need an XP driver for that printer. What brand and model is it? |
#9
|
|||
|
|||
How do I uninstall an INF file?
On 2020-7-16 10:02, Paul wrote:
Lu Wei wrote: On 2020-7-16 1:30, JJ wrote: ... Yes, I've shown the hidden ones and it was not anywhere including non-PNP drivers. If the INF file actually have an uninstallation task, try executing the task from the Command Prompt like this. Â* rundll32 setupapi,InstallHinfSection DefaultUninstall 132 driver.inf Double-quote the INF file if the file path has spaces. I tried the command and also tried replacing "DefaultUninstall" to "DefaultInstall". Both returns a dialogue window "Installation failed". So it turns out the driver did not get installed at all. The problem is the context menu installation do not return any results. I have also tried "Add printer wizard" (it's a network printer, and "add hardware from control panel" is only for connected hardware). It shows error like "the driver is not compatible with current version of Windows or is not applicable." I uploaded the file he https://paste.mozilla.org/fUECMyTN Is there any line saying it is not compatible with Windows XP? WinXP = setupapi.log and friends. Checked setupapi.log and other log files in Windows directory, and found nothing related in it. So the failed installation did not write any log. The driver itself could be a virtual print driver, or perhaps something to make a Dymo label-maker work. It doesn't bind to a hardware identifier like a normal driver. That's what I see in it. It also isn't doing a #include and executing a Microsoft INF. It's not a normal driver. It's Xerox Global Print Driver: https://www.support.xerox.com/suppor...ngSystem=winxp The downloaded package contains two directory: ntprint.inf_x86 and X-GPD_5.469.9.0_PS_32_Driver.inf, both have an inf file, both failed to install with the same symptom. The other inf: https://paste.mozilla.org/ox0GRjo2 I doubt maybe the specific network printer I want to install is not compatible with the driver, but even if so, I think I could install the driver first, since it's a "universal" driver, and then use it directly when encounter another compatible printer. -- Regards, Lu Wei IM: PGP: 0xA12FEF7592CCE1EA |
#10
|
|||
|
|||
How do I uninstall an INF file?
On 2020-7-17 1:32, JJ wrote:
On Thu, 16 Jul 2020 09:04:13 +0800, Lu Wei wrote: I uploaded the file he https://paste.mozilla.org/fUECMyTN Is there any line saying it is not compatible with Windows XP? That's not an INF file for your printer. It's the NTPRINT.INF file, which is for Core Printer drivers, or base drivers for printer devices. NTPRINT.INF is part of Windows 2003 (NT5.2; newer than XP) and later. And "Core Printer" is a driver model for printer which is available only in Vista and later. So, you'll need an XP driver for that printer. What brand and model is it? The specific printer is Fuji Docucentre S2110 and the driver is supposed to be universal; In fact there is another inf file which failed with the same symptom, which I have just uploaded too; Please also check my another reply to Paul. -- Regards, Lu Wei IM: PGP: 0xA12FEF7592CCE1EA |
#11
|
|||
|
|||
How do I uninstall an INF file?
Lu Wei wrote:
On 2020-7-16 10:02, Paul wrote: Lu Wei wrote: On 2020-7-16 1:30, JJ wrote: ... Yes, I've shown the hidden ones and it was not anywhere including non-PNP drivers. If the INF file actually have an uninstallation task, try executing the task from the Command Prompt like this. rundll32 setupapi,InstallHinfSection DefaultUninstall 132 driver.inf Double-quote the INF file if the file path has spaces. I tried the command and also tried replacing "DefaultUninstall" to "DefaultInstall". Both returns a dialogue window "Installation failed". So it turns out the driver did not get installed at all. The problem is the context menu installation do not return any results. I have also tried "Add printer wizard" (it's a network printer, and "add hardware from control panel" is only for connected hardware). It shows error like "the driver is not compatible with current version of Windows or is not applicable." I uploaded the file he https://paste.mozilla.org/fUECMyTN Is there any line saying it is not compatible with Windows XP? WinXP = setupapi.log and friends. Checked setupapi.log and other log files in Windows directory, and found nothing related in it. So the failed installation did not write any log. The driver itself could be a virtual print driver, or perhaps something to make a Dymo label-maker work. It doesn't bind to a hardware identifier like a normal driver. That's what I see in it. It also isn't doing a #include and executing a Microsoft INF. It's not a normal driver. It's Xerox Global Print Driver: https://www.support.xerox.com/suppor...ngSystem=winxp The downloaded package contains two directory: ntprint.inf_x86 and X-GPD_5.469.9.0_PS_32_Driver.inf, both have an inf file, both failed to install with the same symptom. The other inf: https://paste.mozilla.org/ox0GRjo2 I doubt maybe the specific network printer I want to install is not compatible with the driver, but even if so, I think I could install the driver first, since it's a "universal" driver, and then use it directly when encounter another compatible printer. http://download.support.xerox.com/pu...ide_071019.pdf 1) Use "Add Printer" interface. 2) When it asks for an install file location, browse to where "X-GPD_5.469.9.0_PCL6_32_Driver.inf" folder is located. It should grab x2UNIVX.inf, since that's the only one I see at the top level, and it has a long list of printer names in it. Paul |
#12
|
|||
|
|||
How do I uninstall an INF file?
On 2020-7-17 9:36, Paul wrote:
... Â*Â* 1) Use "Add Printer" interface. Â*Â* 2) When it asks for an install file location, browse to Â*Â*Â*Â*Â* where "X-GPD_5.469.9.0_PCL6_32_Driver.inf" folder is located. Â*Â*Â*Â*Â* It should grab x2UNIVX.inf, since that's the only one I see at Â*Â*Â*Â*Â* the top level, and it has a long list of printer names in it. I had tried "Add printer" wizard and selected x2UNIVX.inf which shows error like "the driver is not compatible with current version of Windows or is not applicable." But I tried another option just now, that is, do not choose "network printer" in the wizard, instead, choose "local", but use a newly created "standard tcp/ip port" in the next step, and then the installation could continue, files are copied, until "print test page" failed. But the new Xerox Global Printer is there installed. So I think maybe S2110 is truly not compatible with the "global" driver, but next time if a compatible printer is connected to that IP address, I think it would work normally. Now I wonder, what is the difference of installing a network printer and a local printer to a tcp/ip port? -- Regards, Lu Wei IM: PGP: 0xA12FEF7592CCE1EA |
#13
|
|||
|
|||
How do I uninstall an INF file?
Lu Wei wrote:
On 2020-7-17 9:36, Paul wrote: ... 1) Use "Add Printer" interface. 2) When it asks for an install file location, browse to where "X-GPD_5.469.9.0_PCL6_32_Driver.inf" folder is located. It should grab x2UNIVX.inf, since that's the only one I see at the top level, and it has a long list of printer names in it. I had tried "Add printer" wizard and selected x2UNIVX.inf which shows error like "the driver is not compatible with current version of Windows or is not applicable." But I tried another option just now, that is, do not choose "network printer" in the wizard, instead, choose "local", but use a newly created "standard tcp/ip port" in the next step, and then the installation could continue, files are copied, until "print test page" failed. But the new Xerox Global Printer is there installed. So I think maybe S2110 is truly not compatible with the "global" driver, but next time if a compatible printer is connected to that IP address, I think it would work normally. Now I wonder, what is the difference of installing a network printer and a local printer to a tcp/ip port? Maybe there is some slight difference in that INF file, in how the two situations are handled. The driver does not use regular PNP identifiers for the printer, and I have no idea where that information and naming convention comes from. I couldn't tell whether the 2110 was in that file or not. The name strings use a funny truncation method. Paul |
#14
|
|||
|
|||
How do I uninstall an INF file?
On 2020-7-17 17:15, Paul wrote:
Now I wonder, what is the difference of installing a network printer and a local printer to a tcp/ip port? Maybe there is some slight difference in that INF file, in how the two situations are handled. The driver does not use regular PNP identifiers for the printer, and I have no idea where that information and naming convention comes from. I couldn't tell whether the 2110 was in that file or not. The name strings use a funny truncation method. The official driver download page says there's no driver for XP, and that's why I tried this "Global" driver. It seems not global at all! Is there a true global printer driver that could speak to all, or a large portion of printers? -- Regards, Lu Wei IM: PGP: 0xA12FEF7592CCE1EA |
#15
|
|||
|
|||
How do I uninstall an INF file?
Lu Wei wrote:
On 2020-7-17 17:15, Paul wrote: Now I wonder, what is the difference of installing a network printer and a local printer to a tcp/ip port? Maybe there is some slight difference in that INF file, in how the two situations are handled. The driver does not use regular PNP identifiers for the printer, and I have no idea where that information and naming convention comes from. I couldn't tell whether the 2110 was in that file or not. The name strings use a funny truncation method. The official driver download page says there's no driver for XP, and that's why I tried this "Global" driver. It seems not global at all! Is there a true global printer driver that could speak to all, or a large portion of printers? There are multiple "universal print driver for X" type drivers. Initially, Microsoft made a framework for PostScript printers, and that was the first one I used. This was extended to separate packages for PCL printers. The manufacturer takes them and customizes them. Making them a little less universal. HP took the Microsoft universal Postscript, and that's what I installed for a virtual printer. In addition, we have "OS choice". Hardly anyone makes WinXP materials today, and in the year 2014, the packages weren't quite as developed as they are today. So if you somehow used archive.org to look for older ones, chances are they would be for PostScript printers. I was really surprised to see that Xerox one, offer any sort of older option. Today, it would be more normal for them to be Vista+ (but without saying the word Vista in the release notes, because Vista and Win7 are out of support). But the thing about printer drivers, is, never give up. You don't know what is out there, until you try. I use the universal PostScript driver, for "Print to Postscript" capability, and then I toss the file into Distiller to make a PDF. As an example of not even needing a printer, to get some mileage from that junk :-) Paul |
|
Thread Tools | |
Display Modes | |
|
|