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-06-07T04:32:40+00:00

    Updating to build 1803 seemed to fix it for all user accounts.

    Our recent problem computers were all running 1803.

    Just sharing one more +1 that all of the accounts on my home computer are now fixed with 1803.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  2. Anonymous
    2018-05-02T12:53:00+00:00

    I just want to confirm, if you torpedo the factory partitions and install from media generated from the media creation tool or your own image, does this reliably solve the problem?

    It does not, experienced this issue with the Windows 10 installer (iso) downloaded from Microsoft's site a few weeks ago.  Also seeing this on Dell OEM laptops and desktops.  I'm wondering how much it would cost to hire a lawyer and fight Microsoft for all of our time.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  3. Anonymous
    2018-04-23T15:53:39+00:00

    Hi All

    We are now seeing this issue on all builds with 1709 pre installed.

    Deleting the Packages folder in User\appdata\local when logged in with a different account. Log the affected user back in fixes this on a user by user basis. As the folder is regenerated.

    Workaround....

    needs a permanent fix.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  4. Anonymous
    2018-03-30T05:34:16+00:00

    Oh, and we are not seeing this with stock 1709.  And this is occuring whether or not the is a laptop, tablet, or desktop, on the domain or not on the domian, inside the corp firewall, or in the guest network.

    Just to let you know, I am seeing this on a non-Lenovo PC.  I think this is a more fundamental problem since this PC has been running for about 2 years and just recently this started happening.  Just letting you know it is not just Lenovo machines being hit.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  5. Anonymous
    2018-02-25T23:14:02+00:00

    Hey Jon.

    I have searched across the web and did'nt found any other working solution.

    (That doesnt mean there is one :-)

    I'll know its a pain to recreate the user profile(s), but in my case i was lucky to have all my data on an server (network drive).

    The issue is gone for me since ill wrote the OP, so i'll assume it's a permanent fix.

    Sorry for not having a better solution,

    but if you find one, just let us know :-)

    Tobias

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments