Create an account on the HP Community to personalize your profile and ask a question
09-13-2017 04:04 PM - edited 09-15-2017 01:14 AM
The problem isn't resolved until HP releases a hotfix that allows newly unboxed machines to go through the update process properly. Until that time it would be nice if HP actively participated in their own forums with people who are handing them work arounds that could possibly appease their customers.
As to the "this is a fix, not work around", it still feels like an untested work around because windows update was not aware of the HP software since you disabled all of those services during reboot. Once you re-enable the Windows update service and re-enable all of the software services that you disabled, the update service might determine that it needs more drivers, or possibly even different drivers and the whole process could start over again. You might walk away at night and be facing a black screen again as Windows replaced **bleep** while you slept.
WHAT I DID INSTEAD:
I did a fresh install of Windows 10 (a current up to date version) from my own media (nuked HP's sad sad image) and only let certain needed devices update (video primarily). I then disabled the Windows 10 update service and will leave it disabled until i can confirm this issue has been resolved in appropriate ways by HP and Microsoft.
True Computing Technologies
09-13-2017 04:35 PM
The owner of the company I work for had this issue with her Spectre.
App Readiness disable did do the trick, but I noticed that the service would still start with windows though it was disabled.
If you would like to have a fix in this that will launch your desktop immediately each time, do the following.
open notepad and include the following in the notepad:
net stop appreadiness
save notepad as fixwindows.bat or whateveryouwanthere.bat <- has to have the .bat extesnion and save as "All Files" in order for the file to be assigned the extension of .bat isntead of .text.
save the file in this directory:C:\Users\<YOURUSERNAME>\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup
this will execute the .bat file killing the appreadiness service each time you boot, saving you the time and headache of killing the service until M$ gets their stuff together and fixes it.
09-13-2017 05:03 PM
09-13-2017 06:54 PM
In response to SkylarTStoleson above regarding creation of a .bat file to automatically shutdown App Readiness:
I like the idea of automating, however putting the .bat file in the startup directory did not work for me because on my Windows 10 machine, I could not get it to run as administrator as a startup item.
So, instead, I put the following into a .bat file and stored it in a "junk" directory I created on my C:/ drive:
net stop "AppReadiness"
I then created a Basic Task (using the Task Scheduler) that runs the .bat file at login at highest privelege. This works on my machine and I get a fairly swift startup now. I also check the services tab in the Task Manager to assure that the App Readiness service has re-started and is running again. If it is not running and an update occurs in the background, the update install could possibly fail.
This is what I am doing until MS or HP can provide a proper solution. I'm afraid of using System Restore or uninstalling the recent updates at this point.
I think this is getting a bit messy...but that's what tends to happen with workarounds. Hoping for a proper fix/update soon!
09-13-2017 08:37 PM - edited 09-13-2017 08:56 PM
WAY TO GO!!!! Thank you!
I was so frustrated with my new computer black screening after updating a Win10 update that I was ready to install a Linux OS haha. You saved the day. Simply stopping the App Readiness service fixed the issue.
HP - you guys are pretty bad. Pick your game up. There are many other options in this industry, you need to do better.
This is likely an issue caused by HP bloatware that is incompatible with the Microsoft update.
09-13-2017 08:43 PM
And to add - you can actually do this without being in safe mode or anything.
Just Ctrl+Alt+Delete from the blac desktop, and stop the service from within task manager. Takes maybe 30 seconds. An imperfect solution to be sure, but it at least is a time saver while HP and Microsoft play the blame game.