JFX

Well, these are all WIM files, and yes everything you can create with dism is supported.

Well, no. But there isn't any reason to use it ,too. It just a customization option, some like, it some not, but most people properly don't care about. So no, I don't add an option for it. Such things belong in the unattended file.

Here is another tool that a bit more talky attachment=38367:ximage.zip You can run it like imagex, it should show Info, warning or error message while applying

VHD drives are disabled from boot drive by default. Right-click on VHD button and unckeck the popup menu

Properly one of the oldest bugs, fixed in 3.5.1.

You should have mentioned why you think it's fast. 1. reason why Wimlib is so much slower could be cause it's a cross platform library. Properly using a not so great compiler. 2. There seams to be a bug, while applying and image to NTFS. Apparently, it messed up hard links. Well if it writes 2GB more data, it's actually not that slow.

Fast? It took 2,5 minutes here, that's much slower that normal wim file. Well the speed dependent on the used wimgapi.dll. Currently the Windows 8.1 versions is the fastest, but this one is no longer compatible with windows xp.

Thanks for the report. I see no reason to still call it Beta. WinNTSetup 3.5 Final added support for WimBootfixed mounted ISO files on Windows 8 was not unmounted on exitfixed EditionID was not detected on self made WIM filesfixed missing English fallback on not translated stringsadded combo box to select bcdboot firmware optionadded new cmdline switch: -bcd:{ALL|BIOS|UEFI} to specific bcdboot firmware option

Dism will check if the WIMBoot entry is set in the Wim XML. But this check can be skipped by setting an environment variable: set WIM_SKIP_WIMBOOT_CHECK=1

@jaclaz Well here, the link you gave has the same tutorial as the one I posted (at least the same pictures).

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.