Windows 10, fully up to date - Version 1511 (OS Build 10586.0)

Cannot open Start Menu, Cortana, Volume Controls, Notifications - anything on the task bar.

This issue was caused by:

1) explorer.exe being terminated one time, yesterday

I have tried every fix available through standard searches. Everything included here has been tried.

I can see any time I click anything on the task bar, a WerFault.exe runs, which is "Windows Error Reporting", but this is only through watching Taskmanager, as nothing actually comes up when I click anything.

I can't even right-click non-Windows applications on the task bar, such as right-clicking a Chrome window to close it or whatever else.

If attempting to open Start Menu, Event Viewer generates 5 events:

1) Faulting application name: ShellExperienceHost.exe, version: 10.0.10586.0, time stamp: 0x5632d93d

2)

Fault bucket 133232457255, type 5
Event Name: MoAppCrash
Response: Not available
Cab Id: 0

3)

Faulting application name: SearchUI.exe, version: 10.0.10586.0, time stamp: 0x5632d66d

4)

Activation of app Microsoft.Windows.ShellExperienceHost_cw5n1h2txyewy!App failed with error: The app didn't start. See the Microsoft-Windows-TWinUI/Operational log for additional information.

5)

Activation of app Microsoft.Windows.Cortana_cw5n1h2txyewy!CortanaUI failed with error: The app didn't start. See the Microsoft-Windows-TWinUI/Operational log for additional information

  • Which update of Windows 10 do you have? – hxri Apr 20 '16 at 13:59
  • I presume you have tried to restart the machine? – Ramhound Apr 20 '16 at 14:02
  • As-is this is too broad, IMO; we need more information. Have you looked in the Event Logs yet? How about as the Problem Reports in the Control Panel? They should give you information that WerFault collected, hopefully pointing to the cause of your error. – Ƭᴇcʜιᴇ007 Apr 20 '16 at 14:03
  • Version 1511 (OS Build 10586.0). It generally wouldn't be possible to try every presently available troubleshooting method without several reboots. – pay Apr 20 '16 at 14:03
  • 10586.0 IS NOT the current Windows 10 build. It is 10586.218 as of April 12th 2016. Which means your missing about 5-6 months of updates, basically every update, since Nov 2015. At the very least you should be at 10586.3 since that was the day 1 patch for that build. – Ramhound Apr 20 '16 at 14:03

The dump shows an Access Denied error:

Stowed Exception Array @ 0x00000095c833dae0

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

    Stack    : 0x283e6815780
        7ff9d4c11734 combase!RoOriginateError+0x54
        7ff9cfd93f20 wincorlib!Platform::Details::ReCreateException+0x90
        7ff9cfdbcfb7 wincorlib!__abi_WinRTraiseAccessDeniedException+0x17
        7ff7f577b306 ShellExperienceHost!__abi_WinRTraiseException+0xca
        7ff7f5746374 ShellExperienceHost!Windows::UI::Xaml::Application::Start+0x94
        7ff7f57462d0 ShellExperienceHost!main+0x40
        7ff7f574a82e ShellExperienceHost!_main+0xa6
        7ff7f574a041 ShellExperienceHost!__mainCRTStartup+0x1ad
        7ff9d3cf8102 kernel32!BaseThreadInitThunk+0x22
        7ff9d4fec264 ntdll!RtlUserThreadStart+0x34

0:000> !PDE.dse 00000095c833dae0
Stowed Exception Array @ 0x00000095c833dae0

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

    Stack    : 0x283e6815780
        7ff9d4c11734 combase!RoOriginateError+0x54
        7ff9cfd93f20 wincorlib!Platform::Details::ReCreateException+0x90
        7ff9cfdbcfb7 wincorlib!__abi_WinRTraiseAccessDeniedException+0x17
        7ff7f577b306 ShellExperienceHost!__abi_WinRTraiseException+0xca
        7ff7f5746374 ShellExperienceHost!Windows::UI::Xaml::Application::Start+0x94
        7ff7f57462d0 ShellExperienceHost!main+0x40
        7ff7f574a82e ShellExperienceHost!_main+0xa6
        7ff7f574a041 ShellExperienceHost!__mainCRTStartup+0x1ad
        7ff9d3cf8102 kernel32!BaseThreadInitThunk+0x22
        7ff9d4fec264 ntdll!RtlUserThreadStart+0x34

0:000> !PDE.dse 00000095c833dae0
Stowed Exception Array @ 0x00000095c833dae0

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

    Stack    : 0x283e6815780
        7ff9d4c11734 combase!RoOriginateError+0x54
        7ff9cfd93f20 wincorlib!Platform::Details::ReCreateException+0x90
        7ff9cfdbcfb7 wincorlib!__abi_WinRTraiseAccessDeniedException+0x17
        7ff7f577b306 ShellExperienceHost!__abi_WinRTraiseException+0xca
        7ff7f5746374 ShellExperienceHost!Windows::UI::Xaml::Application::Start+0x94
        7ff7f57462d0 ShellExperienceHost!main+0x40
        7ff7f574a82e ShellExperienceHost!_main+0xa6
        7ff7f574a041 ShellExperienceHost!__mainCRTStartup+0x1ad
        7ff9d3cf8102 kernel32!BaseThreadInitThunk+0x22
        7ff9d4fec264 ntdll!RtlUserThreadStart+0x34

Run Process Monitor in background, while trying to open the startmenu or any other operation which causes the crash, and look in the Result column which operation fails with Access Denied error.

Also try to run this update which repairs the ACL which also can cause the errors.

  • If I clear the list, and filter by "Access Denied", I get A LOT of WerFault.exe, SearchUI,exe, ShellExperienceHost.exe - That is produced by attempting to open the Start Menu - The operation on ShellExperienceHost before the WerFaults is CreateFile – pay Apr 20 '16 at 16:10
  • Sorry I meant there is a lot of WerFault, but only a few of the other entries – pay Apr 20 '16 at 16:13
  • CreateFile is a good start. Now look at the details of the CreateFle operation to see more details – magicandre1981 Apr 20 '16 at 16:16
  • The path on those operations is also pointing to C:\Windows\System32\twinapi.appcore.dll for ShellExperienceHost – pay Apr 20 '16 at 16:23
  • share the unfiltered PML file and I'll take a look myself. I think this is easier. – magicandre1981 Apr 20 '16 at 16:25

One of our Windows 10 PCs exhibited this behaviour after the anniversary update was installed. Clicking on the start menu wouldn't work. When I looked in the Event Log it said:

Faulting application name: ShellExperienceHost.exe, version: 10.0.14393.187, time stamp: 0x57cf9d73
Faulting module name: nvumdshimx.dll, version: 21.21.13.6909, time stamp: 0x579f36b5
Exception code: 0xc0000005
Fault offset: 0x0000000000051979
Faulting process id: 0x1594
Faulting application start time: 0x01d2290588da8cb1

The faulting module nvumdshimx.dll turned out to be part of an Nvidia driver installation. Once I removed the Nvidia drivers the start menu worked again.

  • 2
    Good info. AMD here, but the event entry posted at Microsoft Answers doesn't reveal anything about the cause. – Laurie Stearn Dec 19 '17 at 14:05

Your Answer

 

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Not the answer you're looking for? Browse other questions tagged or ask your own question.