Discussion Locked

Install previous version of UNIDRV.DLL

0 helpful
14 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

We are experiencing a problem where a service (Fabsoft?s Reform print spooler service) on our W2K Domain Controller is not starting up automatically after a reboot. This apparently began after an update to the Universal Printer Driver UNIDRV.DLL. What process actually updated this I have not yet determined. This file is currently at version 0.3.1282.1, product version 5.1.2600.1147. The previous version which worked without this problem was 0.3.1281.0, product version 5.1.2600.1106. I have a copy of the previous version with the service?s install files. I have renamed all copies of the updated version including in the C:\winnt\system32\spool\drivers\w32x86\3 and C:\winnt\servicepackfiles\i386 and placed a copy of the previous version in these two locations, but after rebooting the previous version is overwritten with the updated again. Where can I find what it causing the updated version to overwrite?
Thanks in advance!

14 replies

by bfilmfan

The system restore point is replacing the driver. It was most likely upgraded by either a service pack update or a security hotfix.

Have you contacted Fabsoft on getting a new version of their software to address the issue?

by rainier_d

We are running Windows 2000 Server which I don't believe has restore points. I also believe a service pack or hotfix replaced the driver but I need to know how to downgrade the driver so it doesn't get replaced.
Unfortunatly Fabsoft only supports their current software version and we are using the previous version.

by bigmat

How about a work around, I have a little DLL hell too, What I have done in the past it just deposit the dll's in a different location, and using the PATH environment variable order the PATH statement in the order in which you wish the DLL's to be used from where ever they are eg
mkdir d:\mydll's
in PATH environment variable set it to be something like PATH= d:\mydlls;original PATH enteris like c:\winNT\system32....
The thing with the path statement is it gets read front to back, so whatever the application is it'll read the first DLL it needs, regardless of what Billy's software does to the rest your Server. And Yeah get onto Fabsoft, this sort of thing happens too much. they need to start developing in .NET maybe to get away from this DLL issue.

by rainier_d

Being a universal driver used by several printers in addition to Reform, I'd rather find a fix than a work around.

by zaferus

Have you tried registering the new file? Use start-run: regsvr32 c:\windows\system32\unidrv.dll (after you copy the correct file in). This should keep Windows from freaking out about the file.

by rainier_d

Yes, I did register the new file. I even tried un-registering the new file and re-registering the old one. Neither helped.

by dmiles

The file is probably protected. Check the %systemroot%\system32\dllcache
folder. Be sure to also check the dependency structure to see what else may
need to be replaced.

You can run depends.exe against the DLL to check dependencies

You'll find depends.exe within
http://www.dependencywalker.com/

Description of the Windows 2000 System File Checker Tool
http://www.microsoft.com/resources/...le_checker.mspx

Description of the Windows 2000 Windows File Protection Feature
http://support.microsoft.com/?id=222193

by rainier_d

I thought so too, so I replaced the version in the dll cache with the older version I wanted. No luck, a reboot updated the dll cache as well.

by sgt_shultz

wow, i can't wait to hear the answer on this one. i would call ms on this one.
meanwhile, i did find confirmation that unidrv.dll is updated via 2000 sp3. do you mind me asking how you know it is being overwritten? how many copies can you find? you have ditched all the new ones and it is coming out of a cab or something when windows find it has mssing system files and replaces them? like sfc must be running at boot or something? so like if you ditched EVERY unidrv.dll, it would come back with the new one. it has to be coming out of the sp3 update folder doesn't it? can you see sfc running? did you try unregistering and reregister the dll as suggest?

by rainier_d

I finally gave up on fixing this, set up a separate server and moved the Reform program, as well as our FaxWare program which also was affected, to this server. Now, even though it is at the same update level as the previous server, I'm experiencing no problems with the driver. Sorry I can't advise of a definite fix.

This discussion is closed to new replies.