Problems viewing Temporary Internet File Folder

[Hercules1946]

Hello everyone - Ive just joined the forums. After Malwarebytes had found some PUP files and seemed unable to delete them, I tried to locate the files manually (using the path detailed by Malwarebytes).
I got as far as C:/Users/[Uname]/Local Settings/Temporary Internet Files and was told that access was denied to the TIF. I tried looking for properties to reset, but right-click gave no options.
So it seems that possibly hazardous files can be stored below this folder that can't be removed because of the access restrictions. What can I do to gain access to the files?

I have Vista Home Premium 64 Bit
Internet Explorer 9

 

[MilesAhead]

The easiest method would be to use Unlocker. It allows you to delete protected files on next boot. It can do it because it runs before login.

 

[Hercules1946]

The easiest method would be to use Unlocker. It allows you to delete protected files on next boot. It can do it because it runs before login.

The main purpose of this program seems to be to delete files and Im really wanting to see whats in there as there are a lot of files. I have four users on the machine and each one has a path structure C:\Users\[Name]\Local Settings\Temporary Internet Files\ Content.IE5\..\ with loads of files. None of these can be accessed, the ownership can't be changed as there are no accessible properties for the TIF level. Also IE points to a different file structure C:\Users\[Name]\Appdata\Local\Microsoft|Windows\Temporary Internet Files, which means unwanted files will never be removed.
Will this Unblocker allow files to be viewed only and if not what other way is there?
Im wondering if these folders might be some kind of indirect pointer to a different file structure which programs can navigate but Windows Explorer can't. If I use CMD prompt to display the sub-directories, they aren't there, but if I type an individual sub directory name in ithe CD command they are there ...

 

[MilesAhead]

Are you using the true administrative account? Unfortunately I use IE only if there's no alternative. So I'm not very experienced with its quirks and usage. The folder sleight of hand may be due to directory redirection on 64 bit OS. 32 bit programs use SysWow64 emulation. If not sure about the admin account see tutorials how to activate the true Administrative account.

 

[townsbg]

C:/Users/[Uname]/Local Settings/ is a shortcut that Microsoft has placed there but also prohibited access to (don't ask me why). The real path is C:\Users\[Uname]\AppData\Local\Microsoft\Windows\Temporary Internet Files. However you can use either disk cleanup or my favorite ccleaner to clear internet temp files as well as other garbage. The user profile directory structure was changed in Vista and the path you posted is the old path used in XP.

 

[Hercules1946]

C:/Users/[Uname]/Local Settings/ is a shortcut that Microsoft has placed there but also prohibited access to (don't ask me why). The real path is C:\Users\[Uname]\AppData\Local\Microsoft\Windows\Temporary Internet Files. However you can use either disk cleanup or my favorite ccleaner to clear internet temp files as well as other garbage. The user profile directory structure was changed in Vista and the path you posted is the old path used in XP.

Hi Townsbg
I thought I recognised that file structure from my old XP machine..... Its strange how they have got there though, because this computer was bought new with Vista pre-installed ????
I eventually used a bit of code I found on the net to clear the files out. I think it was used as a .cmd file? that kills IE and then removes all the files.

Thanks to everyone who has posted, and Im sorry about the delay in replying.

 

[townsbg]

Those links where added to my installation so I don't know why but they are added to all installations. The only thing I can think of is backwards compatibility. Strange though that they won't let people use the links but that M$ for you; they do things their way and don't care what others think or if it really makes any sense. The path I posted is the correct structure as introduced in Vista.