click-click

I'm getting a crash dump on Win7 x64 when selecting Local Windows Installations. Works okay on 64-bit Win8, Win10 and 32-bit Win7 (v4.2.5.0). I can provide a dump if needed.

RemoveBootMountsOnExit What does this refer to and mean? Is it just an unmount of a VHD when WinNT is finished applying an image?

I currently have a 32Gig bootable Flash with W10-32bit + Tools, etc. for recovery purposes. It is basically a stripped down system that I use for normal work. No drivers are installed so that the W10 drivers are used on whatever hardware is being booted. The one problem I have is the build time needed for a newly updated Flash. It takes about an hour for WinNT to apply the image if the VHD (16GB) is on the flash drive and only 2-3 minutes if the VHD resides on an SSD. If I then copy the VHD to the flash, it takes even longer than one hour to copy it over. The flash is a Sandisk Ultra USB3, but it gets terribly slow from 30MB/s in the beginning to 2-3 MB/s during the copy. In the end everything works fine. Could VHD_WIMBOOT be of any help in reducing the build time or make better use of the VHD and what options would you suggest?

I'm not sure if what I am asking is possible, but I would like to create a recovery flash drive that will boot on PCs that have either UEFI or legacy set in the BIOS. I currently have a recovery flash that I created with WinNTSetup that has W10 installed in a VHD. The system boots and runs well if the hardware BIOS is set for legacy. The other day I tried to boot from a laptop that was set up for UEFI and the flash gets ignored and there is no way to boot it unless I go into the BIOS and set it to legacy. Not all BIOS implementations allow a legacy mode, so is there a way to avoid having to create 2 flash recovery drives to accommodate both modes?

You might want to start here.

@JFX I keep forgetting what some of the WinNTSetup ini values do or mean. I assume they are related to the command line switches. Are these explained anywhere or could you briefly explain the different values below? [WinNT6\READY] OEM=\sources\$OEM$ BCD= (0, 1, 2, ?, ?) BootSect=(0, 1, 2, ?, ?) Win7USBBoot=(0. 1, ?, ?) AddOtherOS=(0 ,1, ?, ?) Also where is the wimlib.ini supposed to be put if you enable using wimlib as stated in the ReadME. for wimlib - in \Tools with the other ini files? [Options] UseWimLIB=1

Oooops. I didn't bother to hit OK and kept using Cancel.

I would like to use WinNTSetup to install Win7 on a VHD that was defined for a VM in Oracle's VirtualBox. Is there a way to do this? If I mount the vhd on my local system, WinNTSeup wont' let me use the same drive letter for the boot drive. Seems like VBOX supports booting from a VHD.

I noticed up to 3.9.1 the enabled=0 in the diskpart directory was the default and now it is enabled=1. What happens if you accidentally do a CTRL+SHIFT+D when the GUI is active?

Okay, that's what I was thinking, but by chance I thought there might be a different set off system icons for the notification area. I just hate the big "^" icon when not showing all icons.

@JFX Link in OP indicates Get Waik Tool files no longer present. The latest version I have is 18.04. Is that the latest?

@JFX Does the Disable the new taskbar icons of Windows 10 setting give you the old icons back? Can you post the reg entry for this so I can try it out to see what it does without having to install?

Oh boy, I did not realize some of this stuff could be done from the command line. I never thought of using F1 from the GUI. Thanks for the link and the command line pointer. That is better and easier for me.

Thanks, I did stumble upon vhdtool and this is what I ended up doing to clone the WinNTSetup VHD creation because I need a different volume label than what WinNTSetup sets. Are these the correct commands to use? Also, do you know where I can find the vhdtool that includes the /repair option. I haven't been able to find it yet. vhdtool /create <filename> <size> /quiet select vdisk attach vdisk automount disable attributes disk clear readonly create partition primary online volume attributes volume clear readonly Active format assign

@JFX Do you use diskpart from WinNTSetup when creating a VHD with the instant creation option? When I run diskpart create vdisk file="d:\Win2Go ltsb.vhd" maximum=16384 it takes longer than the instant creation option via WinNTSetup although both VHDs seem to have the same properties and size. What commands do you use with the instant creation option? Thanks for any infos...

Sorry, I I missed that. I saw (Recommended) and did not take notice of the option below.

I noticed that when you create a VHD with WinNTSetup, it does a full format which takes forever using a USB flash drive. Is it also possible to do a quick format when using the VHD create option?

The usb was formatted with the normal format and the rest was done by winntsetup which I used to created the VHD etc. I also let it updated the boot record (which may be the problem). The usb was clean before I started with WinNT.

I recently wanted to created a bootable usb flash using a Win10 VHD. Everything works fine with WinNT (3.8.7.4), but for some reason the BCD is created with 2 VHD entries with the same name. The 2nd entry's partition and device are unknown and boots but eventually fails indicating system needs to be reinstalled. The 1st entry boots fine. I'm not sure what the 2nd entry is for and I deleted it with Bootice so the correct entry is used. Any idea why the 2nd entry is created? WinNTSetup.log

Was this discussed anywhere and what is the purpose? new ini option "DefaultSKU" compact mode (Win7?) I don't remember seeing anything about ctrl+shft+D related to an enabled setting either.

Thank you sir. I'm embarrassed for not trying that switch. I was assuming it was the default and did not think to try. Sorry.... Can the %ISOFILE% be a download link to an iso file or must the iso already be downloaded to get the ranges?

I wanted to test this using en_Win10_1709_multi_dec_x86_dvd_100406359.iso to see what the offset was for the install.wim, but nothing gets listed just specifying install.wim. If I leave the [file] blank, I get the following: [README.TXT] Range=51200-51334 [[BOOT]\1-Boot-NoEmul.img] Range=1064960-1069055 [[BOOT]\2-Boot-NoEmul.img] Range=1069056-1069567 How does one specify the [file] in the iso to get it's range, or is iso2offset only for the ADK? I don't have the ADK downloaded so I can't get a list of any offsets from that.

Thanks.. I'm not sure what to do with the cab files. Will the msi know what to do with them? I could not get the adksetup.exe to work for me. I only selected Application Compatibility Tools and the download would always fail. I finally figured out that I needed the 1607 version (10.1.14393 ) of the adksetup.exe for it to work. Edit: I ran the msi from your link and that was enough for what I needed to do. I used the Compatability Adminstrator from the installed toolkit to unblock the Power Manager setup.exe so I could see if the app still works on W10 and it does.

Can this tool be used to get only the Application Compatibility Toolkit (ACT)) from the ADK? I have a program (Lenovo Power Manager) that I want to install but it is blocked for W10, I understand it can be unblocked with ACT, but I don't really want to install the ADK just to get this component. What would I need to enter using GWT -range

Now that's thinking ahead. I don't have Winbuilder installed and wasn't to keen on doing so. You saved the day with this nifty tool and thanks for the heads-up on v2. Is that the recommended one?