W7 only boots after installation disk timeout

hcra

New member
Local time
5:32 AM
Messages
1
Hello. I have a Z77 mobo with a new SDD and a HDD from the old PC. At first I installed W7 to the SDD and I could only boot into it when I disconnected the HDD. When I started PC, the logo was shown for a second or so, and then it went into repair mode, the "preparing installation files" progress bar ran twice and the system booted into GRUB that was left on the HDD. I've tinkered in BIOS a lot trying to fix this, but to no avail.

Now I've decided to also install Linux (OpenSUSE 12.2) to the SDD, and hoped that GRUB2 would solve my problems. Nope, it didn't detect my W7 at all! (however, it did detect the two(?) old W7 mount points from the HDD). I couldn't even get to boot it by forcing "Windows Boot Manager" from BIOS. I tried to fix this with DVD repair, at first I couldn't get it to work by launching the DVD in UEFI mode, the other one worked, but it only messed up my GRUB2 and I couldn't boot to either system. After some unsuccesful tinkering with bootrec, I found this thread and followed what OP and the best answer guy did, which sums up roughly to this:
Code:
C:\> bootsect /nt60 C: /force
C:\> diskpart
DISKPART> select disk 1
DISKPART> select partition 3
DISKPART> active
DISKPART> extend filesystem
DISKPART> exit
C:\> bootrec /rebuildbcd
Then, Windows Repair detected my installation and said it fixed the problem. Now I still can't boot into my system normally (again, it reboots after "Windows is loading files"), however, I can get it to boot after the timeout ("Press any key to boot from DVD") from W7 installation disk! I have no idea what's going on.
Here is a screenshot from diskmgmt:

The strange thing is the 128MB partition - I suppose this could have been MSR partition, while gparted shows it's a Linux partition! Is this possible, that OpenSUSE installer messed it up?
Any help would be greatly appreciated!

Also:
Code:
C:\Windows\system32>bcdedit /v

Windows Boot Manager
--------------------
identifier              {9dea862c-5cdd-4e70-acc1-f32b344d4795}
device                  partition=C:
path                    \bootmgr
description             Windows Boot Manager
locale                  en-US
default                 {a2d81753-0084-11e2-876a-e3fdd9956fab}
displayorder            {a2d81753-0084-11e2-876a-e3fdd9956fab}
timeout                 30

Windows Boot Loader
-------------------
identifier              {a2d81753-0084-11e2-876a-e3fdd9956fab}
device                  partition=C:
path                    \Windows\system32\winload.exe
description             Windows 7 Professional
locale                  en-US
osdevice                partition=C:
systemroot              \Windows
resumeobject            {41181bc9-0032-11e2-aed6-806e6f6e6963}
 

My Computer

OS
Windows 7 Professional x64

My Computer

Computer Manufacturer/Model Number
Insane hobo technologies. ;-)
OS
Windows 7 x64
CPU
Intel i7 2600k
Motherboard
Asrock z68 extreme 4 gen 3
Memory
G.skill Ripjaw 16gigs @ 1866
Graphics Card(s)
Nvidia gtx580 (evga)
Sound Card
Integrated HD audio + hdmi
Monitor(s) Displays
24" ASUS widescreen + 42" insignia
Screen Resolution
1080p (1920x1080)
Hard Drives
128 Samsung 830
256 Samsung 840
3 x 1tb storage drive (various)
1 western digital 1tb (eSATA)
1 Seagate 1tb (eSATA)
PSU
1 kilowatt SLI/Crossfire rated Silverstone modular
Case
NZXT Phantom + additional 220 fan
Cooling
Zalmann
Keyboard
Microsoft wireless 3000 (v2)
Mouse
MS - wireless 5000 (bluetrack)
Internet Speed
depends on if you ask me or my provider.
Other Info
The above information is provided as is, and the author assumes no responsibility for issues it may cause with your sanity or fanboyism.
Your apparentlly have an EFI BIOS which installs Win7 to a GPT disk, however it seems like it has been reformatted to an MBR disk so that C has had written to it the System BOot files which in a GPT disk occupy those first two partitions.

To make sure rightclick on the small panel to the left of the drive map which says Disk0. Does it offer to convert to an MBR or a GPT disk. That will tell you which it is now.

If it's an MBR disk you should have wiped the GPT protective partitioning before repairing or installing. I would immediately back up my data to wipe the HD with Diskpart Clean Command then follow these steps to get a perfect Clean Reinstall - Factory OEM Windows 7.

If it's still a GPT disk then first you need to study and understand how these function with an EFI BIOS because it is new-generation and requires different steps for install as well as repair. You can confirm an EFI BIOS by looking for EFI Boot Disk in the BIOS setup boot order listings:
The 30-year-long Reign of BIOS is Over: Why UEFI W... - Input Output
Technical Note: UEFI BIOS vs. Legacy BIOS - YouTube
Installing Windows 7 on UEFI based computer - Ask the Core Team - Site Home - TechNet Blogs
Installing Windows 7 in native EFI mode from USB - bit-tech.net Forums
UEFI (Unified Extensible Firmware Interface) - Install Windows 7 with - Windows 7 Forums Installing Windows to an EFI-Based Computer
 
Back
Top