[Chris - Thecleancar]

I need advice (once again)

I have 2 folders/files on my HDD as follows C:\9906b90d6b3a10793\%temp%dd_msxml_retMSI.txt and C:\Config Msi

These look like they are left over from an install or update.
This PC is running XP Home SP2.
I have copied 2 small sections of the .txt file (total size 51k) below for information

=== Logging started: 05/05/2007 11:17:01 ===
Action start 11:17:01: INSTALL.
Action start 11:17:01: LaunchConditions.
Action ended 11:17:01: LaunchConditions. Return value 1.
Action start 11:17:01: FindRelatedProducts.
Action ended 11:17:01: FindRelatedProducts. Return value 1.
Action start 11:17:01: IsPendingRebootKey.
No PendingFileRenameOperations

AddRefcountMsxml returns the code 0
<EndFunc Name='Wdsfpca_AddRefcountMsxml' Return='0' GetLastError='0'>
Action ended 11:17:03: InstallFinalize. Return value 1.
Action start 11:17:03: RemoveExistingProducts.
Action ended 11:17:03: RemoveExistingProducts. Return value 1.
Action ended 11:17:03: INSTALL. Return value 1.
Property(S): ProductCode = {5A710547-B58E-488B-828D-CA9A25A0533C}
Property(S): Manufacturer = Microsoft Corporation
Property(S): ProductVersion = 6.00.3890.0

Would it be wise to delete these folders/files ?

Thank you in advance for any help or advice.

[Advertisements]

msi reminds me of msi live update i ran yesterday after my reformat.
the thing with that was msi live update saved install files to a directory in program files by default.
i assume that the install files were automatically removed, but i havent checked yet.
apparently, if your directory is an installation directory, its creator didnt include a "delete installation files" clause.
anywho, its either something with msi or or what ive read could be "microsoft installer."

while some here may disagree, i would delete it.
i delete everything i do not know what its purpose is and have come across problems very seldom.
especially right under my nose in C.
im pretty confident in XP to correct any issues this may cause, if not XP, then myself, and for your sake, everyone elese here smarter than me.
but you can always wait for more opinions.
im sure some1 will come up with a solid answer on your directories origins.

[washout]

msi reminds me of msi live update i ran yesterday after my reformat.
the thing with that was msi live update saved install files to a directory in program files by default.
i assume that the install files were automatically removed, but i havent checked yet.
apparently, if your directory is an installation directory, its creator didnt include a "delete installation files" clause.
anywho, its either something with msi or or what ive read could be "microsoft installer."

while some here may disagree, i would delete it.
i delete everything i do not know what its purpose is and have come across problems very seldom.
especially right under my nose in C.
im pretty confident in XP to correct any issues this may cause, if not XP, then myself, and for your sake, everyone elese here smarter than me.
but you can always wait for more opinions.
im sure some1 will come up with a solid answer on your directories origins.

[bobmad]

Here is the other opinion. I never delete a program or directory when I do not KNOW what it is.

If I see one that I don't know, I'll research it before I delete.

[/* old man stroy on]
I once had a designer at a company I worked for who was having an error message appear 1/10 times he booted his machine. He told me about it once. I checked on it and it was driver related (early days of windows 2000). I was waiting for a newer driver to come out.

He never told me the error was reoccurring until one day I was trying to help him boot his machine. His machine was having serious problems.

Long story short I eventually found out he tried to fix this intermittent error by deleting the program that started just before the error message. The program he deleted was Command.com.

Took me some time to fix. I've had other employees erase their config, autoexec, assorted .DLL's because they didn't know what they were. [old man story off */]

Now I'm Paranoid.....but are you paranoid if they ARE out to get you?

Be careful. You are both obviously too smart to do something like I described. Please stay that smart.

[1101doc]

Research is always best before action. The question of unknown files really is vital only when it is an active file: .sys, .ocx, .exe, .dll, .msc, .mmc, .vbs, and so on.
Any file on the system can be scanned for known problems at two excellent online services:
http://www.virustota.../en/indexx.html
http://virusscan.jotti.org/

Yes, sometimes .temp files are left over after updates, and I fully understand the desire to know what is being stored on the local drive. But since one of the files relates to Windows Installer, and contains the term "config," I would want to be sure that I knew what I was doing before I made any modifications, and/or deleted it.

When in doubt, don't.
If it ain't broke....

[washout]

found this option on windows knowledge base.
it was in an article relating to a failed install of office.
just rename the folder from "Config MSI" to "Config MSI.old."
if you have a problem, either xp will fix it or it wont.
in the latter, just name it back.

[Chris - Thecleancar]

Thanks to washout, 1101doc and bobmad

I think I'll leave well alone and do a bit more 'Googling' on this.

Thanks