What is msmx<a lot of numbers and letters>-enu.log?

[Laurel]

Two weeks ago a folder appeared on by C drive named 59e4e42bc21a9ced9730.
Inside it was a log file named msxml4-KB927978-enu.log. Following are the
first couple of inches of the contents of this file. Does anyone have any
idea where this came from?

=== Verbose logging started: 11/16/2006 7:54:11 Build type: SHIP UNICODE
3.01.4000.2435 Calling process: C:\WINDOWS\system32\msiexec.exe ===
MSI (c) (9C:BC) [07:54:11:457]: Resetting cached policy values
MSI (c) (9C:BC) [07:54:11:457]: Machine policy value 'Debug' is 0
MSI (c) (9C:BC) [07:54:11:457]: ******* RunEngine:
******* Product: c:\59e4e42bc21a9ced9730\msxml.msi
******* Action:
******* CommandLine: **********
MSI (c) (9C:BC) [07:54:11:457]: Client-side and UI is none or basic: Running
entire install on the server.
MSI (c) (9C:BC) [07:54:11:477]: Grabbed execution mutex.
MSI (c) (9C:BC) [07:54:12:038]: Cloaking enabled.
MSI (c) (9C:BC) [07:54:12:038]: Attempting to enable all disabled priveleges
before calling Install on Server
MSI (c) (9C:BC) [07:54:12:058]: Incrementing counter to disable shutdown.
Counter after increment: 0
MSI (s) (F4:00) [07:54:12:148]: Grabbed execution mutex.
MSI (s) (F40) [07:54:12:148]: Resetting cached policy values
MSI (s) (F40) [07:54:12:148]: Machine policy value 'Debug' is 0
MSI (s) (F40) [07:54:12:148]: ******* RunEngine:
******* Product: c:\59e4e42bc21a9ced9730\msxml.msi
******* Action:
******* CommandLine: **********
MSI (s) (F40) [07:54:12:479]: Machine policy value 'DisableUserInstalls'
is 0

 

[Wesley Vogel]

msxml4-KB927978-enu.log can be deleted, it's the log from this Windows
Update.

kb927978 is this and it came out November 16, 2006...

MS06-071: Security update for Microsoft XML Core Services 4.0
http://support.microsoft.com/kb/927978

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In

 

[Rock]

Two weeks ago a folder appeared on by C drive named 59e4e42bc21a9ced9730.
Inside it was a log file named msxml4-KB927978-enu.log. Following are the
first couple of inches of the contents of this file. Does anyone have any
idea where this came from?

It's a long file for a windows update (see that knowledge base article
number for info on what the update was). It's safe to delete the log file
and the folder it's in.

Next time scan the messages in this newsgroup before posting. This
questions has been asked and answered numerous times lately.