--compact [WARNING]'s

Comments, questions, bug reports, etc.
Post Reply
misty
Posts: 12
Joined: Tue Aug 18, 2015 10:23 am

--compact [WARNING]'s

Post by misty »

Hi synchronicity,

Just been playing around with the new (and experimental) --compact option. Test system was a Windows 7 installation with the wofadk.sys driver added. I captured this as a .wim file, then applied this new wim using the --compact switch.

When applying the .wim using a Windows 10 based WinPE no errors/warnings were displayed.

When applying the same .wim using WinPE 3.1 (and also Windows 7), lots of warnings were displayed.

The "Creating files:" stage finished without error. Output from creating files stage

Code: Select all

Applying image 1 ("Windows 7 WIMBOOT Test") from "E:\WOFADK_Tests\X61_test2.wim"
 to directory "D:\"
Creating files: 31000 of 57831 (53%) done
Output from Extracting File Data stage -

Code: Select all

Applying image 1 ("Windows 7 WIMBOOT Test") from "E:\WOFADK_Tests\X61_test2.wim"
 to directory "D:\"
Creating files: 57831 of 57831 (100%) done
[WARNING] "D:\\ProgramData\Microsoft\Windows\WER\ReportQueue\NonCritical_x86_75b
11f60c67a23d08b6a59ab85bfd23d6f45b0b1_cab_07b0f314\Report.wer": Failed to compre
ss extracted file using System Compression (err=317): The system cannot find mes
sage text for message number 0x%1 in the message file for %2
[WARNING] "D:\\ProgramData\Microsoft\Windows\WER\ReportQueue\NonCritical_x86_f74
c622fd971a6513349e3af22655fffcb279f_cab_06c4f3fe\Report.wer": Failed to compress
 extracted file using System Compression (err=317): The system cannot find messa
ge text for message number 0x%1 in the message file for %2
[WARNING] "D:\\Windows\winsxs\x86_microsoft-windows-i..libraries.resources_31bf3
856ad364e35_6.1.7600.16385_en-us_50108a601c8fd1e2\appcmd.exe.mui": Failed to com
press extracted file using System Compression (err=317): The system cannot find
message text for message number 0x%1 in the message file for %2
[WARNING] "D:\\Windows\winsxs\x86_microsoft-windows-i..libraries.resources_31bf3
856ad364e35_6.1.7600.16385_en-us_50108a601c8fd1e2\iisreset.exe.mui": Failed to c
ompress extracted file using System Compression (err=317): The system cannot fin
d message text for message number 0x%1 in the message file for %2
[WARNING] "D:\\Windows\winsxs\x86_microsoft-windows-i..libraries.resources_31bf3
856ad364e35_6.1.7600.16385_en-us_50108a601c8fd1e2\iisrstas.exe.mui": Failed to c
ompress extracted file using System Compression (err=317): The system cannot fin
d message text for message number 0x%1 in the message file for %2
[WARNING] "D:\\Windows\winsxs\x86_microsoft-windows-i..libraries.resources_31bf3
856ad364e35_6.1.7600.16385_en-us_50108a601c8fd1e2\iissetup.exe.mui": Failed to c
ompress extracted file using System Compression (err=317): The system cannot fin
d message text for message number 0x%1 in the message file for %2
[WARNING] "D:\\Windows\winsxs\x86_microsoft-windows-i..lprovider.resources_31bf3
856ad364e35_6.1.7600.16385_en-us_90915dfee6dde798\AppHostNavigators.dll.mui": Fa
iled to compress extracted file using System Compression (err=317): The system c
annot find message text for message number 0x%1 in the message file for %2
[WARNING] "D:\\Windows\winsxs\x86_microsoft-windows-i..lprovider.resources_31bf3
856ad364e35_6.1.7600.16385_en-us_90915dfee6dde798\XPath.dll.mui": Failed to comp
ress extracted file using System Compression (err=317): The system cannot find m
essage text for message number 0x%1 in the message file for %2
[WARNING] "D:\\Windows\winsxs\x86_microsoft-windows-i..ce-server.resources_31bf3
856ad364e35_6.1.7600.16385_en-us_288c39308ca69336\CISVC.EXE.mui": Failed to comp
ress extracted file using System Compression (err=317): The system cannot find m
essage text for message number 0x%1 in the message file for %2
[WARNING] Suppressing further warnings about System Compression failures.
Extracting file data: 367 MiB of 4955 MiB (7%) done
Despite the warnings, the operating system booted without any noticable issues.

There was a marginal difference in used space reported by right clicking on the running operating system's drive and selecting properties -
* 6.71 GB - when applied using a Windows 10 based WinPE
* 6.73 GB - when applied using a Windows 7 based WinPE

Any thought on what is causing these warnings? I have no idea whether this is a wofadk.sys issue or wimlib-imagex.

Regards,

Misty
synchronicity
Site Admin
Posts: 474
Joined: Sun Aug 02, 2015 10:31 pm

Re: --compact [WARNING]'s

Post by synchronicity »

Thanks for the report. I'm not 100% what's happening but it looks like there is a native error code (NTSTATUS) being returned, probably by wofadk, which isn't mapped to a Win32 error code on Windows 7. I'm guessing this is the "Compressing this object would not save space." error code, which isn't actually an error but is an expected case which is supposed to be ignored.

If this theory is correct, the solution will be to have wimlib call the native function NtFsControlFile() insteaf of the Win32 function DeviceIoControl(), then check for the native error code instead of the Win32 error code.

I'll post here when this is in a new build --- until then I think you are safe ignoring these warnings.
synchronicity
Site Admin
Posts: 474
Joined: Sun Aug 02, 2015 10:31 pm

Re: --compact [WARNING]'s

Post by synchronicity »

I've implemented the above-mentioned solution in wimlib v1.8.3-BETA2. Feel free to test it if you have a chance.
Post Reply