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

I was able to resolve this for a user without deleting the user.

I had this issue on a Lenovo.  

wsappx was causing high CPU, fully occupying a single core.  Upon logon the user had a black screen post KB4093112 update and to make matters worse the start menu and some other buttons were no longer working if the black screen finally dissapeared.

I had two user accounts on the laptop.  A local account that was not affected and a domain account that got affected by this issue.

I did the following operations on the local account that was not affected.  If you only have one account. Use task manager and start cmd as administrator to make a new user account to do these operations.

With the non impacted account, launch powershell as administrator and run:

Get-AppxPackage -User <impactedusername> | Remove-AppxPackage

This will spawn some errors but keeps processing.   Once done open explorer and navigate to c:\users&lt;impactedusername>\appdata\local\

Rename the directory "Packages" to Packages.backup

Now reboot the computer and login as the impacted user.  Windows will recreate basic AppxPackages that we removed and create a fresh start menu.  wsappx will no longer be crashing and will be updating packages properly now.  If needed, you can reinstall build in apps 

https://www.cnet.com/how-to/how-to-reinstall-default-apps-in-windows-10/

I can confirm this works.

I actually went another route, but very similar

(Get-AppXProvisionPackage -Online).PackageName | Out-File -Path C:\Temp\AppLists.txt

Opened the Appslist.txt created and removed the Apps from the list that I wanted to keep, Store, Calculator, DesktopAppInstaller.

Then back in powershell

$apps = get-content C:\Temp\AppLists.txt

$apps | Foreach {Remove-AppXProvisionPackage -Online -PackageName "$_"}

This stops these apps from being provisioned for new users, as it was any new users to the computer having the problem.

Doesn't work for current users would have to use David's command or remove their profile and re-add it.

For those who do not have another user, here is one solution. 

(Got some specific symptoms that I couldn't find help for yet, so maybe this will address someone's situation and be of some help) I have a Lenovo Laptop, with originally one user account. black screen only happens after login. Task manager works but freezes often, and other programs that I try to load often refuse to launch, namely control panel. 

From that black screen once you login, CTR+ALT+DLT and launch task manager. For me, control panel (control.exe) refused to launch when I ran it, for some reason. If it works for you, definitely go that route. If not:

run cmd from task manager. (be sure you run the task as admin)

Add a new user and add to admin group:

net user /add <username> <password>

net localgroup administrators <username> /add

that should work for creation of a new user, so restart your PC and that new account should be unaffected. You can then transfer your files and programs to your new account, and scrap the old one which is quite the ass-pain.

Or you can follow the steps that have been generously outlined earlier in the thread, to repair those service problems.

It isn't the computer, it is the oem image that appears to be the latest iteration of 1709 that is the common thread.

It isn't the computer, it is the oem image that appears to be the latest iteration of 1709 that is the common thread.

Actually it's worse than that.  There are plenty of folks who have reported (including myself) a perfectly healthy computer suddenly exhibiting this behavior.  My own computer came new to me back in ~2015 so this has nothing to do with oem images.

First of all thanks for the tip!

It worked for me.

I first had to use the tip from NossonCotlar to create a new account because all accounts on the machine were affected.

Then went through the steps suggested by David Dejaeghere and see... everything works fine again.

One last remark:

I can confirm that the issue is not linked to Dell or Lenovo computers or some bad OEM installation. In my case, it affected an old Desktop computer I put together back in 2010 and upgraded over the years from Xp to Windows 10. By the way, our two other Lenovo laptops did not show the symptoms...

It might not be related, but the only thing I noticed on the affected computer was some instability poping up around December 2017 which remained up to recently. I thought I finally traced the issue (and solved it?) back to the NVIDIa graphics card driver, but in the mean time the PC had crashed numerous times (on both user profiles) and maybe something got messed up in Windows Apps?

Cheers.