New
#11
As you stated so eloquently.
OkaySo, now, back to the problem at hand.
Have a nice day.
I spent some time looking at Process Monitor to see what things take place when "open file location" is selected. Unfortunately, there are about 8000 things that happen.
I tell the users that I support to avoid tools that move apps from one computer to another computer - even if the two computers use the same OS. I've seen too many problems caused by these apps.
:-(
I completely understand. If it was a user setting issue, I would think that creating a new user and/or using the hidden Admin account would work. Neither accounts' OPEN FILE LOCATION function.
The odd thing..when I manually stop and restart explorer, OPEN FILE LOCATION works temporarily and then goes back to the same behavior.
Perhaps it's a preference someplace? I am registry editing comfortable..if I knew where explorer gets its startup defaults from I could probably find it.
Rick
Try running portable Explorer++ for test purposes.
Pin the executable to your taskbar if you like for easy access. Navigate to a shortcut and right click then "Open File Location"
If it works then it might be time to start looking at shell extensions.
Attached is a list of all my shell extensions.
Explorer++ allows me to RESOLVE LINK the shortcut and open the file location.
Hmmm
Rick
Since Explorer++ works it means that it is not a system file problem but likely to be a software problem. These things can be hard to track down. What software did you use to provide that list of shell extensions?
There are various ways to look at shell extensions or anything that integrates with Explorer but I've never found a single utility that lists everything.
Try portable Autoruns
Extract the files to a folder somewhere. Right click Autoruns.exe and choose "Run as administrator" then wait for "Ready" to appear at the bottom of the window once the scan has completed. Click on the Explorer tab and view the listed entries.
If you see any software listed where you do not use the right click context menu entry then you can uncheck the entry to disable it. For everything else listed in the "Explorer" tab - note the names of the software and check that you are using the latest patched versions.
If you like you could also save Autoruns results as a text file and upload it and maybe we can spot something.
I used Shellexview portable (no install) to view all the shell info. Its a nirsoft application.
I ran Autorun. Removed everything that i could think of and still the same behavior. Stop explorer process and restart with RUN from task manager. OPEN FILE LOCATION works fine until explorer loads completely. I agree it MUST be some setting that is stopping functionality. I am stumped as to which one.
I did read that Internet Explorer 9, when installed caused a similar behavior, but the fix was to uninstall. I have 11 installed now and have tried removing it it. No change.
I am usually quite good at locating and eliminating this type of issue. This has has me stumped.
Rick
RE: ShellExView.
As a test run ShellExView and sort by "Company"
Scroll down the list and try disabling any non microsoft entries then reboot and test to see if the issue remains.
Also grab a copy of ShellMenuView from Nirsoft and run it. Sort by "Company" then look through the list at non microsoft entries where the "File Type" column shows:
Directory
Drive
Folder
*
Consider disabling those as a test.
If you've got Ccleaner you could also take a look at Tools> Startup> Context Menu
Check for and install updates for any non microsoft software that installed a shell extension.
If you still get the same problem after disabling non microsoft entries undo the changes that you made (re-enable the entries that you disabled)
If the problem is fixed then re-enable entries in small groups until the problem returns.
If the above doesn't produce any results you might want to consider running a scan with UVK and then zip and upload the results.
If you have a system image backup you might want to run the following fix although it's not guaranteed to solve the problem:
Note: Don't mess about with UVK just yet. Try the other steps first.