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-04-25T13:40:23+00:00

    Hi Everyone,

    Extremely frustrating issue. It affects Fujitsu OEM PCs as well. Tried various fixes suggested above but nothing worked reliably. At the end, we had to rebuild (factory reset) three PCs - one of them twice. It seems the issue is somehow related to the preinstalled MyOffice app. So we don't uninstall it (we only remove it from start for every user that loggs in) as part of our standard build now.

    Symptoms:

    • First non-admin account to log into the PC takes very long time to get to desktop (5 - 10 mins)
    • After that, users get black screen after logon, start menu doesn't work or some apps don't work (e.g. Photos)
    • wsappx maxes out one CPU core

    O.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2018-04-24T00:27:43+00:00

    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.

    I've tried this, but the re-install of apps seems invariably to hang and I'm left with profiles with no apps, and new profiles are similarly crippled. Any specifics of the process you can share that seem repeatable?

    Was this answer helpful?

    0 comments
  3. Anonymous
    2018-04-23T05:09:19+00:00

    That is my assumption: Strange factory-images...

    Was this answer helpful?

    0 comments
  4. Anonymous
    2018-04-23T01:24:12+00:00

    The I guess the technician building the image might have started with a pervious version of windows and this has just been carrying in their image from feature update to feature update. I've noticed workstations I've ordered from Dell always ship with the latest feature update, though interestingly enough the installation usb Dell has been shipping is v1511.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2018-04-23T01:21:21+00:00

    Interesting idea, but that KB is from 2015. If the machine came pre-loaded with v1709 (as did mine), I would assume (admittedly, perhaps an incorrect assumption) that v1709 would include the cumulative updates available since 2015. If your machine Is v1709 and already included this kb perhaps that is why the tool isn't fixing the issue? I agree that based on the remediation we are 100% treating a symptom. But maybe the item you pointed out is the wrong underlying cause?

    Was this answer helpful?

    0 comments