Windows 10 1709 - wsappx process high cpu load & and black screen after login for some users

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