Loss Of Start Menu with 17xx Creators Update

Discussion in 'Windows 10' started by DeathStalker77, Jan 28, 2018.

  1. DeathStalker77

    DeathStalker77 MDL Senior Member

    Nov 8, 2009
    281
    15
    10
    So it doesn't get overlooked in the other post, the subject of which *was* solved -

    I have no idea what keeps causing this. I have an Nvidia 1080 card. The Start Menu functionality breaks (literally *just* having the system running). It starts out with this error -
    Package Microsoft.Windows.ShellExperienceHost_10.0.16299.15_neutral_neutral_cw5n1h2txyewy+App was terminated because it took too long to suspend.

    Then generates this error -
    The program ShellExperienceHost.exe version 10.0.16299.15 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel.
    Process ID: 1608
    Start Time: 01d398483c05eaf9
    Termination Time: 4294967295
    Application Path: C:\Windows\SystemApps\ShellExperienceHost_cw5n1h2txyewy\ShellExperienceHost.exe
    Report Id: ca6153a1-ffce-42cd-a7df-f618455c477e
    Faulting package full name: Microsoft.Windows.ShellExperienceHost_10.0.16299.15_neutral_neutral_cw5n1h2txyewy
    Faulting package-relative application ID: App

    After this, the Start Menu (and related functions) cease to work. I have to enable the built-in Admin account, log into it, and copy over the ShellExperienceHost package.

    I have been dealing with this since the release of the Creator's Update - it never happened on 1607. :(

    Any help on this would be so incredibly appreciated, I cannot put it into mere words ......
     
  2. DeathStalker77

    DeathStalker77 MDL Senior Member

    Nov 8, 2009
    281
    15
    10
    No idea if this is related or not, but also found this in the Event Viewer (repeatedly) -

    The application System with process id 4 stopped the removal or ejection for the device PCI\VEN_8086&DEV_6F02&SUBSYS_00008086&REV_01\3&11583659&0&08.

    As well as these (all in a row) -

    The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
    {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D}
    to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

    The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID
    {C2F03A33-21F5-47FA-B4BB-156362A2F239} and APPID {316CDED5-E4AE-4B15-9113-7055D84DCC97}
    to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

    The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
    {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID
    {4839DDB7-58C2-48F5-8283-E1D1807D0D7D}
    to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

    The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID
    {C2F03A33-21F5-47FA-B4BB-156362A2F239} and APPID
    {316CDED5-E4AE-4B15-9113-7055D84DCC97}
    to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

    The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
    {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID
    {4839DDB7-58C2-48F5-8283-E1D1807D0D7D}
    to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

    The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID
    {C2F03A33-21F5-47FA-B4BB-156362A2F239} and APPID
    {316CDED5-E4AE-4B15-9113-7055D84DCC97}
    to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

    The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
    {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID
    {4839DDB7-58C2-48F5-8283-E1D1807D0D7D}
    to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

    The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID
    {C2F03A33-21F5-47FA-B4BB-156362A2F239} and APPID
    {316CDED5-E4AE-4B15-9113-7055D84DCC97}
    to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

    Mind you, this is a *clean* install - no other software installed. :(
     
  3. Joe C

    Joe C MDL Guru

    Jan 12, 2012
    2,166
    1,161
    90
    #3 Joe C, Jan 28, 2018
    Last edited: Jan 28, 2018
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  4. DeathStalker77

    DeathStalker77 MDL Senior Member

    Nov 8, 2009
    281
    15
    10
    Ok, I will try running DDU as soon as the initial install is done - you can't avoid it automatically installing the drivers from Windows Update - and will then immediately install the Nvidia driver package. Will post an update. (This will be my *5th* re-install in 3 days :(

    This, imho is just plain SLOPPY! M$ is hiring monkeys to program their crap, and forcing updates on us should be illegal. Not surprising though, considering the number of illegal things Gates did in the early years of the company. While I still like Windows better than Apple (I hate *anything* Apple), their quality control is non-existent. Countless failures of OS versions.