This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
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.
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
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.
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.
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?
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.
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:
(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.
I have experienced the same problem with brand new Dell Latitudes 54xx series.
1709 loaded by default. (Yay!)
Runs great out of the box!! Configured for AzAD join. and installed required software and ready for deployment!!!
(Right??)
WRONG.
First user deployed to experienced 5-10 wait time during logon. Rebooting makes the issue worse.
I didn't believe it until I saw it myself.
I just setup 10 others the same way ready to ship to project site. (oh sh***!)
So , I've been working this issue relentlessly (100s of reboots - 100s of user login combinations to try to turn off the service, etc.)
since Thursday Mar 29.
Tried everything!!
Wsreset
gpedit to turn off the WIndows store.
Nothing worked. More than one reboot, and the issue returned.
I determined I would hack the registry and set the service to 4 (disabled.)
This worked, but I'm concerned future apps will not install correctly, or userx will actually try to use the store.
- So that's not the solution - The service is there for a reason, and it works correctly until something "triggers" it into exorcist mode.
All kinds of strategies to resolve the issue...
... something is corrupting the default user profile... what could it be?
I uninstalled the bloatware. Considered hw drivers, but... didn't feel right, all the hw was working great.
Windows updates and patches (one for "OEM images, etc" was VERY promising, until rebooting, and the issue returned.)
AND
Initial OOBE logon user was perfect.
Every time. Every stinking time!!
(Only exceptions was after another user profile started the appxsvc, then it continued to run regardless the user.)
The only thing left was Office 365....
I setup a brand new unit OOBE, did not install O365.... new user logon was :20s.
YES! 20 Seconds!!
I've been timing the default user profile build so I could determine what changes had effect.
Went from a PAINFUL 6 minute logon time. (With AppxSvc still clocking 25% of cpu non-stop) to...
20 Seconds....
Now the bad news:
O365 must be deployed.
Looking through any and all o365 docs for help.
I posted this not as a solution but to add information to the diagnosis.
Good luck everyone.
If I find a solution I will post it here!
