Jump to content











Photo
- - - - -

Capture and apply Windows Full Flash Update (FFU) images

dism

  • Please log in to reply
115 replies to this topic

#101 ReTokener

ReTokener

    Frequent Member

  • Developer
  • 234 posts

Posted 2 weeks ago

Hola alacran,

thank you for the very detailed procedure. :thumbsup:

 

Because i am a wimboot beginner, i take small steps to understand the different stages.
At the top of the list is the recording of an image. I am using (with success) the customwimbootcompress.ini you sent me (with wimlib-clc).

Spoiler

 

This way I created a simple wimboot system.
I will try to implement your suggestions later on.

 

Best regards   T.



#102 ReTokener

ReTokener

    Frequent Member

  • Developer
  • 234 posts

Posted 2 weeks ago

The question still remains: what version of dism did MS use to capture Windows partition in wimboot mode?

 

Regards   T.



#103 alacran

alacran

    Gold Member

  • .script developer
  • 1173 posts
  •  
    Mexico

Posted 2 weeks ago

Yes that works very fine on wimlib, but on Dism this line: \Windows\System32\drivers\*.sys create problems, because only the drivers that come into the install ISO from MS are expanded correctly, all other drivers you installed are created supposedly expanded but they are full of zeros, THIS IS THE BIGGEST ISSUE as all the PC drivers you installed are corrupt, even worst if you want to RAMBOOT because SvBus driver is corrupted too.

 

alacran



#104 alacran

alacran

    Gold Member

  • .script developer
  • 1173 posts
  •  
    Mexico

Posted 2 weeks ago

The question still remains: what version of dism did MS use to capture Windows partition in wimboot mode?

 

Regards   T.

 

Only valid is 8.1 udate 1 and its respective Dism version.  Wich in turn is not valid for Capture/apply 10.

 

Compact mode is the replacement of wimboot on all Dism versions for 10. 

 

alacran



#105 ReTokener

ReTokener

    Frequent Member

  • Developer
  • 234 posts

Posted 2 weeks ago

 

(...)because only the drivers that come into the install ISO from MS are expanded correctly

I understand, thank you very much.

 

Best regards   T.



#106 alacran

alacran

    Gold Member

  • .script developer
  • 1173 posts
  •  
    Mexico

Posted 2 weeks ago

@ Retokener

 

On wimlib-clc I never have selected RpFix or NoRpFix, and all my capture/apply to/from standart WIM or to/from wimboot have been working very fine.

 

On DMS I selected Reset to Default, to clean all changes done and I noticed the following:

 

On capture Tab NoRpFix is preselected.

 

On options Tab NoRpFix is NOT preselected.

 

I think both should be preselected or not, but same way both, Is that correct?

 

I would like more info about what this option does, the Tooltip info do not seems clear enough for me.

 

And also i would like to know how it works on DMS compared to how wimlib-clc deals with it.

 

alacran



#107 alacran

alacran

    Gold Member

  • .script developer
  • 1173 posts
  •  
    Mexico

Posted 2 weeks ago

From wimlib Capture document:

 

 

--rpfix, --norpfix
Set whether to fix targets of absolute symbolic links (reparse points in Windows terminology) or
not. When enabled (--rpfix), absolute symbolic links that point inside the directory tree being cap-
tured will be adjusted to be absolute relative to the root of the directory tree being captured. When
disabled (--norpfix), absolute symbolic links will be captured exactly as is.
The default behavior of wimcapture is equivalent to --rpfix. The default behavior of wimappend
is equivalent to --rpfix if reparse point fixups have previously been done on WIMFILE, otherwise
--norpfix.

In the case of a multi-source capture, (--source-list specified), passing --norpfix is recommended.
Otherwise, reparse point fixups will be disabled on all capture sources destined for non-root loca-
tions in the WIM image, while capture sources destined for the WIM root will get the default behav-
ior from the previous paragraph.

 

  • The default behavior of wimcapture is equivalent to --rpfix.
  • The default behavior of wimappend is equivalent to --rpfix if reparse point fixups have previously been done on WIMFILE
  • otherwise --norpfix.

 

On DMS capture Tab NoRpFix is preselected, and I think it should be unselected.

 

From wimlib Apply document:

 

 

--rpfix, --norpfix
Set whether to fix targets of absolute symbolic links (reparse points in Windows terminology) or
not. When enabled (--rpfix), extracted absolute symbolic links that are marked in the WIM image
as being fixed are assumed to have absolute targets relative to the image root, and therefore wimap-
ply prepends the absolute path to the extraction target directory to their targets. The intention is that
you can apply an image containing absolute symbolic links and still have them be valid after it has
been applied to any location.
The default behavior is --rpfix if any images in WIMFILE have been captured with reparse-point
fixups done. Otherwise, it is --norpfix.

 

  • The default behavior is --rpfix if any images in WIMFILE have been captured with reparse-point
  • fixups done.
  • Otherwise, it is --norpfix.

 

And as the default capture mode is --rpfix the usual apply mode will be --rpfix too, unless an image was captured with NoRpFix explicitly selected.  

 

On DMS options Tab NoRpFix is NOT preselected wich seems good to me.

 

From: https://docs.microso...ine-options-s14

 

 

/NoRpFix     Disables the reparse point tag fix. A reparse point is a file that contains a link to another file on the file system. If /NoRpFix is not specified, reparse points that resolve to paths outside the value specified by /ImageFile will not be captured.

 

Just same as your Tooltip.

 

  • I will assume on Dism Capture the default behavior is RpFix if NoRpFix is NOT explicitly selected.
  • And Apply will be same way unless NoRpFix was explicitly selected during Capture.

This seems also consistent with wimlib behaviour.

 

Then according with this info I think on DMS both tabs Capture and Options (related to apply) NoRpFix should be unselected by default.

 

Is this correct?

 

alacran


  • ReTokener likes this

#108 ReTokener

ReTokener

    Frequent Member

  • Developer
  • 234 posts

Posted 2 weeks ago

I found this explanation on technet  - default is without /NoRpFix.



#109 ReTokener

ReTokener

    Frequent Member

  • Developer
  • 234 posts

Posted 2 weeks ago

 

Then according with this info I think on DMS both tabs Capture and Options (related to apply) NoRpFix should be unselected by default.

 

Is this correct?

Yes I agree.

 

Best regards   T.


  • alacran likes this

#110 wimb

wimb

    Platinum Member

  • Developer
  • 2682 posts
  • Interests:Boot and Install from USB
  •  
    Netherlands

Posted 2 weeks ago

Because i am a wimboot beginner, i take small steps to understand the different stages.

 

A good way to start with WIMBOOT is to begin here and also read the Manual Attached File  VHD_WIMBOOT.pdf   696.57KB   32 downloads


  • ReTokener likes this

#111 alacran

alacran

    Gold Member

  • .script developer
  • 1173 posts
  •  
    Mexico

Posted 2 weeks ago

I wrote a recommended procedure to make manually by means of DMS your wimboot VHDs, http://reboot.pro/to...-4#entry213355 now we can use DMS to create the boot files/folders and latter use BootIce to only edit them as required.

 

Since DMS has been uptated to DismMountService_191122, now it includes on Extras menu an embeded litlle program BCDBootGUI, very usefull for creating directly from DMS and on a graphic mode the boot files and folders from/to the selected partitions, having it also the option to select the location (and then the version) of the BCDBoot.exe you want to use for this task, it is recommended to download GetWaikTools_v18.10.zip (as this downloads a Dism version bug free for capturing FFU images) easy way is using the link on Help menu >>>  Download DISM by GetWaikTools (JFX), then on that page find the link to old version to download it, just unpack it to DMS folder and run it from there.

 

When running GetWaikTools select ADK for Win 10 and Dism for Windows 10 to download the Dism files and also a few more files from the ADK including the mentioned BCDBoot.exe file, it is very useful to have this files/folders available on your DMS folder when running it from a WinPE as not all WinPE contain them (or the right version). See attached Pictures.

 

alacran

Attached Files


  • ReTokener likes this

#112 alacran

alacran

    Gold Member

  • .script developer
  • 1173 posts
  •  
    Mexico

Posted 2 weeks ago

Restoring a single partition or only some especific files/folders from an FFU image:

 

Restoring only some especific files or folders from an FFU image:

 

From my post: http://reboot.pro/to...e-3#entry213296

 

 

Then I mounted the FFU with DMS to a folder on my HD and only thing visible is Windows partition, the other two partitions do not appear (Yes, I have active since the source Wim and also on the running OS show all Hiden files, folders and drives and also unactivated Hide Protected files of OS), but on Windows Disk Management it is possible to assing a letter to each one of the partitions of the mounted FFU and this way all can be seen, good if we need to extract only some files/folders from a partition to a location on our HD, from the Mount folder only Windows remain visible, then removed the assigned letters and dismounted the FFU without making changes.

 

As said if we are looking for only some especific files or folders, after mounting the FFU image to a folder on our HD if we open that folder, we only see there the OS partition, all other are hiden, (Don't close DMS, just minimize it) on Disk Managament we can see all the partitions of the image we mounted but without any drive letter assigned, then we can assing a letter to lets say only our Documents partition (wich is not seen on mounting folder) to be able to see it from our OS as any other drive and just find the files/folders we are looking for and copy them wherever we want, after this on Disk Managament we unassing the previouly assigned letter and go back to DMS and dismount the FFU image without making changes to it, to keep our image intact.

 

Restoring a single partition from an FFU image is also possible:

 

I ran a test to probe this can be done. To make things easier the test was made on small VHDs:

 

Created a 3 GB fixed size Test-1.vhd, with 2 partitions first primary partition 1536 MB NTFS Active, labeled as 10x64-WB, second primary partition the remaining space NTFS formated labeled as Documents, Applied 10x64-WB.vhd Wimboot mode to first partition by means of DMS, copied some files/folders to second partition just to have some info into it, and made a FFU image, and dismounted the VHD,  and closed DMS.

 

Created a second 3 GB fixed size Test-2.vhd, with 2 partitions first primary partition 1536 MB NTFS Active, labeled as Win, second primary partition the remaining space NTFS formated labeled as Docs.

 

Without dismounting Test-2.vhd, ran DMS and mounted the FFU to Mount folder on internal HD, ran PartitionGuru and my internal HDs and also both VHDs were visible there, no matter Test-1.vhd didn't have any drive letters assigned on Disk Managament, then selected Documents partition on Test-1.vhd and cloned it to Docs partition on Test-2.vhd selecting the second from the 3 options available to keep partition layout, but only copy used sectors, it worked very fine, latter did same thing with first partition on both VHDs also selecting same cloning option.

 

After doing this I closed PartitionGuru and went back to DMS and dismounted the FFU image without making changes to it, to keep the image intact.

 

Then went to "This PC" and opened it and the two cloned partitions where available there with its original label names assigned on Test-1.vhd, opened both and all info was there.

 

So this probes without any dubt it is possible to extract and clone a single partition from an FFU image.

 

PartitionGuru Free: 4.9.5.508: https://www.eassos.c...onguru-free.php

 

MiniTool Partition Wizard Free v11.5: https://www.partitio...on-manager.html

 

NOTES:

 

PartitionGuru cloning requires the target partition to be formatted, seems best option to restore single partitions on our running PC.

 

MiniTool Partition Wizard requires the target partition to be free space (unformatted), seems best option to restore single partitions to another blank disk.

 

Haven't tested yet if MiniTool Partition Wizard requires some little adjusments to the procedure, but I'm sure it will work, as I have cloned (they use the term copy) ext4 partitions that are also not mounted (seen) on Windows.

 

Of course the disadvantaje of an FFU image compared with a WIM image, is the FFU image needs to have enought space to mount an FFU image of a big size disk, and the time required to do it.

 

alacran


  • ReTokener likes this

#113 ReTokener

ReTokener

    Frequent Member

  • Developer
  • 234 posts

Posted 2 weeks ago

Recent finding:

Capturing GPT-disk to FFU creates file ~exactly double the size than capturing a MBR-disk with same content.

test 1:

MBR disk 55GB with ~9.5GB data -> captured to FFU results in 5.3GB FFU file.

converted disk to GPT.

test 2:

GPT disk 55GB with ~9.5GB data -> captured to FFU results in 10.6GB FFU file.

 

is there a mistake in my experiment which leads to wrong result? Or is the result according to any rule?

 

regards   T.

 



#114 cdob

cdob

    Gold Member

  • Expert
  • 1449 posts

Posted 2 weeks ago

How does a capture FFU handle zero sectors?

 

Did you 'Zero free space (good for virtual disk optimization)' first?

https://docs.microso...wnloads/sdelete


  • ReTokener likes this

#115 ReTokener

ReTokener

    Frequent Member

  • Developer
  • 234 posts

Posted 2 weeks ago

 

cdob:

Did you 'Zero free space (good for virtual disk optimization)' first?

thank you cdob :thumbsup:

"zero freespace" has reduced the resulting file to the ~same amount as captured MBR-disk.

 

first I tried formatting the "payload"-drive but still the resulting file was too large.

 

the strange thing was that the FFU file was small again when I reset the (EDIT : uncleaned GPT) drive to MBR and captured then.

 

best regards   T.



#116 ReTokener

ReTokener

    Frequent Member

  • Developer
  • 234 posts

Posted 2 weeks ago

sorry I made a mistake on my last post.

correct is

the strange thing was that the FFU file was small again when I reset the (EDIT : uncleaned GPT) drive to MBR and captured then.

 

 

T.





Also tagged with one or more of these keywords: dism

1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users