(SOLVED) For everyone who is having black screen after login problems

[Langenbacher]

Thanks for the analysis mdklassen!

I think HP needs to provide a description of what this 'fix' does, especially in view of how many people have already applies their own fixes.  HOW does it fix it? Should we undo our own fixes?

[mdklassen]

> I think HP needs to provide a description of what this 'fix' does,  HOW does it fix it? 

Are you asking that HP (and Microsoft) provide detailed technical information about EVERY update that they issue?

In how many different languages do you want that information to be produced?

What would you do with that information?

Or, is: http://ftp.hp.com/pub/softpaq/sp81501-82000/sp81965.html

a sufficient description?

Every month, before running Windows Update, you are running a "black box" computer, with proprietary software.

After running Windows Update, you are running a DIFFERENT "black box" computer.

> especially in view of how many people have already applied their own fixes.  Should we undo our own fixes?

Always undo any "temporary fixes" or "bypasses", if you ever want HP to try reproduce a problem on your computer, when they use a similar computer under their control.

Every auto mechanic at a dealership has been trained & certified to fix automobiles sold by that dealership.

They are not trained nor certified to fix automobiles NOT sold by that dealership.

So, an HP Support technician will have problems with your "customized" installation.

Expressed differently, do not call HP support for a problem with your DELL computer.

[ChrisJ4]

Read the solution after my original post...thanks so much you guys, it worked!

Pavilion 24 fires up just as expected. I guess there must be a batch of these machines where the software between suppliers missed the cross-over somewhere (being generous here :smileysurprised:)

But it worked for me anyway...two mouse clicks preceded by two weeks of rage...I've got to learn after 30 years it's to be expected with IT stuff  

[SalimZhulkhrni]

---

@ChrisJ4 wrote:

Read the solution after my original post...thanks so much you guys, it worked!

Pavilion 24 fires up just as expected. I guess there must be a batch of these machines where the software between suppliers missed the cross-over somewhere (being generous here :smileysurprised:)

But it worked for me anyway...two mouse clicks preceded by two weeks of rage...I've got to learn after 30 years it's to be expected with IT stuff  

---

the solution of disabling the appreadiness service or installing the file from the above link  from hp website ?

[minnesotadon]

I downloaded sp81965.exe, executed it, and rebooted, but it did not fix the problem on my new HP Envy x360 convertible laptop.

[Babs125]

I also got the black screen after logon with the Windows 10 update of 9/12/17,  I also had to go into task manager and disable the service called app readiness.  As long as I keep that disabled my Spectre X360 works as usual.

[CindyCz]

Yes, I have been experiencing the exact same issue on my brand new HP All in One.  I've only had it for less than 2 weeks!  I tried the one solution regarding the "App Readiness" service but that didn't work for me.  Sure hope Microsoft comes up with a solution fast!!!  This is so frustrating. 

[minnesotadon]

Hopefully a fix is on the way soon. In the meantime, this shortened version of a previously-suggested workaround works on my new Envy x360 - bootup after logon is immediate.  Execute NET STOP "App Readiness" once at user logon, (it will be restarted automatically):

Open Task Scheduler by typing it into the Cortana window.  Then:

Action Tab -> Create Task

General:

     Give it a name, e.g. AppReadyFix

     Run only when user is logged on
     Run with highest privileges
     Hidden

Triggers, New

     At log on of any user
     Check Enabled, all other boxes clear

Action, New

     In Program/script enter: NET

     In Add arguments enter: STOP "App Readiness"

Conditions:

     All checkboxes clear

Settings:

     Defaults are OK

Delete or disable that Task Scheduler entry when there is a real fix, because this workaround could cause intermittent bootup problems when the App Readiness service is working correctly.

[CindyCz]

Okay, I stand corrected.   It turns out I didn't actually disable the "App Readiness"  service like I thought I had.  Now that I did disable it properly and rebooted,   my desktop came up immediately after login.  

Now,  now just anxiously awaiting the fix!

[OmenDex]

I Grabbed the 880 spesific fix and it did not seem to work, does the fix work for you Brim223?