Windows Explorer Freezes

Hi Everyone,

I am experiencing random freezing of a Windows Explorer (file manager) window. What this means, is that I cannot click on a file, I cannot minimize, close the window etc.

However, I can open another instance (or more) of Windows explorer, that I can open files, copy & paste, drag & drop, close the window, etc

The only way I can get rid of the frozen window is going to task manager & telling Explorer.exe to restart

Has anybody else experienced this & if so, is there a fix?

Thanks in advance

You are talking about what is called File Explorer in Windows 10 ? Do you receive any windows stating it has stopped responding, when you go to Task Manager before ending it, did it show in the first processes tab that it was not responding ?

Can you try this in Safe mode and let me know if the issues persists.
https://www.tenforums.com/tutorials/2...dows-10-a.html

Scan system directory
If File Explorer crashes on startup, go to your Start Screen and launch the run box.
On the Run box type “cmd” and click ok”.
On the cmd window type “SFC /SCANNOW” and press enter.
Wait while System File Checker is repairing your computer.

File explorer is correct. I guess I'm used to it being called Windows Explorer. I can try going to safe mode, but it's so random, it could do it right away & the next time might be days later.

When I look in task manager nothing says not responding, nor do I get anything that says it froze.

Last, File explorer doesn't crash, it just freezes

mayorville said:

File explorer is correct. I guess I'm used to it being called Windows Explorer. I can try going to safe mode, but it's so random, it could do it right away & the next time might be days later.

When I look in task manager nothing says not responding, nor do I get anything that says it froze.

Last, File explorer doesn't crash, it just freezes

Can be the cause of a third party software, shell extension or driver the reasons to try in safe mode. I know this can be hard to wait on it, but it is one way to be sure if it is or not. Can take the suggestion of other person run a System File checker also.

Have you received all Windows updates up through Dec.8 successfully ?

System File Checker, (Admin) Command Prompt copy and paste this and press enter, let it finish
sfc /scannow

Same open command prompt copy and paste this, press enter, let it finish

Dism /Online /Cleanup-Image /RestoreHealth

Both will take time to complete, then Reboot (restart) PC after both are complete.

Sorry for the delay. Yes I am current on Windows updates.

I tried running the SFC /scannow & it came back with:

Windows Resource Protection found corrupt files but was unable to fix some
of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
example C:\Windows\Logs\CBS\CBS.log. Note that loO gging is currently not
supported in offline servicing scenarios.

When I open the CBS.log file, most of it says "00004f40@2015/12/20:07:46:53.175 Primitive installers committed for repair"

The last portion of it is below:

------------------------------------------------------------------------------------------------------------------------------------------------------
2015-12-19 23:46:53, Info CSI 00004f48 Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22\opencl.dll do not match actual file [l:10]"opencl.dll" :
Found: {l:32 Ui1iPYLRlrK/KdPVb2btwB5JqasIeak0eCk42vnG8bQ=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}
2015-12-19 23:46:53, Info CSI 00004f49 [SR] Cannot repair member file [l:10]"opencl.dll" of microsoft-windows-RemoteFX-clientVM-RemoteFXWDDMDriver-WOW64-C, version 10.0.10586.0, arch Host= amd64 Guest= x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2015-12-19 23:46:53, Info CSI 00004f4a@2015/12/20:07:46:53.263 Primitive installers committed for repair
2015-12-19 23:46:53, Info CSI 00004f4b Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22\opencl.dll do not match actual file [l:10]"opencl.dll" :
Found: {l:32 Ui1iPYLRlrK/KdPVb2btwB5JqasIeak0eCk42vnG8bQ=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}
2015-12-19 23:46:53, Info CSI 00004f4c [SR] Cannot repair member file [l:10]"opencl.dll" of microsoft-windows-RemoteFX-clientVM-RemoteFXWDDMDriver-WOW64-C, version 10.0.10586.0, arch Host= amd64 Guest= x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2015-12-19 23:46:53, Info CSI 00004f4d [SR] This component was referenced by [l:125]"Microsoft-Windows-RemoteFX-VM-Setup-Package~31bf3856ad364e35~amd64~~10.0.10586.0.RemoteFX clientVM and UMTS files and regkeys"
2015-12-19 23:46:53, Info CSI 00004f4e Hashes for file member \??\C:\Windows\SysWOW64\opencl.dll do not match actual file [l:10]"opencl.dll" :
Found: {l:32 g2VAunZ6/2J1G3oL7kf9fjInPUA9VYeiJcl9VKgizaY=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}
2015-12-19 23:46:53, Info CSI 00004f4f Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22\opencl.dll do not match actual file [l:10]"opencl.dll" :
Found: {l:32 Ui1iPYLRlrK/KdPVb2btwB5JqasIeak0eCk42vnG8bQ=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}
2015-12-19 23:46:53, Info CSI 00004f50 [SR] Could not reproject corrupted file [l:23 ml:24]"\??\C:\Windows\SysWOW64"\[l:10]"opencl.dll"; source file in store is also corrupted
2015-12-19 23:46:53, Info CSI 00004f51@2015/12/20:07:46:53.293 Primitive installers committed for repair
2015-12-19 23:46:53, Info CSI 00004f52 [SR] Repair complete
2015-12-19 23:46:53, Info CSI 00004f53 [SR] Committing transaction
2015-12-19 23:46:53, Info CSI 00004f54 Creating NT transaction (seq 2), objectname [6]"(null)"
2015-12-19 23:46:53, Info CSI 00004f55 Created NT transaction (seq 2) result 0x00000000, handle @0x4ec
2015-12-19 23:46:53, Info CSI 00004f56@2015/12/20:07:46:53.304 Beginning NT transaction commit...
2015-12-19 23:46:53, Info CSI 00004f57@2015/12/20:07:46:53.321 CSI perf trace:
CSIPERF:TXCOMMIT;21234
2015-12-19 23:46:53, Info CSI 00004f58 [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction have been successfully repaired
---------------------------------------------------------------------------------------------------------------------------------------------

It looks like other people are also having the same issue, as I found this:

http://answers.microsoft.com/en-us/w...89d137b?page=1

When I run dism /online /cleanup-image /restorehealth,

it comes back with the following error: Error: 0x800f081f
The source files could not be found.
Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see http://go.microsoft.com/fwlink/?LinkId=243077.

When I was reading the Microsoft answers thread, it appears I need to extract the windows files from the ISO & have it point to that folder, which I will try later on today

I'm also trying other things also like instead of using Edge, I'm using IE to see if maybe Edge might also be causing the issue.

This issue is due to NVIDIA Display drivers as many here and even me have this issue. I can see it by the OpenCl.dll it is trying to repair.
Assuming you have a NVIDIA Video card. Do not think this is related to your explorer issues.
There is a way to correct this and then reinstall NVIDIA Drivers and do run a SFC scan. Something needs to be corrected by NVIDIA or Microsoft.

Do you have a Windows 10 ISO file ? If not can get one here, choose correct version, first one Windows 10 and correct bit,32 or 64bit
http://www.microsoft.com/en-us/software-download/techbench


Know had issue with file explorer, see if you can do this.
After you download the ISO mount the ISO from File explorer, right click the ISO select Mount (from Context Menu)
In File explorer notice the drive letter used to Mount the ISO and use this letter in place of the X in this command and copy and paste it into (Admin) Command Prompt

DISM /Online /Cleanup-Image /RestoreHealth /source:WIM:X:\Sources\Install.wim:1 /LimitAccess

Let it finish may take awhile, let me know of outcome. If successful try regular command
Dism /Online /Cleanup-Image /RestoreHealth

If that is successful run sfc /scannow

Let me know how it goes, it then may show it found files and was able to correct them this time.

After that download latest NVIDIA drivers for your Display adapter.