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: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2018-04-27T15:17:18+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?

    Was this answer helpful?

    0 comments
  2. Anonymous
    2018-04-30T16:23:52+00:00

    We had to do exactly the same; any form of recovery offered by Dell reintroduced the issues: Recovery Partition, Recovery USB shipped by Dell Support.

    Only when using older Windows 10 media would the Dell machines work properly.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2018-05-02T01:26:55+00:00

    I had this problem and it now seems to be gone. I'm frankly not sure exactly what fixed it but I wanted to share my experience.

    1. This is on a 5 year old HP desktop running Windows 10 Home with 2 accounts.
    2. Resetting / uninstalling within Apps mostly just hung. I couldn't find a reset function for most of the apps anyway.
    3. I tried the Get-AppxPackage -User ... | Remove-AppxPackage from a different user. As promised there were a lot of errors. This didn't help. In fact it somehow seemed to make it worse as now the other account that didn't originally have the problem also developed it.
    4. I created a new Admin account and it too had the problem.
    5. Tried the Get-AppxPackage ... on the other user account and it hung after a while.
    6. Decided to check Windows Update. It claims KB4093112 was installed on 4/28 and also on 4/30. Also KB4093110 was installed on 4/28.
    7. I ran System Restore. The most recent recovery point was before the 4/28 updates.
    8. System wouldn't boot after the restore. I ran restore again with the same recovery point from the System Recovery menu and this time it booted.
    9. Still had the problem!
    10. Windows update still says all of the above were installed and also says KB4093112 failed to install on 5/1 (After the recovery). Don't know if this is normal for Windows Update to show the history of updates that were done after the restore point.
    11. Rebooted a couple of times and the problem went away. Windows Update now says KB4093110 installed on 5/1. This appears to be the last event before things got back to normal. I am afraid that if it re-installs KB4093112 successfully the problem will come  back.

    I also observed wsappx in Resource Monitor. It was consistently updating \programdata\microsoft\windows\apprepository\StateRepository-Machine.srd-wal. The last I looked before the problem went away the file was 900MB. Now with things back to normal it is 0 bytes.

    Will post again if it come back.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  4. 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
  5. Anonymous
    2018-05-03T08:50:50+00:00

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

    Was this answer helpful?

    0 comments