Re: Printers uninstalling with July patch?



Hi,

As I understand it, this is the Office 2003 MSO.DLL update, and yes it does appear to mess with the document image writer, but why would it mess with other hardware printers?? Good question...

Kurt Levitan wrote:
Has anyone seen their print drivers uninstall when applying July's patches? I was updating one of my home systems when I noticed that 2 of my printers were uninstalled. One of them, Document Image Writer, reinstalled itself immediately while my HP 6100 did not reinstall until after the reboot.

Here are some of the event log entries.

Event Type: Warning
Event Source: Print
Event Category: None
Event ID: 3
Date: 7/15/2006
Time: 12:36:17 PM
User: NT AUTHORITY\SYSTEM
Computer: KURTHOME-B
Description:
Printer Microsoft Office Document Image Writer was deleted.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Event Type: Warning
Event Source: Print
Event Category: None
Event ID: 20
Date: 7/15/2006
Time: 12:36:26 PM
User: NT AUTHORITY\SYSTEM
Computer: KURTHOME-B
Description:
Printer Driver Microsoft Office Document Image Writer Driver for Windows NT x86 Version-3 was added or updated. Files:- mdigraph.dll, mdiui.dll, mdiui.dll.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Event Type: Warning
Event Source: Print
Event Category: None
Event ID: 3
Date: 7/15/2006
Time: 12:37:24 PM
User: KURTHOME-B\Kurt
Computer: KURTHOME-B
Description:
Printer hp officejet 6100 series was deleted.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Event Type: Information
Event Source: Windows Update Agent
Event Category: Installation Event ID: 19
Date: 7/15/2006
Time: 12:39:16 PM
User: N/A
Computer: KURTHOME-B
Description:
Installation Successful: Windows successfully installed the following update: Security Update for Office 2003 (KB917151)

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 57 69 6e 33 32 48 52 65 Win32HRe
0008: 73 75 6c 74 3d 30 78 30 sult=0x0
0010: 30 30 30 30 30 30 30 20 0000000 0018: 55 70 64 61 74 65 49 44 UpdateID
0020: 3d 7b 33 37 30 43 44 32 ={370CD2
0028: 37 45 2d 43 41 44 39 2d 7E-CAD9-
0030: 34 33 38 33 2d 39 33 45 4383-93E
0038: 35 2d 32 32 38 37 36 41 5-22876A
0040: 33 32 41 35 45 43 7d 20 32A5EC} 0048: 52 65 76 69 73 69 6f 6e Revision
0050: 4e 75 6d 62 65 72 3d 31 Number=1
0058: 30 30 20 00 00 .

The KB917151 update was the one that finished closest to the problem. I do not know if it is the culprit.


Thank you for your help.
- Kurt




--
Gerry Hickman (London UK)
.