Hi alacran, to install compact mode from Windows 7 you need the WofADK driver from latest ADK to be installed.

 

Not sure what you mean with requirements, there aren't any set for compact mode.

 

I have WofADK driver in C:\Program Files\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\x86\DISM\wofadk.sys

Isn't it installed in that location?, Do I need to put it in system32?, Do I have to do something else?

 

I had the idea that in order to make a compact mode install we need to mark the check box near to wimboot and I have done it during all my deployments, I guess that's why .wim had to be in same disk, so from your post I understand it is not necesary to mark that check box, Is it right?

 

Best Regards

Edited June 24, 201511 yr by alacran

Location of the driver does not matter, but you can check if it's correctly installed by "net start wofadk" from admin command prompt.

 

But also important make sure you also have updated the adk wimgapi.dll in the tools folders.

 

Compact mode is currently only avalible via command line (NT6 -compact)

The switch overrides all other options like wimboot.

@ JFX

 

Yes adk wimgapi.dll is in the tools folders (x86 and x64) it is v10.0.10075.0, downloaded first time I ran WinNTSetup 3.80 RC3 just to download required files as usual.

 

The way I'm running it is this: I create a shortcut to WinNTSetup_x64.exe and open it with right button\properties and in the first line just add: " NT6 -compact" without quotes, then it starts in GUI, from the Win10x64 VHD it is working flawlessly, but not from Win7x86 or Win7x64 on HDD, it opens ok but can't apply the .wim, of course when in x86 I use WinNTSetup_x86.exe NT6 -compact

 

"net start wofadk" command gives me "command not reconized". I think wofadk is not properly installed on my win7's,  but i don't know how to do it yet. any ideas?

 

Best Regards

Edited June 25, 201511 yr by alacran

Yes, looks like the driver is not installed. Normally the adksetup will write the following registry options.

Or, if you use GWT, "WimMountInstall.exe /install" can be used.

 

 

Windows Registry Editor Version 5.00

 

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\WofAdk]

"DebugFlags"=dword:00000000

"DependOnService"=hex(7):46,00,6c,00,74,00,4d,00,67,00,72,00,00,00,00,00

"Discription"="WofAdk Mini-Filter Driver"

"DisplayName"="WofAdk"

"ErrorControl"=dword:00000001

"Group"="FSFilter Compression"

"ImagePath"=hex(2):5c,00,3f,00,3f,00,5c,00,43,00,3a,00,5c,00,50,00,72,00,6f,00,\

  67,00,72,00,61,00,6d,00,20,00,46,00,69,00,6c,00,65,00,73,00,20,00,28,00,78,\

  00,38,00,36,00,29,00,5c,00,57,00,69,00,6e,00,64,00,6f,00,77,00,73,00,20,00,\

  4b,00,69,00,74,00,73,00,5c,00,31,00,30,00,5c,00,41,00,73,00,73,00,65,00,73,\

  00,73,00,6d,00,65,00,6e,00,74,00,20,00,61,00,6e,00,64,00,20,00,44,00,65,00,\

  70,00,6c,00,6f,00,79,00,6d,00,65,00,6e,00,74,00,20,00,4b,00,69,00,74,00,5c,\

  00,44,00,65,00,70,00,6c,00,6f,00,79,00,6d,00,65,00,6e,00,74,00,20,00,54,00,\

  6f,00,6f,00,6c,00,73,00,5c,00,61,00,6d,00,64,00,36,00,34,00,5c,00,44,00,49,\

  00,53,00,4d,00,5c,00,77,00,6f,00,66,00,61,00,64,00,6b,00,2e,00,73,00,79,00,\

  73,00,00,00

"AutoAttach"=dword:00000000

"Start"=dword:00000003

"SupportedFeatures"=dword:00000003

"Tag"=dword:00000002

"Type"=dword:00000002

 

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\WofAdk\Instances]

"DefaultInstance"="WofAdk Instance"

 

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\WofAdk\Instances\WofAdk Instance]

"Altitude"="40730"

"Flags"=dword:00000000

 

 

After a restart the service will be available.

 

BTW, the AutoAttach and Start options are set different from the normal wof driver from Windows 8/10.

Most users will properly want to change them.

I got this installing win10 Preview

 

I ran the install from XP. This is build 10159. Input was a decrypted esd. When booting, the OS it goes to a recovery screen saying the system needs to be repaired because there is something wrong with the BCD. I looked at the BCD and it doesn't have any entries in it. I had to manually create a BCD so the OS would boot.

Edited July 3, 201511 yr by click-click

I see someone had this problem before and it was related to XP. BCDBoot XP compatibility was put back in

as stated here. Has XP support for this been removed again?

 

I'm using V3.7.9. I know XP is EOL, but I'm using the POSReady 2009 version which doesn't go EOL until 2016

Edited July 3, 201511 yr by click-click

Still getting same error using XP with v3.8. Installing Win10 using Win7 doesn't give you that error.

BCDboot.exe isn't fully compatible with Windows XP, so I use some workarounds to get it working.

Properly one is causing that problem now with win10.

Version 3.8.1 is ready and should fix WinXP related problems.

I hope it wasn't too much work. I would have accepted 'no longer supported' too.  Thanks ...

 

BTW, does WinNTSetup support upgrading on top of an  installed system? For example, upgrading

a Win10 build  to a newer Win10 build without doing a clean install. All of my WinNTSetup procedures

till now have been fmt -> install fresh, so I 'm not sure if upgrading is supported.

Thank you very much , the program is great! Good luck and all the best ! ..

@click-click

Wasn't much work, just took a bit time to test it with all sources the fix was meant for.

I try to keep XP supported as long as possible.

Please continue reporting any problem you notice.

 

Nope, upgrading an installation isn't possible with WinNTSetup.

 

 

@Ozi

You're welcome!

Edited July 16, 201511 yr by JFX

So quiet here

 

What about this tweak for Windows 10:

Windows Registry Editor Version 5.00[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\System]"DisableLogonBackgroundImage"=dword:00000001

Only seems to work when you have the latest updates (incl. kb3074678 and kb3074686).

Hi, JFX,

Unfortunately 3.8.1.1 wont start under Win 10.0.0.166

3.8 works like a charm, but 3.8.1.1 starts and stop. Both x86 and x64.

Just for info. I'll continue to use 3.8 till next edition.

Greetings

@Atari800XL

Not so sure, about adding tweaks for Win10.

There would be so many ones, but there is not much space in th GUI left.

 

@belivakov

Hmm, works nice here, running on Windows 10 RTM, maybe a Preview bug?