Firstly - I'm liking the new site.
Secondly - wimlib-imagex continues to impress me. I have mentioned this elsewhere - wimlib is my preferred tool for managing .wim files and is IMNSHO superior to the Microsoft tools. And it's in active development and redistributable.
Thirdly - now that I've buttered you up, on to a request.
I've come across references to a new driver included in the ADK for Windows 10 - wofadk.sys. There are reports of wimlib being able to apply a .wim file in wimboot/compact mode using this driver, including a post by JFX on the wimlib sourceforge site -
here -
My own attempt to apply using the --wimboot switch whilst running wimlib-imagex from a WinPE 3.1 build resulted in the following errors -There is a new driver in the Windows 10 ADK called "WofADK".
After starting and attaching it to the destination volume,
wimlib can apply in wimboot and compact mode on Windows 7 and 8.x, too.
The wofadk service appeared to be running ok in WinPE - the registy settings in a post by JFX (here) were added to my offline WinPE (registry settings amended - start=0 and AutoAttach=1).Applying image 1 ("32-bit Windows 8.1 Enterprise (wimboot)") from "I:\wimboot_x8
6.wim" to directory "I:\"
[WARNING] FSCTL_SET_EXTERNAL_BACKING failed (err=1314); data was 48 bytes:
0100000001000000010000000000000000000000000000005ba93c9db0cff93f52b521d7420e43f6
eda2784f00000000
[WARNING] Retrying after 100ms...
[WARNING] FSCTL_SET_EXTERNAL_BACKING failed (err=1314); data was 48 bytes:
0100000001000000010000000000000000000000000000005ba93c9db0cff93f52b521d7420e43f6
eda2784f00000000
[WARNING] Retrying after 100ms...
[WARNING] FSCTL_SET_EXTERNAL_BACKING failed (err=1314); data was 48 bytes:
0100000001000000010000000000000000000000000000005ba93c9db0cff93f52b521d7420e43f6
eda2784f00000000
[WARNING] Retrying after 100ms...
[WARNING] FSCTL_SET_EXTERNAL_BACKING failed (err=1314); data was 48 bytes:
0100000001000000010000000000000000000000000000005ba93c9db0cff93f52b521d7420e43f6
eda2784f00000000
[WARNING] Too many retries; returning failure
[ERROR] "I:\\BOOTNXT": Couldn't set WIMBoot pointer data (err=1314): A required
privilege is not held by the client
ERROR: Exiting with error code 75:
Failed to set WIMBoot pointer data.
Is using wofadk.sys as opposed to the original wof.sys supported in wimlib? And if not, are you considering adding support.
Regards,
Misty