wofadk.sys Support?

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

wofadk.sys Support?

Post by misty »

@synchronicity
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 -
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.
My own attempt to apply using the --wimboot switch whilst running wimlib-imagex from a WinPE 3.1 build resulted in the following errors -
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.
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).

Is using wofadk.sys as opposed to the original wof.sys supported in wimlib? And if not, are you considering adding support.

Regards,

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

Re: wofadk.sys Support?

Post by synchronicity »

Hi,

I have no idea why this doesn't work.

I've had a similar problem reported once before, and it was stated that it occurred even when wimlib-imagex was run as an Administrator.

I don't currently have an easy way to reproduce this --- maybe you could link to the boot.wim for a Windows PE that reliably reproduces the problem?
JFX
Posts: 40
Joined: Tue Aug 18, 2015 3:59 pm

Re: wofadk.sys Support?

Post by JFX »

Hi,

the problem is a missing privilege.

Wimgapi request following privileges before it start applying a WIM file.

SeSecurityPrivilege
SeTakeOwnershipPrivilege
SeBackupPrivilege
SeRestorePrivilege
SeManageVolumePrivilege

At least the last one is missing in wimlib apply.
misty
Posts: 12
Joined: Tue Aug 18, 2015 10:23 am

Re: wofadk.sys Support?

Post by misty »

@synchronicity
FYI, I also posted about this error on the WinNTSetup thread at MSFN (see post #1269 - #1271).

@JFX
Thanks for offering your insight here too.

@everyone
Now need to rule out whether this is an issue with my WinPE build, or wimlib, or my wofadk.sys settings. Can't do much for a few days as I'm on holiday and have limited PC access.

Regards,

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

Re: wofadk.sys Support?

Post by synchronicity »

@JFX

Yes, I was wondering whether the "privilege not held" error code is real or just a red herring. Unfortunately, I've had reports of the FSCTL_SET_EXTERNAL_BACKING ioctl failing with a completely irrelevant error code before, so I have to be a little careful.

wimlib acquires all the privileges you listed except for SeManageVolumePrivilege, as you pointed out. I'll see if I can find out more about whether this privilege is really needed. It would be strange (but plausible) that it would be required when using wofadk.sys but not when using wof.sys.
synchronicity
Site Admin
Posts: 472
Joined: Sun Aug 02, 2015 10:31 pm

Re: wofadk.sys Support?

Post by synchronicity »

Hi,

wimlib v1.8.2-BETA4, which I just posted, will acquire SeManageVolumePrivilege.

Try it and see if you still get this error or not.

- synchronicity
misty
Posts: 12
Joined: Tue Aug 18, 2015 10:23 am

Re: wofadk.sys Support?

Post by misty »

@synchronicity
Great (and fast!) work. The new beta resolved this issue. I'm currently writing this on a wimboot Windows To Go - the installation was completed using a WAIK WinPE 3.1 build to run wimlib-imagex - the only modifications made to WinPE were the addition of wofadk.sys and the required registry settings.

Many thanks.

p.s. Thanks also to JFX
Post Reply