D
D
Dmitry Logvinenko2011-12-14 13:16:32
Windows
Dmitry Logvinenko, 2011-12-14 13:16:32

How to restore Windows 7 bootloader after installing Win 8 Dev?

During the installation of Windows 8 Dev, it, of course, erased the loader from 7.
The layout is like this:

  • (hd0,0) and mbr - Grub4Dos.
  • (hd0,1) and PBR - Windows 7, non-working loader from 8 and scraps of loader 7
  • (hd0,4) - Windows 8 was here, it's not here anymore, cheers.

G2D was easily restored using a flash drive and a second computer.
During normal loading using G2D line by line:
chainloader (hd0,1)+1
this thing appears:
03.jpg.
Windows 7 is loaded line by line
chainloader (hd0,1)/bootmgr
, but hibernation and, accordingly, hybrid sleep mode do not work (extremely critical).
Actually, the question is how to return everything back.

Answer the question

In order to leave comments, you need to log in

4 answer(s)
O
Oleg Karnaukhov, 2011-12-15
@BupycNet

recently booted Windows from a flash drive, partition, etc. NTFS has a feature - load bootmgr if it exists.
Judging by the picture, this is a piece of the bootloader from Win8. Give a listing of the three sections.
In general, I advise you to erase all bootmgr and other hidden files at the root that are definitely not needed (of course, wisely) and install the win7 bootloader from the disk. It's just that the win7 bootloader remained, but pieces of win8 clog it.
oh yes, under Windows itself, try www.oszone.net/11294/ execute directly when Windows is running. In fact, it should put a working bootloader, scoring everything that interferes.

A
asm0dey, 2011-12-16
@asm0dey

For some reason I didn't get it. And there is an option to put a hornbeam. It will probably pick up all bootloaders.
You can also try EasyBCD - it can fix bcd - you can add a boot point yourself.

D
Dmitry Logvinenko, 2011-12-16
@dmlogv

I agree, it was necessary to do this (I paint in detail):

  1. We make (get it, extract it from the basement) a bootable device (in my netbook case, a USB flash drive) with Windows 7 on board.
  2. We reboot the equipment, boot, of course, not from hard, but from the installation drive.
  3. We patiently wait for the offer to install the system, but select the "System Restore" link somewhere deep below.
  4. We select the system we need from a long list
  5. Open the command line by clicking on the last item
  6. Now we need to find on which disk our current Windows is located (if we forgot to look in the previous paragraph :):
    Run to succession
    dir c:\
    dir d:\
    dir e:\
    It took me three times to get to the familiar folder structure.
  7. Now let's delete! Ideally:
    rd e:\$WINDOWS.~BT /s
    rd e:\Boot /s
    del e:\bootmgr /s
    Only I didn’t succeed in deleting the first folder and the third file (it went from under running Windows) - well, okay, the killed Boot folder is enough for the recovery tools to think that everything is bad, and finally did their own case.
  8. We go further:
    bcdboot e:\windows /s e:
    (On e: I ended up with a partition with a broken system).
    bootrec /fixmbr
    bootrec /fixboot
  9. Reboot and restore G2D if needed. In my case, this was enough.

Thanks, BupycNet, for the link, I followed it before the question on Habré, I thought there were more convenient ways.

A
Andrey Tretyakov, 2011-12-16
@inscriptor

Try to get an installation disk (or a flash drive - depending on what you installed it from), and select System Restore there, and then according to the circumstances (described, for example, here and here ).
To return the Win7 loader, it is important to find exactly its installation disk.
I myself put 8 a certain time ago, then I decided to delete it. I thought that she had an identical bootloader with win8, and used the one from 8-rki - unsuccessfully. Then I realized that they are different, took a disk with win7 - and everything was restored.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question