HP desktop I just put new hard drive in and installed Windows 10.
The Windows 7 hard drive was failing, had no backup or image.
Tried to access drive with USB but drive too far gone.
Decided to install Windows 10 as an upgrade. After a few minor glitches like no activation, was finally able to install and activate.
Used USB Build 10586, 1511 and was able to activate using the Key on the COA sticker. (Thanks, alphanumerical).
PC now will take up to 20 minutes before boot.
The black screen, blue Windows flag and spinning dots just sits there.
All of a sudden, it continues to boot.
I don't have any programs, (oops, sorry, apps), starting.
In fact, it just booted now to the User name, passed, and now is at Desktop. Had been starting for about 20 minutes as I'm posting this.
In the Task Manager, Startup, I don't have anything enabled.
Pete
In the post you did mention the dual boot, then you installed a copy of W8.1 then acivated it, then you installed W10 activaing it with the W7 key, i think Windows is getting confused about what and how activate OSs.HP desktop I just put new hard drive in and installed Windows 10.
The Windows 7 hard drive was failing, had no backup or image.
Tried to access drive with USB but drive too far gone.
Decided to install Windows 10 as an upgrade. After a few minor glitches like no activation, was finally able to install and activate.
Used USB Build 10586, 1511 and was able to activate using the Key on the COA sticker. (Thanks, alphanumerical).
PC now will take up to 20 minutes before boot.
The black screen, blue Windows flag and spinning dots just sits there.
All of a sudden, it continues to boot.
I don't have any programs, (oops, sorry, apps), starting.
In fact, it just booted now to the User name, passed, and now is at Desktop. Had been starting for about 20 minutes as I'm posting this.
In the Task Manager, Startup, I don't have anything enabled.
Pete
No, I was giving background.
This is a clean install on a new hard drive. No dual boot.
I never installed 8.1, where do you see I said that.
If you forget what I said about my initial attempts, I just have a Windows 10 Home, clean installed on a new hard drive, that takes up to 20 minutes to get past initial boot screen.
Sorry about the confusion.
Pete
That is what is written in your System Specs:"OS 8.1 with W-10 Pro Dual Boot"No, I was giving background.
This is a clean install on a new hard drive. No dual boot.
I never installed 8.1, where do you see I said that.
If you forget what I said about my initial attempts, I just have a Windows 10 Home, clean installed on a new hard drive, that takes up to 20 minutes to get past initial boot screen.
Sorry about the confusion.
Pete
If you just installed and the OS is activated, you are not supposed to have installed many programs and relating settings and having an SSD I would reinstall the OS it wouldn't take more than a 15/20 minutes.
I'm working on a customer's PC. Not my own.
For what its worth, I had the original hd installed as the second drive. It was not in the boot sequence.
However, when I removed it, PC now boots normally. First time I've had a second drive causing a slow boot.
Probably should have noticed when it was the initial boot sequence that was taking so long.
Thanks to all who chipped in.
Pete
Well, in your original post you stated that the original drive was failing. There's nothing unusual in failing drive slowing down the boot process.For what its worth, I had the original hd installed as the second drive. It was not in the boot sequence.
However, when I removed it, PC now boots normally. First time I've had a second drive causing a slow boot.
I'm should be more clear. The failing, (failed) drive was listed last in the BIOS Boot.
The new drive is listed as first boot.
The boot process should never have reached the bad drive.
I put it there with the thought that I might be able to use a more forensic type program to access the data from the bad drive.
Never thought it would affect the boot time or even be considered.
Pete
Obviously if that's the 1st Boot in the BIOS which it wasn't.Well, in your original post you stated that the original drive was failing. There's nothing unusual in failing drive slowing down the boot process.
