Resolved: Windows 10 Build 9926 Start Menu, Cortana Search, Action Center & Metro Apps Won’t Work

Home / Resolved: Windows 10 Build 9926 Start Menu, Cortana Search, Action Center & Metro Apps Won’t Work
Share This:

windows10microsoftlogo_medium

After getting Build 9926 installed on my tablet, things seemed to be going smooth. Then after a few reboots, I found that the Start Menu, Action Center, and Cortana Search bar wouldn’t open. I also couldn’t open any Metro Apps.

Luckily I was able to find a fix using Powershell.

Right click on the task bar and select Task Manager. Then select More Details. In the File Menu, select Run New Task and type Powershell. Be sure to check the box to run it with administrative privileges.

Once in Powershell, copy this command first and hit enter:

Get-appxpackage -all *shellexperience* -packagetype bundle |% {add-appxpackage -register -disabledevelopmentmode ($_.installlocation + “appxmetadataappxbundlemanifest.xml”)}

You’ll see a Deployment Operation Progress popup. Wait for this to complete and it should fix the Start Menu and Action Center.

To get the Cortana Search and your Metro Apps to work, you’ll have to run this one from Powershell:

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

This second command basically downloads and reinstalls all of your Metro Apps, including the built-in Windows ones like Cortana Search.

Also make sure you have all Windows Updates installed.

Alternative Method:
I’ve read that performing this also works:
Set the following GPO (Group Policy), Computer Configuration -> Administrative Templates -> Windows Components -> App Package Deployment -> Allow deployment operations in special profiles to Enabled. Reboot.

11 Comments

  1. Robert Russell on Facebook January 30, 2015 at 8:15 pm - Reply

    Jason Fields maybe try running the 2nd command on your Surface Pro 1 and see if it fixes your Settings problem.

  2. Jason Fields on Facebook January 30, 2015 at 8:18 pm - Reply

    I don’t have build 9926 on my SP1 – I have 9879, and the new Settings Metro won’t open – I am upgrading another model of laptop to 9926, then I will work on SP1 – will install fresh if I have too…

  3. Robert Russell on Facebook January 30, 2015 at 8:20 pm - Reply

    Do other Metro apps work on the SP1? Or is it just the Settings app?

    Only problem I have left is my audio driver.

  4. Jason Fields on Facebook January 30, 2015 at 8:20 pm - Reply

    All Metro apps work just fine just settings metro app haha – it is strange

  5. Kaito March 1, 2015 at 3:59 pm - Reply

    all it returns are errors.
    here is what the report says:

    Time ID Message
    —- — ——-
    3/1/2015 14:51:47 301 The calling process is C:\WINDOWS\system32\WindowsPowerShell\v1.0\PowerShell.exe
    3/1/2015 14:51:47 603 Started deployment Register operation on a package with main parameter: file:///
    C:/Program%20Files/WindowsApps/Microsoft.Windows.ShellExperienceHost_2015.120.95
    0.1657_neutral_~_8wekyb3d8bbwe/appxmetadata/appxbundlemanifest.xml and Options:
    0. See http://go.microsoft.com/fwlink/?LinkId=235160 for help diagnosing app
    deployment issues.
    3/1/2015 14:51:47 10002 Creating Resiliency File C:\ProgramData\Microsoft\Windows\AppRepository\c026e407
    -4863-4a52-b789-6c3bcdb4cef8_S-1-5-21-4252413829-4141475687-3045121313-1001_44.r
    slc for Register Operation on Package
    Microsoft.Windows.ShellExperienceHost_2015.120.950.1657_neutral_~_8wekyb3d8bbwe.
    3/1/2015 14:51:47 607 Deployment Register operation on package
    Microsoft.Windows.ShellExperienceHost_2015.120.950.1657_neutral_~_8wekyb3d8bbwe
    has been de-queued and is running for user CHASE-PC\Michael.
    3/1/2015 14:51:47 613 Adding uri to the list of Uris: C:\Program Files\WindowsApps\Microsoft.Windows.S
    hellExperienceHost_2015.120.950.1657_neutral_~_8wekyb3d8bbwe\appxmetadata\appxbu
    ndlemanifest.xml.
    3/1/2015 14:51:47 614 Bundle Uri C:\Program Files\WindowsApps\Microsoft.Windows.ShellExperienceHost_20
    15.120.950.1657_neutral_~_8wekyb3d8bbwe\appxmetadata\appxbundlemanifest.xml
    contains packages: “shellexperiencehost.language-ar.appx”: Microsoft.Windows.She
    llExperienceHost_1.0.0.2_neutral_ShellExperienceHost.la12faaeb0_8wekyb3d8bbwe
    “shellexperiencehost.language-bg.appx”: Microsoft.Windows.ShellExperienceHost_1.
    0.0.2_neutral_ShellExperienceHost.la37fae74a_8wekyb3d8bbwe
    “shellexperiencehost.language-ca.appx”: Microsoft.Windows.ShellExperienceHost_1.
    0.0.2_neutral_ShellExperienceHost.lad91c27a9_8wekyb3d8bbwe
    “shellexperiencehost.language-cs.appx”: Microsoft.Windows.ShellExperienceHost_1.
    0.0.2_neutral_ShellExperienceHost.laa1e8577a_8wekyb3d8bbwe
    “shellexperiencehost.language-da.appx”: Microsoft.Windows.ShellExperienceHost_1.
    0.0.2_neutral_ShellExperienceHost.la44cb1f10_8wekyb3d8bbwe
    “shellexperiencehost.language-de.appx”: Microsoft.Windows.ShellExperienceHost_1.
    0.0.2_neutral_ShellExperienceHost.la20a7da14_8wekyb3d8bbwe
    “shellexperiencehost.language-el.appx”: Microsoft.Windows.ShellExperienceHost_1.
    0.0.2_neutral_ShellExperienceHost.la49d90638_8wekyb3d8bbwe
    “shellexperiencehost.language-es.appx”: Microsoft.Windows.ShellExperienceHost_1.
    0.0.2_neutral_ShellExperienceHost.la848308a6_8wekyb3d8bbwe
    “shellexperiencehost.language-et.appx”: Microsoft.Windows.ShellExperienceHost_1.
    0.0.2_neutral_ShellExperienceHost.lacbc29e61_8wekyb3d8bbwe
    “shellexperiencehost.language-fi.appx”: Microsoft.Windows.ShellExperienceHost_1.
    0.0.2_neutral_ShellExperienceHost.la261b5d93_8wekyb3d8bbwe
    “shellexperiencehost.language-fr.appx”: Microsoft.Windows.ShellExperienceHost_1.
    0.0.2_neutral_ShellExperienceHost.la8f2d9609_8wekyb3d8bbwe
    “shellexperiencehost.language-he.appx”: Microsoft.Windows.ShellExperienceHost_1.
    0.0.2_neutral_ShellExperienceHost.la6a7165ac_8wekyb3d8bbwe
    “shellexperiencehost.language-hi.appx”: Microsoft.Windows.ShellExperienceHost_1.
    0.0.2_neutral_ShellExperienceHost.lac6c42aa0_8wekyb3d8bbwe
    “shellexperiencehost.language-hr.appx”: Microsoft.Windows.ShellExperienceHost_1.
    0.0.2_neutral_ShellExperienceHost.la6ff2e13a_8wekyb3d8bbwe
    “shellexperiencehost.language-hu.appx”: Microsoft.Windows.ShellExperienceHost_1.
    0.0.2_neutral_ShellExperienceHost.la20b377fd_8wekyb3d8bbwe
    “shellexperiencehost.language-it.appx”: Microsoft.Windows.ShellExperienceHost_1.
    0.0.2_neutral_ShellExperienceHost.la811421d9_8wekyb3d8bbwe
    “shellexperiencehost.language-ja.appx”: Microsoft.Windows.ShellExperienceHost_1.
    0.0.2_neutral_ShellExperienceHost.laa4146823_8wekyb3d8bbwe
    “shellexperiencehost.language-ko.appx”: Microsoft.Windows.ShellExperienceHost_1.
    0.0.2_neutral_ShellExperienceHost.la822b22c8_8wekyb3d8bbwe
    “shellexperiencehost.language-lt.appx”: Microsoft.Windows.ShellExperienceHost_1.
    0.0.2_neutral_ShellExperienceHost.lab6cad1eb_8wekyb3d8bbwe
    “shellexperiencehost.language-lv.appx”: Microsoft.Windows.ShellExperienceHost_1.
    0.0.2_neutral_ShellExperienceHost.la84fcb369_8wekyb3d8bbwe
    “shellexperiencehost.language-nb.appx”: Microsoft.Windows.ShellExperienceHost_1.
    0.0.2_neutral_ShellExperienceHost.la005bacb7_8wekyb3d8bbwe
    “shellexperiencehost.language-nl.appx”: Microsoft.Windows.ShellExperienceHost_1.
    0.0.2_neutral_ShellExperienceHost.la9ed88139_8wekyb3d8bbwe
    “shellexperiencehost.language-pl.appx”: Microsoft.Windows.ShellExperienceHost_1.
    0.0.2_neutral_ShellExperienceHost.la2e1ea195_8wekyb3d8bbwe
    “shellexperiencehost.language-pt.appx”: Microsoft.Windows.ShellExperienceHost_1.
    0.0.2_neutral_ShellExperienceHost.laac0539cc_8wekyb3d8bbwe
    “shellexperiencehost.language-ro.appx”: Microsoft.Windows.ShellExperienceHost_1.
    0.0.2_neutral_ShellExperienceHost.laaf3a3add_8wekyb3d8bbwe
    “shellexperiencehost.language-ru.appx”: Microsoft.Windows.ShellExperienceHost_1.
    0.0.2_neutral_ShellExperienceHost.la1f17c006_8wekyb3d8bbwe
    “shellexperiencehost.language-sk.appx”: Microsoft.Windows.ShellExperienceHost_1.
    0.0.2_neutral_ShellExperienceHost.la73ea98bc_8wekyb3d8bbwe
    “shellexperiencehost.language-sl.appx”: Microsoft.Windows.ShellExperienceHost_1.
    0.0.2_neutral_ShellExperienceHost.la3cab0e7b_8wekyb3d8bbwe
    “shellexperiencehost.language-sr-latn.appx”: Microsoft.Windows.ShellExperienceHo
    st_1.0.0.2_neutral_ShellExperienceHost.lab940571c_8wekyb3d8bbwe
    “shellexperiencehost.language-sv.appx”: Microsoft.Windows.ShellExperienceHost_1.
    0.0.2_neutral_ShellExperienceHost.la8c86f4a0_8wekyb3d8bbwe
    “shellexperiencehost.language-th.appx”: Microsoft.Windows.ShellExperienceHost_1.
    0.0.2_neutral_ShellExperienceHost.lac510f3c6_8wekyb3d8bbwe
    “shellexperiencehost.language-tr.appx”: Microsoft.Windows.ShellExperienceHost_1.
    0.0.2_neutral_ShellExperienceHost.la753d091d_8wekyb3d8bbwe
    “shellexperiencehost.language-uk.appx”: Microsoft.Windows.ShellExperienceHost_1.
    0.0.2_neutral_ShellExperienceHost.la5681c760_8wekyb3d8bbwe
    “shellexperiencehost.language-vi.appx”: Microsoft.Windows.ShellExperienceHost_1.
    0.0.2_neutral_ShellExperienceHost.la76020a0c_8wekyb3d8bbwe
    “shellexperiencehost.language-zh-hans.appx”: Microsoft.Windows.ShellExperienceHo
    st_1.0.0.2_neutral_ShellExperienceHost.lab5bb78dc_8wekyb3d8bbwe
    “shellexperiencehost.language-zh-hant.appx”: Microsoft.Windows.ShellExperienceHo
    st_1.0.0.2_neutral_ShellExperienceHost.lafafaee1b_8wekyb3d8bbwe
    “shellexperiencehost.appx”:
    Microsoft.Windows.ShellExperienceHost_1.0.0.2_x64__8wekyb3d8bbwe.
    3/1/2015 14:51:47 613 Adding uri to the list of Uris: C:\Program Files\WindowsApps\Microsoft.Windows.S
    hellExperienceHost_1.0.0.2_x64__8wekyb3d8bbwe\AppxManifest.xml.
    3/1/2015 14:51:47 726 Windows cannot find the resource package manifest in the bundle file:
    C:\Program Files\WindowsApps\Microsoft.Windows.ShellExperienceHost_1.0.0.2_neutr
    al_ShellExperienceHost.laa4146823_8wekyb3d8bbwe\AppxManifest.xml.
    3/1/2015 14:51:47 561 Not staging roaming data for package
    Microsoft.Windows.ShellExperienceHost_8wekyb3d8bbwe. The application state is
    already present.
    3/1/2015 14:51:47 10000 About to service package
    Microsoft.Windows.ShellExperienceHost_1.0.0.2_x64__8wekyb3d8bbwe. Setting the
    package state to disabled returned with 0x0.
    3/1/2015 14:51:47 8100 Starting validation and setting the Trust Label on package
    Microsoft.Windows.ShellExperienceHost_1.0.0.2_x64__8wekyb3d8bbwe with flags 0x9.
    3/1/2015 14:51:47 8106 Package Microsoft.Windows.ShellExperienceHost_1.0.0.2_x64__8wekyb3d8bbwe has
    Trust Label already. Flags: 0x9
    3/1/2015 14:51:47 8101 Finished validation and setting the Trust Label on package
    Microsoft.Windows.ShellExperienceHost_1.0.0.2_x64__8wekyb3d8bbwe with flags 0x9.
    3/1/2015 14:51:47 6231 error 0x80070002: Windows cannot register the package because of an internal
    error or low memory.
    3/1/2015 14:51:47 306 error 0x80070002: While processing the request, the system failed to register
    the windows.activatableClass.collector extension due to the following error:
    The system cannot find the file specified.
    .
    3/1/2015 14:51:47 316 error 0x80070002: Cannot register the request because the following error was
    encountered during the registration of the windows.activatableClass.collector
    extension: The system cannot find the file specified.
    .
    3/1/2015 14:51:47 300 error 0x80073CF6: Cannot register the
    Microsoft.Windows.ShellExperienceHost_8wekyb3d8bbwe package due to the
    following error: Package could not be registered.
    .
    3/1/2015 14:51:47 605 The last successful state reached was PackagesInUseClosed. Failure occurred
    before reaching the next state RegistrationChanged.
    3/1/2015 14:51:47 8100 Starting validation and setting the Trust Label on package
    Microsoft.Windows.ShellExperienceHost_1.0.0.2_x64__8wekyb3d8bbwe with flags 0x9.
    3/1/2015 14:51:47 8106 Package Microsoft.Windows.ShellExperienceHost_1.0.0.2_x64__8wekyb3d8bbwe has
    Trust Label already. Flags: 0x9
    3/1/2015 14:51:47 8101 Finished validation and setting the Trust Label on package
    Microsoft.Windows.ShellExperienceHost_1.0.0.2_x64__8wekyb3d8bbwe with flags 0x9.
    3/1/2015 14:51:47 6231 error 0x80070002: Windows cannot register the package because of an internal
    error or low memory.
    3/1/2015 14:51:47 328 error 0x80070002: While processing the request, the system failed to register
    the windows.activatableClass.collector extension due to the following error:
    The system cannot find the file specified.
    .
    3/1/2015 14:51:47 332 error 0x80070002: Cannot register the request because the following error was
    encountered during the registration of the windows.activatableClass.collector
    extension: The system cannot find the file specified.
    .
    3/1/2015 14:51:47 10001 Finished servicing package
    Microsoft.Windows.ShellExperienceHost_1.0.0.2_x64__8wekyb3d8bbwe. Setting the
    package state to enabled returned with 0x0.
    3/1/2015 14:51:47 401 Deployment Register operation with target volume C: on Package
    Microsoft.Windows.ShellExperienceHost_2015.120.950.1657_neutral_~_8wekyb3d8bbwe
    from: (C:\Program Files\WindowsApps\Microsoft.Windows.ShellExperienceHost_2015.
    120.950.1657_neutral_~_8wekyb3d8bbwe\appxmetadata\appxbundlemanifest.xml)
    failed with error 0x80073CF6. See http://go.microsoft.com/fwlink/?LinkId=235160
    for help diagnosing app deployment issues.
    3/1/2015 14:51:47 404 AppX Deployment operation failed for package
    Microsoft.Windows.ShellExperienceHost_2015.120.950.1657_neutral_~_8wekyb3d8bbwe
    with error 0x80073CF6. The specific error text for this failure is: error
    0x80070002: Windows cannot register the package because of an internal error or
    low memory.

    • Dan July 31, 2015 at 11:25 pm - Reply

      I received the same errors when running the script. Did you ever find a solution?

  6. John Doe March 25, 2015 at 1:55 pm - Reply

    Mr. Russell, the world rejoiced the day you were born. 🙂 Thank you!

  7. Udonitron August 22, 2015 at 1:27 pm - Reply

    Same thing is happening to me, the powershell command does nothing.
    Just after making a post on G+ about how MS is killing the info on updates I came upstairs to find my PC with a black screen, unresponsive so I had to hard reset it and sure enough it finished Windows updates only to reboot while it was finishing up.
    Now my Note, One Drive, etc keep crashing and I have a dead Start and Notification menu.
    I said no more to this “ad based OS” and went to do a roll back and well…I cannot do that because in MS’s infinite wisdom they allowed their media creation tool to overwrite your much needed BT & WS folders thus eliminating the ability to revert…bravo MS!
    I loathe where MS is going now and want nothing to do with 10 anymore.

    Actually…the only thing that works with a left click on my task bar is task view and show hidden icons.
    Start, search, networks, volume, and notifications are unresponsive however I can right click on them.
    When I try to do a refresh and keep my files it tells me everything needs to be reinstalled so what is the point.
    I cannot create a new account either as those choices do nothing when I click on them, the OS is totally borked.

  8. William November 26, 2015 at 2:44 pm - Reply

    @Udonitron – Bravo! I couldn’t agree more. Windows 10 has been nothing but a pain in my *ss since I first had the misfortune of coming in contact with it’s likes! It is absolutely the worst attempt I’ve seen from MS and I’ve been around since 3 dot 1! No WMC is a deal breaker to begin with. No Start menu, no search bar, no edge, no store… I mean, c’mon! Nothing works! You can’t even open edge to connect to the internet! What a POS! If I could return it I would. I’m purchasing a copy of 7 and I’ll keep it until the day I die, end of story.

  9. Susan December 9, 2015 at 1:17 am - Reply

    I have been struggling with the no Cortana, no Edge, no start menu etc since a week or two after I finally got a new computer and all I have had is grief with it…no solution seem to work. I have tried the suggestions and with no difference…. Why has Microsoft not fixed this mess yet????!!!

Leave a Comment