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

I wanted to update my previous post: I tested my "solution" on a couple more affected computers, but have not been able to replicate the success. It could be a fluke that it ever worked. However, I'm working on another fix that shows promise. I will post it after I have a chance to test on more computers.

I have seen this on brand-new Dell computers, straight out of the box, but only on profiles created after the initial admin is created. We provision with local profiles first, and then if the environment requires it, domain profiles. I've spent many hours trying to repair, but the only way around it seems to be a full reset of the device and then not letting upgrades install, putting the machines on pause for 30 days.

Same issue here experienced on multiple machines.  This is getting ridiculous.

• Computer Configuration > Administrative Templates > System > Logon > Show first sign-in animation = Disabled
• Computer Configuration > Administrative Templates > Windows Components > Search > Allow Cortana = Disabled
• Computer Configuration > Administrative Templates > Windows Components > Cloud Content > Turn off Microsoft consumer experience = Enabled

I'm following up my previous post with an update. I found after additional testing that the Group Policy settings I posted don't do anything. However, the following has worked consistently on 3 different computers, with domain or local user accounts. No telling if this will work for anyone else, but I hope it may help someone out there.

1. Do a Windows 10 Upgrade Install using the Media Creation Tool (https://www.microsoft.com/en-us/software-download/windows10, click Download tool now). You can either run it online, or create a USB drive. After the initial download and USB drive creation, I find that it is faster to run off the drive than online. Before the install begins, it will ask if you want to keep your programs and data, answer Yes (default). You won’t have to reinstall anything afterwards, which is nice because all of my computers are prepped.
2. After that is done, login as a local admin. I use the account that was created during OOBE, let's call it Administrator.
3. Open C:\Users. Rename the ‘Default’ folder to ‘Default.bak’ (you would need to show hidden files to see this folder).
4. Make a copy of a working profile folder in C:\Users and rename it ‘Default’ (I use the 'Administrator' folder). Choose Skip for all files that can’t be copied. Rename the copy as 'Default'.
5. Open the 'Default.bak' folder. Copy 'ntuser.dat' into the new 'Default' folder.
6. Delete the bad user profile.
7. Open a program by pressing Shift + Right-click and choose ‘Run as a different user’. Use the credentials of the user you’re trying to fix. This will create the user’s new profile folder.
8. Restart, then login with a user you’re trying to fix. It should hopefully work. If not, repeat 6-8 and it should work on the retry.

I’ve tried it with and without an upgrade install, and it simply won’t work without it. I think the reinstall fixes some corrupted Store Apps. I should warn that I have not built out one of these 'repaired' user profiles to ensure that there are no hidden issues. For now this is good enough for me and I have 10 of these new computers to deploy in a few days, so I'm pressing on. Good luck.

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.

https://www.tenforums.com/performance-maintenance/104767-5-min-delay-cold-start-between-login-screen-bg-screen-7.html

Yeah, I just killed the entire store.

Hopefully my Drawboard users dont end up affected in this way, as they would be unhappy.