My mother has a HP Touchsmart 600 that I upgraded from Windows 7 to Windows 10. Windows 10 works fine on there, once it finally boots up. I've noticed this scenario:
- Power Button to turn on computer
- BIOS Displays
- Windows 10 logo displays
- screen goes completely black for a couple of seconds
- Screen comes back on, stays dark/gray and I can see my mouse pointer and it moves. The boot process hangs here for several minutes, usually and most of the time, the computer doesn't even go past this point.
- EVENTUALLY, after several minutes, Windows 10 finally gets to the login screen, if it is going to login.
What's the reason for this, and is there a way to resolve this? I'm thinking Windows 7 even took an unusual amount of time to bootup.
Try turning off Fast Startup: Fast Startup - Turn On or Off in Windows 10 - Windows 10 blog
Isn't Fast Startup a feature NOT available in Windows 7? I had the same problem prior to upgrading.
Could the culprit be the on screen keyboard failing to load properly?
It's a Win 10 feature, the computer is at Win 10.My mother has a HP Touchsmart 600 that I upgraded from Windows 7 to Windows 10.
WHAT is a Win 10 feature? You quoted the wrong text. I assume you meant Fast Startup is a Windows 10 feature? Actually, it looks like Fast Startup was introduced into Windows 8 and is obviously also in Windows 10, therefore was not in Windows 7. That said, I don't see how Fast Startup could be the culprit, considering I had the same problem in the Windows 7 environment.
I was just agreeing with you and quoting your text that said you upgraded to Win 10. Pretty useless post I guess, sorry.
It's cool. Don't worry about it. I MIGHT have fixed the problem without performing the arduous task of a clean install. I tried to uninstall as many HP items as possible, but there were a couple that would not budge. One thing I didn't bother trying to uninstall is a HP Webcam. I assume if I did that, Windows 10 MIGHT install its own driver. I think that's what might've happened when I uninstalled the HP Keyboard OSD, which I think actually was the culprit. I'd read somewhere that this driver/app or whatever you want to call it, was 32-bit, whereas the machine is 64-bit. Based on the number of apps that load during startup, I could almost safely assume why this was causing a problem, as I'm guessing the app couldn't address any available memory and load with ease, causing a slowdown or in most instances, a crash.