Currupt files - Unable to delete

17-05-2005, 19:56

I've just got back from my mates house who rung me up since he has a problem with his computer. He said he kept getting a load of error messages on start up when Windows began a scan on files, and when I saw the list it was a load of files in the Temp internet files folder, and after the list had been completed a BSOD came up and restarted the system. Skipping the scan lets me get into Windows, and then everything from there is fine. Now, I can't see what the message is on the BSOD as it keeps restarting instantly after it comes up, and I checked to make sure "auto restart" was unticked and it is, so it's not listening to that command. I looked in the folder where the files were, and by the file names either a virus has got them or the HDD has got it's self currupt. The file names just had random letters/numbers/symbols, like 48vhd-? etc. I tried to delete them and it said it couldn't read from the source file, and therefore cannot delete them.

I've done a virus scan with Avast totally updated, ran Spy Bot and Adaware, updated Windows fully and cleared the temp internet files folder (automatically and manually) which all have not worked. I can't run a full disk scan to scan for bad sectors as it always starts with the files, resulting in the currupt files and coming up with the BSOD again.

His system is running Windows 2000 Pro SP4.

Is there any way to get rid of these files? Has a virus infected the system or is the currupt files and the BSOD a sign of a dieing HDD?

Thanks!

Raistlin · 17-05-2005, 19:58

Not sure what they are but have you tried deleting them from the Command Prompt?

17-05-2005, 19:59

Quote:

Originally Posted by Raistlin

Not sure what they are but have you tried deleting them from the Command Prompt?

I never gave that a try, was the command delete file/folder-address-here?

Raistlin · 17-05-2005, 20:05

I think it's

del <insert entire path here> actually, although you should be able to go to the individual folder (by using the cd <directory name here> command) and then just tell it to del <file name here>.

Been a while since I tried it like that though, you may find that Winodoze still protects the files

Gareth · 17-05-2005, 20:06

Yeah, but you could try using del /F

Do a del /? to see a list of all the possible parameters for the delete command.

17-05-2005, 20:17

Will give it a try the next time I go around, thanks

greencreeper · 17-05-2005, 21:33

Start... Run... cmd
chkdsk /f
Reboot

Richard M · 17-05-2005, 21:38

Temporary Internet Files?
Nothing like some good old IE-Windows integration eh?

Raistlin · 17-05-2005, 21:39

Quote:

Originally Posted by Richard M

Temporary Internet Files?
Nothing like some good old IE-Windows integration eh?

Aaaaaaargggghhhhhh - here we go again......

Tezcatlipoca · 17-05-2005, 21:50

Quote:

Originally Posted by Raistlin

I think it's

del <insert entire path here> actually, although you should be able to go to the individual folder (by using the cd <directory name here> command) and then just tell it to del <file name here>.

Been a while since I tried it like that though, you may find that Winodoze still protects the files

There's a way around it

I had problems recently with undeletable files, & even using the Command Prompt didn't work (on its own).

A Google found this....

1) Open a Command Prompt, & "cd" yourself to the location of the undeletable files.

2) Bring up the Task Manager. Select the Processes tab, find & select "explorer.exe" & select "End Process"

3) Use the Command Prompt to delete the file(s)

4) Go back to the Task Manager, go to "File" then "New Task (Run...)" & enter "explorer.exe".

NB: This was using XP Pro

17-05-2005, 22:12

Quote:

Originally Posted by Richard M

Temporary Internet Files?
Nothing like some good old IE-Windows integration eh?

Don't you ever quit?

GC, wouldn't that just do what is already happening on boot up?

greencreeper · 17-05-2005, 22:17

Quote:

Originally Posted by Electrolyte

GC, wouldn't that just do what is already happening on boot up?

On boot is it running a scandisk or chkdsk? If it's crashing when running the latter, that would not be good

17-05-2005, 22:37

Quote:

Originally Posted by greencreeper

On boot is it running a scandisk or chkdsk? If it's crashing when running the latter, that would not be good

Not sure which one it is, but it starts off with all the files first then physically on the drive.

greencreeper · 17-05-2005, 22:47

Quote:

Originally Posted by Electrolyte

Not sure which one it is, but it starts off with all the files first then physically on the drive.

Sounds like a scandisk.

Halcyon · 17-05-2005, 22:51

Is there no way to get into Safe Mode and scanning from there ?