Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Explorer crashes when moving files 2

Status
Not open for further replies.

DColcl

MIS
Sep 22, 2003
436
US
Moving files from one location to another crashes my Windows Explorer. I have Vista Business (Fully Patched) on a new Sony Laptop. I have the latest versions of Office 2007, Roxio and Norton 360 (Fully Patched), Virtual PC 2007. These are the latest programs that I have installed since I "remember" being able to transer files without Windows Explorer crashing.

In the event log I'm told to go to C:\Users\Dcolcl\AppData\Local\Temp\WEREC81.tmp.version.txt However, I am unable to find the location to change my View so that I can see hidden folders.

In Windows XP all I needed to go was to go to Tools\Folder Options and in the View tab simply change my settings. I'm unable to find this in Windows Vista's version of Explorer.

anyone able to show me how to navigate to these hidden folders so that I can read the error log?

Thank you,

Dan
 
okay. a simple Windows search gave me the answer to the way to view hidden files/folders. however, eventhough I am an Administrator to this laptop, I am denied access to the Local Settings folder. I do not see a "Runas Admin" when I right-click on this folder.

How do I get access to these hidden system files? Yes, I checked Windows Help this time and ..... it was no help.

Dan
 
Can you find what you want at this location?
C:\Users\Usernamexxxx\AppData\Local\Temp

"Run as administrator" is for use with .exe files not folders or files.

What is the location of the Local Settings folder you are trying to access?

The files that you may be talking about may be covered by this quoted explanation from a Microsoft Vista Tech.

"Here is the reason behind it. "The junctions are there to only provide appcompat for legacy apps and aren’t meant for a user to traverse through. The junctions have been explicitly set to block read through them by setting Everyone Deny Read. The main reason here is because these are just links to the actual location, so you dont want backup tools and other tools operating on your data twice, once from the original path and once via the junctions. There are scenarios where some of these junctions actually form a loop to support the appcompat for the old namespace in comparison to the new and in those cases allowing read through them is disastrous, for e.g. setup was broken for a week when the file system wasnt honorign the deny read.

Also as far as a user goes, you will never see these as they are system hidden, and you will need to take explicit action to see them by default."

Built-in Administrator Account Disabled

Is disabling Vista's User Account Control wise?
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top