JFX

The oem switch had indeed a problem with relative paths, should work now with version 3.8.5.1.

No, thee is no automatic formating.

There is no ini option for that. but yes it possible with command line. WinNTSetup_x64.exe NT6 -oem:"C:\$OEM$"

Put the $OEM$ folder next to the install.wim.

$OEM$ folders are supported for all sources. You can either define it using command line or change the default "\sources\$OEM$" location by clicking on that label. A separate "SetupComplete feature" doesn't make much sense, just use a $OEM$\$$\Setup\Scripts\SetupComplete.cmd.

Final version of 3.8.5 is out. - disable pagefile should now disable swapfile too

If you like to create a customized winpe, Win7PE SE is much easier to configure.

Hi Nexus, The wallpaper is set by a program, properly in startnet.cmd or any other batch file launched on PE start. Themes are enabled by a tool call UX.exe, if you delete it the PE should stick with classic theme.

There isn't a real difference in the method in any of these 3. WinNTSetup ignores the Edition check, means you can apply other images than Enterprise, but the licensing / activation problems will be yours. It also skip the setting of sanpolicy and the removal of recovery console. That can be done by adding the options to your unattend.xml. For Windows 7 installs it also raises the PollBootPartitionTimeout

Updated to version 2.2.1 - reduced "xpwimboot" download by 3MB - added "xpcards" switch to download cards.dll - added "xpdiskcopy" switch to download diskcopy.dll

There is a "-silent" switch that can do exactly that.

No, for vista you have to do one install from CD, this one will have usually C: as system drive. A than syspreped and captured image will always apply as C:.

@click-click Vista doesn't let one change the drive letter in fast install mode. You will need to make a normal setup, sysprep and capture that one. This new image will always apply as C:. @simplex Seems with last rewrite of commanline parsing, I forgot '/' and it only accept '-' as commandline prefix. But you should also define the installation drive with -tempdrive:C: EDIT: fixed command line in Beta4

Hi nitro0001, No, unfortunately is not possible to do an upgrade install with WinNTSetup.

@changuk98 Turning wheels is a very common problem, if it takes more than 5 minutes you can usually forget this installation. 0x000000e is either related to mismatch of the device data stored in \Boot\BCD and the actual partition settings, or the device is really not accessible. There is not much you can do in that case. Maybe trying the original setup of Windows 10.

Have you tried this: ttps://social.msdn.microsoft.com/Forums/en-US/77b19c3c-7417-4eff-be5a-dec7f8bd16a6/how-to-prevent-driver-install-from-checking-windows-update?forum=quebecservicingdeployment

Hi changuk98, it's a bit hard to understand you and the problem you have. What exactly are you doing and what bluescreen do you have? Does it work if you apply in normal mode, no wimboot/compact? Are there any 3th party driver need for your pc? @alacran Next version will log the time required to apply the wim file.

Okay, beta 2 is out, with a lot of bugfixes. I also updated the SFXCreator for the ones who prefer to package the program to a single 7z exe.

Hi misty, that error comes from the missing "SE_MANAGE_VOLUME_PRIVILEGE" privilege. Wonder why I have that privilege enabled by default on my main PC.

@alacran 1) Yes, Wimboot doesn't work with esd files 2) Green is fully supported, Red means it will not work Yellow means it's not supported by Microsoft, but should work with WofADK and exclusion list of WimBootCompress.ini inside the Tools folder 3) If your Win8.1u1.wim is not located on NTFS drive wimboot is not possible. Compact is currently still red, cause I still want to check Win8.1 more, maybe there are conflicts with the older wof driver of it's own. 4) Win7 option will be yellow in next beta, forgot one check that exclude it.

Fist Beta version of 3.8.5 is ready! this one is all about adding compact mode for Win7/8.x/10 - it will automatically install wofadk driver if needed - it will also add this driver to new installation if needed - there is a WimBootCompress.ini in the Tools folder that should work for all windows version @click-click Updated the Beta1, now should fix the problem you mentioned.

No idea what's changed in this version. The download link has not changed, also all tools versions remains the same.

@Atari800XL You can specific a folder regtweaks The folder can be relative to Winntsetup NT6 -regtweaks:"tweaks\Win10" will add all *.reg files in your q:\winntsetup\tweaks\Win10\

@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?

@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!