Author Topic: updated wim.trid.xml wim-nosplit.trid.xml for Reconstruct.WIM2  (Read 101 times)

jenderek

  • Full Member
  • ***
  • Posts: 152
Hello trid users,

some days ago i run TrID with verbose option on Windows imaging found
in directory sources on recovery USB stick for modern Windows systems

Besides a hidden system marked boot.wim and a Reconstruct.WIM there exist
also a Reconstruct.WIM2. All are described correctly as "Windows Imaging Format"
by wim-nosplit.trid.xml or "Windows Imaging Format (generic)" by
wim.trid.xml ( see appended output/trid-v.txt).

Unfortunately the used file name extension "WIM2" in last image is not
mentioned in Ext line inside trid definitions.

So i add this file name extension inside the 2 definitions wim.trid.xml and
wim-nosplit.trid.xml.

The procedure to reproduce such image  is describe for example on web page
like:

https://www.tenforums.com/tutorials/4200-create-recovery-drive-windows-10-a.html

Start Microsoft’s recovery drive creating tool "RecoveryDrive.exe", which
normally found in System32 sub directory inside Windows directory.

If the option to back up system files to the recovery drive is chosen
additional disc image with WIM format are created. The first is called
Reconstruct.WIM and the second is called Reconstruct.WIM2. So i mention this
fact in remark line, because for splited multiple part images normally file
name extension "swm" is used. I found no explanation why here WIM2 is used.

The tool also creates a file $PBR_ResetConfig.xml with XML based
instructions to reconstruct the Windows operating system disc. Apparently by
"DiskpartScriptPath" directive referring to script $PBR_Diskpart.txt the tool
DISKPART.EXE is called with instructions to partition and format the system disc.

I do not know if these observations are always true, because i found no precise
description of the recovery process.

With the 2 updated trid definitions now also Windows image Reconstruct.WIM2
is now described with unusual file name extension "WIM2" ( see appended
output/trid-v-new.txt) more precisely. TrID definitions and output are
stored in archive sources.zip. I hope that all 2 XML files can be used in
future version of triddefs.

With best wishes
Jörg Jenderek

Mark0

  • Administrator
  • Hero Member
  • *****
  • Posts: 2076
    • Mark0's Home Page
Re: updated wim.trid.xml wim-nosplit.trid.xml for Reconstruct.WIM2
« Reply #1 on: August 11, 2020, 09:57:09 PM »
Thanks for the info. At the moment I don't think it's really necessary to add the second extension, but I will surely give it some thought.