OptiPlex 7050, Windows 10, after login, black screen with mouse cursor

---

@Ralph Sanchezwrote:

Dell-AlanD,

Since you said that you're replying individually, could you please reply to me as well? I posted in a separate thread with a very similar, and seemingly related, issue:

https://www.dell.com/community/Windows-10/Windows-10-s-Microsoft-Store-broken-for-domain-user-accounts/m-p/6057804#M11879

 

---

Hi Ralph, 

This is the suggested solution I posted in the thread.

1. Try the fix below, I have reworded one command statement as I believe it may have been causing the fix to not execute correctly
2. Reinstall the OS using the Dell recovery media from the support site, not the recovery partition
3. Reinstall the OS using the Microsoft Windows 10 image

Here is the latest revision of the steps to apply the fix. It is imperative that all steps are followed correctly

1. Disable the App Readiness Service (wsappx)
In the run box type msconfig. Go to the services tab and disable App Readiness (uncheck all except App Readiness and then tap the disable button)
2. Restart the machine
3. Open an elevated powershell (Windows Key + X)
In the taskbar type powershell. Right click on it and select Run as Administrator. Accept the UAC prompt
4. Type the following command - Get-AppxPackage *office* | Remove-AppxPackage and hit enter
5. Renable the App Readiness Service as per step 1
6. Restart the machine
Once this is completed, the Office hub will be “blank” (the tiles in start menu) and they can be unpinned from the Start Menu.

Alan

---

@Dell-Alan Dwrote:

---

@rrosati-totalsolutions.comwrote:

---

@Dell-Alan Dwrote:

Hi all, 

Thanks for bringing this to our attention. After some investigation from our engineer teams it would appear the issue is being caused by conflicting installs of Microsoft Office. Can you try the following as a workaround and let me know if it resolves the issue for you:-

1. Disable the App Readiness Service (wsappx)
In the run box type msconfig. Go to the services tab and disable App Readiness (uncheck all except App Readiness and then tap the disable button)
2. Restart the machine
3. Open an elevated powershell
In the taskbar type powershell. Right click on it and select Run as Administrator. Accept the UAC prompt
4. Type the following command -Run Get-AppxPackage *office* | Remove-AppxPackage
5. Renable the App Readiness Service as per step 1
6. Restart the machine

Once this is completed, the Office hub will be “blank” (the tiles in start menu)  and they can be unpinned from the Start Menu.

Alan

---

Alan,

We found this suggestion previously and tried it with no luck. Just tried it again on an affected machine. It seems that the issue itself is related to the AppX Deployment Service being messed up. When we run the Powershell command, it just hangs on "Deployment operation progress: Microsoft.MicrosoftOfficeHub_17.8830........" and under that line it says "Initialized". But it stays like that forever and never does anything.

 

It looks like other users are reporting this same issue in this thread: https://www.dell.com/community/Windows-10/Windows-10-s-Microsoft-Store-broken-for-domain-user-accounts/td-p/6057804

 

 

---

That sounds like there could be an issue with your group policy account. Try the steps as outlined here and then rerun the steps I listed above.

Alan

---

Alan,

We tried this "Allow deployment operations in special profiles to Enabled" policy setting on a few machines (across different domains/environment). It didn't help with the PowerShell command getting stuck on Initialized.

Ryan

---

@rrosati-totalsolutions.comwrote:

---

@Dell-Alan Dwrote:

---

@rrosati-totalsolutions.comwrote:

---

@Dell-Alan Dwrote:

Hi all, 

Thanks for bringing this to our attention. After some investigation from our engineer teams it would appear the issue is being caused by conflicting installs of Microsoft Office. Can you try the following as a workaround and let me know if it resolves the issue for you:-

1. Disable the App Readiness Service (wsappx)
In the run box type msconfig. Go to the services tab and disable App Readiness (uncheck all except App Readiness and then tap the disable button)
2. Restart the machine
3. Open an elevated powershell
In the taskbar type powershell. Right click on it and select Run as Administrator. Accept the UAC prompt
4. Type the following command -Run Get-AppxPackage *office* | Remove-AppxPackage
5. Renable the App Readiness Service as per step 1
6. Restart the machine

Once this is completed, the Office hub will be “blank” (the tiles in start menu)  and they can be unpinned from the Start Menu.

Alan

---

Alan,

We found this suggestion previously and tried it with no luck. Just tried it again on an affected machine. It seems that the issue itself is related to the AppX Deployment Service being messed up. When we run the Powershell command, it just hangs on "Deployment operation progress: Microsoft.MicrosoftOfficeHub_17.8830........" and under that line it says "Initialized". But it stays like that forever and never does anything.

 

It looks like other users are reporting this same issue in this thread: https://www.dell.com/community/Windows-10/Windows-10-s-Microsoft-Store-broken-for-domain-user-accounts/td-p/6057804

 

 

---

That sounds like there could be an issue with your group policy account. Try the steps as outlined here and then rerun the steps I listed above.

Alan

---

Alan,

We tried this "Allow deployment operations in special profiles to Enabled" policy setting on a few machines (across different domains/environment). It didn't help with the PowerShell command getting stuck on Initialized.

Ryan

---

Hi Ryan, 

I'm not sure if this will help but you could try the steps outlined here to try and reset Powershell. Ultimately, you may have to reinstall from the recovery media to resolve issues with Powershell.

Alan

I've been working with MS on this issue. Today the engineer had a KB that fixed the problem. Hopefully it works for everyone else too!

http://www.catalog.update.microsoft.com/Search.aspx?q=KB4093105 

-Jon

Did you do anything else beside running the update to fix the issue?

Would like to know as well does installing the Patch from the MS Catalog solve the problem for the profile on reboot. Or id you require any additional steps, like deleting the user profile first ?

Thanks

The April 23, 2018—KB4093105 Cumulative Update solves this issue!

All that is needed is to download the update here:

https://www.catalog.update.microsoft.com/Search.aspx?q=KB4093105

Login as a local PC admin account and install. TIP: (Before you restart, ensure if you disabled "App Readiness" service during trouble shooting that you set it back to "Manual" start.)

After restart, I logged back in as local admin and updated the store and verified all updates worked correctly.

Signed out and back in as Domain user profile and waited for Windows Store to update or manually Open Store and click Downloads and Updates -> Get Updates.

All profiles I tested worked without needing to recreated or delete.

Hope this works for you as well, Cheers!

---

@ScottMcDwrote:

The April 23, 2018—KB4093105 Cumulative Update solves this issue!

All that is needed is to download the update here:

https://www.catalog.update.microsoft.com/Search.aspx?q=KB4093105

Login as a local PC admin account and install. TIP: (Before you restart, ensure if you disabled "App Readiness" service during trouble shooting that you set it back to "Manual" start.)

After restart, I logged back in as local admin and updated the store and verified all updates worked correctly.

Signed out and back in as Domain user profile and waited for Windows Store to update or manually Open Store and click Downloads and Updates -> Get Updates.

 

All profiles I tested worked without needing to recreated or delete.

Hope this works for you as well, Cheers!

---

Hi Scott, 

Thanks for confirming the resolve and the steps you have taken to ensure it was successful. Hopefully others will confirm the fix too.

Alan

Hi all, 

Thanks to @ScottMcD for the feedback and confirming the Microsoft fix resolves the issue. As per his post, please ensure that AppReadiness is running before applying the Microsoft update and it should resolve the black screen issues.

Alan

We are still having issues with workstation getting black screens on login after that update. These black screens do not last as long but are still a hindrance sometimes lasting up to 8 minutes.

We also had one that seemed to still have problems after the update.  We went into the Windows Store and let it update everything that it showed updates for.  But then I also used a GPO to disable the Windows Store.  Not sure which step fixed it.

Hi All,

I can confirm that the patch sorted the issue out for me with a problematic desktop. I deployed a couple new machines this week and with the new Windows 10 update to 1803 the issue seems to have gone so you can also try running that update

Steps taken on problem machine:

1. Download the update and save to C:\Temp

2. Set AppReadiness service to manual

3. Reboot machine and login with an account with admin credentials (I got the black screen issue, but you can open task manager with CTRL+ALT+DEL and go to new task >  c:\temp

4. Install the update

5. Reboot

When the machine rebooted I was able to login with a problem profile and the issue was resolved, desktop shows up, apps work again, start menu works again etc.

Matt

---

@Quynnwrote:

We are still having issues with workstation getting black screens on login after that update. These black screens do not last as long but are still a hindrance sometimes lasting up to 8 minutes.

---

Hi Quynn, have you enabled AppReadiness and installed the Microsoft update as per my last post?

Alan

---

@mjh_smileitwrote:

Hi All,

I can confirm that the patch sorted the issue out for me with a problematic desktop. I deployed a couple new machines this week and with the new Windows 10 update to 1803 the issue seems to have gone so you can also try running that update

Steps taken on problem machine:

1. Download the update and save to C:\Temp

2. Set AppReadiness service to manual

3. Reboot machine and login with an account with admin credentials (I got the black screen issue, but you can open task manager with CTRL+ALT+DEL and go to new task >  c:\temp

4. Install the update

5. Reboot

When the machine rebooted I was able to login with a problem profile and the issue was resolved, desktop shows up, apps work again, start menu works again etc.

 

Matt

---

Hi Matt,

Thanks for updating the thread. It's great to hear you have resolved the issue. Thanks also for clarifiying the steps you used for other user that may find them useful.

Alan