Windows 10: Only one folder crashes when right-clicked

I am having a heck of a time trying to solve an unusual problem.

The folder in question is the Downloads folder in "This PC". This folder is not the downloads folder I wish to use and so I have another folder set up, which works fine in Quick Access. So I want to change the shortcut in "This PC" to that folder.
I right-click on the Downloads folder in "This PC" and Explorer locks up and has to be restarted by clicking the red X icon. This only seems to occur when I right click on that folder. The crash doesn't happen anywhere else in Explorer.
I can access this folder by double-clicking, but I can't right click on it. I can't right click on files in the contents either without the crash occurring.

What I've done so far:

• SFC /scannow --- no problems detected
• Changed download location in Edge. ---- didn't do anything
• ShellExView. Disabled all non-Microsoft context menus. ----didn't do anything
• What is Hang---- it found a glitch

There was a bunch of code below this. I can post it if you think it is helpful. I am out of ideas.

:)

 

2017-11 Cumulative Update for Windows 10 Version 1709 failed

I think a clean install might be the only option, everything else is updated and computer isnt old at all. The pain is I cant back up my personal files because strangely one of the symptoms is when I right mouse click to copy (or just move from one folder
to another) explorer crashes.

 

Explorer.com on Windows 10 crashes and restarts when I try to create a new folder.

I renamed the two dll's and it still crashes.

Dump File: explorer.exe.7808.dmp

I caught one thing that is making the problem manageable, the "New Folder" button inside the File sub-category in Explorer creates folders without crash. Also, ctrl+shft+n creates them without incident. It still crashes when I right click to create a folder
or try to create one while saving a file inside a program, ie Word. Do these methods work outside shell.dll?

Thank you again for all the advice,

Slate

 

Hi, in Shellexview, did you also note under Options, 32 bit options? This exposes another set of extensions.

Have you also checked the rt click in:
a. Safe Mode
b. After a clean boot?

 

A) I set ShellEXView to 32bit and disabling the 2 options didn't result in any changes.
Going to try your suggestion letter B) later.

 

Does explorer crash, if you right click in tree view, too?

 

Yes, in the tree view- that is where I frequently try to click it.

Update:
Booted in Diagnostic mode via MSCONFIG. Was able to right click the folder in Tree View. No crash, was able to access properties but it only gave me the general properties tab- no other options were available. So I wasn't able to change any settings there.
I believe that I need to find a way to change the system download folder.

 

Try option 2 or others in tutorial to reset user folder location by Brink.

When you reset your download location you can try to move it. If you check tutorials, there is one to move folder around etc.

Edit: there is another tutorial by Kari: How to move user folders around. More sophisticated.

Neither of them directly solve your problem, but it may be solved in the way.

 

The folder is possibly crosslinked, and refers to itself in a recursive manner.

see

Drive Error Checking in Windows 10 - Windows 10 Forums

to check your drive for errors

You will probably need to run Chkdsk C: /f from an admin command prompt, and perhaps check the drive L: as well

 

Thanks for everyone's help! AndreTen- downloading and running the BAT file got the folder unstuck, which then allowed me to move it to the folder I wanted designated for the downloads. Tried right clicking 3 times and the error is gone!

 

That's great. Good job!

Just to confirm (for possible future reference), you downloaded .bat file from Brink's tutorial and that solved the problem?

 

Yes, that's correct. I used the specific bat file for downloads. There are many in the Brink's tutorial site. I used it 2 weeks before but it didn't work- presumably, I downloaded the wrong bat file? Either way it works now.