Running TBWinRE/TBWinPE on UEFI without a Boot Disk

Mr.X · Nov 5, 2021

It threw only this data:

Code:

                            PARTINFG, Version 1.02
          Copyright (c) 2009,2013 TeraByte, Inc. All Rights Reseverd

                          Run Date: 11/5/2021 4:00 PM

===============================================================================
                 MBR Partition Information (HD0 - 0x81460F84)
                   (CHS: 1022/254/63)  (WCHS: 19457/255/63)
+====+====+=============+====+=============+=============+=============+
| 0: | 80 |    0   1  1 |  7 | 1023 254 63 |          63 |    69529257 |
| 1: |  0 | 1023 254 63 |  7 | 1023 254 63 |    69529320 |   230709465 |
| 2: |  0 | 1023 254 63 |  7 | 1023 254 63 |   300238785 |     8128890 |
| 3: |  0 | 1023 254 63 |  7 | 1023 254 63 |   308367675 |     4209030 |
+====+====+=============+====+=============+=============+=============+
===============================================================================
                            BOOT SECTOR INFORMATION
-------------------------------------------------------------------------------
       File System ID: 0x7   LBA: 63  Total Sectors: 69529257   ID: 0x1
                                  Jump: EB 52 90
                              OEM Name: NTFS  
                         Bytes Per Sec: 512
                         Sec Per Clust: 8
                           Res Sectors: 0
                                Zero 1: 0x0
                                Zero 2: 0x0
                                  NA 1: 0x0
                                 Media: 0xF8
                                Zero 3: 0x0
                         Sec Per Track: 63
                                 Heads: 255
                           Hidden Secs: 63
                                  NA 2: 0x0
                                  NA 3: 0x800080
                         Total Sectors: 0x424EEA8
                               MFT LCN: 0x116
                          MFT Mirr LCN: 0x115
                         Clust Per FRS: 0xF6
                      Clust Per IBlock: 0x1
                             Volume SN: 0x1D77C1031F24180
                              Checksum: 0x0
                             Boot Flag: 0xAA55
-------------------------------------------------------------------------------
    File System ID: 0x7   LBA: 69529320  Total Sectors: 230709465   ID: 0x2
                                  Jump: EB 52 90
                              OEM Name: NTFS  
                         Bytes Per Sec: 512
                         Sec Per Clust: 8
                           Res Sectors: 0
                                Zero 1: 0x0
                                Zero 2: 0x0
                                  NA 1: 0x0
                                 Media: 0xF8
                                Zero 3: 0x0
                         Sec Per Track: 63
                                 Heads: 255
                           Hidden Secs: 69529320
                                  NA 2: 0x0
                                  NA 3: 0x800080
                         Total Sectors: 0xDC058D7
                               MFT LCN: 0x7074
                          MFT Mirr LCN: 0x10D
                         Clust Per FRS: 0xF6
                      Clust Per IBlock: 0x1
                             Volume SN: 0x1D7631C84348EB0
                              Checksum: 0x0
                             Boot Flag: 0xAA55
-------------------------------------------------------------------------------
    File System ID: 0x7   LBA: 300238785  Total Sectors: 8128890   ID: 0x3
                                  Jump: EB 52 90
                              OEM Name: NTFS  
                         Bytes Per Sec: 512
                         Sec Per Clust: 8
                           Res Sectors: 0
                                Zero 1: 0x0
                                Zero 2: 0x0
                                  NA 1: 0x0
                                 Media: 0xF8
                                Zero 3: 0x0
                         Sec Per Track: 63
                                 Heads: 255
                           Hidden Secs: 300238785
                                  NA 2: 0x0
                                  NA 3: 0x800080
                         Total Sectors: 0x7C0978
                               MFT LCN: 0x93C1
                          MFT Mirr LCN: 0x2A
                         Clust Per FRS: 0xF6
                      Clust Per IBlock: 0x1
                             Volume SN: 0x1D7AEDCAC713F20
                              Checksum: 0x0
                             Boot Flag: 0xAA55
-------------------------------------------------------------------------------
    File System ID: 0x7   LBA: 308367675  Total Sectors: 4209030   ID: 0x4
                                  Jump: EB 52 90
                              OEM Name: NTFS  
                         Bytes Per Sec: 512
                         Sec Per Clust: 8
                           Res Sectors: 0
                                Zero 1: 0x0
                                Zero 2: 0x0
                                  NA 1: 0x0
                                 Media: 0xF8
                                Zero 3: 0x0
                         Sec Per Track: 63
                                 Heads: 255
                           Hidden Secs: 308367675
                                  NA 2: 0x0
                                  NA 3: 0x800080
                         Total Sectors: 0x403980
                               MFT LCN: 0x14
                          MFT Mirr LCN: 0x13
                         Clust Per FRS: 0xF6
                      Clust Per IBlock: 0x1
                             Volume SN: 0x1D7AEDC6ABA9590
                              Checksum: 0x0
                             Boot Flag: 0xAA55
-------------------------------------------------------------------------------

Mr.X · Nov 5, 2021

And what about this?
Mr.X said: ↑
Edit:
It occurred to me today to run a Strelec's WinPE then run mountvol.exe and oddly it showed different GUIDs for all the same volumes:
Code:
\\?\Volume{81460f84-0000-0000-007e-000000000000}\
C:\

\\?\Volume{81460f84-0000-0000-00d0-dd4908000000}\
D:\

\\?\Volume{81460f84-0000-0000-0082-8fca23000000}\
E:\

\\?\Volume{81460f84-0000-0000-0076-a2c224000000}\
F:\
I believed GUIDs were stamped on every partition at disk level, OS independent.
Click to expand...

Brian K · Nov 5, 2021

You have a MBR disk. No GUIDs. Here is one of my GPT disks...

Code:

===============================================================================
            GPT Found (HD4) {8B9E0625-CEAB-CDC3-DC5D-585E6A73FFFF}
-------------------------------------------------------------------------------
Revision: 10000   Hdr Size: 92   Max Entries: 128    PE Size: 128  PE LBA: 2
Primary LBA: 1                  Backup LBA: 2000409263    
 FAvail LBA: 34                 LAvail LBA: 2000409230    
--------------------------------------------------------------------------------------------------------------------------------------------------------------
  Num            Name                Attr            Start            End                     GUID Type                                 GUID
 ----- ----------------------- ---------------- --------------- --------------- --------------------------------------  --------------------------------------
    0  Microsoft reserved part                0             34           32801  {E3C9E316-0B5C-4DB8-817D-F92DF00215AE}  {8437D240-C7EA-6A6E-DC5D-585E6A73FFFF}
    1  EFI System                80000000000000          34816          854015  {C12A7328-F81F-11D2-BA4B-00A0C93EC93B}  {22D78A25-509D-98B4-DC5D-585E6A73FFFF}
    2  Win11                                  0         854016       144025599  {EBD0A0A2-B9E5-4433-87C0-68B6B72699C7}  {3F4B39D1-2F65-11EB-9C29-900054140D30}
    3  RE                      8000000000000001      144025600       145274879  {DE94BBA4-06D1-4D40-A16A-BFD50179D6AC}  {FBD2371F-BC79-4D84-B1A2-84A4462484F6}
    4  TBWinPE347                             0      145274880       146298879  {6F422ADF-746F-7449-2048-696464656E2A}  {529738E3-3629-3665-F5EA-255F2974FFFF}
    5  TBWinRE347                             0      146298880       147834879  {6F422ADF-746F-7449-2048-696464656E2A}  {3CDBA6BF-0C87-993E-036E-D05E91F50000}
    6  Mint202-cinn                           0      147834880       188590079  {0FC63DAF-8483-4772-8E79-3D69D8477DE4}  {2AEA84BB-5818-B536-D2BC-F75E1674FFFF}
    7  W10-for-upgrade                        0      188590080       331950079  {6F422ADF-746F-7449-2048-696464656E2A}  {5F2B22D7-B005-F107-500E-5C612266FFFF}
    8  W11_fresh                              0      331950080       463022079  {6F422ADF-746F-7449-2048-696464656E2A}  {E6391968-DF04-B273-EA0B-5E618565FFFF}
    9  DATA                                   0      566808576      2000408575  {EBD0A0A2-B9E5-4433-87C0-68B6B72699C7}  {2B2E9FAC-B485-5444-D9B2-585E6573FFFF}

Mr.X · Nov 5, 2021

Brian K said: ↑

You have a MBR disk. No GUIDs. Here is one of my GPT disks...
Click to expand...

Brian, bear with me. I'm still learning...

Then why mountvol.exe showed volumes GUIDs for every partition I have:
Code:
Possible values for VolumeName along with current mount points are:

    \\?\Volume{9e92db18-e845-11eb-b906-806e6f6e6963}\
        C:\
And a partition manager yields same info about the volumes my HDD has:

Look, both programs throw the same value.

Brian K · Nov 5, 2021

I haven't used mountvol.exe in the past. However it does show the same partition GUIDs as partinfo.

Mr.X · Nov 5, 2021

Brian K said: ↑

I haven't used mountvol.exe in the past. However it does show the same partition GUIDs as partinfo.
Click to expand...

Yet I'm still in doubt. You said partinfo.exe didn't throw any GUID value cause I'm on a MBR disk, you implying that only GPT disks can have a GUID. If that is true why my MBR disk has GUIDs in its volumes?

Brian K · Nov 5, 2021

Mr.X said: ↑

Yet I'm still in doubt.
Click to expand...

Me too.

Mr.X · Nov 6, 2021

MudCrab said: ↑
Setting up TBWinRE Recovery Partition and Booting from Windows Boot Manager on UEFI/GPT Systems

Here are the basic steps to set this up. I think I have all the required details listed, but if something is missing or not clear, just ask. There are also variations on this method that are useful, but I don't want to confuse things by adding them here. See how this goes first...
Create an NTFS partition on the drive and assign it a letter. This partition will hold the TBWinRE files (usually 350-400MB) and the backup image. Size it as needed. (You may already have already created this partition.)

Make a folder to hold the TBWinRE build files. I suggest copying the “tbwinre” folder from the IFW installation to an alternate location so you can work with them more easily. For example, you might use “D:\TBWinRE Recovery”. You would most likely want to put them on a drive that would not be part of the automatic restore.
Run TBWinPE/RE Builder (TBWinPE.exe) and create the build how you want. In this case, you would be configuring IFW to perform an automatic restore and then reboot. However, you could do any operation (backup, restore, validate, etc.). For example, you could configure it to validate a backup so no restore takes place while testing and setting up. Below is one way it could be configured.
Assuming default build options are being used…

On the “Project Type” screen, click the Settings button.

Click the TBLauncher tab.

Select the “IFW – Image for Windows will be run with specified parameters” option.
Enter your IFW command line in the Parameters box. For example, it may look like one of the following:
Code:
/r /uy /d:w0 /f:w0@0x5:"\Backup\Base" /sp:0x1,0x2,0x3,0x4 /rb:4
Code:
/r /uy /d:{6DC69B20-2C93-40AE-AE07-B3025C4E29D8} /f:{6DC69B20-2C93-40AE-AE07-B3025C4E29D8}@0x5:"\Backup\Base" /sp:0x1,0x2,0x3,0x4 /rb:4
Click OK to close Settings.
Continue through the wizard to create the TBWinRE build. Select the option to create the CD/UFD/ISO. When finished you can just close it (no need to run MakeDisk).

Copy the entire contents of the ISO folder to the recovery partition you created. After the copy, the partition should contain the following folders & files in the root folder: boot, efi, sources, TBData, bootmgr, bootmgr.efi

Create the “TBWinRE-Create-BCD-Entry.cmd” script (contents below) in your TBWinRE build folder. Edit the DrvLetter variable at the start to be the drive letter assigned to the recovery partition.

From an Administrator Command Prompt, run the “TBWinRE-Create-BCD-Entry.cmd” script. This will add items to the BCD to boot TBWinRE on the recovery partition.

To boot the item, from an Administrator Command Prompt, run the “TBWinRE-Boot-BCD-Entry.cmd” script. This will configure the boot item for a one-time boot and restart the computer.
Notes:

The scripts don’t do any error or permission checking. They’re just doing the basics at this point.

The scripts must be run as an Administrator. I recommend running them from an Administrator Command Prompt so you can verify the output (in case of errors) instead of running directly from Explorer.

The “TBWinRE-Remove-BCD-Entry.cmd” script can be run to remove the BCD items that were added. However, if the System partition is part of the restore and the backup image version of it doesn’t have the items, then there’s nothing to remove after Windows boots back up. Keep in mind that you may want to create the backup image AFTER you create the BCD items so that they remain available after doing a restore (otherwise, you’d have to recreate them first).

If you have a drive letter assigned to the recovery partition and setup the script to use that letter and then remove the letter assignment (to hide the partition), if you need to run the “TBWinRE-Create-BCD-Entry.cmd” script again you will need to either reassign the drive letter to the partition first or edit the script to reference the volume number instead (e.g. \Device\HarddiskVolume5).

Any excess BCD items that don’t get removed or that remain due to errors or testing can always be manually deleted. The default description for the entries is “TBWinRE Recovery” and they can be seen by running “bcdedit /enum all” at an Administrator Command Prompt.

If you need to modify the IFW command parameters, just run TBWinPE/RE Builder, change the parameters, create the build, then copy the ISO folder contents to the recovery partition. (You can just copy over the updated \sources\boot.wim instead of everything if you want.)

When setting the IFW parameters to use for an automatic restore you may want to omit the “/uy” parameter during testing so that IFW will prompt to overwrite the partitions. This way you can verify everything is working correctly before going fully automatic.

Contents of "TBWinRE-Create-BCD-Entry.cmd" Script
Code:
@echo off
setlocal enableextensions enabledelayedexpansion
cls
cd /d %~dp0

:: vars
set DrvLetter=E:
set DrvDesc=TBWinRE Recovery

:: ======================================

:: get BCD GUID for entry
for /f "usebackq tokens=2 delims={}" %%G in (`bcdedit /create /application osloader`) do set BCDGUID={%%G}

:: get BCD GUID for options entry
for /f "usebackq tokens=2 delims={}" %%G in (`bcdedit /create /d "%DrvDesc%" /device`) do set BCDOPTSGUID={%%G}

:: configure BCD entry
bcdedit /set %BCDGUID% systemroot \Windows
bcdedit /set %BCDGUID% detecthal Yes
bcdedit /set %BCDGUID% winpe Yes
bcdedit /set %BCDGUID% osdevice ramdisk=[%DrvLetter%]\sources\boot.wim,%BCDOPTSGUID%
bcdedit /set %BCDGUID% device ramdisk=[%DrvLetter%]\sources\boot.wim,%BCDOPTSGUID%
bcdedit /set %BCDGUID% description "%DrvDesc%"

:: configure BCD ramdisk options for entry
bcdedit /set %BCDOPTSGUID% ramdisksdidevice partition=%DrvLetter%
bcdedit /set %BCDOPTSGUID% ramdisksdipath \Boot\boot.sdi

:: create boot entry script
echo @echo off > TBWinRE-Boot-BCD-Entry.cmd
echo bcdedit /bootsequence %BCDGUID% >> TBWinRE-Boot-BCD-Entry.cmd
echo shutdown -r -t 0 >> TBWinRE-Boot-BCD-Entry.cmd

:: create remove entry script
echo @echo off > TBWinRE-Remove-BCD-Entry.cmd
echo bcdedit /delete %BCDGUID% >> TBWinRE-Remove-BCD-Entry.cmd
echo bcdedit /delete %BCDOPTSGUID% >> TBWinRE-Remove-BCD-Entry.cmd
Click to expand...
I decided to putt the TBWinRE folder in this path C:\Boot\IFW\TBWinRE (a la MReflect )
Then these lines:
Code:
:: vars
set DrvLetter=C:
set DrvDesc=TBWinRE
Correct?

FYI I want to revive these fabulous scripts again but only for Restore Operation since Backup Operation can be done within Windows + IFW-VSS/Phylock and no reboot required.

Also I want to continue on this thread but want to rename it to a more appropriate name, how about this:
Auto Restore with IFW + TBWinRE on BIOS/UEFI

It's alike the one @n8chavez 's thread he created the other day.

What do you think?

Or is not necessary to use TBWinRE anymore?

Brian K · Nov 6, 2021

I thought I'd provided a method to do a TBWinRE auto restore in the @n8chavez thread. No?

Mr.X · Nov 6, 2021

Brian K said: ↑

I thought I'd provided a method to do a TBWinRE auto restore in the @n8chavez thread. No?
Click to expand...

Yes you did, oops

Do you mind if I continue here based on the same information you did there?
I don't want to hijack @n8chavez thread...

So if you don't mind I'll post my lines in the next comment.

Mr.X · Nov 6, 2021

Line saved for TBWinRE from running through an IFW restore:

Code:

/r /uy /um /d:#0x81460F84@0x1 /f:#0xBE026DDC@0x1:"\LAPPY\OS\IFW\OS_Full_10-27-21" /v /t /rft /usemd /log:0

Same line but some parameters added by me for two scenarios:

Code:

For a MBR disk

/r /uy /um /d:#0x81460F84@0x1 /f:#0xBE026DDC@0x1:"\LAPPY\OS\IFW\OS_Full_10-27-21" /v /t /rft /wco /usemd /log:0 /rb:4

Code:

For an hypothetical GPT disk

/r /uy /um /d:{81460f84-0000-0000-007e-000000000000} /f:{81460f84-0000-0000-0076-a2c224000000}@0x1:"\LAPPY\OS\IFW\OS_Full_10-27-21" /v /sp:0x1,0x2,0x3,0x4 /t /rft /wco /usemd /rb:4

What do you think?

Brian K · Nov 6, 2021

Mr.X said: ↑

{81460f84-0000-0000-007e-000000000000} /f:{81460f84-0000-0000-0076-a2c224000000}
Click to expand...

I don't think they are valid GPT GUIDs for IFW. All the 0000 worries me.

Here is a sample restore for GPT...
Code:
/r /uy /um /d:{8B9E0625-CEAB-CDC3-DC5D-585E6A73FFFF} /f:{ED486460-7118-1AD0-A75D-585E9773FFFF}@0x2:"\TeraByte_TBI_Backups\C_2021-10-29-1800_DIFF_2021-11-06-1906" /sp:0x1,0x2,0x3,0x4 /vb /wco /rb:4

Mr.X · Nov 6, 2021

Brian K said: ↑
I don't think they are valid GPT GUIDs for IFW. All the 0000 worries me.

Here is a sample restore for GPT...
Code:
/r /uy /um /d:{8B9E0625-CEAB-CDC3-DC5D-585E6A73FFFF} /f:{ED486460-7118-1AD0-A75D-585E9773FFFF}@0x2:"\TeraByte_TBI_Backups\C_2021-10-29-1800_DIFF_2021-11-06-1906" /sp:0x1,0x2,0x3,0x4 /vb /wco /rb:4
Click to expand...
Oh I know I know, that's why I wrote "hypothetical"
How about the rest of the lines syntax?

Brian K · Nov 6, 2021

They look fine.

Mr.X · Nov 6, 2021

Re TBWinRE build I didn't read the tutorial I just followed TBWinPE.exe GUI steps using defaults except network initialization. Is it ok?

Brian K · Nov 6, 2021

Sure, that's fine. You don't really need to use Settings.

Brian K · Nov 7, 2021

If you just want to boot into TBWinRE (use your path)...
Code:
"D:\tbwinre\tbwinpe.exe" /bootwim "D:\tbwinre\ISO\sources\boot.wim"

Mr.X · Nov 7, 2021

Brian K said: ↑
If you just want to boot into TBWinRE (use your path)...
Code:
"D:\tbwinre\tbwinpe.exe" /bootwim "D:\tbwinre\ISO\sources\boot.wim"
Click to expand...
Well, I did it and it worked out, full restore operation
This solution of yours is fabulous and elegant and easy to setup, well you need to get acquainted with IFW and sub-components.
Thank you very much!

This are my tbwinre.exe scripts and I know I know, paths are quite long but I prefer to use default installation paths for IFW and sub-components:

restore_mbr_disk.cmd
Code:
"C:\Program Files\TeraByte Drive Image Backup and Restore Suite\tbwinre\TBWinPE.exe" /bootwim "C:\Program Files\TeraByte Drive Image Backup and Restore Suite\tbwinre\ISO\sources\boot.wim" /run "C:\Program Files\TeraByte Drive Image Backup and Restore Suite\tbwinre\restore_mbr_disk.txt"
restore_gpt_disk.cmd
Code:
"C:\Program Files\TeraByte Drive Image Backup and Restore Suite\tbwinre\TBWinPE.exe" /bootwim "C:\Program Files\TeraByte Drive Image Backup and Restore Suite\tbwinre\ISO\sources\boot.wim" /run "C:\Program Files\TeraByte Drive Image Backup and Restore Suite\tbwinre\restore_gpt_disk.txt"
Only thing that changes is the txt file name.

Mr.X · Nov 7, 2021

Now here are my txt files:

restore_mbr_disk.txt

Code:

/r /uy /um /d:#0x81460F84@0x1 /f:#0xBE026DDC@0x1:"\LAPPY\OS\IFW\OS_Full_11-06-21" /t /rft /wco /usemd /rb:4 /priority:4

Notes:
1. Watch carefully to Partinfo and IFW infos and edit accordingly: paths, filenames and disks GUIDs.

Parameters for specific scenarios:
/v
Use this parameter to have Image for Windows perform a standard validation on theimage file(s) prior before restoring them.
Default if omitted: Image for Windows does not validate the image files before restoring
them.

/rp:n
This option is intended for use when restoring multiple partitions from a backup image located on a recovery partition to the drive containing the recovery partition. All partitions on the drive except the partition indicated by the ID value n will be deleted prior to the restore. Typically this option would be used with /x /rft or /x /m /rft. Scaling of the restored partitions will operate as if a full drive image were being restored.
This option is only supported when restoring multiple partitions and cannot be used when restoring an entire drive image.
Due to the way this option functions and scaling is performed, placing the recovery partition at the start of the drive is recommended. This allows easy scaling to different size drives when restoring.
Example: A Windows drive contains the following four partitions:
ID 0x1 Recovery Partition
ID 0x2 System Reserved
ID 0x3 Windows
ID 0x4 Data
The Recovery partition contains a backup image of partitions 0x2, 0x3, and 0x4. A restore of those partitions that would scale to a different size drive would be performed by running the following command:
imagew /r /d:w0 /f:w0@0x1:\Recovery.tbi /sp:0x2,0x3,0x4 /x /rft /rp:0x1 /ubp
Default if omitted: Image for Windows will not support scaling a multi-partition restore.

restore_gpt_disk.txt

Code:

/r /uy /um /d:{81460f84-0000-0000-007e-000000000000} /f:{81460f84-0000-0000-0076-a2c224000000}@0x1:"\LAPPY\OS\IFW\OS_Full_11-06-21" /sp:0x1,0x2,0x3,0x4 /t /rft /wco /usemd /rb:4 /priority:4

Notes:
1. Watch carefully to Partinfo and IFW infos and edit accordingly: paths, filenames and disks GUIDs.

Parameters for specific scenarios:
/v
Use this parameter to have Image for Windows perform a standard validation on theimage file(s) prior before restoring them.
Default if omitted: Image for Windows does not validate the image files before restoring
them.

/rp:n
This option is intended for use when restoring multiple partitions from a backup image located on a recovery partition to the drive containing the recovery partition. All partitions on the drive except the partition indicated by the ID value n will be deleted prior to the restore. Typically this option would be used with /x /rft or /x /m /rft. Scaling of the restored partitions will operate as if a full drive image were being restored.
This option is only supported when restoring multiple partitions and cannot be used when restoring an entire drive image.
Due to the way this option functions and scaling is performed, placing the recovery partition at the start of the drive is recommended. This allows easy scaling to different size drives when restoring.
Example: A Windows drive contains the following four partitions:
ID 0x1 Recovery Partition
ID 0x2 System Reserved
ID 0x3 Windows
ID 0x4 Data
The Recovery partition contains a backup image of partitions 0x2, 0x3, and 0x4. A restore of those partitions that would scale to a different size drive would be performed by running the following command:
imagew /r /d:w0 /f:w0@0x1:\Recovery.tbi /sp:0x2,0x3,0x4 /x /rft /rp:0x1 /ubp
Default if omitted: Image for Windows will not support scaling a multi-partition restore.

And I like that you can make annotations notes remarks whatever and they do not interfere with its operation. These notes serve me to annotate parameters and its function for certain scenarios so I can edit the txt file accordingly, you know my memory these days is pfff! Quite volatile!!! :argh:

Brian K · Nov 7, 2021

Nice work. Glad you have been able to sort it out. TBWinRE looks complicated but I don't think it is. Just a matter of copy/paste command lines.

Mr.X · Nov 7, 2021

I think if Terabyte Unlimited is going to add support for Auto Restore on IFW this the way to go, same principle as your solution but fully assisted by IFW GUI.

Mr.X · Nov 16, 2021

Which one in your experience is worth to use, Phylock or VSS?
Thanks in advance.

TheRollbackFrog · Nov 16, 2021

Phylock has consistency issues as well. Although it does "freeze" the FileSystem as well, it does not in any way allow users of that FileSystem to flush and make their databases consistent prior to the imaging operation. VSS calls out those users and informs them of the impending freeze so that consistency may be made, Phylock does not.

All the early imaging Systems that offered some sort of Phylock-like freeze have the exact same issues, even the early Macrium REFLECT solution.

Brian K · Nov 16, 2021

I think TeraByte Support now favors VSS over PHYLock.

Mr.X · Dec 8, 2021

@Brian K @n8chavez
Code:
Added /boottbwr (BootTBWinRE) option to offer reboot to TBWinRE when unable to lock on restore.
Do you think this is the option we always wanted?

Log in or Sign up

Running TBWinRE/TBWinPE on UEFI without a Boot Disk

Mr.X Registered Member

Mr.X Registered Member

Brian K Imaging Specialist

Mr.X Registered Member

Brian K Imaging Specialist

Mr.X Registered Member

Brian K Imaging Specialist

Mr.X Registered Member

Brian K Imaging Specialist

Mr.X Registered Member

Mr.X Registered Member

Brian K Imaging Specialist

Mr.X Registered Member

Brian K Imaging Specialist

Mr.X Registered Member

Brian K Imaging Specialist

Brian K Imaging Specialist

Mr.X Registered Member

Mr.X Registered Member

Brian K Imaging Specialist

Mr.X Registered Member

Mr.X Registered Member

TheRollbackFrog Imaging Specialist

Brian K Imaging Specialist

Mr.X Registered Member

Log in or Sign up

Running TBWinRE/TBWinPE on UEFI without a Boot Disk

Mr.X Registered Member

Mr.X Registered Member

Brian K Imaging Specialist

Mr.X Registered Member

Brian K Imaging Specialist

Mr.X Registered Member

Brian K Imaging Specialist

Mr.X Registered Member

Brian K Imaging Specialist

Mr.X Registered Member

Mr.X Registered Member

Brian K Imaging Specialist

Mr.X Registered Member

Brian K Imaging Specialist

Mr.X Registered Member

Brian K Imaging Specialist

Brian K Imaging Specialist

Mr.X Registered Member

Mr.X Registered Member

Brian K Imaging Specialist

Mr.X Registered Member

Mr.X Registered Member

TheRollbackFrog Imaging Specialist

Brian K Imaging Specialist

Mr.X Registered Member

Useful Searches