Mystery files appearing

  • Thread starter Thread starter mcbennett
  • Start date Start date
M

mcbennett

I'm not sure this is the right group for this quewstion, but here
goes.
Files have from time to time appeared on my C: drive with the names,
and I quote,
7690c47d56d55049bf313cdf0b754,
67120ffd353ffcfa51d0264606e74396 and
188411718c5c2dd7c5.
A little investigation indicates the first has something to do with
service pack 2, but should I keep it? I have no clue on the others.
I create enough needless junk on my own, which I pare down from time
to time. Can I include this stuff in my purges?

Thanks
 
Hi,

You can delete them. As you mention SP2, I'm thinking maybe you are running
XP? This is a Vista group, and it's best to ask questions in the appropriate
group for your software to avoid misinformation.

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP

Windows help - www.rickrogers.org
My thoughts http://rick-mvp.blogspot.com
 
I'm running Vista Home Premium..
But I will delete, and thanks.
 
I'm running Vista Home Premium..
But I will delete, and thanks.
Later, that same day . . . Well, yes. I did remove them. Luckily
for me I establised a Restore point before I did. A half hour ago
Windows Explorer failed with a message that sounded like it had
something to do with what the expunged files did.
So I did a Restore, and the files are back, and I think the thing
works.

Nice try
 
Might want to check and see what's in them then, because it's not normal.

Yup, that's down below a bit. I looked to see if the MVP site could
help, but found all of this thread already there. OK, lots of copying
for me now (is Snipping Tool in Home Premium? HP's HELP section talks
about it but I can't find it.)

OK.
The first file in C: is
7690c47d845049bf313cdf0b754
and it contains (folders in caps, files lower case)
AMD64, I386, UPDATE, and a whole lot of .dlls and .exes and .gdl etc.

next is 67120ffd353ffcfa51d0264606e74396
It has a whole batch of eula files, (e.g. ei;a/1035.rtf), a lot of
setup*.dll, some WapEes.????.dll and so on

and finally 188411718c5c2dd7c5 which only has one file in it,
msxml6-KB927977-enu-x86.log, andI won't spend as much bandwidth as U
could with a full reading, but fyi, here's the start.

=== Verbose logging started: 12/4/2006 8:06:38 Build type: SHIP
UNICODE 3.01.4000.2435 Calling process:
C:\WINDOWS\system32\msiexec.exe ===
MSI (c) (54:F4) [08:06:38:625]: Resetting cached policy values
MSI (c) (54:F4) [08:06:38:625]: Machine policy value 'Debug' is 0
MSI (c) (54:F4) [08:06:38:625]: ******* RunEngine:
******* Product: c:\188411718c5c2dd7c5\msxml6.msi
******* Action:
******* CommandLine: **********
MSI (c) (54:F4) [08:06:38:625]: Client-side and UI is none or basic:
Running entire install on the server.
MSI (c) (54:F4) [08:06:38:625]: Grabbed execution mutex.
MSI (c) (54:F4) [08:06:38:828]: Cloaking enabled.
MSI (c) (54:F4) [08:06:38:828]: Attempting to enable all disabled
priveleges before calling Install on Server
MSI (c) (54:F4) [08:06:38:843]: Incrementing counter to disable
shutdown. Counter after increment: 0


One further note- after the note about using system restore, the
program still seemed not quite right, so I went back to a full backup
I'd made two days before that, found these files and overwrote them
into what is now what I have now, and things are better.

Curiouser than ever.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Back
Top