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

Anonymous
2018-01-05T10:47:44+00:00

I'll had an issue that wsappx takes all the cpu of one core (ill think its single threaded app).

Have searched the internet and dont found an solution.

just a few hints that a clean boot solved the issue for some but that didnt worked for me.

The issue also just poped up on some users of the machine, some users where fine.

But when the "defect" user has logged in into his account the wsappx goes crazy and dont come down, also when another user takes the local session.

Here are some thread about the issue: https://www.google.at/url?sa=t&rct=j&q=&esrc=s&source=web&cd=4&cad=rja&uact=8&ved=0ahUKEwiuvpPZ0cDYAhVSb1AKHcsxAtQQFghBMAM&url=https%3A%2F%2Fanswers.microsoft.com%2Fen-us%2Finsider%2Fforum%2Finsider\_wintp-insider\_perf-insiderplat\_pc%2Fwsappx-process-takes-more-cpu-usage%2F73393475-312c-4044-8c9e-a5f78f4d7c4c&usg=AOvVaw0uM47U4309VlEkdo0XGWzA

https://answers.microsoft.com/en-us/windows/forum/windows\_10-performance-winpc/very-high-cpu-usage-on-windows-10/9565a1cb-a993-474f-8e2a-fa1e89b6bd4a

https://answers.microsoft.com/en-us/windows/forum/windows\_10-performance-winpc/windows-10-constantly-running-high-cpu-usage-from/dc19af6d-cff1-4e72-a1bf-1c513062f95f

Another issue i have faced was that after logging in, some users facing black screen.

There was a mouse cursor and task manager could be lunched (with ctrl-alt-del) but nothing else showed.

Seemed that explorer stucked in loading.

After googling it turns out that "AppReadiness" (german: App-Vorbereitung) service caused that issue.

After disabling the service the users could logon again.

Here is a thread about the issue and with the workaround: https://h30434.www3.hp.com/t5/Desktop-Boot-and-Lockup/SOLVED-For-everyone-who-is-having-black-screen-after-login/td-p/6318990/page/2

Now i have found a solution for this which works for booth issues and solved them!

Just clear the two user accounts (Control Panel - User account - manage other user account).

You must be logged on from another, working user account.

This olved booth issue 100% for two other user accounts without any workaround.

Hope this helps someone with this bad issue!

Tobias

Windows for home | Windows 10 | Windows Hello, lock screen and sign-in

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

79 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2018-02-15T15:34:44+00:00

    Thanks for documenting this issue.  I have the same behavior, where AppXSVC goes crazy, but only in the event a particular user logs in.  

    Can you clarify - did you delete the user, and then add them back in and that solved it?

    Was this answer helpful?

    90+ people found this answer helpful.
    0 comments
  2. Anonymous
    2018-02-25T15:40:36+00:00

    Hi Tobias,

    Is this really the only solution? It seems like it should be possible for someone to track down what caused the problem and provide a patch to fix this.

    If the only "fix" is to delete the user then this falls into the "solution was to reinstall Windows" group of fixes.... I.e. no fix at all.

    The only reason I'm moaning about this is because I know how much of a pain in the ass it is to move all the documents etc across to a new user account, and who's to say that this problem won't reappear at some later stage on another user account....?

    Can't keep on deleting users can we!

    Best wishes,

    Jon

    Was this answer helpful?

    50+ people found this answer helpful.
    0 comments
  3. Anonymous
    2018-03-06T23:55:34+00:00

    I had the wsappx high CPU issue today and was able to fix it without deleting user accounts. What worked for me was to go into Settings-->Apps, then sort by date and reset all the recently updated Microsoft apps.  After doing this for maybe 6 different apps, the high CPU issue stopped immediately.

    I am speculating that the issue is due to some sort of cache corruption which the reset resolves.

    FWIW, I tried a bunch of other solutions suggested on the web without success. These included changing the pagefile settings, disabling the Microsoft Store with regedit (which did not even work to do that) or with Group Ploicy editor.

    Was this answer helpful?

    40+ people found this answer helpful.
    0 comments
  4. Anonymous
    2018-02-15T21:19:58+00:00

    Yes, delete the User profiles from within "Control Panel - User Accounts" when logged on with another user.

    After recreating the user, the issue is gone for me.

    Tobias

    Was this answer helpful?

    30+ people found this answer helpful.
    0 comments
  5. Anonymous
    2018-04-13T06:40:07+00:00

    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/

    Was this answer helpful?

    10+ people found this answer helpful.
    0 comments