same problem.
also crashed on shell32!checkfiletypeforshellnew+32 because of null pointer
I fixed it just renamed/removed
\HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Discardable\PostSetup\ShellNew
from windows registry
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I have been having problems creating new folders for months, since at least late 16 or early 17. The problem has grown worse and I can no longer create folders at all in my primary account. I have no problems renaming folders.
There are other discussions on Microsoft regarding this problem. I have spent over a day trying these recommendations and I tried a third party app to see if there was a conflict between com objects. No progress.
I am running the latest version of Win 10 but this issue has continued over several updates.
I enabled the main administrator account and no problems with that user. I am running out of ideas and am leaning toward either a complete rebuild and/or changing my primary user to the admin account, which I know is not recommended. My concern is that this might come up again and I would like to figure out what is going on.
I pulled up my event logs and am posting what I have below.
Any ideas?
Thanks,
Slate
Fault bucket 120794819141, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0
Problem signature:
P1: explorer.exe
P2: 10.0.15063.447
P3: 951324bb
P4: SHELL32.dll
P5: 10.0.15063.483
P6: cbf15fae
P7: c0000005
P8: 0000000000435536
P9:
P10:
Attached files:
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER57BC.tmp.WERInternalMetadata.xml
These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_explorer.exe_2dec53faf366302309f415ee046c83639e8f8_10d58a87_2a5c5a5c
Analysis symbol:
Rechecking for solution: 0
Report Id: bf267806-c538-4918-b86f-311ed8da9292
Report Status: 268435456
Hashed bucket: 99fb82bd8143ad4ef202387f256fd6f8
Faulting application name: explorer.exe, version: 10.0.15063.447, time stamp: 0x951324bb
Faulting module name: SHELL32.dll, version: 10.0.15063.483, time stamp: 0xcbf15fae
Exception code: 0xc0000005
Fault offset: 0x0000000000435536
Faulting process id: 0x1e7c
Faulting application start time: 0x01d3058433c0eaf1
Faulting application path: C:\WINDOWS\explorer.exe
Faulting module path: C:\WINDOWS\System32\SHELL32.dll
Report Id: bf267806-c538-4918-b86f-311ed8da9292
Faulting package full name:
Faulting package-relative application ID:
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Answer accepted by question author
same problem.
also crashed on shell32!checkfiletypeforshellnew+32 because of null pointer
I fixed it just renamed/removed
\HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Discardable\PostSetup\ShellNew
from windows registry
There are some third party modules loaded in Safe Mode however I did not see any of the three previously referenced.
Can you provide the following information which may help determine any issue(s):
Windows Key + R > type msinfo32 in the "Open" box > OK > File > Save > then save as an .nfo file
Then make the resulting .nfo file available via OneDrive.
Also, can you do the following:
Windows Key + R > type eventvwr in the "Open" box > OK > expand "Custom Views" and then right-click "Administrative Events" > select "Save all events in Custom View As" and save as an .evtx file
Then make the resulting .evtx file available via OneDrive.
I might suggest to try to obtain a user mode dump which has the potential to pinpoint the cause.
You can configure Windows to create user-mode dumps. Create a System Restore Point first.
If you copy and paste the following in Notepad and save as a .reg file (save with the .reg extension and give it any name such as dump.reg), then right-click the .reg file and select "Merge" to add to the registry, a .dmp file at the time explorer.exe crashes should be created in the C:\CrashDumps folder:
Windows Registry Editor Version 5.00[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps\explorer.exe]"DumpFolder"=hex(2):43,00,3a,00,5c,00,43,00,72,00,61,00,73,00,68,00,44,00,75,\00,6d,00,70,00,73,00,00,00
After Explorer (explorer.exe) crashes, can you then make the .dmp file available (provide link) via a public folder on OneDrive or similar site?
Here's a link on using OneDrive:
http://windows.microsoft.com/en-ca/onedrive/share-file-folder
More info on collecting user-mode dumps:
http://msdn.microsoft.com/en-us/library/bb787181(VS.85).aspx
To stop the creation of the user mode dump files run the following registry file:
Windows Registry Editor Version 5.00
[-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps\explorer.exe]
You can delete the C:\CrashDumps folder anytime.
I tried the DISM.exe /Online /Cleanup-image /Restorehealth and DISM.exe /Online /Cleanup-Image /RestoreHealth /Source:C:\RepairSource\Windows /LimitAccess
Explorer still locks up and restarts when I try to make a directory. I have the cbs log file if that might be useful. I can create directories using mkdir from the command prompt. I am suspecting my shell32.dll or explorer.exe may be corrupt. Can I copy and replace these files from another source without excessively risking crashing my whole computer?
After trying that I appear out of options. Besides this issue my computer has been running great for 3 years and I hate the idea of rebuilding it. Any other thoughts?
Thank you,
Slate
Hi,
This issue regarding the folders that you're unable to access may arise due to a corrupted profile or operating system already. Since the issue occurred after several updates, we suggest that you use the inbox Deployment Image Servicing and Management (DISM) tool.
DISM hleps you to resolve some Windows corruption errors. Here's how:
It may take several minutes for the command operation to be completed.
DISM.exe /Online /Cleanup-image /Restorehealth
Important When you run this command, DISM uses Windows Update to provide the files that are required to fix corruptions. However, if your Windows Update client is already broken, use a running Windows installation as the repair source, or use a Windows side-by-side folder from a network share or from a removable media, such as the Windows DVD, as the source of the files. To do this, run the following command instead:
DISM.exe /Online /Cleanup-Image /RestoreHealth /Source:C:\RepairSource\Windows /LimitAccess
Note Replace the C:\RepairSource\Windows placeholder with the location of your repair source. For more information about using the DISM tool to repair Windows, reference Repair a Windows Image. 3. Type the following command and press Enter.
It may take several minutes for the command operation to be completed.
sfc /scannow 4. Close the command prompt, and then run Windows Update again.
DISM creates a log file (%windir%/Logs/CBS/CBS.log) that captures any issues that the tool found or fixed. %windir% is the folder in which Windows is installed. For example, the %windir% folder is C:\Windows.
If the issue persists, we recommend that you create a backup and perform a clean install. You may follow the steps on this link.
Note: Kindly save your important files to an external drive before performing the troubleshooting steps to avoid data loss.
Do let us know if you have any other concerns.