JFX

Yes, imagex will do, it. Here's a small guide that looks good.

The 8.1 Dism can capture and apply eds files.

Normally WimBoot only supports optimized WIM files, exported or captured with the /WimBoot parameter. These files have XPRESS compression with smaller dictionary size. However, normal XPRESS or LZX compressed WIM files can be used, too. But not esd files. Not sure what's the exact requirement for WIM file placement, definitive not CDFS/UDF, maybe not even removable drives at all. But for sure local NTFS drives.

Well, you could simply use my WinNTSetup. Or you would need your Windows 8.1 32bit DVD. Using the setup.exe on the 32bit DVD you can make use of the command line option /installfrom to specific the install.wim form your 64 bit windows http://technet.microsoft.com/en-us/library/cc766446(v=ws.10).aspx

Okay thanks for the info. I added a combo box to Beta 4, with the 3 firmware option that bcdboot has. As well as a new cmdline switch: -bcd:{ALL|BIOS|UEFI}

Hmm, I changed it to only create EFI boot files if the selected boot disk is an EFI system partition. Cause there was a report here, that EFI files causing problem in MBR mode. So you mean, you have a MBR USB-Stick with a FAT32 boot partition, and you can boot that in (U)EFI without compatible mode? Guess I really should add a check box for EFI files (and select it by default)

Thanks, I think, I fixed it in Beta3

No, Dism can't return the xml data, only imagex.exe can do. You can download it with my Get WAIK Tools

@ljycslg That was a bug, new 3.5 beta2 unmount all iso when it exits. @bios83 You use a Core version of Windows 8, but only Pro and Server editions support VHD booting. But your screen shot say you use Pro Try right click on VHD button and uncheck the check box that appears. Can you attach the xml from your wim file. You can get the XML by using imagex.exe imagex -info install.wim > install.xml

@bios83 Sure it's possible, just select a mounted VHD as installation drive @ljycslg There is no point in forcing imdisk, the native ISO driver of windows 8 is always used.

You have to run it on a Windows 8.1 Update or WinPE5.1, because of the new WOF driver. If you select a Windows 8.1 Update Wim file there will be a new check box displayed.

New 3.5 beta1 is out! - added WimBoot support WinNTSetup does support normal WIM files for wimboot, means you don't have to capture them using the WimBoot command. However, the stronger the compression the lower the performance of course.

Hmm, if anyone can give me a valid reason for ADK update than yes. But as far I can see it, all changes of the Update are only for the WimBoot feature. And cause Wimboot features depend on WOF driver, one needs a Windows 8.1 updated OS, that already has all these tools

This light gray label is the name and the version of the Software Licensing Description Table in your BIOS. It shows you that this machine is licensed to run a specific version of windows.

Hi wimb, that's properly a missing ADVPACK.DLL in system32 (or syswow64 on x64 PE). I'll drop this dependency in some future version.

@SIW2 There shouldn't be a problem with lng parameter and cfg file. One solution I forgot to mention is setting an environment variable: set winntsetup_lng=2052 @tranngocyd Well, yes it should work nicely, or do you noticed any problem. Only thing it doesn't do is flashing the NVRAM.

Yeah, some files are missing because the download would require a few hundred MB. But you can simply use the Waik_4 tools, they are still compatible with Windows XP.

Hi SIW2, you can either use command line (example add. -lng:1028 to load Lang\1028.dll ) or create a file call language.dll in the Lang folder. You can always get the current English template by clicking on the title bar and select "create language file"

I used an API that's not available on XP, so it should have displayed a "function not found in kernel32.dll" error.

Hmm, that strange it should have displayed and error message, well it does if I run it through the ide. However fixed and re-uploaded now.

So a new final version available, with minor changes to the latest beta Version v3.4.0 - adding support for XP/2003 WIM files - fixed problems with Final OnePiece XP Update packs - EFI Boot files are now only created on EFI partitions - UAC tweak disables now also defender

The older 8.1 dism can apply esd already. So can the old wimgapi.dll (6.2.9200.16384) that I'm using.

Yes, Winntsetup supports esd. But only decrypted ones (likes the ones dism creates) For decypting there seems to be tool available at MDL forum but i have not tried it yet.

@ilkertezcan, yes the tools are updated with the Windows Deployment Tools-x86_en-us.msp patch But I'm not sure if it useful to add the download, cause the only changes are for the new WimBoot feature. And deploying a wimboot image would still not be possible using the new tools. So the only reason for bigger download would be the Wimboot optimization (recompression) of an wim image.

Tranngocyd, winntsetup is no partition software, you have to make sure there is an EFI partition already. Easiest way is to create partitions with bootice