Hi,
I have the exact same problem - black screen after logon and unusable start menu, info center etc.
I tried what you described but it changed nothing - any other idea?
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
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.
Hi,
I have the exact same problem - black screen after logon and unusable start menu, info center etc.
I tried what you described but it changed nothing - any other idea?
All of my Dell PCs ordered in 2018 have had this issue. I also upgraded some machines last fall from v1511 to v1709 using the Media Creation Tool and I had many issues with stock apps not loading after the upgrade. I'm not unconvinced this is a bug v1709 vs bad images from Dell. Thanks for finding a work around. Still will need to use this for each domain user that logs into the machine until a permanent fix becomes available... what a chore, but glad I can now fix this.
I tried removing all the nonsense provisioned apps but still have this issue on every account that logs in other than the first.
First of all thanks for the tip!
It worked for me.
I first had to use the tip from NossonCotlar to create a new account because all accounts on the machine were affected.
Then went through the steps suggested by David Dejaeghere and see... everything works fine again.
One last remark:
I can confirm that the issue is not linked to Dell or Lenovo computers or some bad OEM installation. In my case, it affected an old Desktop computer I put together back in 2010 and upgraded over the years from Xp to Windows 10. By the way, our two other Lenovo laptops did not show the symptoms...
It might not be related, but the only thing I noticed on the affected computer was some instability poping up around December 2017 which remained up to recently. I thought I finally traced the issue (and solved it?) back to the NVIDIa graphics card driver, but in the mean time the PC had crashed numerous times (on both user profiles) and maybe something got messed up in Windows Apps?
Cheers.
It isn't the computer, it is the oem image that appears to be the latest iteration of 1709 that is the common thread.
Actually it's worse than that. There are plenty of folks who have reported (including myself) a perfectly healthy computer suddenly exhibiting this behavior. My own computer came new to me back in ~2015 so this has nothing to do with oem images.
It isn't the computer, it is the oem image that appears to be the latest iteration of 1709 that is the common thread.