[German]Microsoft’s September 2017 patch day seems to have caused strange thing on HP systems (logon problems with black screen on Windows 10 Creators Update, 3D Drive Guard error messages). Within this blog post I give some background information about the black screen log in issue and introduce fixes for the black screen bug.
Black login screen at Windows 10 V1703
On September 12,2017 Microsoft released some updates for Windows. Since then, HP device owners have been experiencing various issues with their machines. One issue is the black screen bug during login in Windows 10 version 1703.
The user ends with a black screen, that disappears after 6-8 minutes or even longer. I’ve covered this issue within my German blog post MS Patchday: Kritische Fixes und neue Probleme (Sept. 2017). The bug is caused by cumulative update KB4038788 for Windows 10 Version 1703, but only on HP systems.
A first workaround: Disable App-Readiness service
Deactivating the App Readiness service should resolve the issue. At reddit.com there is this thread on the topic. The bug was discussed also within various blogs. German site golem.de has linked to a German HP forum thread, discussing Start HP devices after update to this HP support thread, which mentions App readiness service. But the solution linked above isn’t sufficient. I like to point to this German HP support thread, where support specialist Michael_B outlined the solution.
1. Launch msconfig.exe (via search bar for instance).
(Source: HP support forum)
2. Go to tab Services (Dienste in German) in system configuration program and uncheck App readiness entry (App-Vorbereitung in German).
Click OK and reboot Windows, then the service should not be run. It’s also a good idea to disable Windows fast boot. This topic is also discussed within this English HP support forum thread.
A German blog reader mentioned also, resetting BIOS setting to factory default shall help – but I’m not sure, it that has an effect.
What is App readiness for?
The App readiness service belongs to Windows and is used, during first login of a user. It initializes all apps. It runs also during installing a new app. The service has been introduced in Windows 8.1 (see also) and seems to cause trouble from time to time.
During writing my blog post More Microsoft Updates (September 12, 2017), I searched the web and found some older posts mentions black screen login issues. Carl Stalhood tweeted on September 7, 2016 about a 10 seconds delay on Citrix desktop.
— Carl Stalhood (@cstalhood) 7. September 2016
The issue is covered within this Citrix support article. Also this Microsoft Answers forum thread discussed in December 2016 a black login screen in Windows 10 and naming App readiness. Also German blog reader Michael Bormann posted a comment, mentions the following:
Some (few) HP users has the same issue KB4034674 (August Update), a dark login screen that took up to 20! minutes before the desktop appeared.
Michael pointed to this HP forum post, where he has outlined a workaround (see my text above). And he mentioned that he has deactivated HP’s Jump Start.
A fix from HP
Michael Bormann (who is an external expert in HP’s support forum) has posted another comment pointing to HP’s fix sp81965.exe. The file contains two .exe programs: ImgEnh4SysLogon.exe and HPCUST2.exe, to optimize the login process. Michael told me, that ImgEnh4SysLogon.exe checks, which Windows environment is present. Then HPCUST2.exe sets some registry entries. But we haven’t found out the details.
Addenum: Microsoft confirms the issue
A comment given below pointed out, that Microsoft has published the article KB4043345, saying:
After installing a Windows Store application update, some users may experience a black screen on their device for 5-10 minutes upon rebooting the OS.
Some OEM factory images create incorrect registry keys during image creation. These registry keys conflict with the app readiness service. After 5-10 minutes of black screen the user will regain use of their device. This issue is triggered on every reboot.
Microsoft proposes, to open registry editor and navigate to:
The delete the entries for:
Microsoft announced a fix for this issue during next patchday. The HP fix mentioned above cleans the same registry entries.
Some note from Michael Bormann
Michael (an external HP expert) has analyzed the HP fix with Windows Debugger and Procmon on his HP Omen. Michael has send me the following details via e-mail.
The registry value within the given key will be simply deketed, if present. I haven’t this HP key on my test machine under:
The HP-keys are not present on my HP Omen, because I’ve installed WinDbg with .NET Framework 4.7
Therefore I haven’t the black screen error after update.
I will write a 2nd blog post where I cover the other issue with HP’s 3D Drive Guard, caused by the last Microsoft update.
Microsoft Office non-security updates (September 5, 2017)
More Microsoft Updates from 08/29/2017 and 09/05/2017
Microsoft September 2017 Patchday Summary
Patchday September 2017: Updates for Windows 7/8.1
Windows 10 Updates September 12, 2017
Microsoft Office Security Updates (September 12, 2017)
Update to Adobe Flash 184.108.40.206 and more
More Microsoft Updates (September 12, 2017)
Cookies helps to fund this blog: Cookie settings