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-19T14:38:59+00:00

    They are reinstalled because of a shared manuscript. I dont recommend messing with that.  However it should work. a clean reinstall of those apps after removing them  helped for me. 

    You can use non dell media to reinstall windows the activation will work fine. Your bios shares a key with tje Microsoft servers and it will accept the dell oem license.  There is no black magic involved ;)

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2018-04-20T21:12:30+00:00

    With the non impacted account, launch powershell as administrator and run:

    Get-AppxPackage -User <impactedusername> | Remove-AppxPackage

    I can't get the Get-AppxPackage -User command to run on a domain account - getting an error which I suspect is a permissions issue. Not sure how I can fix or work around this.

    Get-AppxPackage : The trust relationship between this workstation and the primary domain failed.

    I'm attempting to run the command from an elevated powershell on a local admin account, not domain admin account.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2018-04-20T22:08:24+00:00

    With the non impacted account, launch powershell as administrator and run:

    Get-AppxPackage -User <impactedusername> | Remove-AppxPackage

    I can't get the Get-AppxPackage -User command to run on a domain account - getting an error which I suspect is a permissions issue. Not sure how I can fix or work around this.

    Get-AppxPackage : The trust relationship between this workstation and the primary domain failed.

    I'm attempting to run the command from an elevated powershell on a local admin account, not domain admin account.

    Please double check the username.  I remember the same error but was upon retrying it worked out fine.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2018-04-21T03:36:43+00:00

    Please double check the username.  I remember the same error but was upon retrying it worked out fine.

    I'm pretty sure I have the username correct. When I run the same command on the local account, it works fine. Is there maybe a special syntax I'm missing for domain usernames? should I prefix with the domain or use name@domain.whatever?

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  5. Anonymous
    2018-04-21T15:19:14+00:00

    Look at the user folder on the computer (C:\Users) and use that exact name. Sometimes if there's duplicates or sign in name has been changed, it can be different that expected.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments