09-14-2017 03:05 PM
After flipping through recent comments it looks like the black screen issue I am experiencing is pretty common. How long do you think it will take Microsoft and/or HP to fix the issue? Days, weeks, months, ever? I have no idea what to expect?
09-14-2017 11:06 PM
> How long do you think it will take Microsoft and/or HP to fix the issue? Days, weeks, months, ever?
I am sure that HP has made Microsoft aware of the problem.
That implies that Microsoft will release an update on October 10 -- the next "2nd Tuesday of the month" date for releasing updates. So, it could be "less than one month".
Or, for "critical" problems, Microsoft has been known to release "out-of-band" updates, as soon as the updated software passes their internal Quality Assurance reviews, for all languages that Windows 10 supports. So, it could be "days" or "weeks".
Or, for computers that have not updated since the 2nd Tuesday in this month, it's possible that the update will be "pulled" from Windows Update -- meaning that the update will not be available to those not-yet-updated computers. Or, a "version 2" of the update will be available via Windows Update, both to "updated" and "not-yet-updated" computers.
09-15-2017 04:39 AM
Microsoft will blame HP, HP will blame Microsoft. And off it will go.
It's couple of days already and there's no mention of this issue going wide-spread & balistic except on this forum. So don't hold your breath in anticipation for a quick resolution here.
09-15-2017 08:03 AM
You can temporarily fix the black or blank screen at startup by opening Cortana.
Then enter msconfig or ask Cortana to open msconfig.
Open System Configuration.
Select the Services tab.
Uncheck and/or disable App Readiness.
Restart your PC.
09-15-2017 07:47 PM - edited 09-15-2017 07:48 PM
> Installed Windows 10, version 1703, on Asus, Asrock, and Gigabyte motherboards.
> No problems with App Readiness.
Now, please run Microsoft Windows Update on each system, and tell us if those updates from Microsoft have introduced the symptoms.
> So I would guess the problem is on HP's end.
How did you reach that conclusion?
09-19-2017 04:48 AM
For reference from another thread:
Well, there you go:
MS bulletin that was just published: