Disabling the context menu items didn't really do much, sorry.
I now have Explorer++ and when I resized and snapped that window, the problem wasn't there so it's probably a software problem. If it's a software problem is there anything I can still do about it?
Here's what you can try for now. Download the attached file:
WER_Explorer.reg
Save it to your desktop.
Then go to:
Start > Run
then type:
regedit.exe
press Enter
Navigate to:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting
Right click on the registry key named Windows Error Reporting and choose Export
Give the file a name like WER_Backup.reg and save it somewhere so that you can easily find it again.
Then exit Registry Editor.
Double click on the file you downloaded (WER_Explorer.reg) and choose Yes when asked if you want to add it into the registry.
Reboot when done. Wait a few minutes after the reboot then try to crash Explorer. Once it has crashed have a look here and check to see if you have a dump file:
C:\Localdump
Zip the crash dump and upload it and attach it to a new post for us to look at.
NoteUntil the probem is fixed there's a handy utility that can restart Explorer with a single click.
Sordum's Small Tools
Rexplorer is part of Sordum's Small Tools package. If you extract the files and copy rexplorer.exe to somewhere handy you can run it when needed.
Let us know if you need help with extracting the file (Restart Explorer Utility) and running it.
Last edited by Callender; 25 Aug 2015 at 12:23. Reason: add info
Callender: I just did all those steps up until when I crashed Explorer. I checked C:\ and there's no Localdump directory or any new directory created. When I crashed Windows Explorer right before looking for C:\Localdump, I opened Task Manager, terminated Windows Explorer, and when it the popup said "Windows Explorer is not responding," I clicked "Restart the program" and not "Close the program."
In the control panel I selected "show hidden files" and unchecked "hide operating system files" and I still can't find C:\Localdump
Okay try this:
Start> Run then type services.msc - press Enter
Scroll down to Windows Error Reporting Service and if it's disabled - right click and set startup type to Manual. Then start the service. If it's set to Manual already but not running - start the service.
Then try this method of merging WER_Explorer.reg
Make sure that you are using an account with admin rights and that UAC is switched on.
Right click on the WER_Explorer.reg file and click on Merge.
Click on the Run button in the Security Warning pop-up.
Click on Continue (UAC), Yes, and OK when prompted.
Reboot.
The location you need to look for Explorer crash dumps is C:\Localdumps and not C:\Localdump
I just mention LocalDumps vs Localdump in case you tried to copy and paste the location instead of manually browsing to it!
If the above doesn't work - I have no idea why. It's never failed to work in the past!
There are other steps to try. Here is one of them:
Do you have Autoruns ?
If not - download it and run it. Wait for the scan to finish:
Once the scan is complete choose File > Save and save as a text file. Upload the text file and attach it to your next post. It will show Explorer Shell Extensions and we can see if any are currently known to be a problem.
Last edited by Callender; 25 Aug 2015 at 16:54. Reason: add info
What I meant to explain in the above post was - make sure Windows Error Reporting service is actually running before crashing explorer.
Hi Callender, as I'm going through these steps, I would like to ask: When you say "Reboot." you mean restarting the computer, right?
EDIT:
I uploaded the txt file that resulted from the scanning from AutoRuns.
Also, would changing to Win10 get rid of the problem? Will Windows 10 have a different explorer.exe program?
Last edited by NilmFoir; 25 Aug 2015 at 21:18.
Reboot does indeed mean restart. I'll look at your uploaded file later as I'm at work at the moment.
Re: Windows 10. Unless you are a confident user who knows how to make a system image backup I'd say it's early days for Windows 10. Personally I will wait for at least 6 - 12 months before deciding if I want to upgrade.
Other members could better answer your questions on Windows 10 but why not read through posts on Ten Forums?
Okay - any luck with crash dumps after starting Windows Error Reporting service?
From your uploaded file check version numbers then check for updates for:
7Zip
Google Drive
Notepad++
VMware Workstation
Microsoft Security Essentials
WinSCP from Martin Prikryl
Libre Office
Adobe Acrobat
Norton Anti Theft is out of date and no longer supported and should be removed.
See: https://support.norton.com/sp/en/us/...rProfile_en_us
Install any available updates or uninstall anything in the list that you don't use.
If the problem isn't resolved then it will mean downloading and scanning more thouroughly with some other software.
I think I just solved this problem 2-3 days ago (That's why I forgot to post here for a few days) However there might or might not be one caveat to my current blissful situation, which I will describe later in this post.
Whenever WinExplorer would crash on me, it happened whenever the window was in a maximized state and I would drag the top bar downward to resize it. An important detail I forgot to tell everyone was that the window would be the smallest dimensions a Windows Explorer window could be. And it would crash. :\
I was wondering if something was attempting to make the window smaller than its minimum possible dimensions, contributing to its crashing? But I'm not sure about that.
The way I solved this problem was that I used a program in which you can right-click the corner of a non-maximized window and select among three dimensions to resize the window to, instead of stretching the window manually with your mouse. After the trillionth time I crashed and restarted Explorer, I opened it up again and it was conveniently in a non-maximized state (the vast majority of the times when I open explorer, it starts out maximized). Then I right-clicked the corner of the window and set the non-maximized window to a certain width+height that was small yet greater than the minimum dimensions a winexplorer window can be. And it doesn’t crash anymore when I resize or snap it.
But I haven’t marked this thread as solved yet because there may or may not be one potential problem: If I were to (with my touchpad) stretch the window to its minimum possible dimensions, would the problem come back? I don’t wish to attempt this, but in the future I might forget and accidentally do this.
Thanks for letting us know. Setting specific window sizes isn't something I know much about. My explorer windows always open the same size as when the last used setting (all explorer windows)
Quote
