When attempt to install SP1, installer crashes and show error

CODE
http://windows.microsoft.com/en-US/windows7/windows-7-windows-server-2008-r2-service-pack-1-sp1-installation-error-0x800F0A12
I think this is a problem caused by the first invisible partition. Unseen by the system created by Windows7 when you install on a blank disk.
How do install SP1 without a reinstall Win7? This post has been edited by Marucins: Mar 4 2011, 07:03 AM
QUOTE (Marucins @ Mar 4 2011, 08:01 AM)

When attempt to install SP1, installer crashes and show error

CODE
http://windows.microsoft.com/en-US/windows7/windows-7-windows-server-2008-r2-service-pack-1-sp1-installation-error-0x800F0A12
I think this is a problem caused by the first invisible partition. Unseen by the system created by Windows7 when you install on a blank disk.
How do install SP1 without a reinstall Win7?not sure if this is possible.
1st of all it might be bugged w7 by itself
2nd bugged sp1, try to redownload
3rd try to install w7 with ingegrated sp1, there are alot of different distros on internets
QUOTE (Marucins @ Mar 4 2011, 11:01 AM)

When attempt to install SP1, installer crashes and show error
I think this is a problem caused by the first invisible partition. Unseen by the system created by Windows7 when you install on a blank disk.
How do install SP1 without a reinstall Win7?
Is it related to OSX?
I previously had a problem to have MacOSX and Windows 7 on the same drive. First invisible 200Mb partition 0xEF conflict with Win7. I changed signature to 0xDA.
Now both systems works.
Weird, I've been using windows 7 for long on my hybrid disk (shared with time machine) without problem, I also updated it to SP1.
i had this problem when i tried installing win7 to the second hard drive. (the first hd had just snow on it). the "fix" was to unplug/disconnect the first harddrive and the installation went fine after that. its got something to do with the win7 installer tryin to create that system partition on the first harddrive all the time.
This also happens if you boot Windows 7 with Chameleon, you will not be able to sleep/hibernate or install SP1.
Work is underway over here to fix this issue:
http://forum.voodooprojects.org/index.php/topic,2091.0.html
If your BIOS supports UEFI you can activate it.
If you are using UEFI, you don't need Hybrid MBR(windows 7 works with GUID natively).
Windows 7 has been installed at GUID without Hybrid MBR by me. I used only UEFI.
P.S. I know English not wery well
QUOTE (dominatornsk @ Jan 26 2012, 07:14 PM)

If your BIOS supports UEFI you can activate it.
If you are using UEFI, you don't need Hybrid MBR(windows 7 works with GUID natively).
Windows 7 has been installed at GUID without Hybrid MBR by me. I used only UEFI.
P.S. I know English not wery well
No, only Windows 7-x64 is able to work with UEFI and on GUID partitions.
For Windows 7-ia32 you have to do MBR partitions.
And Win7 x64 UEFI boot works only from pure GPT disk. It does not like hybrid.
That makes it hard to have same win install that can be booted with UEFI and/or MBR. At least I was not able to do it. Requires adding/removing hybrid MBR when switching boot method.
QUOTE (dmazar @ Jan 30 2012, 06:18 PM)

And Win7 x64 UEFI boot works only from pure GPT disk. It does not like hybrid.
That makes it hard to have same win install that can be booted with UEFI and/or MBR. At least I was not able to do it. Requires adding/removing hybrid MBR when switching boot method.
Change the EFI partition signature 0xEF <-> 0xDA in a bootloader before started Win?
Tried it again - managed to boot Win from UEFI only from pure GPT disk. As soon as it is made hybrid (anything except one standard protective MBR partition) - windows consider it MBR disk and UEFI boot is not possible. At least, I was not able to boot it - my knowledge here is limited.
So, switching between BIOS/UEFI boot for Win requires installation on GPT disk and changing MBR. At least I learned something about win recovery, bcdedit, bcdboot, bootrec, diskpart and stuff.
On a GPT disk microsoft requires a MSR partition directly before the first Windows data partition, this partition has an opaque filesystem and can't be accessed or at least I've never seen or found a way. I think microsoft intended it that way so they could use it as the core for secure booting TPM. This is where the windows boot manager resides. On an MBR disk it resides on either the System Reserved or the Windows partition itself, both of which have transparent filesystems. It may be possible to move the boot manager from a MBR installation to the data partition itself as if it was originally installed there, I haven't tried. But if I try to boot a GPT installed Windows from MBR I always get the Windows is loading files bar across the bottom and then the Windows logo appears, disappears and tells me it couldn't continue to boot because of some error that I'm too lazy to look up since I have it running much faster and better in UEFI anyway.... I just stumbled upon this because I used disk utility in OS X to create a partition and it converted my disk to hybrid MBR. haha, dumb.