JFX

Version 3.8.1 is ready and should fix WinXP related problems.

Updated to download the WIn10 RTM ADK tools.

If winpeshl.exe doesn't find a winpeshl.ini file it will start windows setup by running %SystemDrive%\setup.exe.

I'm not aware of any new W10 ADK versions. For the public there were only 2 this year. Maybe users of the insider program got more?

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.

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. 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.

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.

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.

Was a Rar5 archive, downgraded now to v4.

Okay, RC3 will close, if the reboot timeout hits or the button is pressed.

There would be some ways to force a winpe to reboot, but I would not like to integrate these. For example killing some of the critical processes, starting by your defined CmdLine in HKEY_LOCAL_MACHINE\SYSTEM\Setup Better to find out why 'wpeutil reboot' don't work.

Yes, I mean the WSearch services of NT6 and the CiSvc one of XP.

Yes, this could happen with 3.8 version, i changed folder deletion to SHFileOperation, but I did not read the remarks posted there. Will be fix in Final version. BTW: there will be a "-nosearch" switch, too. Is there anything else that uses much CPU and slowdown a postinstall phase?

So, RC2 is out and should fix the mentioned problems. http://1drv.ms/1KkvDty

Hmm, I could reproduce an app crash on the RC version but not on the final. PureBasic's string management looks a bit strange to me, Sometimes an empty string is an address to and 0 terminated string, ok, but sometimes it's a 0 pointer That explains the error you get. I'll try to fix this with the next version and also make command line setup identical to the normal GUI.

The "-setup" switch requires critical things like source, syspart and tempdrive to be passed by command line.

It's Indeed the disableUAC tweak that cause the reboot problem. Never noticed this, cause it does not happens with fully unattended setups.

Good question how to disable it on the fly, but next version will fix this anyway. But what bothers me is, that the disableuac tweak cause a reboot loop right before user creation

I guess the problem is what they wrote on defender settings GUI: "You can turn this off temporarily, but If it's off for a while we'll turn it back on automatically" It seems with every Windows start defender is enabled again.

Ok, new almost stable version ready. You can now apply in compact mode, if you start like this: "WinNTSetup_x64.exe NT6 -compact" This version now depends on latest wimgapi.dll, and automatically downloads it. So do not just replace the exe files, let it download the files once. Version 3.8.0 RC1 http://1drv.ms/1HbUDQM - fix VHD checks for windows 8 Core edition- fix dpi issues- fix reg import of empty values- fix win 10 bcd error- fix VHD GUI- fix user creation- fix gui issues- fix vhd creation may trigger format dialog- XP/Vista will try to load Tools\x??\wingapi.old if exists- added support for new WofADK driver- post processing PrepopulateList- support for METADATA_ONLY Wimfiles- downloads ADK 10 RC wimgapi.dll- support for custom.wim wimboot images- new command line option -ref:{reference.wim}- new command line option -wbc:{custom_wimbootcompressed.ini}- new command line option -compact- reattach Wof(ADK) after bootsect volume dismount

Yes compact mode is the next "version" of wimboot. But WIMGAPI does not allow to set the compression option, it seems to always use Xpress4K. Don't know if it makes sense to add such an option, or would it not be better to use compact.exe later?

Yes, all newer Oses support booting from VHD. Starting with Windows 8 also from VHDX.

Windows 7 is first windows, that supports booting from a VHD. Older ones would need a 3rd party boot manager and a driver. I will not add support for any of these. But you could try: http://reboot.pro/topic/18547-vhd-xp-setup-install-xp-in-vhd/

Currently it's not possible to apply a custom.wim. I'll add this to the next version. Such a "ref" command line option will be a good thing , too.

What have you done to get such an error? Normally nointegritychecks should be enough for bootmgr to accept an altered winload.exe.