Windows 10 Install Fail

ronbo613

Golden Member
Jan 9, 2010
1,237
45
91
0xC19001-0x40017
Installation failed in the SECOND_BOOT phase with an error during BOOT operation


Not much information available. Eset NOD32 AV blocking installation? Devices like eSATA external hard drives and webcam attached to the computer? Devices not attached but drivers installed like joystick and film scanner?

I'm wondering if I should start dismantling my computer or just wait another month or two to install Windows 10.
 

ronbo613

Golden Member
Jan 9, 2010
1,237
45
91
Seems to be one of those issues where the solution is "uninstall all your hardware and software one unit at a time until it works". Everything is working fine on Win 7 Pro, I don't think I want to dismantle the computer for Windows 10. I'll disconnect a couple eSATA hard drives and the USB stuff to see if it works, but that's about it. If a popular program like Eset NOD 32 was preventing Windows 10 installations, everybody would know about it. I'll try installing from a DVD to save some time, but I am losing interest quickly. I'll try it on my Win 7 Pro laptop.

I do have a cloned boot drive, well worth the money for peace of mind in these kind of situations.
 

Eug

Lifer
Mar 11, 2000
24,154
1,801
126
I "solved" this problem by doing a clean install of Windows 7 (and updating to Service Pack 1), then updating to Windows 10.

Win 10 kept on giving me different error messages (including the one the OP had) when I tried to update my previous Win 7 install.

I wonder if it has anything to do with my SSD though, because it is a Sandforce based model which has sleep/hibernate issues with both Windows 7 and Windows 10. I got around this (hopefully) by turning off hibernate completely.
 

ronbo613

Golden Member
Jan 9, 2010
1,237
45
91
I "solved" this problem by doing a clean install of Windows 7 (and updating to Service Pack 1), then updating to Windows 10.
I've always built a new computer when I went to a new Windows operating system. My biggest concern was that Windows 10 was not going to be compatible with the hardware and software I have and that has apparently been the case. To do a clean install of Win7 and reload all my software is too much work, especially when the computer is working fine and does everything I need. The operating system may be free, but how much is it going to cost me to get it to work?
 

Eug

Lifer
Mar 11, 2000
24,154
1,801
126
I've always built a new computer when I went to a new Windows operating system. My biggest concern was that Windows 10 was not going to be compatible with the hardware and software I have and that has apparently been the case. To do a clean install of Win7 and reload all my software is too much work, especially when the computer is working fine and does everything I need. The operating system may be free, but how much is it going to cost me to get it to work?

I guess it depends on how much you want Windows 10 right. Can't hurt to wait. In fact, it is probably advisable to wait. You have a year, and honestly, Windows 10 is buggy as hell right now.

That said, there is no guarantee the update will work even if you try 6 months from now with an updated ISO.
 

Puffnstuff

Lifer
Mar 9, 2005
16,208
4,888
136
With 10 and the free upgrade you have to upgrade in place first. You do this to activate your copy of 10 with your hardware and once done and you don't like it you can either roll back or you can clean install with the 10 dvd that you create from the media creator tool. You don't have to enter any keys while clean installing and once you boot with it in place your copy of 10 will be activated to your hardware automatically.
 

ronbo613

Golden Member
Jan 9, 2010
1,237
45
91
I guess it depends on how much you want Windows 10 right. Can't hurt to wait. In fact, it is probably advisable to wait. You have a year, and honestly, Windows 10 is buggy as hell right now.
The hassle seems to outweigh the benefits of whatever Windows 10 provides at this point, waiting is a good option(and the easiest).

I have a sneaking suspicion that the problem may be a PCIe SATA card that has a couple drives attached to it. Not a complex device, but the drivers for these things are always old. Windows 10 may not have driver support for the card, generic as it is.