Boot.ini

Darwin4Ever · 03 Sep 2019

Hi,

I have the following :
1) a HDD with

Windows10_64-bit
Windows10_32-bit
A number of logical partitions

2) a SSD on which I cloned the HDD/Windows10_32-bit
3) a bootmanager (not Windows bootmanager) which allows me to select which partition to boot.

Booting from the SSD/Windows10_32-bit doesn't work !

If I leave the HDD/Windows10_32-bit as bootable, and boot from SSD, actually HDD/Windows10_32-bit is launched
If I set HDD/Windows10_32-bit as NOT-bootable, and boot from SSD, Windows10 is looping for ever on the Windows10 logo.

In Windows XP this indicated a wrong HDD/partition reference in boot.ini, which could be edited from within another OS to solve that problem.

How can I solve this on the SSD/Windows10_32-bit ? There is no longer a boot.ini and I can't boot into the SSD/Windows10_32-bit

FYI: HDD/Windows10_32-bit remains needed too !!!

Samuria · 03 Sep 2019

Welcome to the forum. Can you post a screenshot from disk manager showing all the details we need to see if your using uefi,gpt disk etc

Darwin4Ever · 03 Sep 2019

Non UEFI-BIOS and MBR HDD/SSD

Boot.ini-2019-09-03-15_22_03-diskgenius-v5.1.2.766.jpg

Boot.ini-2019-09-03-15_23_23-diskgenius-v5.1.2.766.jpg

Megahertz · 03 Sep 2019

When you cloned the Win 10 from the HDD to the SSD it also cloned the disk HDD ID into the SSD.
To be able to boot from the SSD do the following:
- Detach all other disks (Take the power cable) leaving on only the SSD
- Boot from the Win 10 32 bits installation disk, go to repair and do a startup repair.
- See if boots on from the SSD.

Darwin4Ever · 04 Sep 2019

Not sure if it's important related to the HDD ID : I did not clone the HDD, just one partition.

Problem is, the other logical partitions are needed and part of the setup. Maybe I'm wrong, but disabling the HDD doesn't seem to be a good idea (even temporary).

Why are handy things (boot.ini being just an example) always removed and replaced by something that makes things only difficult and/or impossible ?

Megahertz · 04 Sep 2019

On a MBR, BIOS transfer the boot to the priority boot disk. The MBR on the disk transfer the boot sequence to a boot loader on a partition (the partition that is set as active). This boot (master) loader (or boot manager) can boot the OS on that partition or transfer to another boot loader on another partition or even on another disk. This partition is identified by a partition ID. Linux Grub is an example of a master boot loader, and you wrote that you have a similar master boot loader that manages boot loaders sequence (transfer the boot sequence to another boot loader on another partition or even on another disk).
The instructions I gave you on post #4 is to correct the partition ID on the SSD. The next step would be to configure your boot manager and include the SSD as an option.

Darwin4Ever · 07 Sep 2019

Megahertz said:

The instructions I gave you on post #4 is to correct the partition ID on the SSD. The next step would be to configure your boot manager and include the SSD as an option.

I tried the instructions on post #4 : no luck, result is "Could not repair your PC". Despite the fact that the cloned \Boot directory with the BCD exists on the SSD.
The next step (configure boot manager) isn't necessary as already configured (see post #1)