Windows 10: Explorer.exe hangs with mouse right click W10

Not with every boot, but 1 of 3 in average. After upgrade from W8.1 explorer exe hangs with mouse right click when clicking on a folder in file explorer, does not hang when clicking on a file. Also working on desktop. A reboot will make the problem go away, but shut down hangs also, have to reset via power button. The problem does not occur with every boot. Would appreciate any help on this. MS tech support could not find any solution and it's crowded because of W10 upgrades.



Event ID log from application hang: The program explorer.exe version 10.0.10240.16431 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel.
Process ID: 2570
Start Time: 01d0e24fdef25a3b
Termination Time: 23
Application Path: C:\Windows\explorer.exe
Report Id: 257ee579-4e43-11e5-9bd1-c86000bc291c
Faulting package full name:
Faulting package-relative application ID:

:)

 

File Explorer hangs on Windows 10

I've discovered at least one cause of the hanging. It's an interaction between Carbonite, a remote backup system, and File Explorer.

Carbonite has several configurations for scheduling backups. One configuration blocks backups during certain hours of the day; another allows backups at all hours. I found that Explorer hangs sometimes when Carbonite is set to 'Do not backup during certain
hours.' When I set Carbonite to 'Back up continuously,' File Explorer functions properly.

I discovered this by using Windows Task Manager to analyze the wait chain for explorer.exe after Explorer hung. When Carbonite was set to 'Do not backup during certain hours,' explorer.exe waited for Carbonite to complete. However, Carbonite didn't complete
because it was set to wait, so explorer.ex waited as well. When I changed Carbonite to 'Back up continuously,' explorer.exe stopped waiting immediately and functioned properly.

Test this yourself the next time Explorer hangs. In Task Manager, right-click Windows Explorer and select 'Go to details.' Find explorer.exe, right-click it, and select 'Analyze wait chain.' Note that Explorer doesn't hang all the time, so there must be
something else going on in addition to the Carbonite connection.

explorer.exe is set to Normal priority. I'm going to set it to High and see how that plays out.

 

I cannot copy and paste on Windows 10. I can copy but am unable to paste. The right hand click on the mouse does not do anything

Hi!

Ctrl +C for copy, Ctrl + V for paste. Right click hardware may be broken. Your copy of W10 may be broken. My copy of W10, copies and pastes with mouse click, so there is nothing wrong with W10.

 

Hey mate,

run this scan: SFC Command - Run in Windows 10 - Windows 10 Forums

Make sure you have updated all drivers. Meaning you should go to your computer/motherboard manufacturer and get the most recent Win10 drivers. These are important to have installed.

 

Hi, thanks for reply.

Unfortunately my motherboard does not have any specific W10 drivers (Asus has not released any), it's 2 years old.
SFC scannow returns, can't fix all system files, which is weird cause after the upgrade did a clean install of W10. Many though have similar experiences.

 

Hey mate,

Without the correct drivers, there will always be the chance that the computer stops responding. You will have to make the decision to stay with windows 10, or revert to the old install: Windows 10 - Go Back to Previous Windows - Windows 10 Forums

You can keep trying... Use that SFC scan again, and restart after each instance... 2 more times. Sometimes it takes that long. Other than that, there may be other experts who can walk you through more steps you may be able to take to make things run well enough.

 

Hi there. Just because it's new does not necessarily mean it's ok. You may want to run DISM command before sfc /scannow for the Windows component store may corrupted. scannow cannot fix anything if it is corrupted. It also may take 2 or 3 tries scannow to fix files.

DISM - Repair Windows 10 Image - Windows 10 Forums

 

Have tried booting into Safe Mode to see if the same problem occurs?

 

It could be a corrupt context menu option, so if that's the case, a computer refresh/reset should easily resolve it. If 're not comfortable with doing that, download CCleaner, go to the Tools, go to Startup, go to Context Menu, then remove some stuff under "Directory" and "Folder" that think could be causing the problem.

 

Thanks for reply. Ran dism /online /cleanup-image /restorehealth and it completed successfully. The problem is also that the error is not on every boot. Sometimes the explorer.exe hang problem occurs once per 2 days. Not had the chance yet to boot into safe mode etc. Have read about context menu corruption but have not succeeded to solve it that way either. Running SFC scannow, to check if something has changed. After DISM the SFC scannow is OK, it repaired some files.

 

Please run it till it says nothing needs a repair (a restart after each one). Up to 3 times until clear or it says no more about repair.

 

SFC scannow returns with nothing to fix. Have to follow up a few days to see if the problem has been fixed or not. A couple of reboots and have not experienced the hangup, maybe it's fixed-or not. As said have to run Windows for a few days. Thanks for help. If it's solved have to give credit to someone for fixing the issue...?

 

splitsecond, chances this can be your issue as third party software puts items in your context menu when you right click causing issues to explorer.exe common issue in past. Use CCleaner disable one at a time. One other choice is clean boot see if it happens there, this is if still have issues and SFC or Dism could not help you. Happens in clean boot could also be some conflict with a running process from third party application. http://windowsinstructed.com/clean-b...ndows-windows/

 

Hopefully that did it for you. If you choose to, you may rep members by clicking on the thumb up icon on the lower left of anyone's post.

 

You fixed the issue. We just acted as guides *Wink