msxlm4...enu.log file

I just noted an obscure folder on my D: particition with a long filename, and in it was another file with a name like msxlm4, then lots of characters, ending in enu.log. It looks like some type of installation file, although I don't think I'm installed anything lately. It has a lot of lines in it preceded by "MSI." I've attached a few lines here at the bottom. I tried to upload the whole file, but get a message that I cannot upload it.

Is this something I can delete?

Terry


=== Verbose logging started: 11/21/2006 20:29:57 Build type: SHIP UNICODE 3.01.4000.2435 Calling process: C:\WINDOWS\system32\msiexec.exe ===
MSI (c) (B8:0C) [20:29:57:921]: Resetting cached policy values
MSI (c) (B8:0C) [20:29:57:921]: Machine policy value 'Debug' is 0
MSI (c) (B8:0C) [20:29:57:921]: ******* RunEngine:
******* Product: d:\931ccb476d9ec8413e5e0032\msxml.msi
******* Action:
******* CommandLine: **********
MSI (c) (B8:0C) [20:29:57:921]: Client-side and UI is none or basic: Running entire install on the server.
MSI (c) (B8:0C) [20:29:57:921]: Grabbed execution mutex.
MSI (c) (B8:0C) [20:29:57:984]: Cloaking enabled.
MSI (c) (B8:0C) [20:29:57:984]: Attempting to enable all disabled priveleges before calling Install on Server
MSI (c) (B8:0C) [20:29:57:984]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (10:2C) [20:29:58:000]: Grabbed execution mutex.
MSI (s) (10:98) [20:29:58:000]: Resetting cached policy values
MSI (s) (10:98) [20:29:58:000]: Machine policy value 'Debug' is 0
MSI (s) (10:98) [20:29:58:000]: ******* RunEngine:
******* Product: d:\931ccb476d9ec8413e5e0032\msxml.msi
******* Action:
******* CommandLine: **********
MSI (s) (10:98) [20:29:58:000]: Machine policy value 'DisableUserInstalls' is 0
MSI (s) (10:98) [20:29:58:031]: File will have security applied from OpCode.
MSI (s) (10:98) [20:29:58:046]: SOFTWARE RESTRICTION POLICY: Verifying package --> 'd:\931ccb476d9ec8413e5e0032\msxml.msi' against software restriction policy
MSI (s) (10:98) [20:29:58:046]: SOFTWARE RESTRICTION POLICY: d:\931ccb476d9ec8413e5e0032\msxml.msi has a digital signature
MSI (s) (10:98) [20:29:59:734]: SOFTWARE RESTRICTION POLICY: d:\931ccb476d9ec8413e5e0032\msxml.msi is permitted to run at the 'unrestricted' authorization level.
MSI (s) (10:98) [20:29:59:734]: End dialog not enabled
MSI (s) (10:98) [20:29:59:734]: Original package ==> d:\931ccb476d9ec8413e5e0032\msxml.msi
MSI (s) (10:98) [20:29:59:734]: Package we're running from ==> C:\WINDOWS\Installer\f9b4bd6.msi
MSI (s) (10:98) [20:29:59:781]: APPCOMPAT: looking for appcompat database entry with ProductCode '{37477865-A3F1-4772-AD43-AAFC6BCFF99F}'.
MSI (s) (10:98) [20:29:59:781]: APPCOMPAT: no matching ProductCode found in database.
MSI (s) (10:98) [20:29:59:781]: MSCOREE not loaded loading copy from system32
MSI (s) (10:98) [20:29:59:828]: Machine policy value 'TransformsSecure' is 0
MSI (s) (10:98) [20:29:59:828]: User policy value 'TransformsAtSource' is 0
MSI (s) (10:98) [20:29:59:828]: Machine policy value 'DisablePatch' is 0
MSI (s) (10:98) [20:29:59:828]: Machine policy value 'AllowLockdownPatch' is 0

 

Go ahead a delete it.

It is from a Windows Update (for its new update for MSXML), and the MSI "Microsoft Installer" sometimes leaves behind long and oddly named folders with little setup files inside. For example, it left behind on your D: drive a folder named: 931ccb476d9ec8413e5e0032

Delete the folder and its contents.

 

Thank you, Bill. I thought it might be something like that, but I just wanted to be sure it wasn't something more sinister.

Terry