Forum Home
Press F1
Thread ID: 148259	2019-10-02 21:51:00	"Operating system not found" after changing active HDD	Vicx (11114)	Press F1

Post ID	Timestamp	Content	User
1464263	2019-10-02 21:51:00	Win10 is installed on SSD and documents on a secondary 1tb HDD. I wanted to upgrade to a 2tb so copied all my data from the 1tb then replaced it. Win wouldn't boot without it plugged in, so booted up again and checked the status in computer management. I noticed the 1tb was set as active instead of the SSD so I set the SSD to active, rebooted then got the error "Operating system not found" on boot, with or without the 1tb plugged in. Every step of the way the SSD was always first to boot in BIOS. Win10 is installed on the SSD so I don't know why it says there's no OS, I only used the 1tb for documents. Win10 1809 disk management: imgur.com	Vicx (11114)
1464264	2019-10-02 22:28:00	The cause will be because the boot loader is on the 1TB drive not the SSD, if you had of cloned the 1TB it usually brings the boot loader with it. By changing the active from the 1TB , it basically broke /removed it. You can try rebuilding the boot loader ( leave the other drives disconnected) by the method in this video on youtube www.youtube.com Sometimes works sometimes Not. Had similar yesterday and used Macrium reflect to fix it, you need to download, install on a working computer, then make a ISO CD / USB and boot from that, follow instructions kb.macrium.com Again sometimes works sometimes not.	wainuitech (129)
1464265	2019-10-02 22:54:00	This is why it's recommended to install windows with only a single drive connected because windows installer likes to put boot files on other drives if it finds them. MS either need to stop this practice or make it an obvious choice during setup IMHO. Hopefully Wainuis link helps, I've had success sorting this in the past using EasyBCD to repair the bootloader but to do that you first need to boot into windows. For me on discovering the PC wouldn't boot I put the old second drive back in, loaded up EasyBCD and used it to make the C: drive bootable, then removed the drive again and booted up.. There are probably better methods but this one was easy and worked for me.	dugimodo (138)
1464266	2019-10-02 23:12:00	I see that you have Win10 1809 on the SSD. What you could try is leave the 1TB attached, go to Microsoft media creator, download the ISO for 1903 and then burn that to a DVD (your system is probably 64bit). Turn the PC off, disconnect the 1TB leaving just the SSD and the optical drives attached. Install the 1903 from the DVD to the SSD. Reboot and see that it works. Turn the PC off, attach your HDDs and you should be able to reboot to the 1903 operating system.	Bryan (147)
1464267	2019-10-03 01:05:00	Had similar yesterday and used Macrium reflect to fix it, you need to download, install on a working computer, then make a ISO CD / USB and boot from that, follow instructions kb.macrium.com I spent ages trying to make a bootable Win10 USB, had vague errors every step of the way, even once I finally got into it. Gave up and tried Macrium and it was done in minutes, didn't need to read a tutorial, it was all straight forward. Everything's working fine now. This is why it's recommended to install windows with only a single drive connected because windows installer likes to put boot files on other drives if it finds them. I've learned my lesson now, will make sure only the SSD is plugged in during installation next time. 10025	Vicx (11114)
1464268	2019-10-03 02:13:00	The cause will be because the boot loader is on the 1TB drive not the SSD, if you had of cloned the 1TB it usually brings the boot loader with it. By changing the active from the 1TB , it basically broke /removed it. You can try rebuilding the boot loader ( leave the other drives disconnected) by the method in this video on youtube www.youtube.com . There are other programs too, I've always managed to fix it. As he says....you broke the boot loader.	piroska (17583)
1