printer problems since patch Tuesday

  • Thread starter Thread starter Mike Koch
  • Start date Start date
That's the fix for now. HP is aware of this issue. I am not sure how far
they got into resolving their driver version conflict.

They way I work around this is to set all the printers that need the driver
upgrade to a driver that is not used by any other device. I add the AGFA
driver that is first in the driver list. DO NOT delete the printers just
assign the printers the AGFA driver. Delete the old driver (I have had to
kill explorer.exe to unload the UI drivers that are loaded), then install
the new drivers. If more that one driver is using the same module you may
need to perform this for multiple driver at the same time.

Set one of the printers to the new driver and open the properties. Then the
rest.

--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base here:
http://support.microsoft.com/default.aspx?scid=fh;[ln];kbhowto
 
Hi, we have the same problem with the acumulative patch for w2k and lexmark
printers. So far we took the same solution of uninstalling the patch. I
contacted lexmark and have no response yet. Let me know if you got some help
or solution

MB
 
Hello,

Lexmark Support has anounced a Microsoft Hotfix KB908506 that should
resolve the Problem. Can´t find the hotfix at Microsoft for download.
Think you have to open a call to get it.

D. M.
 
Function Address

I too seem to have the Function Address 0x77fcb21d error message when attempting to do a test print to a Dell 5300 network printer. In my case the client computer has the KB896423 update but the domain controller does not, so my questions to the others who have the same error message is:

Is your domain controller a windows 2000 server and has it been patched with KB896423? Has anyone been able to find a solution to this problem (other than uninstalling the hotfix?).
 
Kb896423

Hie
We are experiencing the same problem with our W2K workstations after applying KB896423 with Lexmark T632.
We have found a way to bypass the problem but it's not the best solution. I saw that Microsoft agree the pb comes from the patch KB896423 and that they should update this patch. have you any news from Microsoft ? or Lexmark ?
Thanks for your reply. You can contact me through this forum.
 
Hi "Cari"

I looked for the mentioned patch released the past 19 October, but it works
only for W2k English versions. When do you(MS) plan to release the spanish
version for example?

MB
 
Kb 908506

I got microsoft support on the phone this afternno and they told me that the patch works for any language. The only "oups" is that they won't write it for the moment and told me to try it on a test machine ...
Thanks Microsoft.
By the way, I'm using a french version of W2K
 
Fred, How do you uninstall the update?
I have a Canon L75 printer and Win2K Pro and since I downloaded the update KB891861 earlier today, I now get this message when I try to print.
"THE SYSTEM HAS DETECTED CONFLICTING PRINT SETTINGS"
I have spent over 7 hours trying to fix it. I've uninstalled the printer driver numerous times, to no avail. Any idea what to do without creating mor problems? I am out of my mind at this point. Please help.
Fred Yarbrough said:
Found the fix.

Simply remove the following Microsoft Update and reboot and things are good
to go.

Update Rollup 1 for Windows 2000 Service Pack 4 (KB891861)



Thanks,
Fred


"Mike Koch" wrote in message
news:%23$bs%[email protected]...
> We've been experiencing numerous printer problems ever since the latest
> Microsoft patches were released and installed. It only seems to affect
> Windows 2000 Professional machines (our WinXP workstations do not exhibit
> the problem), and it's only certain printers - the IBM/Lexmark printers.
> When any Win2KPro user attempts to print to one of those printers, a small
> error dialog appears (I don't have a sample, but it wasn't helpful,
> referring to a hex address, didn't even necessarily look printer-related).
> Same dialog appears if the user attempts to view the printer property
pages
> (the properties dialog never comes up).
>
> This problem is growing wider as the day progresses and more users accept
> the prompt to reboot to complete the patch installations. Third party apps
> crash and die when they attempt to print to one of these printers.
Microsoft
> apps are misbehaving if one of these printers is the users' default
printer.
>
> I've tried removing the printers from the workstation completely and
> reinstalling from the print server. I tried removing the printer and
> deleting the driver files manually, to make sure the ones from the print
> server actually got downloaded and installed. No change. I checked on
IBM's
> site for a newer driver, but it appears that we're already using the
latest
> driver. I'm in the process of building a test machine to do some more
> experiments without impacting user productivity, but I'm running out of
> ideas. Yes, we'd like to upgrade them all to Windows XP, but that takes
time
> and I need a quicker fix for this problem.
>
> Anybody have any ideas?
>
> Thanks,
> Mike
>
>
Click to expand...
 
Back
Top