Windows 10 1709 - wsappx process high cpu load & and black screen after login for some users

Piggy backing off a post on this thread.

I found that this issue is caused by Windows Store apps that were recently updated.

First, go into the settings and then apps.  Sort by date to see what was recently installed or updated.  Make note of the apps.  This must be done on the profile that is having the issue because the apps might have different dates on a different profile as I found.

Second, you need to uninstall the app(s) or update them.  You can try to do this on the profile that is having the issues but I didn't have luck with this.  If this is a domain machine, log in another domain account.  If it is a local machine, log into another account.

Third, once logged into another account..  you need to install or update the apps in question. 

To uninstall:  You can do this from the apps panel in settings (where you were before).  (You cannot uninstall all apps, and if that is the case you can try to update).

To update:  You need to open the Windows Store app and go into the "Downloads and updates" (click near the top right of the app).  Find the app in question and open it's store page.  Once open it should find an update (the app in question for me found one automatically).

This worked for me for this issue.  I had two apps recently update on a user's domain computer.  One I uninstalled and the other I updated.  I have no idea which caused the issue but it was the Weather app (uninstalled) and Sticky Notes app (updated).

Hope this helps.

Tobias,

There is actually a better way to solve this problem.

You can do it in Task Manager. This will be a long explanation, so here I go: If Windows Explorer is a process and what shows and manages ALL OF THE FILES ON YOUR HARD DRIVE it should solve many problems as it was running on boot. So if it edits Windows Explorer data it could temporarily corrupt that data, Making it harder to get to the desktop program. To fix this you do Ctrl+Alt+Deland select Task Manager. Scroll down and hit **Windows Explorer / File Explorer (Depending on your OS)**and ten hit Restart.

I've encountered a strange situation on 3 new Dell computers now that may be a part of this problem: each of the 3 computers, at some point between coming out of the box and being put on a client's desk have had their drives encrypted with Bitlocker. I personally handled these machines from unboxing to deployment, and at no point in time did I enable Bitlocker for the boot drive. And yet, each of the three machines have had their drives encrypted. I'm absolutely certain this has happened, as the third machine has been in my lab for testing all week.  One of the first things I did was check for encryption when it first came in and the drive was NOT encrypted on Monday. This morning, when I went to check on it, the drive was encrypted. According to the Bitlocker-API Operational log, the first entry appeared at 5pm yesterday.

I don't know what is going on, but this is extremely unusual.

Just tried this on one of my problem machines and unfortunately did not work, but I cannot vouch that my first user profile wasn't problematic, so using it as the "seed" for a default folder might not have worked anyways. Unfortunately, I've wasted too much time on this particular machine and need to get it back to production, so I'm wiping and reinstalling from scratch.

Hi Chris,

Exactly the same here; 3 new Dell devices all plagued with the same issue.

The initial admin account made during the initial setup is fine, all subsequent accounts are faulty.