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 No comments

79 answers

Sort by: Oldest
  1. 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 No comments
  2. 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 No comments
  3. Anonymous
    2018-04-25T14:11:41+00:00

    Hi All

    I have seen a lot of success repairing the apps with the packages rename workaround. We have now also had some PC's that were so broken that we have had to reset it. 

    Initially this issue seemed confined to our new laptops but now some desktops have this issue. This could correlate with when we receive out stock.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2018-04-26T04:30:21+00:00

    Have two brand new surface pros showing these symptoms after a reboot 

    Both domain joined, both updated completely

    Tried all fixes, repairs etc

    Extremely frustrating, spent 5 hours trying to troubleshoot them both with no results 

    Disappointed Microsoft

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  5. Anonymous
    2018-04-26T07:42:37+00:00

    So I had the issues described above too: brand new Yoga520 with 1709 build OEM from Lenovo. I had created a first user (as a family parent) and then immediately continued to adding the children (before updating windows or rebooting etc.)

    This got me a black screen after re-logon with the child account. The parent account was still fine. Tried everything until I decided to reset the machine. Did that and then made sure that I had updated windows with all recent fixes before continuing to create the child user again. I also rebooted the machine a few times, especialy from the 'Windows Update' button (instead of the regular 'start' button). Somehow, 'update and restart' from the start button didn't realy updated the machine. I also executed the above non-permanent fix. That didn't find any issues so I created the child user. Everything seemed to go smooth, I got the desktop, start menu was working so I guessed it was 'fixed'. BTW, I didn't remove any of the preloaded packages from lenovo nor did I go into regedit to change something.

    Then I logged off and on again to the child account and ahhhh, there was the black screen again!!! Damn! The I logged on to the parent account and tried the fix again and hurray...i said it found and issue and fixed it! And indeed, now I could logon to the child account again without issues.

    The machine is working fine for some days now...I lost a couple of days fixing this however but the above post helped me a lot! So I wanted to share my experiences too...

    Thanks and good luck fixing...

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments No comments