BCD Repair: Troubleshooting BCDedit, Fixboot, CMD - Win 7 Home Premium, SSD, Acronis, Norton Ghost

Where on earth does cmd repair from the installation CD (Win 7 Home Premium) look for the location of the BCD file and the boot (for bootrec / fixboot)? How does he know he should look in the wrong place?

I'm moving the system from HDD to SSD and I'm miserable (great for others, because everything is good, but I have to be perfect, without errors).
1. I moved Acronis (C: + mbr + boot alone to fit on SDD), it's good, but after uploading the image there is volmgr 46 error (crash dump failed). In addition, the repair from the disc throws errors.

2. So I moved Norton Ghost from 2003 (this is how SSD and AHCI works, which he has not heard of). Before I did it on SSD I gave active partition, and on active HDD I changed to inactive (diskpart inacive), otherwise BCD installs on HDD and shows 2 entries one for SSD and HDD.
2a. Of course, the system did not start, so I did everything that went from here: https://answers.microsoft.com/pl-pl/windows/f...ozruchowego-windows-7/b1a02e8a-41fe-45dd-96dd -7726ed135ec2

It helped to unplug the HDD cables and again everything from the link, the system started, after connecting the HDD I have:
- everything works great without errors in the event log
-p under Windows bcdedit / enum shows the correct 2 entries for the C: partition (i.e. SSD)
- from installation CD and repairs:
--bootrec / fixboot informs "cannot find item"
--bcdedit / enum "could not open boot configuration data store" and "could not find the requested system device"
- the same lies bootrec / rebuildbcd (I remind you that the system works OK, on SSD C: there is bootsector mbr bootmgr and a valid BCD file in C: \ Boot \).
How do you force these commands to search where you need to?

I apologize for the interrogative form, but ...
Maybe it is worth starting with diskpart and checking what and how the system recognizes and means, and then wondering if and what is "lying"?

Ie. what to check I checked the diskpart under Windows and the installation disc, the differences are:
- disks switched places 0 1 and 1 0
- from the disc the SDD disk is not bootable (HDD neither), paging not, the crash dump is not
- under Win sees everything OK.

In addition, the CD starts without pressing any key (because it does not see any system or maybe a boot).

I suspect that the untrue data is in the C: \ Recovery directory (probably there is the data from the 100 MB partition, because I do not have it, I blocked it by partitioning the disk before installation). I suspect, because one auto-repair referred to Recovery. In addition, the repair from the disc now detects the lack of a valid system partition (probably because it is looking for it on the HDD).