Boot into "recovery environment" from CD or DVD. Can you select a "windows installation" now or can't it find one? if it does find one, select it and press OK (or next, i don't know)
Now select "command prompt" form this menu http://blogs.technet.com/blogfiles/d...umb%5B3%5D.jpg
BOOTREC /FIXMBR
BOOTREC /FIXBOOT
commands complete without errors?
DIR C:\ do you see windows partition?
reboot normally so without dvd. post results
Sorry I didn't see your message...
Now that it seems okay (cf edit of my last post), do you still want me to do that?
"last good known configuration".=> I don't know what it exactly does. It was better if you ust did "system restore" to fix it and go back 1 or 2 days.
But it's working now? So you have windows bootmanager instead of grub as main manager?
How did you add linux to windows bootmenu ...
bcdedit /create /d “Linux” /application BOOTSECTOR
or was it already there (sounds impossible if you didn't have win7 bootmanager before)
linux is working as well?
forget the post about bootrec/fixmbr and fixboot
How to start your computer by using the Last Known Good Configuration feature in Windows XP although it's for winxp .. in win7 it's the same. It's used in case of driver problems. It has nothing to do with firefox problems. Anymore problems yet?
Why did you do "last known good configuration"? What was the error message .. I assume you did it because of an error.
Can you post output from elevated command prompt in win7:
bcdedit /enum all
Well no it's still grub boot manager, but at least both windows and linux start...
Is it possible to switch to windows bootmanager without any risk, knowing that I don't want to reinstall linux... Because if I do the commands you posted at the top of page #2, how will this remove grub?
I mean, I understand that it can add linux to windows bootloader, but after that, I don't know too well what I should do, and wouldn't risk having big troubles again (I haven't much "free time" these days). I saw in the link posted by gregrocker that we should start from a windows install, so I'll use this method next time I'll set up a machine, but for now, is there any other way?
Edit: Well I don't know, after the second run of reparation (which takes a lot of time), instead of saying it found nothing like the first time, it proposed to restore to a preivous configuration (I can't remember the exact terms), I just clicked yes.
I'm posting the output of the command in a few minutes...
Last edited by silverangel; 30 Nov 2011 at 10:14. Reason: new message arrived
So here it is (it's in French ;-) )
Code:Microsoft Windows [version 6.1.7601] Copyright (c) 2009 Microsoft Corporation. Tous droits réservés. C:\Windows\system32>bcdedit /enum all Gestionnaire de démarrage Windows --------------------------------- identificateur {bootmgr} device boot description Windows Boot Manager locale fr-FR inherit {globalsettings} default {current} resumeobject {8cb2d9b0-7c05-11de-842e-b4611d44fefa} displayorder {current} toolsdisplayorder {memdiag} timeout 30 Chargeur de démarrage Windows ----------------------------- identificateur {572bcd56-ffa7-11d9-aae0-0007e994107d} device ramdisk=[\Device\HarddiskVolume1]\winre.wim,{ad6c7bc8-fa 0f-11da-8ddf-0013200354d8} path \windows\system32\boot\winload.exe description Windows Recovery Environment osdevice ramdisk=[\Device\HarddiskVolume1]\winre.wim,{ad6c7bc8-fa 0f-11da-8ddf-0013200354d8} systemroot \windows nx OptIn detecthal Yes winpe Yes Chargeur de démarrage Windows ----------------------------- identificateur {current} device boot path \Windows\system32\winload.exe description Windows 7 locale fr-FR inherit {bootloadersettings} recoverysequence {8cb2d9b4-7c05-11de-842e-b4611d44fefa} recoveryenabled Yes osdevice boot systemroot \Windows resumeobject {8cb2d9b0-7c05-11de-842e-b4611d44fefa} nx OptIn Chargeur de démarrage Windows ----------------------------- identificateur {8cb2d9b4-7c05-11de-842e-b4611d44fefa} device ramdisk=[C:]\Recovery\8cb2d9b4-7c05-11de-842e-b4611d44fe fa\Winre.wim,{8cb2d9b5-7c05-11de-842e-b4611d44fefa} path \windows\system32\winload.exe description Windows Recovery Environment inherit {bootloadersettings} osdevice ramdisk=[C:]\Recovery\8cb2d9b4-7c05-11de-842e-b4611d44fe fa\Winre.wim,{8cb2d9b5-7c05-11de-842e-b4611d44fefa} systemroot \windows nx OptIn winpe Yes Reprendre à partir de la mise en veille prolongée ------------------------------------------------- identificateur {8cb2d9b0-7c05-11de-842e-b4611d44fefa} device boot path \Windows\system32\winresume.exe description Windows Resume Application locale fr-FR inherit {resumeloadersettings} filedevice partition=C: filepath \hiberfil.sys debugoptionenabled No Testeur de mémoire Windows -------------------------- identificateur {memdiag} device partition=C: path \boot\memtest.exe description Windows Memory Diagnostic locale fr-FR inherit {globalsettings} badmemoryaccess Yes Paramètres EMS -------------- identificateur {emssettings} bootems Yes Paramètres du débogueur ----------------------- identificateur {dbgsettings} debugtype Serial debugport 1 baudrate 115200 Erreurs de mémoire RAM ---------------------- identificateur {badmemory} Paramètres globaux ------------------ identificateur {globalsettings} inherit {dbgsettings} {emssettings} {badmemory} Paramètres du chargeur de démarrage ----------------------------------- identificateur {bootloadersettings} inherit {globalsettings} {hypervisorsettings} Paramètres de l'hyperviseur ------------------- identificateur {hypervisorsettings} hypervisordebugtype Serial hypervisordebugport 1 hypervisorbaudrate 115200 Paramètres du chargeur de reprise --------------------------------- identificateur {resumeloadersettings} inherit {globalsettings} Options de périphérique ----------------------- identificateur {8cb2d9b5-7c05-11de-842e-b4611d44fefa} description Ramdisk Options ramdisksdidevice partition=C: ramdisksdipath \Recovery\8cb2d9b4-7c05-11de-842e-b4611d44fefa\boot.sdi Options de périphérique ----------------------- identificateur {ad6c7bc8-fa0f-11da-8ddf-0013200354d8} description Ramdisk Device Options ramdisksdidevice partition=\Device\HarddiskVolume1 ramdisksdipath \boot.sdi C:\Windows\system32>
Chargeur de démarrage Windows
-----------------------------
identificateur {572bcd56-ffa7-11d9-aae0-0007e994107d}
device ramdisk=[\Device\HarddiskVolume1]\winre.wim,{ad6c7bc8-fa
0f-11da-8ddf-0013200354d8}
path \windows\system32\boot\winload.exe
description Windows Recovery Environment
osdevice ramdisk=[\Device\HarddiskVolume1]\winre.wim,{ad6c7bc8-fa
0f-11da-8ddf-0013200354d8}
systemroot \windows
nx OptIn
detecthal Yes
winpe Yes
===============
I don't know how it comes here but I think C:\winre.wim doesn't exist!! it's a hidden system file. And \windows\system32\boot\winload.exe isn't in it as well it should be \windows\system32\winload.exe
Please confirm if C:\winre.wim is on disk or not
I don't know either what it did of course. Next time read carefully.
What I think confiuration is now:
What do you want me to do?
- You didn't fix MBR. MBR has code loaded and jumps to linux partition. There's teh grub menu
- grub menu has 2 options 1 for 1 linux and 1 for win7 if you select win7 it starts C:\bootmgr which displays C:\boot\bcd (bcdedit /enum all gives you the content)
??
- make windows bootmgr the main bootloader and at linux as a menu item
I did not see these files in C: after activating the hidden and system files.
When trying to click on the recovery folder, I get an error message saying it is not accessible.
Edit: well this is out of my knowledge, I cannot say if something is wrong as long as everything seems to work normally.
As for your proposition, yes, if that's not too hard, and besides that I don't know since I don't have visible troubles at the moment.
Quote