I'm trying to add IFW to winre.wim using TBWinRE. I found that I didn't have a winre.wim, so I made one using Windows AIK, and it is in C:\Recovery\WindowsRE. I created a winpeshl.ini file in C:\Windows\System32 following the Windows AIK guide, "[LaunchApp] AppPath=x:\sources\recovery\recenv.exe". I added my winre.wim to the BCD Store, and booted into it and it works just as it should.
The problem is that when I run TBWinRE.cmd option 1, I get the error message, "A "recoverysequence" GUID for the currently booted Windows was not found or is invalid." I have edited the TBWinRE.cmd file for the correct path for IFW, TBIView and TBOSDT, and that's it.
Where do I go from here?
TBWinRE difficulties
-
TeraByte Support
- Posts: 3629
- Joined: Thu May 05, 2011 10:37 pm
Re: TBWinRE difficulties
instead of using TBWinRE, if using the AIK, create a WinPE boot disk - see
http://www.terabyteunlimited.com/howto/#ifwwinpe
"bbearren" wrote in message news:4544@public.image...
I'm trying to add IFW to winre.wim using TBWinRE. I found that I didn't
have a winre.wim, so I made one using Windows AIK, and it is in
C:\Recovery\WindowsRE. I created a winpeshl.ini file in C:\Windows\System32
following the Windows AIK guide, "[LaunchApp]
AppPath=x:\sources\recovery\recenv.exe". I added my winre.wim to the BCD
Store, and booted into it and it works just as it should.
The problem is that when I run TBWinRE.cmd option 1, I get the error
message, "A "recoverysequence" GUID for the currently booted Windows was not
found or is invalid." I have edited the TBWinRE.cmd file for the correct
path for IFW, TBIView and TBOSDT, and that's it.
Where do I go from here?
http://www.terabyteunlimited.com/howto/#ifwwinpe
"bbearren" wrote in message news:4544@public.image...
I'm trying to add IFW to winre.wim using TBWinRE. I found that I didn't
have a winre.wim, so I made one using Windows AIK, and it is in
C:\Recovery\WindowsRE. I created a winpeshl.ini file in C:\Windows\System32
following the Windows AIK guide, "[LaunchApp]
AppPath=x:\sources\recovery\recenv.exe". I added my winre.wim to the BCD
Store, and booted into it and it works just as it should.
The problem is that when I run TBWinRE.cmd option 1, I get the error
message, "A "recoverysequence" GUID for the currently booted Windows was not
found or is invalid." I have edited the TBWinRE.cmd file for the correct
path for IFW, TBIView and TBOSDT, and that's it.
Where do I go from here?
-
TeraByte Support(PP)
- Posts: 1646
- Joined: Fri Aug 12, 2011 12:51 am
Re: TBWinRE difficulties
Do you have the standard WinRE files in the "C:\Windows\System32\Recovery" folder? Usually, "ReAgent.xml" and "WinRE.wim" if not activated. It may be possible to activate WinRE normally and then the script should see it. If the files are there, you could run "reagentc /enable" from an Administrator Command Prompt to attempt to enable it.
Otherwise, to build with TBWinRE, place a copy of your winre.wim file into the "WinRE_Backup" folder in the "TBWinRE" folder (e.g. c:\tbwinre\winre_backup) and run the script using option #2. When it finishes, the boot.wim file in the "TBWinRE\ISO\sources" folder can be copied to replace your existing file (the one you manually setup to boot into) -- just rename to winre.wim.
Otherwise, to build with TBWinRE, place a copy of your winre.wim file into the "WinRE_Backup" folder in the "TBWinRE" folder (e.g. c:\tbwinre\winre_backup) and run the script using option #2. When it finishes, the boot.wim file in the "TBWinRE\ISO\sources" folder can be copied to replace your existing file (the one you manually setup to boot into) -- just rename to winre.wim.
Re: TBWinRE difficulties
I have an IFD boot disk, and I also have BootIt BM installed on my hard drive, so I can get to IFD from there, as well. I'm wanting the IFW option in the Windows Recovery Environment.
TeraByte Support wrote:
> instead of using TBWinRE, if using the AIK, create a WinPE boot disk - see
>
> http://www.terabyteunlimited.com/howto/#ifwwinpe
TeraByte Support wrote:
> instead of using TBWinRE, if using the AIK, create a WinPE boot disk - see
>
> http://www.terabyteunlimited.com/howto/#ifwwinpe
Re: TBWinRE difficulties
I tried both suggestions. After copying winre.wim to C:\Windows\System32\Recovery (ReAgent.xml was there) I ran reagentc /enable from an elevated command prompt, and it reported that it was successful.
However, running TBWinRE.cmd option 1 returns the following:
"Locating WinRE image...
WinRE Location:
[~0,-1]
The syntax of the command is incorrect."
So I tried the second suggestion, only I had to create a "WinRE_Backup" folder, because there wasn't one. When I ran TBWinRE.cmd option 2, I got the same error that I got with option 1. Also, there is no "TBWinRE\ISO\sources" folder, either.
My ReAgent.xml code might be part of my problem. Here it is:
<?xml version="1.0" encoding="UTF-8"?>
-<WindowsRE version="1.0">
<WinreBCD id="{cda73815-38b5-11e0-91c9-782bcb835a54}"/>
<WinreLocation id="2011426113" guid="{00000000-0000-0000-0000-000000000000}" offset="41943040" path="\Recovery\WindowsRE"/>
<ImageLocation id="2011426113" guid="{00000000-0000-0000-0000-000000000000}" offset="41943040" path="\recovery\windowsre"/>
<OsInstallLocation id="0" guid="{00000000-0000-0000-0000-000000000000}" offset="0" path=""/>
<InstallState state="1"/>
<OsInstallAvailable state="0"/>
<WinREStaged state="0"/>
<OperationParam path=""/>
<OsBuildVersion path="7600.20738.amd64fre.win7_ldr.100618-1621"/>
<OemTool state="0"/>
<BootKey state="0"/>
<IsServer state="0"/>
<ScheduledOperation state="4"/>
</WindowsRE>
Any ideas?
TeraByte Support(PP) wrote:
> Do you have the standard WinRE files in the
> "C:\Windows\System32\Recovery" folder? Usually,
> "ReAgent.xml" and "WinRE.wim" if not activated. It may
> be possible to activate WinRE normally and then the script should see it.
> If the files are there, you could run "reagentc /enable" from an
> Administrator Command Prompt to attempt to enable it.
>
> Otherwise, to build with TBWinRE, place a copy of your winre.wim file into
> the "WinRE_Backup" folder in the "TBWinRE" folder (e.g.
> c:\tbwinre\winre_backup) and run the script using option #2. When it
> finishes, the boot.wim file in the "TBWinRE\ISO\sources" folder
> can be copied to replace your existing file (the one you manually setup to
> boot into) -- just rename to winre.wim.
However, running TBWinRE.cmd option 1 returns the following:
"Locating WinRE image...
WinRE Location:
[~0,-1]
The syntax of the command is incorrect."
So I tried the second suggestion, only I had to create a "WinRE_Backup" folder, because there wasn't one. When I ran TBWinRE.cmd option 2, I got the same error that I got with option 1. Also, there is no "TBWinRE\ISO\sources" folder, either.
My ReAgent.xml code might be part of my problem. Here it is:
<?xml version="1.0" encoding="UTF-8"?>
-<WindowsRE version="1.0">
<WinreBCD id="{cda73815-38b5-11e0-91c9-782bcb835a54}"/>
<WinreLocation id="2011426113" guid="{00000000-0000-0000-0000-000000000000}" offset="41943040" path="\Recovery\WindowsRE"/>
<ImageLocation id="2011426113" guid="{00000000-0000-0000-0000-000000000000}" offset="41943040" path="\recovery\windowsre"/>
<OsInstallLocation id="0" guid="{00000000-0000-0000-0000-000000000000}" offset="0" path=""/>
<InstallState state="1"/>
<OsInstallAvailable state="0"/>
<WinREStaged state="0"/>
<OperationParam path=""/>
<OsBuildVersion path="7600.20738.amd64fre.win7_ldr.100618-1621"/>
<OemTool state="0"/>
<BootKey state="0"/>
<IsServer state="0"/>
<ScheduledOperation state="4"/>
</WindowsRE>
Any ideas?
TeraByte Support(PP) wrote:
> Do you have the standard WinRE files in the
> "C:\Windows\System32\Recovery" folder? Usually,
> "ReAgent.xml" and "WinRE.wim" if not activated. It may
> be possible to activate WinRE normally and then the script should see it.
> If the files are there, you could run "reagentc /enable" from an
> Administrator Command Prompt to attempt to enable it.
>
> Otherwise, to build with TBWinRE, place a copy of your winre.wim file into
> the "WinRE_Backup" folder in the "TBWinRE" folder (e.g.
> c:\tbwinre\winre_backup) and run the script using option #2. When it
> finishes, the boot.wim file in the "TBWinRE\ISO\sources" folder
> can be copied to replace your existing file (the one you manually setup to
> boot into) -- just rename to winre.wim.
-
TeraByte Support(PP)
- Posts: 1646
- Joined: Fri Aug 12, 2011 12:51 am
Re: TBWinRE difficulties
You shouldn't be getting the same error with options 1 & 2 unless it's still looking for the winre.wim file (not found in the backup folder or on the system). If it's not finding it in the backup folder I'd suspect something's not quite right with the path (or the file didn't get copied into the backup folder). Additionally, if the backup is found you should see option 3 as "Restore the original winre.wim file" instead of "Exit".
You haven't posted the exact path being used for the TBWinRE build so I don't know if it's custom or in the IFW folder (I assume you're using v1.3 of the script). Double-check that the WinRE_Backup folder exists in the folder with the TBWinRE.cmd script file and that the backup folder contains winre.wim. For example, if the TBWinRE build folder is C:\TBWinRE, the full path would be C:\TBWinRE\WinRE_Backup\winre.wim.
The TBWinRE\ISO folder won't exist until the build has completed (and it hasn't gotten that far yet).
Another thing you could try is disabling WinRE and then enabling it again. This will sometimes fix things. Make sure to save a copy of the winre.wim file somewhere first. Then run the following two commands:
reagentc /disable
reagentc /enable
(Note: Doing this may make changes to or replace your custom WinRE setup.)
--
If that still doesn't let it work, save the output of the BCD to a text file and attach it to a post so I can look at it. From an Administrator Command Prompt, run the following command:
bcdedit /enum all > c:\bcdoutput.txt
Then attach bcdoutput.txt to a post.
You haven't posted the exact path being used for the TBWinRE build so I don't know if it's custom or in the IFW folder (I assume you're using v1.3 of the script). Double-check that the WinRE_Backup folder exists in the folder with the TBWinRE.cmd script file and that the backup folder contains winre.wim. For example, if the TBWinRE build folder is C:\TBWinRE, the full path would be C:\TBWinRE\WinRE_Backup\winre.wim.
The TBWinRE\ISO folder won't exist until the build has completed (and it hasn't gotten that far yet).
Another thing you could try is disabling WinRE and then enabling it again. This will sometimes fix things. Make sure to save a copy of the winre.wim file somewhere first. Then run the following two commands:
reagentc /disable
reagentc /enable
(Note: Doing this may make changes to or replace your custom WinRE setup.)
--
If that still doesn't let it work, save the output of the BCD to a text file and attach it to a post so I can look at it. From an Administrator Command Prompt, run the following command:
bcdedit /enum all > c:\bcdoutput.txt
Then attach bcdoutput.txt to a post.
-
TeraByte Support
- Posts: 3629
- Joined: Thu May 05, 2011 10:37 pm
Re: TBWinRE difficulties
Are you using Windows 7 or 8?
"bbearren" wrote in message news:4558@public.image...
I have an IFD boot disk, and I also have BootIt BM installed on my hard
drive, so I can get to IFD from there, as well. I'm wanting the IFW option
in the Windows Recovery Environment.
TeraByte Support wrote:
> instead of using TBWinRE, if using the AIK, create a WinPE boot disk - see
>
>
[
http://www.terabyteunlimited.com/howto/#ifwwinpe
](http://www.terabyteunlimited.com/howto/#ifwwinpe)
"bbearren" wrote in message news:4558@public.image...
I have an IFD boot disk, and I also have BootIt BM installed on my hard
drive, so I can get to IFD from there, as well. I'm wanting the IFW option
in the Windows Recovery Environment.
TeraByte Support wrote:
> instead of using TBWinRE, if using the AIK, create a WinPE boot disk - see
>
>
[
http://www.terabyteunlimited.com/howto/#ifwwinpe
](http://www.terabyteunlimited.com/howto/#ifwwinpe)
Re: TBWinRE difficulties
Both. I'm dual booting 7 and 8, using the 7 bootmgr.
TeraByte Support wrote:
> Are you using Windows 7 or 8?
TeraByte Support wrote:
> Are you using Windows 7 or 8?
Re: TBWinRE difficulties
I followed this tut for TBWinRE:
http://www.terabyteunlimited.com/howto/ ... torial.htm
The path is G:\TBWinRE.
The full path to the winre.wim file I copied is G:\TBWinRE\TBWinRE_Backup\winre.wim
I'm using the Windows 7 bootmgr with the following menu appearing on boot:
Windows 7 Ultimate
Windows 8 Pro
Windows 7 DVD (shows in the menu as NST WinPE Image)
Windows 8 DVD (shows in the menu as NST WinPE Image)
WindowsRE
And I think my BCD Store needs cleaning up. I tried to attach bcdoutput.txt, but got an error message from the board saying txt is not allowed. Here it is:
Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=\Device\HarddiskVolume2
description Windows Boot Manager
locale en-US
inherit {globalsettings}
integrityservices Enable
default {current}
resumeobject {18070633-44f0-11e2-aab2-97701b3b6de2}
displayorder {current}
{18070637-44f0-11e2-aab2-97701b3b6de2}
{4d6b1dbf-2095-11e2-9031-93eb68b95afe}
{18070639-44f0-11e2-aab2-97701b3b6de2}
{15fe9467-6a83-11e2-9258-782bcb835a54}
toolsdisplayorder {memdiag}
timeout 5
displaybootmenu Yes
Windows Boot Loader
-------------------
identifier {15fe9467-6a83-11e2-9258-782bcb835a54}
device ramdisk=[C:]\Recovery\WindowsRE\winre.wim,{15fe9466-6a83-11e2-9258-782bcb835a54}
path \Windows\System32\Boot\winload.exe
description WindowsRE
locale en-US
osdevice ramdisk=[C:]\Recovery\WindowsRE\winre.wim,{15fe9466-6a83-11e2-9258-782bcb835a54}
systemroot \Windows
detecthal Yes
winpe Yes
Windows Boot Loader
-------------------
identifier {18070631-44f0-11e2-aab2-97701b3b6de2}
device ramdisk=[P:]\Recovery\05f686a1-44d6-11e2-84cb-ac8e6fde2e24\Winre.wim,{18070632-44f0-11e2-aab2-97701b3b6de2}
path \windows\system32\winload.exe
description Windows Recovery Environment (recovered)
locale
osdevice ramdisk=[P:]\Recovery\05f686a1-44d6-11e2-84cb-ac8e6fde2e24\Winre.wim,{18070632-44f0-11e2-aab2-97701b3b6de2}
systemroot \windows
winpe Yes
Windows Boot Loader
-------------------
identifier {18070635-44f0-11e2-aab2-97701b3b6de2}
Windows Boot Loader
-------------------
identifier {18070637-44f0-11e2-aab2-97701b3b6de2}
device partition=D:
path \Windows\system32\winload.exe
description Win8Pro
locale en-US
integrityservices Enable
osdevice partition=D:
systemroot \Windows
resumeobject {2af266ff-454c-11e2-be70-806e6f6e6963}
hypervisorlaunchtype Auto
Windows Boot Loader
-------------------
identifier {18070639-44f0-11e2-aab2-97701b3b6de2}
device ramdisk=[P:]\sources\boot.wim,{18070638-44f0-11e2-aab2-97701b3b6de2}
path \Windows\System32\Boot\winload.exe
description Windows 8 DVD
locale en-US
osdevice ramdisk=[P:]\sources\boot.wim,{18070638-44f0-11e2-aab2-97701b3b6de2}
systemroot \Windows
detecthal Yes
winpe Yes
Windows Boot Loader
-------------------
identifier {current}
device partition=C:
path \WINDOWS\system32\winload.exe
description Windows 7 Ultimate
locale en-US
loadoptions DDISABLE_INTEGRITY_CHECKS
recoverysequence {cda73815-38b5-11e0-91c9-782bcb835a54}
recoveryenabled Yes
osdevice partition=C:
systemroot \WINDOWS
resumeobject {42fadf51-2075-11e2-b14f-806e6f6e6963}
nx OptIn
pae Default
sos No
debug No
Windows Boot Loader
-------------------
identifier {4d6b1dbb-2095-11e2-9031-93eb68b95afe}
device partition=D:
path \WINDOWS\system32\winload.exe
description Windows 7 Home Premium
locale en-US
osdevice partition=D:
systemroot \WINDOWS
resumeobject {3fc0f98e-21c7-11e2-91f0-806e6f6e6963}
Windows Boot Loader
-------------------
identifier {4d6b1dbc-2095-11e2-9031-93eb68b95afe}
device ramdisk=[\Device\HarddiskVolume2]\Recovery\windowsre\Winre.wim,{4d6b1dbd-2095-11e2-9031-93eb68b95afe}
path \windows\system32\winload.exe
description Windows Recovery Environment (recovered)
locale
osdevice ramdisk=[\Device\HarddiskVolume2]\Recovery\windowsre\Winre.wim,{4d6b1dbd-2095-11e2-9031-93eb68b95afe}
systemroot \windows
winpe Yes
Windows Boot Loader
-------------------
identifier {4d6b1dbf-2095-11e2-9031-93eb68b95afe}
device ramdisk=[R:]\sources\boot.wim,{4d6b1dbe-2095-11e2-9031-93eb68b95afe}
path \Windows\System32\Boot\winload.exe
description Windows 7 DVD
locale en-US
osdevice ramdisk=[R:]\sources\boot.wim,{4d6b1dbe-2095-11e2-9031-93eb68b95afe}
systemroot \Windows
detecthal Yes
winpe Yes
Windows Boot Loader
-------------------
identifier {e8709fb6-fa5f-11db-be4d-e219ece5282e}
device unknown
path \Windows\system32\winload.exe
description Windows Vista
locale en-US
inherit {bootloadersettings}
osdevice unknown
systemroot \Windows
resumeobject {e8709fb7-fa5f-11db-be4d-e219ece5282e}
nx OptOut
Resume from Hibernate
---------------------
identifier {18070633-44f0-11e2-aab2-97701b3b6de2}
device unknown
path \WINDOWS\system32\winresume.exe
description Windows Resume Application
locale en-US
inherit {resumeloadersettings}
recoverysequence {18070635-44f0-11e2-aab2-97701b3b6de2}
recoveryenabled Yes
custom:17000077 352321653
filedevice unknown
filepath \hiberfil.sys
custom:25000008 1
debugoptionenabled No
Resume from Hibernate
---------------------
identifier {2af266ff-454c-11e2-be70-806e6f6e6963}
device partition=D:
path \Windows\system32\winresume.exe
description Win8Pro
locale en-US
inherit {resumeloadersettings}
filedevice partition=D:
filepath \hiberfil.sys
debugoptionenabled No
Resume from Hibernate
---------------------
identifier {3fc0f98e-21c7-11e2-91f0-806e6f6e6963}
device partition=D:
path \WINDOWS\system32\winresume.exe
description Windows 7 Home Premium (recovered)
locale en-US
inherit {resumeloadersettings}
filedevice partition=D:
filepath \hiberfil.sys
debugoptionenabled No
Resume from Hibernate
---------------------
identifier {42fadf51-2075-11e2-b14f-806e6f6e6963}
device partition=C:
path \WINDOWS\system32\winresume.exe
description Windows 7 Ultimate (recovered)
locale en-US
inherit {resumeloadersettings}
filedevice partition=C:
filepath \hiberfil.sys
debugoptionenabled No
Resume from Hibernate
---------------------
identifier {a2b7276b-44ce-11e2-8e55-806e6f6e6963}
device unknown
path \WINDOWS\system32\winresume.exe
description Windows 7 Home Premium (recovered)
locale en-US
inherit {resumeloadersettings}
filedevice unknown
filepath \hiberfil.sys
debugoptionenabled No
Resume from Hibernate
---------------------
identifier {e8709fb7-fa5f-11db-be4d-e219ece5282e}
device unknown
path \Windows\system32\winresume.exe
description Windows Resume Application
locale en-US
inherit {resumeloadersettings}
filedevice unknown
filepath \hiberfil.sys
pae No
debugoptionenabled No
Windows Memory Tester
---------------------
identifier {memdiag}
device partition=\Device\HarddiskVolume2
path \boot\memtest.exe
description Windows Memory Diagnostic
locale en-US
inherit {globalsettings}
badmemoryaccess Yes
Windows Legacy OS Loader
------------------------
identifier {ntldr}
device unknown
path \ntldr
description Earlier Version of Windows
EMS Settings
------------
identifier {emssettings}
bootems No
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 {15fe9466-6a83-11e2-9258-782bcb835a54}
description WindowsRE
ramdisksdidevice partition=P:
ramdisksdipath \NST\boot.sdi
Device options
--------------
identifier {18070632-44f0-11e2-aab2-97701b3b6de2}
ramdisksdidevice partition=P:
ramdisksdipath \Recovery\05f686a1-44d6-11e2-84cb-ac8e6fde2e24\boot.sdi
Device options
--------------
identifier {18070636-44f0-11e2-aab2-97701b3b6de2}
description Windows Recovery
ramdisksdidevice unknown
ramdisksdipath \Recovery\18070635-44f0-11e2-aab2-97701b3b6de2\boot.sdi
Device options
--------------
identifier {18070638-44f0-11e2-aab2-97701b3b6de2}
description NST WinPE Image
ramdisksdidevice partition=R:
ramdisksdipath \NST\boot.sdi
Device options
--------------
identifier {4d6b1dbd-2095-11e2-9031-93eb68b95afe}
ramdisksdidevice partition=\Device\HarddiskVolume2
ramdisksdipath \Recovery\windowsre\boot.sdi
Device options
--------------
identifier {4d6b1dbe-2095-11e2-9031-93eb68b95afe}
description NST WinPE Image
ramdisksdidevice partition=R:
ramdisksdipath \NST\boot.sdi
Setup Ramdisk Options
---------------------
identifier {ramdiskoptions}
description RamdiskOptions
ramdisksdidevice partition=P:
ramdisksdipath \NST\boot.sdi
http://www.terabyteunlimited.com/howto/ ... torial.htm
The path is G:\TBWinRE.
The full path to the winre.wim file I copied is G:\TBWinRE\TBWinRE_Backup\winre.wim
I'm using the Windows 7 bootmgr with the following menu appearing on boot:
Windows 7 Ultimate
Windows 8 Pro
Windows 7 DVD (shows in the menu as NST WinPE Image)
Windows 8 DVD (shows in the menu as NST WinPE Image)
WindowsRE
And I think my BCD Store needs cleaning up. I tried to attach bcdoutput.txt, but got an error message from the board saying txt is not allowed. Here it is:
Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=\Device\HarddiskVolume2
description Windows Boot Manager
locale en-US
inherit {globalsettings}
integrityservices Enable
default {current}
resumeobject {18070633-44f0-11e2-aab2-97701b3b6de2}
displayorder {current}
{18070637-44f0-11e2-aab2-97701b3b6de2}
{4d6b1dbf-2095-11e2-9031-93eb68b95afe}
{18070639-44f0-11e2-aab2-97701b3b6de2}
{15fe9467-6a83-11e2-9258-782bcb835a54}
toolsdisplayorder {memdiag}
timeout 5
displaybootmenu Yes
Windows Boot Loader
-------------------
identifier {15fe9467-6a83-11e2-9258-782bcb835a54}
device ramdisk=[C:]\Recovery\WindowsRE\winre.wim,{15fe9466-6a83-11e2-9258-782bcb835a54}
path \Windows\System32\Boot\winload.exe
description WindowsRE
locale en-US
osdevice ramdisk=[C:]\Recovery\WindowsRE\winre.wim,{15fe9466-6a83-11e2-9258-782bcb835a54}
systemroot \Windows
detecthal Yes
winpe Yes
Windows Boot Loader
-------------------
identifier {18070631-44f0-11e2-aab2-97701b3b6de2}
device ramdisk=[P:]\Recovery\05f686a1-44d6-11e2-84cb-ac8e6fde2e24\Winre.wim,{18070632-44f0-11e2-aab2-97701b3b6de2}
path \windows\system32\winload.exe
description Windows Recovery Environment (recovered)
locale
osdevice ramdisk=[P:]\Recovery\05f686a1-44d6-11e2-84cb-ac8e6fde2e24\Winre.wim,{18070632-44f0-11e2-aab2-97701b3b6de2}
systemroot \windows
winpe Yes
Windows Boot Loader
-------------------
identifier {18070635-44f0-11e2-aab2-97701b3b6de2}
Windows Boot Loader
-------------------
identifier {18070637-44f0-11e2-aab2-97701b3b6de2}
device partition=D:
path \Windows\system32\winload.exe
description Win8Pro
locale en-US
integrityservices Enable
osdevice partition=D:
systemroot \Windows
resumeobject {2af266ff-454c-11e2-be70-806e6f6e6963}
hypervisorlaunchtype Auto
Windows Boot Loader
-------------------
identifier {18070639-44f0-11e2-aab2-97701b3b6de2}
device ramdisk=[P:]\sources\boot.wim,{18070638-44f0-11e2-aab2-97701b3b6de2}
path \Windows\System32\Boot\winload.exe
description Windows 8 DVD
locale en-US
osdevice ramdisk=[P:]\sources\boot.wim,{18070638-44f0-11e2-aab2-97701b3b6de2}
systemroot \Windows
detecthal Yes
winpe Yes
Windows Boot Loader
-------------------
identifier {current}
device partition=C:
path \WINDOWS\system32\winload.exe
description Windows 7 Ultimate
locale en-US
loadoptions DDISABLE_INTEGRITY_CHECKS
recoverysequence {cda73815-38b5-11e0-91c9-782bcb835a54}
recoveryenabled Yes
osdevice partition=C:
systemroot \WINDOWS
resumeobject {42fadf51-2075-11e2-b14f-806e6f6e6963}
nx OptIn
pae Default
sos No
debug No
Windows Boot Loader
-------------------
identifier {4d6b1dbb-2095-11e2-9031-93eb68b95afe}
device partition=D:
path \WINDOWS\system32\winload.exe
description Windows 7 Home Premium
locale en-US
osdevice partition=D:
systemroot \WINDOWS
resumeobject {3fc0f98e-21c7-11e2-91f0-806e6f6e6963}
Windows Boot Loader
-------------------
identifier {4d6b1dbc-2095-11e2-9031-93eb68b95afe}
device ramdisk=[\Device\HarddiskVolume2]\Recovery\windowsre\Winre.wim,{4d6b1dbd-2095-11e2-9031-93eb68b95afe}
path \windows\system32\winload.exe
description Windows Recovery Environment (recovered)
locale
osdevice ramdisk=[\Device\HarddiskVolume2]\Recovery\windowsre\Winre.wim,{4d6b1dbd-2095-11e2-9031-93eb68b95afe}
systemroot \windows
winpe Yes
Windows Boot Loader
-------------------
identifier {4d6b1dbf-2095-11e2-9031-93eb68b95afe}
device ramdisk=[R:]\sources\boot.wim,{4d6b1dbe-2095-11e2-9031-93eb68b95afe}
path \Windows\System32\Boot\winload.exe
description Windows 7 DVD
locale en-US
osdevice ramdisk=[R:]\sources\boot.wim,{4d6b1dbe-2095-11e2-9031-93eb68b95afe}
systemroot \Windows
detecthal Yes
winpe Yes
Windows Boot Loader
-------------------
identifier {e8709fb6-fa5f-11db-be4d-e219ece5282e}
device unknown
path \Windows\system32\winload.exe
description Windows Vista
locale en-US
inherit {bootloadersettings}
osdevice unknown
systemroot \Windows
resumeobject {e8709fb7-fa5f-11db-be4d-e219ece5282e}
nx OptOut
Resume from Hibernate
---------------------
identifier {18070633-44f0-11e2-aab2-97701b3b6de2}
device unknown
path \WINDOWS\system32\winresume.exe
description Windows Resume Application
locale en-US
inherit {resumeloadersettings}
recoverysequence {18070635-44f0-11e2-aab2-97701b3b6de2}
recoveryenabled Yes
custom:17000077 352321653
filedevice unknown
filepath \hiberfil.sys
custom:25000008 1
debugoptionenabled No
Resume from Hibernate
---------------------
identifier {2af266ff-454c-11e2-be70-806e6f6e6963}
device partition=D:
path \Windows\system32\winresume.exe
description Win8Pro
locale en-US
inherit {resumeloadersettings}
filedevice partition=D:
filepath \hiberfil.sys
debugoptionenabled No
Resume from Hibernate
---------------------
identifier {3fc0f98e-21c7-11e2-91f0-806e6f6e6963}
device partition=D:
path \WINDOWS\system32\winresume.exe
description Windows 7 Home Premium (recovered)
locale en-US
inherit {resumeloadersettings}
filedevice partition=D:
filepath \hiberfil.sys
debugoptionenabled No
Resume from Hibernate
---------------------
identifier {42fadf51-2075-11e2-b14f-806e6f6e6963}
device partition=C:
path \WINDOWS\system32\winresume.exe
description Windows 7 Ultimate (recovered)
locale en-US
inherit {resumeloadersettings}
filedevice partition=C:
filepath \hiberfil.sys
debugoptionenabled No
Resume from Hibernate
---------------------
identifier {a2b7276b-44ce-11e2-8e55-806e6f6e6963}
device unknown
path \WINDOWS\system32\winresume.exe
description Windows 7 Home Premium (recovered)
locale en-US
inherit {resumeloadersettings}
filedevice unknown
filepath \hiberfil.sys
debugoptionenabled No
Resume from Hibernate
---------------------
identifier {e8709fb7-fa5f-11db-be4d-e219ece5282e}
device unknown
path \Windows\system32\winresume.exe
description Windows Resume Application
locale en-US
inherit {resumeloadersettings}
filedevice unknown
filepath \hiberfil.sys
pae No
debugoptionenabled No
Windows Memory Tester
---------------------
identifier {memdiag}
device partition=\Device\HarddiskVolume2
path \boot\memtest.exe
description Windows Memory Diagnostic
locale en-US
inherit {globalsettings}
badmemoryaccess Yes
Windows Legacy OS Loader
------------------------
identifier {ntldr}
device unknown
path \ntldr
description Earlier Version of Windows
EMS Settings
------------
identifier {emssettings}
bootems No
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 {15fe9466-6a83-11e2-9258-782bcb835a54}
description WindowsRE
ramdisksdidevice partition=P:
ramdisksdipath \NST\boot.sdi
Device options
--------------
identifier {18070632-44f0-11e2-aab2-97701b3b6de2}
ramdisksdidevice partition=P:
ramdisksdipath \Recovery\05f686a1-44d6-11e2-84cb-ac8e6fde2e24\boot.sdi
Device options
--------------
identifier {18070636-44f0-11e2-aab2-97701b3b6de2}
description Windows Recovery
ramdisksdidevice unknown
ramdisksdipath \Recovery\18070635-44f0-11e2-aab2-97701b3b6de2\boot.sdi
Device options
--------------
identifier {18070638-44f0-11e2-aab2-97701b3b6de2}
description NST WinPE Image
ramdisksdidevice partition=R:
ramdisksdipath \NST\boot.sdi
Device options
--------------
identifier {4d6b1dbd-2095-11e2-9031-93eb68b95afe}
ramdisksdidevice partition=\Device\HarddiskVolume2
ramdisksdipath \Recovery\windowsre\boot.sdi
Device options
--------------
identifier {4d6b1dbe-2095-11e2-9031-93eb68b95afe}
description NST WinPE Image
ramdisksdidevice partition=R:
ramdisksdipath \NST\boot.sdi
Setup Ramdisk Options
---------------------
identifier {ramdiskoptions}
description RamdiskOptions
ramdisksdidevice partition=P:
ramdisksdipath \NST\boot.sdi
-
TeraByte Support(PP)
- Posts: 1646
- Joined: Fri Aug 12, 2011 12:51 am
Re: TBWinRE difficulties
>The full path to the winre.wim file I copied is G:\TBWinRE\TBWinRE_Backup\winre.wim
The backup folder name is wrong. It should be "WinRE_Backup":
G:\TBWinRE\WinRE_Backup\winre.wim
I'll take a look at the BCD output.
The backup folder name is wrong. It should be "WinRE_Backup":
G:\TBWinRE\WinRE_Backup\winre.wim
I'll take a look at the BCD output.