Annoying new temp/SP1/hotfix folders on root

shanghai_one · #1 12-04-2003, 06:33 PM

Hey, guys, need to see if anyone's seen this issue.

I have Gateways at work running XP/SP1. Having built an image ground up with all the XP updates and just OfficeXP with it's updates, I went ahead and imaged 10 other machines. Then I noticed on the C drive amongst the regular 7 or 8 folders that were there, that there were 15 or so folders with file names such as "o7d87e03h080wd00g7221e0...". Inside they had filenames and executeables named SP1 and HOTFIX. I had to change the security to Full Control before I could do anything to them. But I couldn't delete them as they errored out saying that "$shutdown$" or something like that was in use. What I had to do was make them hidden so that someone using the pc could find folders without wading through all those temp-like looking folders.

So my question is, did the windows updates do that before they were imaged? or did the imaging process cause those hotfixes to be placed on the root? either way, what can I do about it in the future...or now? I found this problem out after I had reimaged the original pc again with a new software added, so I don't have the original to compare.

I did read one article from microsoft stating that some hotfixes might place the temp file on the root and that I had to call microsoft directly for the fix... but i just can't believe 15 or 16 hotfixes would mess up like that...

thanks

snowmonkey · #2 12-05-2003, 06:09 AM

What imaging software was that ? I have used "Ghost 2003", "Drive Image" and "Acronis" and none of them seen to have this issue !!!

cheers

shanghai_one · #3 12-05-2003, 11:48 AM

I'm using the Altiris system...Don't know if that's the problem. I sure do miss Ghost! But fyi,

"979adf6280325d51c788521b24498b14"

is one of the folder names and inside:

"xpsp1hfm"

is an executeable

and "common" "sp1" "sp2"

are folders residing within.

But I guess I'll just rebuild one and see what happens. Thanks for the input!

shanghai_one · #4 12-07-2003, 12:58 PM

Yeah, it WAS the Altiris package that did it. Altiris is kindof like Microsofts SMS. Since all the pc's have Altiris clients on them, when Altiris notices that the pc doesn't have all the MS updates, it automatically pushes them down to the machine. But of course it's pushing the temp folders down on to the root. Hopefully they can fix it...Thanks

dhorne41 · #5 02-07-2005, 08:31 PM

Hey man...FYI I have the same problem. Except, I'm not using any imaging software, and the folder didn't show up on my root. I have 2 drives (1 SATA and 1 IDE) split into 4 partitions. C:, D:, E:, and F:. C is my root partition which Windows is installed on. Not sure which update did it because I didn't notice it right away, so it was either SP1 or SP2 because I did them in order. It created the strange folder "718b91b598ca5a4469bf" on my 'D' partition. Inside are the 3 subfolders, Common, sp1, and sp2. I left it that way for quite some time. This evening, I Fdisked....reinstalled XP on a clean C partition...but I'm still unable to delete that strange folder on my D drive. What gives?