HDD to SSD cloning boot issue W10

Hello

Yes, sometimes there is a "boot repair" to be done on a small partition so that the PC can "find" the SSD drive as an internal mount.

Due to the particularities, we will wait for someone else who is more efficient.

Clarify this point:

"This would be due to the fact that the drive is ultimately not in the correct PC."

Yes, a "clone" will also pose a problem if we try to put it in a different PC, as it contains many settings, drivers... valid for only one PC most of the time right from startup.

Yes, for starting from an external disk, Ubuntu could do it; you need to set the "boot order" in the BIOS and an Ubuntu installation "to boot from the external USB disk" or "live".

Hello

A cloned disk must be tested on the PC where it was cloned. Your blue screen is because you are installing Windows and the hardware configuration of PC "a" into PC "b", not the same processor, not the same chipset, not the same drivers, etc....

This answers all your questions, as Carier had already responded.

Signature
Waiting for other responses; I'm attracting trolls....

Hello, thank you for your insights. :-)

Okay, so I will test it on the right PC and see how it goes...

In the meantime, I have two new minor problems.

1) When opening the right PC, I couldn't change the disk, the previous disk being embedded in a chassis with, presumably, a ribbon IDE on top of it.

2) This IDE ribbon obviously came off, and upon restarting, I no longer have a keyboard :-p!

I will open another thread, here, for this discussion!

Here is the feedback from Boot-info:

Now that it's said "=> No boot loader is installed in the MBR of /dev/sda/sda1", I don't know how to install a Windows bootloader!

 boot-repair-4ppa2079 [20240813_1108] ============================== Boot Info Summary =============================== => No boot loader is installed in the MBR of /dev/sda. sda1: __________________________________________________________________________ File system: vfat Boot sector type: FAT32 Boot sector info: No errors found in the Boot Parameter Block. Operating System: Boot files: /efi/Boot/bootx64.efi /efi/Microsoft/Boot/SecureBootRecovery.efi /efi/Microsoft/Boot/bootmgfw.efi /efi/Microsoft/Boot/bootmgr.efi sda2: __________________________________________________________________________ File system: Boot sector type: - Boot sector info: sda3: __________________________________________________________________________ File system: ntfs Boot sector type: NTFS Boot sector info: No errors found in the Boot Parameter Block. Operating System: Windows 8 or 10 Boot files: /bootmgr /Boot/BCD /Windows/System32/winload.exe sda4: __________________________________________________________________________ File system: ntfs Boot sector type: NTFS Boot sector info: No errors found in the Boot Parameter Block. Operating System: Boot files: sda5: __________________________________________________________________________ File system: ntfs Boot sector type: NTFS Boot sector info: No errors found in the Boot Parameter Block. Operating System: Boot files: sdb: ___________________________________________________________________________ File system: iso9660 Boot sector type: Unknown Boot sector info: Mounting failed: mount: /mnt/BootInfo/FD/sdb: /dev/sdb already mounted or mount point busy. ================================ 1 OS detected ================================= OS#1: Windows 10 on sda3 ================================ Host/Hardware ================================= CPU architecture: 64-bit Video: HD Graphics 5500 from Intel Corporation Live-session OS is Linuxmint 64-bit (Linux Mint 21.2, victoria, x86_64) ===================================== UEFI ===================================== BIOS/UEFI firmware: X555LAB.600(5.11) from American Megatrends Inc. The firmware is EFI-compatible, but this live-session is in Legacy/BIOS/CSM mode (not in EFI mode). 6d090c6258e6fc0abb7ae02b556a0ae0 sda1/Boot/bootx64.efi 23837e7f81b5b729c2cc673d3da56273 sda1/Microsoft/Boot/SecureBootRecovery.efi 6d090c6258e6fc0abb7ae02b556a0ae0 sda1/Microsoft/Boot/bootmgfw.efi fa557984f7a6b5dac255553895df0331 sda1/Microsoft/Boot/bootmgr.efi ============================= Drive/Partition Info ============================= Disks info: ____________________________________________________________________ sda : is-GPT, no-BIOSboot, has---ESP, not-usb, not-mmc, has-os, has-win, 2048 sectors * 512 bytes Partitions info (1/3): _________________________________________________________ sda1 : no-os, 64, nopakmgr, no-docgrub, nogrub, nogrubinstall, no-grubenv, noupdategrub, not-far sda3 : is-os, 64, nopakmgr, no-docgrub, nogrub, nogrubinstall, no-grubenv, noupdategrub, end-after-100GB sda4 : no-os, 64, nopakmgr, no-docgrub, nogrub, nogrubinstall, no-grubenv, noupdategrub, end-after-100GB sda5 : no-os, 64, nopakmgr, no-docgrub, nogrub, nogrubinstall, no-grubenv, noupdategrub, end-after-100GB Partitions info (2/3): _________________________________________________________ sda1 : is---ESP, part-has-no-fstab, no-nt, no-winload, no-recov-nor-hid, no-bmgr, notwinboot sda3 : isnotESP, part-has-no-fstab, no-nt, haswinload, no-recov-nor-hid, bootmgr, is-winboot sda4 : isnotESP, part-has-no-fstab, no-nt, no-winload, recovery-or-hidden, no-bmgr, notwinboot sda5 : isnotESP, part-has-no-fstab, no-nt, no-winload, no-recov-nor-hid, no-bmgr, notwinboot Partitions info (3/3): _________________________________________________________ sda1 : not--sepboot, no---boot, part-has-no-fstab, not-sep-usr, no---usr, part-has-no-fstab, no--grub.d, sda sda3 : not--sepboot, no---boot, part-has-no-fstab, not-sep-usr, no---usr, part-has-no-fstab, no--grub.d, sda sda4 : not--sepboot, no---boot, part-has-no-fstab, not-sep-usr, no---usr, part-has-no-fstab, no--grub.d, sda sda5 : not--sepboot, no---boot, part-has-no-fstab, not-sep-usr, no---usr, part-has-no-fstab, no--grub.d, sda fdisk -l (filtered): ___________________________________________________________ Disk sda: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors Disk identifier: A5600CC8-57CF-11EF-8336-C8FF28BC179F Start End Sectors Size Type sda1 2048 534527 532480 260M EFI System sda2 534528 567295 32768 16M Microsoft reserved sda3 567296 780205465 779638170 371.8G Microsoft basic data sda4 780206080 781410303 1204224 588M Windows recovery environment sda5 781410304 1953523711 1172113408 558.9G Microsoft basic data Disk sdb: 7.22 GiB, 7751073792 bytes, 15138816 sectors Disk identifier: 0x14eb2669 Boot Start End Sectors Size Id Type sdb1 * 0 5138431 5138432 2.5G 0 Empty sdb2 572 9067 8496 4.1M ef EFI (FAT-12/16/32) sdb3 5140480 15138815 9998336 4.8G 83 Linux parted -lm (filtered): _________________________________________________________ sda:1000GB:scsi:512:512:gpt:ATA CT1000BX500SSD1:; 1:1049kB:274MB:273MB:fat32:EFI system partition:boot, esp; 2:274MB:290MB:16.8MB::Microsoft reserved partition:msftres; 3:290MB:399GB:399GB:ntfs:Basic data partition:msftdata; 4:399GB:400GB:617MB:ntfs::hidden, diag; 5:400GB:1000GB:600GB:ntfs:Basic data partition:msftdata; sdb:7751MB:scsi:512:512:msdos: USB DISK 3.0 Pro:; 2:293kB:4643kB:4350kB:::esp; 3:2632MB:7751MB:5119MB:ext4::; Free space >10MiB: ______________________________________________________________ sdb: 4.43MiB:2510MiB:2506MiB blkid (filtered): ______________________________________________________________ NAME FSTYPE UUID PARTUUID LABEL PARTLABEL sda ├─sda1 vfat 58CE-3D61 a5600cc9-57cf-11ef-8336-c8ff28bc179f SYSTEM EFI system partition ├─sda2 a5600cca-57cf-11ef-8336-c8ff28bc179f Microsoft reserved partition ├─sda3 ntfs 4AB8D0A0B8D08C37 a5600ccb-57cf-11ef-8336-c8ff28bc179f OS Basic data partition ├─sda4 ntfs 9650FA5650FA3D15 a5600ccc-57cf-11ef-8336-c8ff28bc179f └─sda5 ntfs EA8CF0448CF00CB7 a5600ccd-57cf-11ef-8336-c8ff28bc179f DATA Basic data partition sdb iso9660 2023-12-23-05-05-55-00 Boot-Repair-Disk 64bit ├─sdb1 iso9660 2023-12-23-05-05-55-00 14eb2669-01 Boot-Repair-Disk 64bit ├─sdb2 vfat 8D6C-A9F8 14eb2669-02 ESP └─sdb3 ext4 c22af8ef-9c7c-46aa-803e-5b6bc68db12c 14eb2669-03 writable Mount points (filtered): _______________________________________________________ Avail Use% Mounted on /dev/sda1 231.9M 11% /mnt/boot-sav/sda1 /dev/sda3 313.9G 16% /mnt/boot-sav/sda3 /dev/sda4 83.6M 86% /mnt/boot-sav/sda4 /dev/sda5 483.1G 14% /mnt/boot-sav/sda5 /dev/sdb1 0 100% /cdrom Mount options (filtered): ______________________________________________________ /dev/sda1 vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro /dev/sda3 fuseblk rw,relatime,user_id=0,group_id=0,allow_other,blksize=4096 /dev/sda4 fuseblk rw,relatime,user_id=0,group_id=0,allow_other,blksize=4096 /dev/sda5 fuseblk rw,relatime,user_id=0,group_id=0,allow_other,blksize=4096 /dev/sdb1 iso9660 ro,noatime,nojoliet,check=s,map=n,blocksize=2048,iocharset=utf8 ======================== Unknown MBRs/Boot Sectors/etc ========================= /dev/sda1: unknown GPT attributes 8000000000000000 /dev/sda2: unknown GPT attributes 8000000000000000 /dev/sda4: unknown GPT attributes 8000000000000001 Unknown BootLoader on sdb Suggested repair: ______________________________________________________________ The default repair of the Boot-Repair utility would not act on the boot. sprunge.us ko ()

I found it! Apparently I need to download the Windows 10 Media Creation Tool from the Microsoft website!

But there's a problem, the site tells me that I cannot download the Windows 10 Media Creation Tool without having Windows on my PC, which is running Linux! It only offers me to download W10!

Do you have any suggestions to work around these inconveniences?

Thank you

Ok, it's good, I found a way to write a W10 ISO image to a USB key...without Windows using WoeUSB-ng!

After long investigations, I think I have found the problem!

1/ I then launched the W10 installation USB and troubleshooting mode and followed the procedure described below:

 Solution 2: Recreate the Boot Configuration Data file The Boot Configuration Data, also known as BCD, contains the boot configuration parameters regarding how to start your Windows operating system. If the configuration file is corrupted, your Windows 10 will fail to boot with the Windows 10 boot error 0xc000000e. Since your Windows is now impossible to start, you need to create a bootable USB media from the ISO for Windows 10 and then boot from it. Then, follow these steps to recreate BCD on your computer. 1. Click Next on the view of the first screen after you booted your computer from the bootable USB media. click Next 2. You will see the Install now button, but you should not press the Install now button. Instead, you should click on the Repair your computer link located in the lower left corner to continue. click Repair your computer 3. Go to Troubleshoot > Advanced options > Command Prompt. go to the command prompt 4. Choose the account you use to continue. 5. If you have set a password for your computer, enter it to continue. 6. Enter the following command and press the Enter key: bootrec /rebuildbcd 7. As soon as a Windows installation is found, you need to press the Y key on the keyboard to allow it to boot from the list. This will recreate BCD. 8. Once the operation is complete, you need to type bootrec /fixmbr and bootrec /fixboot in succession and press the Enter key after each command.

Everything worked until 'step 8.

I typed:

bootrec /fixmbr

[pc response]The operation was successful.

Then I typed to finish:

bootrec /fixboot

[pc response]Access denied

EDIT: I tried in Windows troubleshooting tools "System Restart Tool". --> windows therefore ran a diagnosis of the pc.

Its return: "System Restart Tool could not repair Windows".

I will focus on this bootrec /fixboot issue and then I will see what happens!

EDIT 2: I will try to rebuild the Windows 10 MBR with a Gparted LiveUSB...

Hello,

What has always worked well for me is creating a Windows disk image on another disk, then replacing the Windows disk and restoring the image on the new one.

There are free giveaway programs that do this.

Sometimes you need to move/resize the partitions afterwards.

To create a disk image, backup the system with the O&O DiskImage 17 Pro program (with the option to create a bootable medium for restoration in case of a malfunctioning system, or to clone it)

For the free giveaway license (be sure to read in case the giveaway is over) there will be others..

O&O DiskImage 17 Pro
https://www.oo-software.com/de/special/ztp996

For the setup (English)

https://www.oo-software.com/en/download/archive

For the manual in pdf (English)

https://www.oo-software.com/en/docs/usersguide/oodi17.pdf

Thaaaank you for these tips, I'm going to give it a try!