Error with latest HP Driver Update from Windows Update

[Scott]

I installed the latest driver updates (2 driver updates for August) and
began having problems with our HP 4200 printers.

On one printer, the users simply weren't able to print anymore. I
noticed a changed a setting in general tab, printing preferences,
"Destination tab, destination features, job storage settings were
changed to "proof and hold" !

Note - trying to open general tab, printing preferences one of these
4200's resulted in an error "Function address 0x78010479 caused a
protection fault. (exception code 0xc0000005) Some or all of the proprty
page(s) may not be displayed. And sure enought that was as far as I
could go.

This is unique to the 4200 printers.

Also, the details section when you do windows update will not display
any detail info about the driver updates. Just a 404 error.

 

[Ranjit]

Note - trying to open general tab, printing preferences
one of these

4200's resulted in an error "Function address 0x78010479 caused a
protection fault. (exception code 0xc0000005) Some or all of the proprty
page(s) may not be displayed. And sure enought that was as far as I
could go.

This is unique to the 4200 printers.

Scott:
I installed the same drivers and now my 4300tn is doing
the same thing as your 4200. Have you been able to
uninstall or reinstall successfully. I need to fix this.

 

[Martin]

Scott:
I installed the same drivers and now my 4300tn is doing
the same thing as your 4200. Have you been able to
uninstall or reinstall successfully. I need to fix this.

Has anyone got a solution for this, same thing happened to me with a 4300tn.

 

[chrisckn]

I am having the same exact problem. This happened on my Print Serve
and so every workstation received this error message when trying t
print from Internet Explorer (File - Print) or if they tried to ope
the "Printing Preferences" on an HP 4200 printer.

I was able to fix the server (I can now print and open the "printin
preferences" from the server, but every workstation on the network no
has these "corrupt" drivers. Removing the printer connection and the
re-adding the printer connection does not "update" or refresh th
drivers. Can anyone tell me how I can force a "refresh" or update t
the drivers when they connect to the print server?

As far as fixing the problem on the server, I had to (PLEASE make sur
you back up first) stop the spooler service, go into the registry, an
remove th
"HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Environments\Window
NT x86\Drivers\Version-3" key under here which pertained to my printe
(HP LaserJet 4200 PCL 6). If you restart the spooler, your 420
printers will not show up. You have to add a local printer, using th
OEM drivers for the HP LJ 4200. One the driver is "re-installed" sto
and start your print spooler again and your 4200 printers will sho
up.

As I mentioned, now the server itself works fine, but this doesn't hel
my users because the workstations still have the corrput drivers. If
delete the drivers out of the \SYSTEM32\SPOOL\DRIVERS\W32X86\
directory manually, then add the printer, the new drivers ar
downloaded to the workstation automatically but I can't figure out ho
to automate this.

Well, hope that helps you. If anyone can help me, I'd appreciate it.

Thanks
Chris

*>Note - trying to open general tab, printing preferences
one of these

Scott:
I installed the same drivers and now my 4300tn is doing
the same thing as your 4200. Have you been able to
uninstall or reinstall successfully. I need to fix this.

-
chrisck

 

[Guest]

How to automate this, you should make a GPO that starts
before user-logon. That is before the .DLL's starts to
load. You can make a script that will do this and roll it
to the users, that is if they are a member of a domain.
The drivers from Microsoft Update was corrupt, and I had
to download an older one from HP which I knew worked

 

[dlight]

I have this same problem with the 4350tn. i have not tried this fix yet but am looking forward to trying it right after i finish this post.

Does any one know which microsoft update it was that caused this?? i have been trying to find this out for months.