Windows 10 ShellExperienceHost 崩溃

Windows 10 ShellExperienceHost 崩溃

我最近将我的 Windows 10 分区从 HDD 克隆到 SSD。

我无法打开“开始”菜单、通知或任何使用 ShellExperienceHost 的东西。这包括计算器应用、Edge 浏览器和右键单击任务栏中的应用时出现的 metro 风格右键菜单。

每次我尝试打开其中一个时,事件日志中都会出现错误:

Faulting application name: ShellExperienceHost.exe, version: 10.0.10240.16515, time stamp: 0x55fa599a
Faulting module name: Windows.UI.Xaml.dll, version: 10.0.10240.16548, time stamp: 0x56133a14
Exception code: 0xc0000409
Fault offset: 0x0000000000533ad2
Faulting process id: 0x39ac
Faulting application start time: 0x01d18ad380a6bb12
Faulting application path: C:\Windows\SystemApps\ShellExperienceHost_cw5n1h2txyewy\ShellExperienceHost.exe
Faulting module path: C:\Windows\System32\Windows.UI.Xaml.dll
Report Id: 61c0dd6c-b61f-42e5-9130-ecfa1fa87cac
Faulting package full name: 
Faulting package-relative application ID: 

如果我使用 WinDbg 打开 ShellExperienceHost.exe,我会得到以下输出:

CommandLine: C:\Windows\SystemApps\ShellExperienceHost_cw5n1h2txyewy\ShellExperienceHost.exe

************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*c:\symbols*https://msdl.microsoft.com/download/symbols
Symbol search path is: srv*c:\symbols*https://msdl.microsoft.com/download/symbols
Executable search path is: 
ModLoad: 00007ff7`70830000 00007ff7`70a03000   ShellExperienceHost.exe
ModLoad: 00007ff9`b66f0000 00007ff9`b68b2000   ntdll.dll
ModLoad: 00007ff9`b4800000 00007ff9`b48ad000   C:\Windows\system32\KERNEL32.DLL
ModLoad: 00007ff9`b3bc0000 00007ff9`b3d9d000   C:\Windows\system32\KERNELBASE.dll
ModLoad: 00007ff9`b44b0000 00007ff9`b472c000   C:\Windows\system32\combase.dll
ModLoad: 00007ff9`b48b0000 00007ff9`b494d000   C:\Windows\system32\msvcrt.dll
ModLoad: 00007ff9`b4370000 00007ff9`b4496000   C:\Windows\system32\RPCRT4.dll
ModLoad: 00007ff9`b4220000 00007ff9`b4361000   C:\Windows\system32\ole32.dll
ModLoad: 00007ff9`b3f90000 00007ff9`b3feb000   C:\Windows\system32\sechost.dll
ModLoad: 00007ff9`93300000 00007ff9`9336a000   C:\Windows\SYSTEM32\wincorlib.DLL
ModLoad: 00007ff9`b6330000 00007ff9`b63ee000   C:\Windows\system32\OLEAUT32.dll
ModLoad: 00007ff9`b61a0000 00007ff9`b6326000   C:\Windows\system32\GDI32.dll
ModLoad: 00007ff9`b3ff0000 00007ff9`b413e000   C:\Windows\system32\USER32.dll
(4910.46c8): Break instruction exception - code 80000003 (first chance)
ntdll!LdrpDoDebuggerBreak+0x30:
00007ff9`b67ae510 cc              int     3
0:000> gn
ModLoad: 00007ff9`b4730000 00007ff9`b4766000   C:\Windows\system32\IMM32.DLL
ModLoad: 00007ff9`b4b10000 00007ff9`b4c6c000   C:\Windows\system32\MSCTF.dll
ModLoad: 00007ff9`b2ff0000 00007ff9`b3021000   C:\Windows\system32\nvinitx.dll
ModLoad: 00007ff9`b63f0000 00007ff9`b6496000   C:\Windows\system32\ADVAPI32.dll
ModLoad: 00007ff9`b2fe0000 00007ff9`b2fea000   C:\Windows\SYSTEM32\VERSION.dll
ModLoad: 00007ff9`b3170000 00007ff9`b317f000   C:\Windows\system32\kernel.appcore.dll
ModLoad: 00007ff9`b2ed0000 00007ff9`b2f3b000   C:\Windows\SYSTEM32\bcryptPrimitives.dll
ModLoad: 00007ff9`b6570000 00007ff9`b6615000   C:\Windows\system32\clbcatq.dll
ModLoad: 00007ff9`75130000 00007ff9`76126000   C:\Windows\System32\Windows.UI.Xaml.dll
ModLoad: 00007ff9`aeaa0000 00007ff9`aebd1000   C:\Windows\SYSTEM32\wintypes.dll
ModLoad: 00007ff9`b0b30000 00007ff9`b0bf8000   C:\Windows\System32\CoreMessaging.dll
ModLoad: 00007ff9`92ba0000 00007ff9`92c06000   C:\Windows\System32\Bcp47Langs.dll
ModLoad: 00007ff9`a8c10000 00007ff9`a8f86000   C:\Windows\System32\iertutil.dll
ModLoad: 00007ff9`b32a0000 00007ff9`b3353000   C:\Windows\system32\shcore.dll
ModLoad: 00007ff9`b0ad0000 00007ff9`b0b2c000   C:\Windows\System32\NInput.dll
windows\dxaml\xcp\dxaml\lib\frameworkapplication_partial.cpp(136)\Windows.UI.Xaml.dll!00007FF97563E864: (caller: 00007FF770885394) FailFast(1) tid(46c8) 8000FFFF Catastrophic failure
(4910.46c8): Security check failure or stack buffer overrun - code c0000409 (!!! second chance !!!)
Windows_UI_Xaml!wil::details::ReportFailure+0x1dee4a:
00007ff9`75663ad2 cd29            int     29h

我已经尝试过:

  • Dism /在线/清理图像/ScanHealth

  • Dism /在线/清理图像/检查健康

  • Get-AppXPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}

  • 删除 %LOCALAPPDATA%\TileDataLayer\Database 并重新启动

  • 创建新用户

除了刷新 Windows 10 并丢失所有已安装的程序(我安装了一个开发环境,需要很长时间才能替换)之外,我还可以尝试其他方法吗?

我正在用 Classic Shell 替换 Windows 开始菜单,但看不到通知区域真是太烦人了。

答案1

我为此苦苦挣扎了好几天,查阅了数百页的解决方案。什么都不管用,直到我遇到了这一页,第 22 页用户保罗·施图姆建议使用Tweaking.com - Windows 修复免费版/专业版

我显然对此非常怀疑,但很多人说它对他们有用,而且在花了这么多时间之后,我愿意尝试任何方法,这要感谢微软的卑鄙支持。

您需要安装它,启动应用程序,在系统提示时以安全启动模式重新启动,然后运行默认选定的修复。无需预扫描、SFC 扫描或修复部分以外的任何操作(强烈推荐的备份和系统还原点除外)。我花了大约 20 分钟,但修复后重新启动后一切都恢复正常。我不知道具体是哪个修复程序起作用了,但这是唯一对我有用的方法。

再次强调,我不指望你会相信我,但微软页面上有不少人对此表示认可。请确保你对此感到满意,并在被要求时进行备份和系统还原。

答案2

深入研究问题后,每次我点击开始菜单时,事件日志中都会出现此错误

错误应用程序名称:ShellExperienceHost.exe,版本:10.0.10586.306,时间戳:0x571afaa5
错误模块名称:Windows.UI.Xaml.dll,版本:10.0.10586.306,时间戳:0x571af9f6

每次我单击“开始”菜单后都会出现此事件。我从 SysInternals 运行进程监视器,单击“开始”菜单,然后看到显示的是ACCESS DENIED用户帐户包。此文件位于:settings.datShellExperienceHost

%localappdata%\ Packages \ Microsoft.Windows.ShellExperienceHost_cw5n1h2txyewy \设置\

(localappdata 是的环境变量C:\Users\USERNAME\AppData\Local\

我删除了该文件,单击了“开始”按钮,但由于被删除,settings.dat它仍然无法打开。因此,我将(整个文件夹)重命名为 ShellExperienceHost UI 应用程序,并使用提升的 PowerShell 窗口中的以下 PowerShell 命令重新安装该应用程序:settings.datMicrosoft.Windows.ShellExperienceHost_cw5n1h2txyewy.old

Get-AppXPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "C:\Windows\SystemApps\ShellExperienceHost_cw5n1h2txyewy\AppXManifest.xml"}

然后重新安装我的用户配置文件的本地包,并将其放回settings.dat原位。现在不再有错误,开始菜单现在正常工作了。

答案3

经过几个月的尝试,我终于能够通过下载适用于 Windows 10 的 .img(类似 .iso)文件来解决这个问题,该文件具有与我安装的确切版本号(Build 10240)相同的版本号。

一旦我有了正确的 .img 文件,我就可以使用它来就地升级到同一版本。尝试将相同的就地升级到最新版本时,在 40% 处不断失败,错误为 0xC1900101-0x30018。

我的开始菜单、通知中心和 Edge 都恢复正常了。

感谢@magicandre1981 的所有帮助。

答案4

从转储中我可以看到您收到一个Access denied错误:

Stowed Exception Array @ 0x00000047c99904e0

Stowed Exception #1 @ 0x00000047c9999868
    0x80070005 (FACILITY_WIN32 - Win32 Undecorated Error Codes): E_ACCESSDENIED - General access denied error

    Stack    : 0x47c9998058
        7ffd96e11dd4 Windows_UI_Xaml!DirectUI::ActivationAPI::ActivateInstance+0x2cf304
        7ffd96c5a4c3 Windows_UI_Xaml!DirectUI::NavigationCache::LoadContent+0x6b
        7ffd96c5a045 Windows_UI_Xaml!DirectUI::NavigationCache::GetContent+0xa1
        7ffd96c5ab4f Windows_UI_Xaml!DirectUI::Frame::PerformNavigation+0xcf
        7ffd96c59e89 Windows_UI_Xaml!DirectUI::Frame::StartNavigation+0x29
        7ffd96c5aa24 Windows_UI_Xaml!DirectUI::Frame::NavigateImpl+0x15c
        7ffd96c5a889 Windows_UI_Xaml!DirectUI::FrameGenerated::Navigate+0x89
        7ffd96c58f4b Windows_UI_Xaml!DirectUI::Frame::NavigateImpl+0x4b
        7ffd96c58ec5 Windows_UI_Xaml!DirectUI::FrameGenerated::Navigate+0x75
        7ffd96c58ced Windows_UI_Xaml!DirectUI::Frame::NavigateImpl+0x41
        7ffd96c58c71 Windows_UI_Xaml!DirectUI::FrameGenerated::Navigate+0x71
        7ffd9677349d Windows_UI_ActionCenter!ActionCenter::App::StaticInitialize+0x55d
        7ffd96772dd3 Windows_UI_ActionCenter!ActionCenter::App::StaticOnLaunched+0x3f
        7ffd96772d7b Windows_UI_ActionCenter!?Invoke@?$__abi_FunctorCapture@V<lambda_237858d95a404202aa0a218454e40d6e>@@X$$$V@Details@Platform@@UEAAXXZ+0x4b
        7ffd967712e9 Windows_UI_ActionCenter!?__abi_Windows_UI_Core_DispatchedHandler___abi_IDelegate____abi_Invoke@?Q__abi_IDelegate@DispatchedHandler@Core@UI@Windows@@2345@UE$AAAJXZ+0x2d
        7ffdaaab3e6c Windows_UI!Windows::UI::Core::CDispatcher::ProcessInvokeItem+0x23c
        7ffdaaab5a54 Windows_UI!Windows::UI::Core::CDispatcher::ProcessMessage+0x1a4
        7ffdaaab57c2 Windows_UI!Windows::UI::Core::CDispatcher::WaitAndProcessMessages+0x1a2
        7ffdaaab5598 Windows_UI!Windows::UI::Core::CDispatcher::ProcessEvents+0xa8
        7ffd96d403bd Windows_UI_Xaml!CJupiterWindow::RunCoreWindowMessageLoop+0x65
        7ffd96d40343 Windows_UI_Xaml!DirectUI::DXamlCore::RunMessageLoop+0x47
        7ffdc64ba306 twinapi_appcore!Windows::ApplicationModel::Core::CoreApplicationView::Run+0x46
        7ffdc64d6490 twinapi_appcore!Microsoft::WRL::Details::MakeAndInitialize<Windows::ApplicationModel::Core::CoreApplicationViewAgileContainer,Windows::ApplicationModel::Core::CoreApplicationViewAgileContainer,enum Windows::ApplicationModel::Core::CoreApplicationViewAgileContainer::WindowType,Windows::ApplicationModel::Core::IFrameworkViewSource * __ptr64 & __ptr64,HSTRING__ * __ptr64>+0x1a4
        7ffdc7cb80c0 SHCore!CSimpleHashTable<unsigned long,Microsoft::WRL::ComPtr<CStreamWriterTimeoutManager::CTimerIdAndWriters>,CDefaultHashPolicy<unsigned long>,CDefaultKeyCompare<unsigned long>,CDefaultResizePolicy,CDefaultRehashPolicy>::RemoveAll+0x128
        7ffdc9582d92 kernel32!BaseThreadInitThunk+0x22
        7ffdcb119f64 ntdll!RtlUserThreadStart+0x34

要查看无法访问的文件/注册表项,请运行进程监控器,过滤ShellExperienceHost.exe并在结果列中查找哪个操作因Access denied错误而失败。

也可以尝试运行本次更新它会修复也可能导致错误的 ACL。

相关内容