Windows XP creating too many MSI log files

Pudgex3 · April 21, 2010

I have a machine with XP Pro. It recenlty started saying there was low disk space. Upon investigating, I found that the Windows\temp directory had over 60 Gigs of stuff in it, mostly MSI log files. I got rid of them all, and when I checked a few hours later, there was already 4 Gigs in there. The computer wasn't being used at all, it was just sitting, idle. Does any body know what is causing these files?

andsome · April 21, 2010

Try running C Cleaner on a regular basis and see what it removes. I use it last thing every time I close down, it only takes seconds.

Here it is.

ɹəuəllıʍ ʇɐb · April 21, 2010

Does any body know what is causing these files?

I agree with the previous poster that CCleaner is a good tool to keep your computer free of junk files.

However, what is causing it? Can you give us some examples of file names?

Pudgex3 · April 21, 2010

Does any body know what is causing these files?
I agree with the previous poster that CCleaner is a good tool to keep your computer free of junk files.
However, what is causing it? Can you give us some examples of file names?

I have been erasing them with a comand prompt script I found, but they keep coming back,

they are MSI2f8ee.LOG, MSI2f8ef.LOG and so on.

I cleaned the folder like an hour ago and there are already over 7000 of them in there. In the time it took me to type this, over 300 new ones were made.

HELP!!!

andsome · April 21, 2010

Have you scanned for Malware?

Boris · April 21, 2010

This would appear to be a Windows Installer logging problem ?

See :-
/>http://support.microsoft.com/kb/223300

Windows Installer can use logging to help assist in troubleshooting issues with installing software packages.
This logging is enabled by adding keys and values to the registry.
After the entries have been added and enabled, you can retry the problem installation and Windows Installer will track the progress and post it to the Temp folder.
The new log's file name is random, but begins with the letters "Msi" and end with a .log extension.
To locate the Temp folder location, type the following line at a command prompt:
cd %temp%

Unfortunately, I have no immediate solution, but will have a think :)

AlanHo · April 21, 2010

You could try using System Restore to get back to a time when all was OK.

You could also try the new Microsoft Fixit centre.....Click Here

Pudgex3 · April 21, 2010

OK, I have new info. I opened a few of the LOG files, and they are all the same

It is a lot, but this is what it says:

=== Verbose logging started: 6/7/2010 19:22:39 Build type: SHIP UNICODE 4.05.6001.00 Calling process: C:\WINDOWS\system32\wbem\wmiprvse.exe ===

MSI © (20:54) [19:22:39:640]: SOFTWARE RESTRICTION POLICY: Verifying package --> 'C:\WINDOWS\Installer\10b6441.msi' against software restriction policy

MSI © (20:54) [19:22:39:640]: SOFTWARE RESTRICTION POLICY: C:\WINDOWS\Installer\10b6441.msi has a digital signature

MSI © (20:54) [19:22:39:640]: SOFTWARE RESTRICTION POLICY: C:\WINDOWS\Installer\10b6441.msi is permitted to run because the user token authorizes execution (system or service token).

MSI © (20:54) [19:22:39:640]: Cloaking enabled.

MSI © (20:54) [19:22:39:640]: Attempting to enable all disabled privileges before calling Install on Server

MSI © (20:54) [19:22:39:640]: End dialog not enabled

MSI © (20:54) [19:22:39:640]: Original package ==> C:\WINDOWS\Installer\10b6441.msi

MSI © (20:54) [19:22:39:640]: Package we're running from ==> C:\WINDOWS\Installer\10b6441.msi

MSI © (20:54) [19:22:39:640]: APPCOMPAT: looking for appcompat database entry with ProductCode '{07287123-B8AC-41CE-8346-3D777245C35B}'.

MSI © (20:54) [19:22:39:640]: APPCOMPAT: no matching ProductCode found in database.

MSI © (20:54) [19:22:39:656]: MSCOREE not loaded loading copy from system32

MSI © (20:54) [19:22:39:656]: Machine policy value 'DisablePatch' is 0

MSI © (20:54) [19:22:39:656]: Machine policy value 'AllowLockdownPatch' is 0

MSI © (20:54) [19:22:39:656]: Machine policy value 'DisableLUAPatching' is 0

MSI © (20:54) [19:22:39:656]: Machine policy value 'DisableFlyWeightPatching' is 0

MSI © (20:54) [19:22:39:656]: APPCOMPAT: looking for appcompat database entry with ProductCode '{07287123-B8AC-41CE-8346-3D777245C35B}'.

MSI © (20:54) [19:22:39:656]: APPCOMPAT: no matching ProductCode found in database.

MSI © (20:54) [19:22:39:656]: Transforms are not secure.

MSI © (20:54) [19:22:39:656]: PROPERTY CHANGE: Adding MsiLogFileLocation property. Its value is 'C:\WINDOWS\TEMP\MSI2e5a8.LOG'.

MSI © (20:54) [19:22:39:656]: No Command Line.

MSI © (20:54) [19:22:39:656]: PROPERTY CHANGE: Adding PackageCode property. Its value is '{B858CDA2-B4FF-4BF7-B03B-552D44FAF6A1}'.

MSI © (20:54) [19:22:39:656]: Product Code passed to Engine.Initialize: '(none)'

MSI © (20:54) [19:22:39:656]: Product Code from property table before transforms: '{07287123-B8AC-41CE-8346-3D777245C35B}'

MSI © (20:54) [19:22:39:656]: Product Code from property table after transforms: '{07287123-B8AC-41CE-8346-3D777245C35B}'

MSI © (20:54) [19:22:39:656]: Product registered: entering maintenance mode

MSI © (20:54) [19:22:39:656]: PROPERTY CHANGE: Adding ProductState property. Its value is '5'.

MSI © (20:54) [19:22:39:656]: PROPERTY CHANGE: Adding ProductToBeRegistered property. Its value is '1'.

MSI © (20:54) [19:22:39:656]: Package name retrieved from configuration data: 'Bonjour.msi'

MSI © (20:54) [19:22:39:656]: Determined that existing product (either this product or the product being upgraded with a patch) is installed per-machine.

MSI © (20:54) [19:22:39:656]: Note: 1: 2262 2: AdminProperties 3: -2147287038

MSI © (20:54) [19:22:39:656]: Machine policy value 'DisableMsi' is 0

MSI © (20:54) [19:22:39:656]: Machine policy value 'AlwaysInstallElevated' is 0

MSI © (20:54) [19:22:39:656]: User policy value 'AlwaysInstallElevated' is 0

MSI © (20:54) [19:22:39:656]: Product {07287123-B8AC-41CE-8346-3D777245C35B} is admin assigned: LocalSystem owns the publish key.

MSI © (20:54) [19:22:39:656]: Product {07287123-B8AC-41CE-8346-3D777245C35B} is managed.

MSI © (20:54) [19:22:39:656]: Running product '{07287123-B8AC-41CE-8346-3D777245C35B}' with elevated privileges: Product is assigned.

MSI © (20:54) [19:22:39:656]: TRANSFORMS property is now:

MSI © (20:54) [19:22:39:656]: PROPERTY CHANGE: Adding PRODUCTLANGUAGE property. Its value is '1033'.

MSI © (20:54) [19:22:39:656]: PROPERTY CHANGE: Adding VersionDatabase property. Its value is '110'.

MSI © (20:54) [19:22:39:656]: SHELL32::SHGetFolderPath returned: C:\WINDOWS\system32\config\systemprofile\Application Data

MSI © (20:54) [19:22:39:656]: SHELL32::SHGetFolderPath returned: C:\WINDOWS\system32\config\systemprofile\Favorites

MSI © (20:54) [19:22:39:656]: SHELL32::SHGetFolderPath returned: C:\WINDOWS\system32\config\systemprofile\NetHood

MSI © (20:54) [19:22:39:656]: SHELL32::SHGetFolderPath returned: C:\WINDOWS\system32\config\systemprofile\My Documents

MSI © (20:54) [19:22:39:656]: SHELL32::SHGetFolderPath returned: C:\WINDOWS\system32\config\systemprofile\PrintHood

MSI © (20:54) [19:22:39:656]: SHELL32::SHGetFolderPath returned: C:\WINDOWS\system32\config\systemprofile\Recent

MSI © (20:54) [19:22:39:656]: SHELL32::SHGetFolderPath returned: C:\WINDOWS\system32\config\systemprofile\SendTo

MSI © (20:54) [19:22:39:656]: SHELL32::SHGetFolderPath returned: C:\WINDOWS\system32\config\systemprofile\Templates

MSI © (20:54) [19:22:39:656]: SHELL32::SHGetFolderPath returned: C:\Documents and Settings\All Users\Application Data

MSI © (20:54) [19:22:39:656]: SHELL32::SHGetFolderPath returned: C:\WINDOWS\system32\config\systemprofile\Local Settings\Application Data

MSI © (20:54) [19:22:39:671]: SHELL32::SHGetFolderPath returned: C:\WINDOWS\system32\config\systemprofile\My Documents\My Pictures

MSI © (20:54) [19:22:39:671]: SHELL32::SHGetFolderPath returned: C:\Documents and Settings\All Users\Start Menu\Programs\Administrative Tools

MSI © (20:54) [19:22:39:671]: SHELL32::SHGetFolderPath returned: C:\Documents and Settings\All Users\Start Menu\Programs\Startup

MSI © (20:54) [19:22:39:671]: SHELL32::SHGetFolderPath returned: C:\Documents and Settings\All Users\Start Menu\Programs

MSI © (20:54) [19:22:39:671]: SHELL32::SHGetFolderPath returned: C:\Documents and Settings\All Users\Start Menu

MSI © (20:54) [19:22:39:671]: SHELL32::SHGetFolderPath returned: C:\Documents and Settings\All Users\Desktop

MSI © (20:54) [19:22:39:671]: SHELL32::SHGetFolderPath returned: C:\WINDOWS\system32\config\systemprofile\Start Menu\Programs\Administrative Tools

MSI © (20:54) [19:22:39:671]: SHELL32::SHGetFolderPath returned: C:\WINDOWS\system32\config\systemprofile\Start Menu\Programs\Startup

MSI © (20:54) [19:22:39:671]: SHELL32::SHGetFolderPath returned: C:\WINDOWS\system32\config\systemprofile\Start Menu\Programs

MSI © (20:54) [19:22:39:671]: SHELL32::SHGetFolderPath returned: C:\WINDOWS\system32\config\systemprofile\Start Menu

MSI © (20:54) [19:22:39:671]: SHELL32::SHGetFolderPath returned: C:\WINDOWS\system32\config\systemprofile\Desktop

MSI © (20:54) [19:22:39:671]: SHELL32::SHGetFolderPath returned: C:\Documents and Settings\All Users\Templates

MSI © (20:54) [19:22:39:671]: SHELL32::SHGetFolderPath returned: C:\WINDOWS\Fonts

MSI © (20:54) [19:22:39:671]: PROPERTY CHANGE: Adding DATABASE property. Its value is 'C:\WINDOWS\Installer\10b6441.msi'.

MSI © (20:54) [19:22:39:671]: PROPERTY CHANGE: Adding OriginalDatabase property. Its value is 'C:\WINDOWS\Installer\10b6441.msi'.

=== Logging started: 6/7/2010 19:22:39 ===

=== Verbose logging stopped: 6/7/2010 19:22:39 ===

It seems to be associated with wmiprvse.exe and I have found a lot of people have issues with this, but I haven't found a cure yet.

AlanHo · April 22, 2010

I cannot help with a solution - but I notice that the date given in the first and last lines of the above report is 6/7/2010, which seems strange.

Has your computer changed it's date setting?

I must admit that if I were faced with this problem I would ensure all my data was properly backed up - then do a reformat and clean reinstall of Windows and my software. It would probably prove to be the quickest solution.

Out of curiosity I trawled google and found this on an old help forum...

: Temp Directory filling up with unnecessary log files, gradual system slow down

Cause : Missing gdiplus.dll file. This causes the Microsoft Installed (msiexec.exe) to continuously search for the dll file and create error log entires in the Temp folder.

Check Windows Task Manager and see two msiexec.exe processes executing continuously to create those error files.

Well here it is.

1. Follow the link http://www.dll-files.com/dllindex/dl....shtml?gdiplus

2. Download the dll file gdiplus.dll

3. Copy the file to the folder C:\Windows\System32 where C:\ is your windows drive

4. Restart

5. Check Windows Task Manager to see that this indeed solves the problem and no more msiexec.exe processes are executing.

Pudgex3 · April 26, 2010

I cannot help with a solution - but I notice that the date given in the first and last lines of the above report is 6/7/2010, which seems strange.
Has your computer changed it's date setting?
I must admit that if I were faced with this problem I would ensure all my data was properly backed up - then do a reformat and clean reinstall of Windows and my software. It would probably prove to be the quickest solution.
Out of curiosity I trawled google and found this on an old help forum...
: Temp Directory filling up with unnecessary log files, gradual system slow down
Cause : Missing gdiplus.dll file. This causes the Microsoft Installed (msiexec.exe) to continuously search for the dll file and create error log entires in the Temp folder.
Check Windows Task Manager and see two msiexec.exe processes executing continuously to create those error files.
Well here it is.
1. Follow the link http://www.dll-files.com/dllindex/dl....shtml?gdiplus
2. Download the dll file gdiplus.dll
3. Copy the file to the folder C:\Windows\System32 where C:\ is your windows drive
4. Restart
5. Check Windows Task Manager to see that this indeed solves the problem and no more msiexec.exe processes are executing.

Thanks for the info, but that didn't work.

The dll was missing, but adding it didn't change anything. As for the msiexec.exe, I just looked and I didn't even see 1 running, let alone 2 continuously.

I think it's time to format and reinstall.

DAMN.

Sign In

Windows XP creating too many MSI log files

Recommended Posts

Pudgex3

Link to comment

Share on other sites

andsome

Link to comment

Share on other sites

ɹəuəllıʍ ʇɐb

Link to comment

Share on other sites

Pudgex3

Link to comment

Share on other sites

andsome

Link to comment

Share on other sites

Boris

Link to comment

Share on other sites

AlanHo

Link to comment

Share on other sites

Pudgex3

Link to comment

Share on other sites

AlanHo

Link to comment

Share on other sites

Pudgex3

Link to comment

Share on other sites

Join the conversation

Browse

Activity

Important Information