/build/static/layout/Breadcrumb_cap_w.png

Ricoh SP3610 USB Printer Uninstall

Hello,

I am in the process of creating a Printer Driver package for Ricoh SP3610 model. We chose the USB method of connection.

So, through package I am taking care of pinter driver install using pnputil.exe. Driver installs fine as the printer works as expected when connected.

The issue is with uninstall. I uninstall the driver files this time using "...\dpinst64.exe" /u oemsetup.inf /q" followed by Remove-Printer command.

But the Ricoh printer icon is grayed out in Devices and Printers list. I also tried restart of spooler services and manually deleting RicohXXX printer related entries but the icon stays.

However, using the context menu to remove device seems to work. Also saw this error in setupapidev.log at one point of time in delete driver section : !    dvi: Access denied from Query and Remove.


Working on driver package after a long time, not sure what am i missing. Any help is appreciated.


Thanks


0 Comments   [ + ] Show comments

Answers (1)

Posted by: anonymous_9363 4 years ago
Red Belt
1
Access denied 

Hmmm...I wonder if this could be a clue...? I strongly suspect that the fact that you're expecting dpinst64 to find that INF by itself is a factor. You should always, always, ALWAYS use explicit paths. Use %~dp0 if that path isn't hard and fast.

Having said that, if you're packaging the driver into MSI - and that's what you should really be doing - there's a merge module that you can download which interfaces with DPInst. Once you have that, installation and uninstallation involves using only the resulting MSI. Adding the printer connection can then be done using the Microsoft 'prn????.vbs' scripts.

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ