Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Repair F8 Repair Your Computer Option


11 Aug 2012   #1

Windows 7 Home Premium 64 Bit
 
 
Repair F8 Repair Your Computer Option

I need help repairing my F8 Repair Your Computer function. It's not working. It just boots directly into Windows 7. Running Acer eRecovery once booted also doesn't work. It just simply reboots. Alt+F10 also doesn't work. So, I can't run a factory restore. I'v gathered that the information I need is:


Code:
 
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
 
C:\windows\system32>bcdedit /enum all
 
Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=\Device\HarddiskVolume1
description Windows Boot Manager
locale en-us
inherit {globalsettings}
default {current}
resumeobject {8803457e-dcd0-11e1-bb52-dd1735160394}
displayorder {current}
toolsdisplayorder {memdiag}
timeout 30
 
Windows Boot Loader
-------------------
identifier {88034578-dcd0-11e1-bb52-dd1735160394}
device ramdisk=[C:]\Recovery\853ec2c3-d0d3-11e1-9392-e53aceb99e
c0\Winre.wim,{88034579-dcd0-11e1-bb52-dd1735160394}
path \windows\system32\winload.exe
description Windows Recovery Environment (recovered)
locale
osdevice ramdisk=[C:]\Recovery\853ec2c3-d0d3-11e1-9392-e53aceb99e
c0\Winre.wim,{88034579-dcd0-11e1-bb52-dd1735160394}
systemroot \windows
winpe Yes
 
Windows Boot Loader
-------------------
identifier {8803457a-dcd0-11e1-bb52-dd1735160394}
device ramdisk=[C:]\Recovery\8803457a-dcd0-11e1-bb52-dd17351603
94\Winre.wim,{8803457b-dcd0-11e1-bb52-dd1735160394}
path \windows\system32\winload.exe
description Windows Recovery Environment
inherit {bootloadersettings}
osdevice ramdisk=[C:]\Recovery\8803457a-dcd0-11e1-bb52-dd17351603
94\Winre.wim,{8803457b-dcd0-11e1-bb52-dd1735160394}
systemroot \windows
nx OptIn
winpe Yes
 
Windows Boot Loader
-------------------
identifier {8803457c-dcd0-11e1-bb52-dd1735160394}
device ramdisk=[C:]\Recovery\0e18341f-e344-11e1-8661-ce906dfc6f
91\Winre.wim,{8803457d-dcd0-11e1-bb52-dd1735160394}
path \windows\system32\winload.exe
description Windows Recovery Environment (recovered)
locale
osdevice ramdisk=[C:]\Recovery\0e18341f-e344-11e1-8661-ce906dfc6f
91\Winre.wim,{8803457d-dcd0-11e1-bb52-dd1735160394}
systemroot \windows
winpe Yes
 
Windows Boot Loader
-------------------
identifier {current}
device partition=C:
path \windows\system32\winload.exe
description Windows 7
locale en-us
inherit {bootloadersettings}
recoverysequence {0e18341f-e344-11e1-8661-ce906dfc6f91}
recoveryenabled Yes
osdevice partition=C:
systemroot \windows
resumeobject {8803457e-dcd0-11e1-bb52-dd1735160394}
nx OptIn
detecthal Yes
 
Resume from Hibernate
---------------------
identifier {8803457e-dcd0-11e1-bb52-dd1735160394}
device partition=C:
path \windows\system32\winresume.exe
description Windows Resume Application
locale en-us
inherit {resumeloadersettings}
filedevice partition=C:
filepath \hiberfil.sys
debugoptionenabled No
 
Windows Memory Tester
---------------------
identifier {memdiag}
device partition=\Device\HarddiskVolume1
path \boot\memtest.exe
description Windows Memory Diagnostic
locale en-us
inherit {globalsettings}
badmemoryaccess Yes
 
EMS Settings
------------
identifier {emssettings}
bootems Yes
 
Debugger Settings
-----------------
identifier {dbgsettings}
debugtype Serial
debugport 1
baudrate 115200
 
RAM Defects
-----------
identifier {badmemory}
 
Global Settings
---------------
identifier {globalsettings}
inherit {dbgsettings}
{emssettings}
{badmemory}
 
Boot Loader Settings
--------------------
identifier {bootloadersettings}
inherit {globalsettings}
{hypervisorsettings}
 
Hypervisor Settings
-------------------
identifier {hypervisorsettings}
hypervisordebugtype Serial
hypervisordebugport 1
hypervisorbaudrate 115200
 
Resume Loader Settings
----------------------
identifier {resumeloadersettings}
inherit {globalsettings}
 
Device options
--------------
identifier {88034579-dcd0-11e1-bb52-dd1735160394}
ramdisksdidevice partition=C:
ramdisksdipath \Recovery\853ec2c3-d0d3-11e1-9392-e53aceb99ec0\boot.sdi
 
Device options
--------------
identifier {8803457b-dcd0-11e1-bb52-dd1735160394}
description Ramdisk Options
ramdisksdidevice partition=C:
ramdisksdipath \Recovery\8803457a-dcd0-11e1-bb52-dd1735160394\boot.sdi
 
Device options
--------------
identifier {8803457d-dcd0-11e1-bb52-dd1735160394}
ramdisksdidevice partition=C:
ramdisksdipath \Recovery\0e18341f-e344-11e1-8661-ce906dfc6f91\boot.sdi
 
C:\windows\system32>

& the name of the folder in the Recovery folder is:

0e18341f-e344-11e1-8661-ce906dfc6f91

I didn't delete or merge/move any partitions. I had a dual boot with Ubuntu recently but, I've since deleted that & restored MBR. I also restored the Boot & BCD as other posts & forums suggested. I'm not sure if those were necessary because my Windows 7 is booting just fine. The issue is that I can't seem to get to the Recovery partition.

I don't want to try referencing others fixes & trying my own. I want to know exactly how to do it correctly. As always any help will be greatly appreciated.


My System SpecsSystem Spec
.

12 Aug 2012   #2
Microsoft MVP

 

You're lucky this is all the corruption GRUB caused since we see cases where it makes Windows 7 irreparable.

You can try to restore System Recovery Options to F8 Advanced Boot Options by running Startup Repair from the installer or System Repair Disk up to 3 separate times with reboots in between each which is how it would normally be restored. However it may not work if the MBR has been corrupted.

If you'll post back a screenshot of your maximized Disk Mgmt drive map with listings, using the Snipping Tool in Start Menu, we can see if anything is obvious.

If you have a System Reserved partition you can try moving the Active flag to C before running the 3 Repairs to see if it will allow it to correctly rewrite WinRE to F8 as it should. I have also been able to do this by deleting and then recreating (NTFS Primary Active) System Reserved partition to write the boot files upon using the 3 Repair method.

None of this will restore the Acer eRecovery link which must have its hotlink restored, explained more here: Dell Recovery Partition - restoring F8 link
Link WinRE to F8 Advanced Boot Tools menu
Our expert SIW2 might be able to help you more with that.

You can also use the Acer Recovery disks you made at setup or order from Acer tech support to completely restore the computer to factory condition including all of the links.

However most tech enthusiasts don't want the bloated factory pre-install so you could also opt to get the superior Clean Reinstall - Factory OEM Windows 7- everything you need is in the blue link. If you choose this option I'd wipe the HD first of GRUB using Diskpart Clean Command.
My System SpecsSystem Spec
12 Aug 2012   #3

Windows 7 Home Premium 64 Bit
 
 

I'll try the System Recovery method first but, how do I set C: as active on a 64-bit system?


Attached Thumbnails
Repair F8 Repair Your Computer Option-disk-management-capture.jpg  
My System SpecsSystem Spec
.


12 Aug 2012   #4
Microsoft MVP

 

The screenshot is not encouraging. There is no System flag on any partition which means we dont' know where the System boot files are located.

It's possible they are on Recovery since it's marked Active signaling where the System boot files should be written, but when this is done it is to enable Recovery to run from boot and you said it doesn't. And they wouldn't have made the System Reserved partition unless it was to be System Active so it looks like the Active flag has been moved.

I think you've lost use of the Recovery partition and OEM partition anyway so I'd strongly consider wiping the drive to assure GRUB is gone and either running Recovery disks or Clean Reinstalling.

Otherwise you can mark the System Reserved partition Active and run three Startup Repairs to see if it will restore F8 Advanced Boot Options. Even if it works the first two partitions on the prime real estate of the HD (with fastest reads/writes) are now useless and would best be deleted and resized into by the remaining two, unless you decide to Recover or Reinstall. Mark Partition Active

Where had you installed Ubuntu, which appears to have messed this up badly?
My System SpecsSystem Spec
12 Aug 2012   #5

Windows 7 Home Premium 64 Bit
 
 

Check out this screenshot. Does this change anything?

I do have a Windows 7 installation disc. What are my options with that?

I've decided to wait to do anything until you say so.
My System SpecsSystem Spec
12 Aug 2012   #6
Microsoft MVP

 

What screenshot?

You can use the disk for repairs or Clean Reinstall - Factory OEM Windows 7.
Make sure it has SP1 or the latest is in Step 1.

We will help you get a perfect one.
My System SpecsSystem Spec
12 Aug 2012   #7

Windows 7 Home Premium 64 Bit
 
 

Sadly, I can't make any restore discs...& wouldn't this option render the Recovery partition unusable?
My System SpecsSystem Spec
12 Aug 2012   #8
Microsoft MVP

 

If Recovery won't run and won't generate Recovery disks then it is useless anyway. Try both again. Restoring the System Boot files to it would not also repair it, just place them on a useless partition you're best to Delete and recover into the other two Partitions.

Same with OEM partition which just stores a bunch of drivers with newer versions on the Acer Support Downloads webpage for your model.
My System SpecsSystem Spec
12 Aug 2012   #9

Windows 7 Home Premium 64 Bit
 
 

Well I can't make Recovery discs because I don't have any discs to burn it to lol. I'm sure I can make Recovery discs if I had discs... Should I just wait to get some discs?
My System SpecsSystem Spec
12 Aug 2012   #10
Microsoft MVP

 

If you can make Recovery Disks successfully it means the partition is still operable. SIW2 might be able to help you restore its hotlink as he knows the codes. Contact him through his posts in the links by clicking his Username.

However I'm certain Recovery should not be marked Active since there is a 200mb System Reserved partition which is only present if it is used as the System Active partition containing the boot files. So you can go ahead and restore its Active flag and run the 3 repairs to see if it will restore F8 Tools.

You never replied where you had Linux installed. When you removed it did you have to repair Windows 7 to get it to boot? Is this how the Active flag got planted on recovery?
My System SpecsSystem Spec
Reply

 Repair F8 Repair Your Computer Option




Thread Tools




Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 11:48 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33