WinNTSetup

Ok, could reproduce it 

It's a win8 thing, on a quality os like Windows 7, this bug does not exist. 

It's a win8 thing, on a quality os like Windows 7, this bug does not exist. 

Well it also happens on quality os like Windows 7 (tested on fresh installed on emulator),
 difference is,
  Win7 pop up message asks to format G: , while WinNTSetup already format it and put to Z: 

ps: maybe me disabling all autoplay option on w8host cause not having popup message ! or maybe a windows update !

Well, not important to me, only informing 



*
Getting more important to me, since I heard there are some rare devices that needs old xp,
 Can we please have vhd support for 2k3/xp (at least on disk and I am not after "portable" ;)) highly probably by adding winvblock driver...
  hopefully it is easy for you 

It would be nice to be able to boot 2k3x86 side by side with Win7x86 when needed by a driver/application 

Hmm, on win8 is indeed a timing issue.

Well, for XP VHD, no I not planing on adding something like this.
However it's not so difficult to do using wimb's VHD_XP_Setup

Only question will be if your EFI is able to chainload Grub4DOS.

Only question will be if your EFI is able to chainload Grub4DOS.

no it can not,
I planned to use with ufd  and like w7x86 later move vhd to disk....


I tried to follow wimb on w7x86 vmware emulator (to avoid things), but failed with bsod7b,
As far as I can figure out, wimb boot .iso to install to empty vhd first (sysprep step) --> which here result with bsod (WinNTSetup wouldn't need this ;))
and on second boot another grub4dos menu to continue setup (which I may guess integrating winvblock to vhd first !)
and it would continue booting with main grub4dos menu, which Windows would boot fine.

Additionally wimb focus to get a portable xp, and work on things accordingly (to me not priority) ... this complicate things which I feel you avoid,

I feel WinNTSetup can do same easily (without portable, without 3 grub4dos menu ,you already did sysprep step),
 it would only "first boot" to xp, probably with nt6x bootmanager ?
  (like WindowsXPMode_en-us where there is already a vhd ;).... , well 2k3 would be better ;) )


Anyway, something to play with much later in summer with a lot of time 

Indeed it could be done without multiple grub menus, by simply injecting the driver instead of using a floppy.

But it can be much easier anyway.
Just install winvblock in virtualbox WinXP and than add the disk image to grub4dos menu.

OK, you will still need to inject sata driver with a tool like driver inject GUI.

Yes, I will work on this with having wide time,

Than I will still ask you add this to WiinNTSetup providing step by step info 

summer 

I planned to use with ufd  and like w7x86 later move vhd to disk....

After a little testing - using an x86 VHD within a Host Windows 8.1 x64 system.
With the x86 VHD residing on an internal Host GPT disk..

I set the USB as the BOOT (so only the Boot files where written to USB) and not Host

Legacy Booting to USB loads the Internal x86 VHD

bcdboot VHD:\windows /s USB: /f bios

= legacy boot files on USB and x86 VHD on internal GPT disk

Also tested EFI boot with Legacy Option for x86 VHD = Can not Boot x86 from EFI Boot Manager or EFI Boot Menu > even with bootia32.efi..

Hi JFX,

Still same story,
 today I tried to install w7x86 sadly professional to vhd, and could not with warning ;)
  reason behind was since univercity have license to it .... and I was introducing winntsetup to a friend, and failed 

instead preventing install to vhd, is it possible to add an option with a warning icon saying "vhd boot not naturally supported"
or a checkbox "install unsupported souce to vhd" or whatever ..... so installing to vhd is possible with unsupported sources,
so we may add winvblock with winvblock.inf and .sys with add driver option,


or much much much better add winvblock to unsupported sources (xp, w7 pro etc) automatically,
 life would be much much easier to everyone


very sorry, I have very limited time to participate with direct info (how to) around....

Right click on VHD button and disable all VHD checks.
I'll will not add winvblock 

Right click on VHD button and disable all VHD checks.

Great I didn't know it was there 
Why didn't you write that before 

I'll will not add winvblock 

I guess !!!! now no problem, adding WinVBlk.INF WVBlk32.sys WVBlk64.sys to add drivers
should work theorically now ?????
for Win7x86
and 2k3 ?????



Edit:
naaah, it seems I need to work harder, summer .... ;)

Seams dism accepts the driver an integrate it.
But for NT5 MSSTMake.exe is used and this one rejects the inf.

and other things
-need a fix for pro license on vhd boot warning, or trials with other bootmanagers,.....
-need to test things for 2k3
etc. etc....

life keep me very busy, summer or later

New version out, that should fix your VHD format problem.

Thanks JFX,

summer 

JFX,
Noticed 3.8 states Wimgapi 3.6.9600

Have you tested the new one.. Seems to work ok for me when I embedded the new ADK files??

Yes, this is a bug that only occurs on Windows 8.

Until now with the new ADK release, the OS version of wimgapi.dll was usually the most up to date one.
So WinNTSetup will always prefer the one in system32 directory.

Hi JFX,

Host Win8.1 En ;)
Win10 x64:
10240.16384.150709-1700.TH1_CLIENTENTERPRISEEVAL_OEMRET_X64FRE_EN-US.ISO

Creating VHD with WinNTSetup_x64.exe v3.8.5.3 gives error:

Error creating VHD

0x80070057 - The parameter is incorrect.

I tested 2 times
Fixed size (Recommended)
Fixed size (Instant Creation)
both same error...

vhd mounted and seen on Disk Management,
 drive letter not assigned which I guess problem is ;).

well, sorry for none quality os 


+
WinNTSetup_x64.exe v3.7.7 work ok on creating VHD, no trouble 


***
Anyway, I mounted VHD manually and continue WinNTSetup v3.8.5.3 , Win10x64 :)
vhd at my hard disk
D:\VHDs\Win10x64\Win10x64.vhd
using a mini ufd for this cases ;) (to me, perfect simple solution to avoid troubles ;) )
https://www.sandisk.com/home/usb-flash/cruzer-fit
(single partition formatted ntfs)

+
thing I noticed,
I feel WinNTSetup tried to add Efi to ufd,
As you mentioned earlier, since WinNTSetup do not format Efi ready,
Boot Part remained "red cross"

I don't know how , but it boots to Win10x64.vhd nicely here :)
(Asus -> Esc to get boot menu, I select ufd ;) )

Shortly I am happy with the result, thanks again for WinNTSetup,
All things on this post is to support 

++
Idea:
If Win10x64 (or other WinXXx64) can be bootable on none-efi pc (I feel it should be),
 maybe you can provide option to create none-efi boot drive entries ;)
   which would be fine after setting things on efi pc 
   and would work on other none-efi pc ....

++
Having Tweak for Automatic Updates "Notify Only" would be nice,
Win10 very quickly start downloading and updating,
 I feel It downloads and updates one by one
 (different than usual download all and start updating)
   This make OS "after boot" verrrrrry slow ;)
   (downloading updating hunderds of MB, installing updates including new drivers etc...)

Besides, Since Win98 I guess, I always set "Notify Only" ;),
 Its position changed at Win10 - now under Settings 
http://www.howtogeek.com/224471/how-to-prevent-windows-10-from-automatically-downloading-updates/
here is something you may be interested
http://www.thewindowsclub.com/make-windows-10-notify-you-before-downloading-or-installing-windows-updates


+++****
And can you include Download link on current first post 

******

I hope above helps WinNTSetup development...
 

Windows Updates are a constant complaint with Win10 - very little detail and no real control over what, when and how..

Hi Lancelot,

thanks for the report, i fixed VHD bug, at least i think.
No version change this time.

For your efi, I don't know, I only pass firmware option to bcdboot.exe.
By default it creates all boot file types.

I don't want to break languages files again, so "Notify Only" tweak will be added with next major release.
For now you can use the custom regtweaks option.

Lancelot, Kyhi, others,
you might also be interested in this:
Windows Update PowerShell Module
https://gallery.technet.microsoft.com/scriptcenter/2d191bcd-3308-4edd-9de2-88dff796b0bc

I now have normal update turned off in W10, and use only this powershell module (also in audit mode), it allows for selective update install.
Seems a lot of people are using it for W10 now.

On some systems I also had to turn off automatic hardware updates, for this I use WinNTSetup with the -regtweaks option, and this reg:

Code: [Select]

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\DriverSearching]
"SearchOrderConfig"=dword:00000000