Maybe anyone knows
Bye and have a nice week-end!
Edited by Schiiwa, 21 October 2011 - 03:22 AM.
Jump to content
Edited by Schiiwa, 21 October 2011 - 03:22 AM.
Im asking myself if it would have been possible to install the WIM with windows-setup (without answer-file), if I had set a /FLAG when i took the capture!???
- exchanged the WinRE.wim - removed the letter and set ID to 27 (on partition 4 )I have the reasonable suspicion, that I can´t avoid a Re-Install
Edited by Schiiwa, 24 October 2011 - 08:38 AM.
What version of Windows 7 are you using?
C:\Windows\system32>reagentc /info Erweiterte Konfiguration für die Wiederherstellungsumgebung Windows RE aktiviert: 1 Windows RE bereitgestellt: 1 Setup aktiviert: 1 Benutzerdefiniertes Wiederherstellungstool: 1 WinRE.WIM-Verzeichnis: Wiederherstellungsumgebung: BCD-ID: fbf3595f-fce2-11e0-811f-a6936763aab2 Setupdateien: Wiederherstellungsvorgang: 4 Vorgangsparameter: Boot Startschlüssel-Abfragecode 0x8500 REAGENTC.EXE: Vorgang erfolgreich ausgeführt
C:\Windows\System32\Recovery\ReAgent.xml C:\Recovery\System32\Recovery\ReAgent.xml Z:\Recovery\System32\Recovery\ReAgent.xml
C:\Windows\system32>reagentc /enable REAGENTC.EXE: Vorgang fehlgeschlagen: 57 C:\Windows\system32>reagentc /disable REAGENTC.EXE: Vorgang fehlgeschlagen: 2 Das System kann die angegebene Datei nicht finden. C:\Windows\system32>reagentc /setreimage /path Z:\Recovery\Winre\Winre.wim /target C:\Windows REAGENTC.EXE: Vorgang fehlgeschlagen: b7 Eine Datei kann nicht erstellt werden, wenn sie bereits vorhanden ist.
Edited by Schiiwa, 24 October 2011 - 09:26 AM.
It gets the information from the BCD. If you type BCDEdit into your command prompt, you will see the data. Here is an example I had from previous troubleshooting.
Edited by Schiiwa, 24 October 2011 - 01:42 PM.
Edited by Schiiwa, 24 October 2011 - 07:11 PM.
but i can't set back the "already made recoveries" to 0! REAGENTC /INFO still says Wiederherstellungsvorgang: 4! Any other value can be changed through ReAgent.xml (for example <OemTool state="0"/>, wich will have affect on the output of "reagentc /info")
If i set <ScheduledOperation state="4"/> to 0, reagent won´t accept it (doesn´t matter whether i do that with enabled or disagled reagent) and if i disable or enable it, it is set to 4 again
So how can i set it back again to 0? it's not dokumented anywere and i'm pretty sure, that reagentc /info doesn't take this Information from BCD
You don´t have to
I can't do a recovery test on this system because I need it for other things atm.
I wonder if that BCD Id ever changes after a recovery... but its obvious that Sysprep makes some changes once it goes into oobeSystem pass.
bootsect /mbr bootrec /fixboot bootrec /fixmbr bootrec /rebuild bcdTWICE
Edited by Schiiwa, 28 October 2011 - 06:37 AM.
Also I don't like reagent very much, because it puts the winre.wim in this nasty GUID-subdir Just use it, to have the bootkey-option, because it uses 2 lines in BCD and i don't know how to create it manually!
Edited by Schiiwa, 04 December 2011 - 07:26 PM.
If used as intended, the recovery partition is hidden by default. It can only be made active by selecting the option in the Windows boot menu. If you have removed Windows, you can't access the boot menu to do this. You'd need to boot into a PE of some sort and use diskpart to unhide and make the recovery partition active.
Edited by Schiiwa, 05 December 2011 - 01:16 PM.
Vista and 7 used slightly different boot methods to get to their WinRE. I find this great because Vista was a pain to do compared to 7.
Anyways, the System Reserved partition may not be 100% required, but since creating it with a recovery partition is required (for support purposes) I never tried to deploy it without one. But yes, the SR partition is marked as active. The order should be:
1. System Reserved
The reason why it boots into Windows and not WinRE each time is because the WinRE partition is marked as a hidden boot volume. So in this case, the BIOS of a computer picks the first available boot volume, the one with Windows on it because it can't see the WinRE partition.
The reason to put the recovery partition first, or the service partition even back in XP days at the beginning of the disk did have some sort of reason for it. I forgot it by now. But you can definately have a recovery partition after the OS volume, for example I always installed the SoftThinks recovery partition (for XP) at the end of the disk just because it was easier to do, and they didn't seem to care what partition it was when dealing with support issues.
It would appear that none of my Microsoft documentation talks about the relevance of the location of the recovery partition.
Question1: (don´t think this will work)
Gremo used the 1st partition as active as u can see here:
Is ist possible to set it active without booting in loops to winre?? Or is it just active because he booted to winre (thats what i expect, as he start with: "I'm booting into WinRE from and hidden partition."
Question2: (should work because the new active part. would be the Sys.-Res. and not the windows one!?)
Do you think when i use your suggestion to include a Sys.-Res.-Partition, will it be bootable without Windows-Partition and WITHOUT winpe to set it active manually?
There it says: "To back up and to restore the Windows RE partition, the partition must not be hidden."
so i should set the ID to 7 before capturing or applying the recovery-partition-image?? (i want to include this, to do the recovery from DVD in case of HDD-replacement)
1. It was marked active during install/deployment. Basically how the recovery partition works is that it is hidden. If you want to boot into it, you need to send a command that unhides it and sets it as the first boot volume. The trick is that after doing your work in WinRE, that a script or program runs to hide the partition again. ID changes to partitions do not take immediate effect, as the BIOS only reads the partition IDs during POST.
2. If you want a scenario where you have:
- System Reserved (active)
- WinRE (hidden)
- Blank partition
You will need some sort of BIOS level software to handle unhiding the partition and allow booting into it, since Windows isn't there to handle the boot request. I used the MBR.EXE program from Terabyte Unlimited in this old project:
Additional: Yes well the public MS documentation is hard to figure out sometimes I'd agree. Basically it is telling you it can't be hidden because if it is, you won't be able to capture it with the supported tools. Sector based imaging software such as Acronis or Ghost can because they don't care if it is hidden or not.
Edited by Schiiwa, 09 December 2011 - 04:19 PM.
- this cannot be 100% true, because when i format OS-Partition, it also boots to winre without any windows-tools! Just when i remove the partition, winre is un/inaccessable... Why is windows that stupid!!!
- I just removed the OS-partition for testing...
- Taking the MBR.EXE won't help me, as the WinRE is already the active partition!
The attachment is the DISKPART script i used for the last configuration! Really strange that BOOTMGR or BCD insist on the Windows-partition and deny if not presend°
0 members, 0 guests, 0 anonymous users