TStandage Posted October 13, 2014 Posted October 13, 2014 Hello, I've been having a problem with a few of our netbooks. They are all Windows 7. I have two which will not save the Printer drivers. I have to keep logging on to the server to reinstall the drivers. I have tried resetting the printer spoiler. I seriously have no other clues on a fix. I'm pretty much new to the technician world. So there might eb aobvious things I'm mission out. So please if you know of a fix. Please tell me! Thank you everyone who comments.
r0cketbev Posted October 13, 2014 Posted October 13, 2014 Welcome, What printer is it, how is it deployed, does it have the latest drivers, what windows is it? RB
TStandage Posted October 13, 2014 Author Posted October 13, 2014 Hello, Thank you for the welcome, Here are the details for you: Printer name: Rioch Aficio MP C2800 PCL 6 Printer drivers: All up to date I think it is deployed by GPO. But I'm not 100% sure. Is there a way I can find out. It is also Windows Service Pack 1, Windows 7, Windows NT 6.1 I hope this helps!
Oaktech Posted October 13, 2014 Posted October 13, 2014 I've had this recently on a ricoh c431 and had to do the following... On a working machine, In C:\windows\system32\driverstore find the folder in which the driver for the printer in question resides ( for ricoh it usually contains oemsetup somewhere in the title) you can search for the INF file from the driver installer if you need to, copy it to the non working machine. In the registry of the working machine, find the print details folder of the printer it's having problems with - it should be something like HKLM\system\current control set\control\print\environments\windows x64\drivers\version-3\ then have a look inside there for the printer in question and look at the InfPath. it should match up with the folder location. Check the non working machine - one of the things above will be wrong. I've seen the following things wrong - driver directories missing, printer entry missing, inf path incorrect or empty. use the information we gathered above to correct it. Please be aware that the above procedure is for x64 systems you may need to modify the procedure slightly for x86 devices. Hope this helps.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now