Thanks Darleen.
Would it make sense to try a Fresh Start first? It seems simpler and a far less complex. What would this omit that a clean install will get?
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Hi:
I have periodic explorer crashes on my Surface Pro 2017, Win Pro x64 (it is fully updated). The crash seems to occur periodically after a Hello Windows log-in (this occurs after the computer was sleeping rather than on a fresh boot). It seems to involve Windows.UI.XamlHost.dll based on the below.
When I look in the Event viewer I see errors like this:
Event ID 1000
Faulting application name: explorer.exe, version: 10.0.16299.125, time stamp: 0xfeba44fb
Faulting module name: Windows.UI.XamlHost.dll, version: 10.0.16299.15, time stamp: 0x00f27b8f
Exception code: 0xc0000409
Fault offset: 0x0000000000001db1
Faulting process id: 0x1880
Faulting application start time: 0x01d38282e4131af4
Faulting application path: C:\WINDOWS\explorer.exe
Faulting module path: C:\Windows\System32\Windows.UI.XamlHost.dll
Report Id: 6e835576-b35e-4d24-b6ce-331b05fa2c55
Faulting package full name:
Faulting package-relative application ID:
If I click on Start > type "view all" then click on "View all problem reports Control panel" the "Windows Explorer" "Stopped working" errors and then double click on one I would get something like this:
Source
Windows Explorer
Summary
Stopped working
Date
11/26/2017 10:53 AM
Status
Report sent
Description
Faulting Application Path: C:\Windows\explorer.exe
Problem signature
Problem Event Name: BEX64
Application Name: Explorer.EXE
Application Version: 10.0.16299.15
Application Timestamp: 66e02565
Fault Module Name: Windows.UI.XamlHost.dll
Fault Module Version: 10.0.16299.15
Fault Module Timestamp: 00f27b8f
Exception Offset: 0000000000001db1
Exception Code: c0000409
Exception Data: 0000000000000007
OS Version: 10.0.16299.2.0.0.256.48
Locale ID: 1033
Additional Information 1: 2eb9
Additional Information 2: 2eb9591f0e04c7cfea277e3f34d3348f
Additional Information 3: 9333
Additional Information 4: 9333781589f3ec46cd357f0fda06eea0
Extra information about the problem
Bucket ID: 15f01e3e317a50b7b6bb92d1b9fc4f7c (116455065336)
I am at a loss to understand what the problem is here. I am glad to disable Hello Windows if this would end the problem. Thanks in advance for any help on this!
[Moved from: Windows / Windows 10 / Windows Hello, lock screen & sign-in]
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.
Thanks Darleen.
Would it make sense to try a Fresh Start first? It seems simpler and a far less complex. What would this omit that a clean install will get?
Hi Nammy,
We'll be investigating this concern further by extracting and reading the latest dump file that you posted. Upon reading this thread, we noticed that necessary troubleshooting were already performed on your device and the issue with crashing Explorer persists. As of this moment, the best option that we can consider is to perform a clean installation of Windows 10. This can repair all software related issues on a Windows system. You can use this article published by Greg Carmack as your reference. We highly advice backing up all of your files before performing the clean installation of Windows since this can wipe all of your data.
Keep us updated on the status of your concern.
Another explorer crash: https://1drv.ms/u/s!AoMjGh2ERllBd8brcpkhwJI\_En0
Only thing new is that it crashed while I was plugged in and after it went to sleep (it has always been while on battery and when I log back in via Windows Hello as the surface is coming out of sleep or hibernate). I am having problems reading the crash dump though I can see from event viewer that I had my usual Event 1000 error with Windows.UI.XamlHost.dll (listed at bottom). Auggy can you see if there is anything else different? I have done tons of windows and firmware updates over the weekend, but obviously they did nothing.
PS Just now I have disabled Windows Hello. Pretty sure this is not going to help given the last explorer crash but it is worth trying...
Faulting application name: Explorer.EXE, version: 10.0.16299.248, time stamp: 0x18ee648b
Faulting module name: Windows.UI.XamlHost.dll, version: 10.0.16299.15, time stamp: 0x00f27b8f
Exception code: 0xc0000409
Fault offset: 0x0000000000001db1
Faulting process id: 0x18f0
Faulting application start time: 0x01d3ba47b453ca8d
Faulting application path: C:\WINDOWS\Explorer.EXE
Faulting module path: C:\Windows\System32\Windows.UI.XamlHost.dll
Report Id: cda75450-45fe-44cd-856f-01f89091d517
Faulting package full name:
Faulting package-relative application ID:
To disable (remove) Hello Windows look for an option here:
Start > Settings > Accounts > Sign in Options > Windows Hello > Remove
Another crash: Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.
Each time I am getting this the Hello Windows startup is a bit slow, it says something like get closer or looking for options, and then when I get in explorer has crashed. Is there a way to disable Hello Windows?