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: Newest
  1. Anonymous
    2018-04-01T15:03:36+00:00

    I am experiencing the exact same problems on a brand new Dell Latitude. It is domain-joined, but besides the first local user that was created during OOBE setup, and the first domain user that logged in right after joining the domain, all other new local users and domain users that login to the computer for the first time have the issues you describe.

    None of the solutions or fixes I found helped (using wsreset.exe to clear the apps cache, running PowerShell cmdlets to re-register the apps, etc.). Even an in-place upgrade install using the Windows Media Creation Tool did not help. Some work-arounds suggest disabling the Microsoft Store or the App Readiness service, but they are not acceptable fixes to me.

    I finally tried something that helped. It does not directly address the problem, but it does seem to clear up the problem and I'm satisfied with it until Microsoft can fix it properly (hopefully in 1803). I'll post it here in the hope that it helps others.

    First, delete the faulty user profiles. Then open Group Policy Editor (gpedit.msc) as admin. Change the following 3 settings:

    • Computer Configuration > Administrative Templates > System > Logon > Show first sign-in animation = Disabled
    • Computer Configuration > Administrative Templates > Windows Components > Search > Allow Cortana = Disabled
    • Computer Configuration > Administrative Templates > Windows Components > Cloud Content > Turn off Microsoft consumer experience = Enabled

    (Source of these settings: https://docs.microsoft.com/en-us/windows/client-management/mandatory-user-profile)

    Reboot, then login with a user that previously had issues. Hopefully you will find, as I did, that everything is functional except that Store apps do not seem to be set up (the Start Menu tiles have a generic download arrow). But if you click each app, the Store opens to the correct download page, and the app can be installed properly.

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2018-03-31T05:10:29+00:00

    Okay so I found a work-around.  It breaks Windows Store apps but for some people this is acceptable.  I have used this myself and it works.  It involves disabling AppXSvc.  I'm planning to wait a few weeks and then re-enable it after hopefully the bug/issue has been fixed.

    https://www.tenforums.com/performance-maintenance/104767-5-min-delay-cold-start-between-login-screen-bg-screen-7.html

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2018-03-30T15:29:46+00:00

    This started happening on my Surface Pros.

    Deleting the profiles once a day is literally not a valid option.

    Has anyone had anything that permanently fixes this issue?

    Was this answer helpful?

    0 comments No 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 No comments
  5. Anonymous
    2018-03-28T21:02:09+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.

    Was this answer helpful?

    9 people found this answer helpful.
    0 comments No comments