Solved Windows 10 desktop Modern apps and taskbar no longer works

August 23, 2016 at 03:28:10
Specs: Windows 10.0.10586 Pro, Intel i7 4770k, 32GB 1600MHz RAM
After Nvidia GeForce Experience crashed during a GPU driver update, my modern apps (Store, Images, Groove, etc..) do not start and return error message "The app didn't start". My start button is unclickable and my search bar does not wor either.

In event viewer I see an event ID 5973 from the source "Apps", stating that the activation of -some modern app-.App failed. This event happens every time I try to launch a modern app, click the start button or use the search bar.

I have tried removing the TileDataLayer, replacing with a fresh one from another user, re-registering Store apps, clearing the Store cache, rebooting various times, and signing in with different users. The issue persists on other users as well.

Is there anything I haven't tried yet that could be worth a shot?

Don't worry if plan A fails, there are 25 more letters in the alphabet ;)


See More: Windows 10 desktop Modern apps and taskbar no longer works

Report •

#1
August 23, 2016 at 04:12:04
Obvious suggestion, but I don't see it mentioned. Have you opened an Administrative Command Prompt and ran:
dism /online /cleanup-image /restoreHealth
sfc /scannow

Also, have you tried creating a new user account, to check if the modern apps on that account work? Outside of that, I'd need to know the details of the events in question. An error number would help.

How To Ask Questions The Smart Way


Report •

#2
August 23, 2016 at 05:59:19
I just ran DISM, it returned
Error: 0x800f081f
The source files could not be found.

The Start button and search bar does not work in new user accounts.

The EventData from event 5973 is

  AppId: Microsoft.Windows.CloudExperienceHost_cw5n1h2txyewy!App 
  ErrorCode: -2144927141 

I also just noticed that in addition to the previously mentioned problems, I cannot right click any apps running in the taskbar. However icons in the tray are clickable.

EDIT:
SFC found corrupted files but was unable to repair. Uploaded a small small section of the log to pastebin http://pastebin.com/BhbYEjB7

Also, there was an Apps 5973 event with the following details:
AppId: Microsoft.Messaging_8wekyb3d8bbwe!ppleae38af2e007f4358a809ac99a64a67c1
ErrorCode: -2144927141

SkypeHost.exe also constantly crashes, eventID is 1000, exception code is 0xc0000409, EventData is

 EventData 

   SkypeHost.exe 
   10.1.2123.36 
   56eb679c 
   msvcr120_app.dll 
   12.0.30501.0 
   5361b019 
   c0000409 
   0004bd1c 
   f88 
   01d1fd42d50498da 
   C:\Program Files\WindowsApps\Microsoft.Messaging_2.15.20002.0_x86__8wekyb3d8bbwe\SkypeHost.exe 
   C:\Program Files\WindowsApps\Microsoft.Messaging_2.15.20002.0_x86__8wekyb3d8bbwe\msvcr120_app.dll 
   ac1433ef-4c45-4d70-b923-62840ca76c22 
   Microsoft.Messaging_2.15.20002.0_x86__8wekyb3d8bbwe 
   ppleae38af2e007f4358a809ac99a64a67c1 

Don't worry if plan A fails, there are 25 more letters in the alphabet ;)

message edited by RainBawZ


Report •

#3
August 23, 2016 at 08:51:17
✔ Best Answer
Looks like you've got some pretty bad corruption going on, or a nasty virus. I'm going to assume you're pretty sure the machine's not infected with anything, and run from there.

DISM /restoreHealth checks your WinSxS directory, and compares it with Microsoft's Windows file database by default. SFC checks your system against your WinSxS directory, and restores any corruption. So we'll need to get DISM up and running before we worry about SFC.

Since DISM depends on Windows Update, I could link to the article detailing how to reset Windows Update, and from there tell you to try DISM again, but I'm lazy and we probably have better things to do with our time.

The easier solution, especially if this system isn't on one of the preview rings, would be to make a Win10 disk, and boot from that disk. Go through the steps to bring up a Command Prompt from the repair system menu, and run:

dism /image:d:\ /cleanup-image /restoreHealth /scratchDir:d:\temp
(Where "d:" is the system drive, and d:\temp actually exists. The recovery disk probably won't see Windows on C:, but rather D: DIR <driveLetter>: helps here.) That'll compare your corrupted system to your recovery disk. From there, you should be able to run:
sfc /scannow /offbootdir=d:\ /offwindir=d:\windows
(Again, "d:" is the system drive, as seen by the recovery disk.)

If you think booting from recovery media is too extreme, you can try an online DISM scan against the recovery disk. The command for that is:

dism /online /cleanup-image /restoreHealth /source:wim:d:\sources\install.wim:1 /limitaccess
(Where "d:" is the recovery disk.)

How To Ask Questions The Smart Way


Report •

Related Solutions

#4
August 23, 2016 at 12:10:53
I don't have any recovery disk at hand, tried following the instructions in the link.

When I was supposed to register the dlls, some failed saying they were either not found, or could not be loaded

Don't worry if plan A fails, there are 25 more letters in the alphabet ;)


Report •

#5
August 23, 2016 at 12:29:17
The "Win10 disk" link will take you to a tool that'll download a Win10 disk for you. You need a USB drive you don't mind formatting, or you'll get an .iso file you can either mount directly and use DISM on, or burn to a DVD.

How To Ask Questions The Smart Way


Report •

#6
August 24, 2016 at 04:06:40
Noticed there was an update available (which Windows Update hasn't downloaded for some reason) on the Windows 10 page you linked, I installed it and it seemed to fix the issue.

Thanks for the help!

Don't worry if plan A fails, there are 25 more letters in the alphabet ;)

message edited by RainBawZ


Report •

Ask Question