HP Users Complain About 10-Minute Login Lag During 'Win 10 Update' (theregister.co.uk)
A number of HP device owners are complaining of seeing black screens for around five to 10 minutes after entering their Windows login information. From a report: They appear to be pointing the finger of blame at Windows 10 updates released September 12 for x64-based systems. One, a quality update called KB4038788, offered a whopping 27 bullet points for general quality improvements and patches, such as an "issue that sometimes causes Windows File Explorer to stop responding and causes the system to stop working." Another, KB4038806, was a "critical" patch for Adobe Flash Player that allowed remote code execution.
People still keep Adobe Flash on their system?
ELOI, ELOI, LAMA SABACHTHANI!?
>> We saw black screens for up to 10 minutes after our Windows 10 upgrade. (Sniff.)
Did it come back AT ALL?
>> Yes, but...
Then I'd call it success. You won't find any sympathy from people whose computers refused to boot after a Windows 10 "upgrade".
It is an HP, has both patches, no problems here.
You're messin' with my Zen Thing, man.....
HP doesn't believe in SSDs. I think they literally believe SSDs are just a myth. So yes, expect login delays as Windows 10 runs a small Defender scan EVERY SINGLE TIME YOU LOG IN! And don't forget indexing and superfetch. But I've noticed that there is a huge CPU bomb of a recompile after the latest update. It processed on a rather fast PC of mine for at least 5 minutes. Still, 1 CPU core and minimum I/O hit on the SSD meant I could still operate the computer at least.
This is normal for Windows 10. Think of it as a feature, not a bug. Log in, and then go stand around the water cooler for ten minutes.
One of our competitors trademarked the term "hypothesis". From now on, we will call them "boneheaded ideas".
We're now seeing Windows 10 machines losing their trust relationship with the DC.
The only way to fix it is to drop and rejoin, but you need a local admin account (or one specifically privileged for those domain operations) on the machine to be able to do that.
And our imaging process sets a random password for the admin account and disables it. Because these are domain machines only and we want them to be secure.
So now we have to hope we've got cached domain admin credentials on these boxes (since we started Windows 10 deployments only recently, it seems like we do so far), unplug from the network, login with cached credentials, create an admin account, drop and rejoin, kill off the admin account, etc.
Fucking Windows 10 every fucking time. FUCK YOU MS!
Last night, I went to use my wife's HP laptop. We share a common login/password. as soon as I pressed enter on the password the updates immediately started. no prompts! When the PC finally booted up all my wife's work was lost because it did not close the open applications gracefully.
needless to say I got in trouble.
I experienced this issue after upgrading to the Windows 10 anniversary edition (build 1607) several months ago. After pouring over various forum posts, disabling 'fast startup' in the power options seems to have fixed the issue for me.
Personally I use Fast Track Windows insider Pro Academic.
Seriously, why?
It sometimes takes Windows longer to install updates than it takes me to install an entire Ubuntu OS. What the hell is it *doing*? It once took me four *hours* to install some Microsoft Visual C++ Redistributable package (of a slightly different version than what I already had) on a fast modern computer with plenty of RAM and a SSD.
Disabling the App Readiness service (disable, not just stop) is a temporary workaround, it will start up normally. It also disables updates on reboot, if that's of any use to you :)
Personally I'd rather have my idiots at home glued to the TV than out doing idiotic things
You know how Windows 7 "sometimes" has trouble sleeping? You've got to put it to sleep twice? Neither I nor my lady has had this problem for days, and then both our machines did it last night, right when Microsoft has released another update.
"You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"