Windows 10: how to fix There’s a problem with Windows Shell Experience Host. Refreshing your PC might...

Ive already tried sfc /scannow and other methods and i even uninstalled an update to fix it but it wouldn't work, the only things that does not work is the action center and the calander wich you find on the cornor of your pc also the pinning tools right clicking the apps task bar how ever i dont want to reset the whole entire pc. ill provide an image of the error. and this error made it that all my saved internet passwords etc gone.

:)

 

Windows Shell Experience Host

Hi,

In answer to your query, Windows Shell Experience Host is a part of Microsoft Windows Operating System that you may have seen in your Task Manager. Sometimes, Windows Shell Experience Host consumes high memory or resources.

If you discover that Windows Shell Experience Host is consuming high memory or resources, we recommend installing the latest update of Windows 10. To do this, you can refer to the support article below:

• Update Windows 10.

We'll be here if you need more help.

 

Problem with "Windows Shell Experience Host"

Hi,

My name is Mohammed Shuaib, an Independent Advisor and I'm here to assist you with the issue of windows shell experience host. Please follow the below to fix the issue.

Fix #1

Step 1:

Go to the search box next to the Windows icon and type CMD

Step 2:

Then right-click on Command Prompt and select Run As Administrator

Step 3:

Type sfc /scannow & press enter

Step 4:

Once the above completes then type DISM /Online /Cleanup-Image /ScanHealth & press enter

Step 5:

After the completes type DISM /Online /Cleanup-Image /RestoreHealth & press enter

Step 6:

Restart the PC

Let me know the status after performing the above.

Regards

Shuaib

Independent Advisor

 

windows shell experience host terminated

I have perhaps a clue that may help you (or Microsoft). I first started seeing windows shell experience host closed from time to time when my PC started from sleep (event id 1002, closed because it stopped interacting
with Windows). But as I traced the events further, this was ALWAYS preceded by windows shell experience host closed upon PC going to sleep (event id 2484. terminated because it took too long to suspend).

Further examination and experiments point to this as a solution:

From Power Shell Admin:

Get-appxpackage -all *shellexperience* -packagetype bundle |% {add-appxpackage -register -disabledevelopmentmode ($_.installlocation + “\appxmetadata\appxbundlemanif

The problem returned after a improper shutdown (electrical outage), and the above command resolved it again.

My problem does not appear to be related to the OS version/patch, corruption, drivers, etc. Microsoft can weigh in, but I suggest trying this command in power shell before any time consuming or other risky updates. One last note, I rebooted after issuing
the power shell command, which may or may not be necessary.