Boot – αρουμε απο το DVD με τα Vista – 7 και τρέχουμε command line απο Recovery Console για να κανουμε επιδιόρθωση MBR & bootsectors
Οπου x: το γράμμα του CD-Drive
bootrec.exe /fixmbr x:bootbootsect.exe /nt60 all /force
bootrec.exe /fixmbr bootsect.exe /nt60 all /force
Rebuild your BCD:
attrib -h -s C:bootBCD del C:bootBCD bootrec.exe /rebuildbcd
Αν όλα πάνε καλά , θα βγάλει ενα μύνημα οτι είναι ΟΚ
Aν χασουμε τον bootloader των windows απο τον grub ή lilo τοτε απλα δινουμε
- The boot sector has been replaced with a non-standard Windows Vista or Windows 7 boot sector.
- The boot sector is damaged.
- An earlier Windows operating system has been installed after Windows Vista or Windows 7 was installed. In this scenario, the computer starts by using Windows NT Loader (NTLDR) instead of Windows Boot Manager (Bootmgr.exe).
Displays these usage instructions.
Applies the master boot code that is compatible with NTLDR to SYS, ALL, or <DriveLetter>. The operating system installed on SYS, ALL, or <DriveLetter> must be a previous version of Windows Vista.
Applies the master boot code that is compatible with BOOTMGR to SYS, ALL, or <DriveLetter>. The operating system installed on SYS, ALL, or <DriveLetter> must be Windows Vista.
Updates the master boot code on the system partition used to boot Windows.
Updates the master boot code on all partitions. ALL does not necessarily update the boot code for each volume. Instead, this option updates the boot code on volumes that can be used as Windows boot volumes, which excludes any dynamic volumes that are not connected with an underlying disk partition. This restriction is present because boot code must be located at the beginning of a disk partition.
Updates the master boot code on the volume associated with this drive letter. Boot code will not be updated if either 1) <DriveLetter> is not associated with a volume or 2) <DriveLetter> is associated with a volume not connected to an underlying disk partition.
Forcibly dismounts the volume(s) during the boot code update. You must use this option with caution.
If Bootsect.exe cannot gain exclusive volume access, then the file system may overwrite the boot code before the next reboot. Bootsect.exe always attempts to lock and dismount the volume before each update. When /force is specified, a forced dismount is attempted if the initial lock attempt fails. A lock can fail, for example, if files on the destination volume are currently opened by other programs.
When successful, a forced dismount enables exclusive volume access and a reliable boot code update even though the initial lock failed. At the same time, a forced dismount invalidates all open handles to files on the destination volume. This can result in unexpected behavior from the programs that opened these files. Therefore, use this option with caution.