Jump to content











Photo
* * * * * 4 votes

wimlib, with ImageX implementation

wim imagex winpe boot

  • Please log in to reply
365 replies to this topic

#301 martinb

martinb

    Newbie

  • Members
  • 15 posts
  •  
    Netherlands

Posted 27 February 2015 - 08:26 AM

I will make some more tests with the 2 versions and will report the details

This time i will run them on the same shadow, just to be sure if the source is 100% identical.

 

 

 

Will give a update in a few days.


Edited by martinb, 27 February 2015 - 08:26 AM.


#302 behdadsoft

behdadsoft
  • Members
  • 2 posts
  •  
    Iran

Posted 16 March 2015 - 08:46 AM

Hi.

 

I have windows 8.1 32 & 64Bit  with update 1.for decrease size and write on DVD 5 I converted Install.wim to two install.esd(32 & 64Bit). Now I want merge this two file to one install.esd but can't find any command for do this work. 

 

Please guide Me.

 

Thanks.



#303 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 14130 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 16 March 2015 - 10:04 AM

Hi.

 

I have windows 8.1 32 & 64Bit  with update 1.for decrease size and write on DVD 5 I converted Install.wim to two install.esd(32 & 64Bit). Now I want merge this two file to one install.esd but can't find any command for do this work. 

 

Please guide Me.

 

Thanks.

Just for the record, the "possibly DETAILED":

http://www.msfn.org/...erge-esd-files/

has been lost over the internet connection....  :whistling:

 

:duff:

Wonko



#304 synchronicity

synchronicity

    Frequent Member

  • Advanced user
  • 165 posts
  •  
    United States

Posted 16 March 2015 - 06:38 PM

If by "merge" you mean "create one file that has all the images in either of the source files", then you can use 'wimlib-imagex export'.  Just export all the images from one file into the other.  Maybe something like this:

wimlib-imagex export 1.esd all 2.esd --solid --recompress --rebuild

Note that this will recompress everything.  If you could export directly from the original WIM files instead this would avoid unnecessary work.



#305 martinb

martinb

    Newbie

  • Members
  • 15 posts
  •  
    Netherlands

Posted 16 March 2015 - 08:26 PM

Hello,

Sorry for the delay, but here are the results between the old and new version
Like you already predicted, i probably made a error on the first test.
I was running in a live environment and probably someone was cleaning his profile while i was running the software


Anyhow, i made a run from the same shadow and i got:

I created a image from a running terminal-server

The time on the old version is 1:08:31
The time on the new version is 0:55:48

The size of the old version is 32.988.797.573 bytes
The size of the new version is 32.966.794.308 bytes
 

Detailed info on the 2 files

WIM Information:
----------------
Path:           \\lacie-5big-2\public\ts-02\201502271849_FULL_M.wim
GUID:           0x6f4571580e9c11c2353b3a7ab6fc67dc
Version:        68864
Image Count:    1
Compression:    LZX
Chunk Size:     32768 bytes
Part Number:    1/1
Boot Index:     0
Size:           32966793476 bytes
Integrity Info: no
Relative path junction: yes
Pipable:        no

Available Images:
-----------------
Index:                  1
Name:                   c:\
Description:
Directory Count:        31759
File Count:             215758
Total Bytes:            63242224039
Hard Link Bytes:        4483005796
Creation Time:          Fri Feb 27 17:49:22 2015 UTC
Last Modification Time: Fri Feb 27 17:51:04 2015 UTC
WIMBoot compatible:     no


WIM Information:
----------------
Path:           \\lacie-5big-2\public\ts-02\201502271849_FULL_M.wim_2
GUID:           0x3d297d257135a412c5273c3daa8250d7
Version:        68864
Image Count:    1
Compression:    LZX
Chunk Size:     32768 bytes
Part Number:    1/1
Boot Index:     0
Size:           32988796741 bytes
Integrity Info: no
Relative path junction: yes
Pipable:        no

Available Images:
-----------------
Index:                  1
Name:                   c:\
Description:
Directory Count:        31759
File Count:             215758
Total Bytes:            63242224039
Hard Link Bytes:        4483005796
Creation Time:          Fri Feb 27 18:45:11 2015 UTC
Last Modification Time: Fri Feb 27 18:46:29 2015 UTC
WIMBoot compatible:     no

I'm still very happy with the significant time decrease.



#306 behdadsoft

behdadsoft
  • Members
  • 2 posts
  •  
    Iran

Posted 17 March 2015 - 08:25 AM

thanks synchronicity for help.



#307 chenall

chenall

    Member

  • Members
  • 60 posts
  •  
    China

Posted 30 April 2015 - 04:04 AM

There has bug in wimboot function.(windows 7 with wof driver).Without wof driver it works

 

I think should not use wof drive when the operating system is not higher than windows 8.1(>=6.3)

E:\wimboot\wimlib>wimlib-imagex.exe apply g:\wimboot.wim  1 r:\ --wimboot
Applying image 1 ("Win7Wimboot") from "g:\wimboot.wim" to directory "r:\"
[WARNING] FSCTL_SET_EXTERNAL_BACKING failed (err=1314); data was 48 bytes:
010000000100000001000000000000000000000000000000fe878c289c59f085d8edf73cc634492c
e6bb328100000000
[WARNING] Retrying after 100ms...
[WARNING] FSCTL_SET_EXTERNAL_BACKING failed (err=1314); data was 48 bytes:
010000000100000001000000000000000000000000000000fe878c289c59f085d8edf73cc634492c
e6bb328100000000
[WARNING] Retrying after 100ms...
[WARNING] FSCTL_SET_EXTERNAL_BACKING failed (err=1314); data was 48 bytes:
010000000100000001000000000000000000000000000000fe878c289c59f085d8edf73cc634492c
e6bb328100000000
[WARNING] Retrying after 100ms...
[WARNING] FSCTL_SET_EXTERNAL_BACKING failed (err=1314); data was 48 bytes:
010000000100000001000000000000000000000000000000fe878c289c59f085d8edf73cc634492c
e6bb328100000000
[WARNING] Too many retries; returning failure
[ERROR] "r:\\Program Files\Common Files\Services\verisign.bmp": Couldn't set WIM
Boot pointer data (err=1314):
ERROR: Exiting with error code 75:
       Failed to set WIMBoot pointer data.
E:\wimboot\wimlib>ver
 
Microsoft Windows [版本 6.1.7601]
 
Thanks!!

Edited by chenall, 30 April 2015 - 04:07 AM.


#308 misty

misty

    Silver Member

  • Developer
  • 879 posts
  •  
    United Kingdom

Posted 30 April 2015 - 01:48 PM

The discussion started by stangm's post has been split from this topic and moved to Create a windows system from scratch using Linux

Regards,

Misty

#309 synchronicity

synchronicity

    Frequent Member

  • Advanced user
  • 165 posts
  •  
    United States

Posted 30 April 2015 - 03:17 PM

chenall, were you running wimlib-imagex as an Administrator?



#310 chenall

chenall

    Member

  • Members
  • 60 posts
  •  
    China

Posted 01 May 2015 - 01:07 AM

chenall, were you running wimlib-imagex as an Administrator?

 

Yes! 

 

windows 7 sp1 or WIN7PE with same error.

 

When wof  driver not  loaded it displays a warning, but it works fine

[WARNING] WOF driver is not available; updating WimOverlay.dat directly.

This is easy to reproduce, install wof  driver on win7 will get this error.



#311 Abbodi

Abbodi

    Newbie

  • Members
  • 20 posts
  •  
    Saudi Arabia

Posted 05 May 2015 - 02:40 AM

Hi

 

While Dism can read the info out of encrypted ESD file (most likely by reading the XML data near the end of file), wimlib gives the Error that the file is encrypted

can wimlib have the same dism function and allow/show the info using the xml data? of course the warning/error about encryption still shown

 

this might seems a silly request, so i apologies if so :)

thanks



#312 synchronicity

synchronicity

    Frequent Member

  • Advanced user
  • 165 posts
  •  
    United States

Posted 05 May 2015 - 03:26 AM

@Abbodi

 

That would be possible, but not easily.  wimlib's API is designed such that you need to "open" the WIM file, using the wimlib_open_wim() function, before you can query the XML data or any other metadata.  And I think it is usually impossible for that to run to completion on encrypted WIMs.  So I don't think there is a clean way to implement it with the current design.



#313 Abbodi

Abbodi

    Newbie

  • Members
  • 20 posts
  •  
    Saudi Arabia

Posted 05 May 2015 - 05:37 AM

Thanks for the clarify.

 

Regards.



#314 cdob

cdob

    Gold Member

  • Expert
  • 1373 posts

Posted 11 May 2015 - 09:33 PM

Given a tablet with a 32 gb disk and install.wim/custom.wim at wimboot mode:
https://technet.micr...y/dn594399.aspx
I like to do a manufacturer restore manually
 

D:\ESD\bin\bin64>wimlib-imagex.exe export custom.wim 1 new.wim
[ERROR] "\Windows\System32\WSManHTTPConfig.exe": stream not found
ERROR: If this is a delta WIM, use the --ref argument to specify the WIM(s) on which it is based.

Thanks for the error message, a useful error message is seldom.
Lesson learned, let's continue.

Next
wimlib-imagex.exe export custom.wim 1 new.wim --ref install.wim
wimlib-imagex.exe apply new.wim 1 F:\ --wimboot
This works, space occupiet 225 mb. I'm happy.

Directly install.wim/custom.wim
wimlib-imagex.exe apply custom.wim 1 F:\ --ref install.wim --wimboot
This works, space occupiet 4.5 gb.
I'm happy still, but wonder: what's going one?

#315 synchronicity

synchronicity

    Frequent Member

  • Advanced user
  • 165 posts
  •  
    United States

Posted 11 May 2015 - 09:48 PM

@cdob

 

Applying an image from a multi-file WIM using the --wimboot option is not really supported.  With the current code, only files whose data was located in the WIM file that includes the image metadata (in your case, "custom.wim") will be extracted as externally backed.  All other files (in your case, those whose data is located in "install.wim") will be extracted as full files.

 

I might be able to support multiple backing WIMs per extraction in a future release.  I hadn't really expected that people would want that support, but you're not the first person to ask.



#316 synchronicity

synchronicity

    Frequent Member

  • Advanced user
  • 165 posts
  •  
    United States

Posted 12 May 2015 - 04:49 AM

@cdob

 

I've just added support for multiple backing WIMs for "WIMBoot mode" extractions to wimlib v1.8.1-BETA4.  Feel free to try it.  There are no additional options needed --- it should work with the command line you posted.



#317 synchronicity

synchronicity

    Frequent Member

  • Advanced user
  • 165 posts
  •  
    United States

Posted 17 May 2015 - 10:49 PM

wimlib v1.8.1 has been released.  From the NEWS file:

 

 

    Fixed a bug in the LZX decompressor: malicious input data could cause
    out of bounds writes to memory (since wimlib v1.2.2).

    The output of the 'wiminfo' command now consolidates various boolean
    flags (such as "Relative path junction") into a single line.

    A file can now have both an unnamed data stream ("file contents") and a
    reparse point stream.  Such files can exist as a result of the use of
    certain Windows features, such as offline storage, including "OneDrive".
    wimlib will now store and restore both streams on Windows as well as in
    NTFS-3g mode.  Microsoft's WIMGAPI also has this behavior.

    On Windows, named data streams of encrypted files are no longer stored
    twice in WIM archives.

    On Windows, named data streams are now correctly extracted to existing
    "readonly" directories.  Before, an error would be reported.

    On Windows, it is now possible to do a "WIMBoot mode" extraction with
    non-standalone WIMs such as delta WIMs.

    On Windows, when doing an extraction in "WIMBoot mode", files larger
    than 4 gigabytes are now never extracted as externally backed.  This
    works around a bug in Microsoft's "WOF" driver.

    The '--enable-verify-compression' configure option has been removed.  If
    you want to verify a WIM file, use the 'wimverify' program.

    The way the "file count", "directory count", "total bytes", and "hard
    link bytes" image statistics (stored in the WIM XML data) is calculated
    has been slightly changed.

    In mounted WIM images, the disk usage provided for each file (st_blocks)
    is now the compressed size rather than the uncompressed size.

    The performance of the NTFS-3g and Windows capture modes has been
    slightly improved.

    On UNIX-like systems, symbolic links whose targets contain the backslash
    character are now handled correctly (losslessly).
 



#318 comcc

comcc
  • Deactivated
  • 4 posts
  •  
    United States

Posted 22 July 2015 - 08:14 PM

@sychronicity (and others involved) I ran across this link: http://answers.micro...e-d3b9118a8864?on ZDNet today, and wondered if you knew about this?

 

I guess it's good to be appreciated, even if it IS anonymously ! Not a word of credit to anyone else in this article. Andre Da Costa might be a Microsoft MVP, but I'm certainly not impressed by his ethics.

 

Thank you so much for all of your hard work on this! You can be proud of what you and the others who have been involved with this have accomplished.



#319 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 14130 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 23 July 2015 - 11:56 AM

I guess it's good to be appreciated, even if it IS anonymously ! Not a word of credit to anyone else in this article. Andre Da Costa might be a Microsoft MVP, but I'm certainly not impressed by his ethics.

JFYI the guy has a certain fame about his posts being let's say "far from accurate/complete/correct or strongly opinionated (when not downright completely wrong)":

http://www.msfn.org/...n-w10-tp-forum/

 

In this specific case the readme.txt does however still contain:

 

# Credits #

qad - decryption program
synchronicity - wimlib
murphy78 - original script
nosferati87, NiFu, s1ave77, and any other MDL forums members contributed in the ESD project

 

Though he seemingly plagiarized a series of tweets by Wzor on 18th March  and, on the other hand, his post has been plagiarized flatly (without giving credits to anyone), *like*:

http://pureinfotech....sing-esd-image/

http://www.beyondwin...dual-boot-by-m/

 

:duff:

Wonko



#320 synchronicity

synchronicity

    Frequent Member

  • Advanced user
  • 165 posts
  •  
    United States

Posted 27 July 2015 - 07:03 PM

For those who are interested:

 

As the file upload service on SourceForge continues to remain down, I've made wimlib-v1.8.2-BETA2 available at https://github.com/e...wimlib/releases.

 

This latest beta includes experimental support for applying WIM images in "compact mode", i.e. compressing the extracted files with Windows 10 "System Compression".  It should be similar to DISM's new "/compact" flag.

 

Also a reminder that wimlib v1.8.0 and later can create slightly smaller ESD files (a.k.a. solid LZMS compressed WIM files) than DISM, and slightly faster.  I haven't heard of many people using this capability, but it's there for those who want it.



#321 synchronicity

synchronicity

    Frequent Member

  • Advanced user
  • 165 posts
  •  
    United States

Posted 02 August 2015 - 11:12 PM

Hello,

 

I am currently in the process of migrating wimlib off SourceForge and to its own dedicated website.

 

The website can be accessed at http://wimlib.net.

 

For now it's quite bare-bones but I will be updating it over the next few days.

 

Let me know if you have suggestions for the website, or if you can't access it for some reason.

 

- synchronicity



#322 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 14130 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 03 August 2015 - 08:22 AM

The website can be accessed at http://wimlib.net.

 

For now it's quite bare-bones but I will be updating it over the next few days.

Well, it might be bare-bones, but it is blazingly fast in loading, is clearly centered on contents rather than (esoteric) looks, thank goodness it does not open on an unrelated centered stock image and stupidly large buttons leading to "scroll down anchors" on the same stupidly long page interspersed with more unrelated stock images.

In one word it's perfect :yahoo: to host a "serious" project (as opposed to an "app" or some "vapourware").

 

:duff:

Wonko



#323 misty

misty

    Silver Member

  • Developer
  • 879 posts
  •  
    United Kingdom

Posted 03 August 2015 - 12:48 PM

Hi Eric,

Nice site - I like the layout and I'm pleased to see that wimlib has it's own home. Haven't reported in for a while so this seems like a good opportunity to say thanks for this great tool - it's still (by far) my preferred tool for managing .wim files. I've been using version 1.8.1. for recent tests - performance is good and it seems very stable. Nice to see the tool is in such active development too - well done!

Some thoughts on the new site. Documentation is good - there's such a wide range of options that some simple examples would be useful. Suggestions -
  • Injecting winpeshl.ini with additional files (e.g. bblean) to create a customised WinPE - very simple to do. This approach is used in my own Mini-WinFE/MistyPE projects (Winbuilder based) and also I believe in Erwan.l's QuickPE (batch file based)
  • Expanding on the above - first extract registry hive(s) from WinPE > mount reg hive(s) > apply changes > unmount hive(s) > inject back into WinPE with any additional files. Slightly more advanced, but better highlights wimlib usage.
Only other thing I think should be added is expanding on "...automatically deduplicates all file contents..." - Single Instance Storage is for me one of the main advantages of the .wim format. I don't think this is really explained - maybe mention .wim as an incremental backup solution for OS and file archiving as examples.

Anyway, great work.

Regards,

Misty

#324 synchronicity

synchronicity

    Frequent Member

  • Advanced user
  • 165 posts
  •  
    United States

Posted 04 August 2015 - 12:42 AM

Thanks for the comments.  @Wonko --- yes, fast and contents-oriented websites are nice.  The trend these days is to bloat websites with ads, images, and JavaScript code/libraries.  @misty --- I definitely agree that there should be more examples in the documentation, and that single instance storage should be emphasized more.



#325 misty

misty

    Silver Member

  • Developer
  • 879 posts
  •  
    United Kingdom

Posted 14 August 2015 - 04:40 PM

@synchronicity

I came across a reference to WIMBOOT having been deprecated in Windows 10 - see here for a bit more info.

Interestingly I was able to create a Windows 10 WIMBOOT on a USB HDD last night using wimlib-imagex!

Any thoughts?

Regards,

Misty




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users