-
So to not mess up other topics, you can use this one to post question ideas and what ever about WinNTSetup here.
Always remember partitioning is entirely up to you.
If there is a red cross icon, it will not work, as you have not selected a correct boot drive.
Latest Release Version: WinNTSetup3.rar (http://jfx.cwcodes.net/WinNTSetup/Release/WinNTSetup3.rar)
-
Would you verify for me bcd boot code (when you have time) with two VHD's on usb?
I will try to test again as I think my results are somewhat flawed..
Also..
C/P MS TechNet
Applies To: Windows 7, Windows 8, Windows 8.1, Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2
A Windows 7 or Windows 8 boot environment is required to natively boot a .vhd
The local disk must have at least two partitions: (already proven false with legacy boot)
a system partition that contains the Windows 8 boot-environment files and Boot Configuration Data (BCD) store,
a partition to store the VHD file.
But you will have to update the system partition to a Windows 8 environment to use the .vhdx file format.
-
The BCD you poested looks okay, it should work.
For the Windows 8, your right even the Core edition supports VHD boot.
You can right click on the VHD button and disable the checks made.
-
Hi JFX,
just came and following slowly,
I will recreate Win7x86 some time tonight, this time with usb3 driver added :lol:
I currently can not install usb3 drivers, ends with bsod .... well we will see, in the end it is nice testing WinNTSetup :)
I could not find instruction about how to use "Reg Tweaks",
should I put .reg files to a folder ? so it will process all .reg file ?
if so, should I convert .reg files ?
:turtle:
-
Yeah, just select a folder with *.reg files in it.
There is no need to convert them, but make sure there standard.
like ControlSet001 becomes CURRENTCONTROLSET
or HKEY_USERS\S-1-5-21-%guid% becomes HKEY_CURRENT_USER
-
Hi KYHI,
Lance, have you accessed your usb's bcd after using WinNTsetup??
I guess yes,
I plan to add usb drivers from dps tonight to get usb3 support,
besides it was an interesting bcd, msconfig (and bcdedit list) lists 1 entry, but on boot there are 4 entries, so answer might be no,
I will focus on that later, I am only human :lol:
+
as you wrote, since WinNTSetup does not format,
it is easy to add to my usb disk :smile:
..
I will follow other posts, slowly slowly :turtle:
-
[attach=1]
Would entry of (Bootstatuspolicy ignoreallfailures) for wintousb.vhd be the possible cause? For unusual MBR?
[attach=2]
Bcd update correctly with the above options and both vhd's bootable
But even when the selection is MBR - an EFI Folder and Bootntx file seem to have been unnecessarily written to disk? Any reason? I'm thinking ALL switch..
[attach=3]
And a quick question - is it possible to include updated tools and windows 8.1 boot files in the download??
As I assume that bcdboot is using Host OS Boot Files - I did notice that WinNTsetup downloaded some tools - it must reference..
Reason being if Host not win7/win8 VHD not possible to boot, unless using win8 boot environment.
Win8.1 ADK Tools with media from PE is a 12MB 7z download
[attach=4]
-
Bootstatuspolicy ignoreallfailures should be only to prevent recovery boot of winre.wim.
Yes, the "ALL" in combo box on proceed page will create EFI files, in your case too.
There all not necessary but might work with some uEFI boards.
You can update the tools manually, if you want, but it's not necessary.
These ones downloaded are form Win 8.0 and still fully compatible with Win 8.1.
-
First off, This Program is awesome..... (Insert WinNTsetup Link Here)
It proves everything I was let to believe from MS to be BS.. Period..
I was able to boot - VHD - off a USB with only one Non GPT partition...
Windows 8.1 x86 and Windows 8.1 x64 both in Legacy Mode and Windows 8.1 x64 in UEFI mode...
F12 brings up my boot menu options - I have the option to boot USB via Legacy or UEFI
Selecting the UEFI Boot Option the x64 version VHD booted straight up..
Selecting the Legacy Boot Option the boot manager gave me the option to boot x86 VHD or x64 VHD
Selected x86 VHD and boot Windows 8.1 x86 in Legacy mode <> Selecting x64 VHD booted Windows 8.1 x64 in UEFI mode (must of redirected the boot to efi manager)
I actually had to disable UEFI Boot in my firmware settings to boot x64 in legacy mode...
Here is what I found That Works for portable windows to go -
USB Format NTFS -
MBR Boot Partition Selection = USB
Yellow Triangle = Allow Bootsect.exe to update Bootcode (Popup appears after clicking "SETUP") > Not needed if MBR Triangle already Green and saves time
Selected Drive Letter Pre-Assignment "M" (Found it keeps my current Host OS drive letter assignments) (VHD windows Dir=M)
JFX, I assume that the second scroll box directs to what bootmgr to add the current boot entry??? (None,All,Bios.Uefi)
Anyway on popup after clicking "SETUP" when using x86 version software > I change from ALL to BIOS (when using x64 software I left as ALL)
The result of doing this Added both the x86 VHD and x64 VHD into bootmgr and only added x64 VHD into EFI bootmgr...
This program proves you can boot UEFI without a separate Fat32 Partition and proves you can boot UEFI on non GPT disk.. A Big Portable Windows Plus... :thumbsup: :thumbsup:
I failed in one respect (as I thought for sure it would not work based on my knowledge outside of this program) I did not test x86 in UEFI mode...
JFX, x86 in UEFI with this program??
I ask because x86 on uefi, failed for Lance, but may have been his host OS lacked "Boot" files on EFI boot partition or USB had GPT partitions
-
Since this program seems to be WAY COOL for Windows 7 and Windows 8 /8.1
For my next test > XP and Vista to VHD and add Boot Entry into current usb bootmgr
I got some time and a mission.. Now I got something to do.. Later
-
Hi KYHI,
If WinNTSetup can put NT5 to VHD,
to have GPT disk support, Try with Win2k3 - (XP x86 don't support GPT)
http://theoven.org/index.php?topic=34.0 ;)
I don't much time, only small time and coming after you :smile:
:turtle:
-
JFX, I assume that the second scroll box directs to what bootmgr to add the current boot entry??? (None,All,Bios.Uefi)
Yes, this option is just the switch that passed to bcdboot.exe.
JFX, x86 in UEFI with this program??
It depends only some newer uEFI support x86. Also it requires a Win 8 x86.
Not sure what you mean with Vista and XP to VHD, that's not possible.
At least it will not be possible to boot cause these systems have no vhd driver.
-
Hi JFX,
how to fix "Boot Part" which remains X ?
Story behind:
I had test this ufd (removable - emtec) with gpt.... (maybe with wintousb) and it was around....
today I convert back to mbr (partitionwizard could do, windows dismanagement and active pm failed)
WinNTSetup could not fix "Boot Part"
at boot, for this ufd bios gives 2 options ,
one with uefi (ufd can not boot, it continues with my host uefi)
other normal (but can not boot, black screen error ~ can not find device to boot ... )
I will re test with another normal ufd, keeping this emtec around :wink:
Big Story:
All I am trying to do is install a nice working Win71x86-vhd, ready to be used for some cases,
but usb3 driver installation failed, and also gpu driver integration does not work (intel)
I decide to create a vhd on internal disk, booting from a ufd, so I can unplug all devices to install usb3 driver
btw, I remember it was possible with fixed vhd via using winvblock like we do on Gena (the beta one inside plugin)........ !
moving slowly..... :turtle:
-
Well, WinNTSetup doesn't not fix boot part, that's up to you, that's why the red X.
You properly just create a FAT32 partition, but not a EFI one.
Actually I not aware of a GUI partition tool other then Bootice, to be able to create one.
(http://i40.tinypic.com/dbnxgp.png)
-
Lance, your external HDD - GPT format? - tell me no..
-
@JFX,
I figured out, partition was not Active, now Active and all working :)
maybe WinNTSetup can make active maybe not, your design,
but it would be nice some routes at hand to follow :)
ex:
Boot Part Fails : 1) First Check if disk active
At last I could fix usb3 driver installation (by unpluging all), now fighting with intel gpu driver :)
It takes too much time to update etc. I hope this time I can finish and backup all
-
@KYHI
no :):)
Summary, I have 5 disk devices:
I have 1 internal disk (gpt) and 4 usb devices (All usb devices basic mbr if I am not testing something)
1 usb HDD,
2 ufd usb sticks - Removable
1 ufd usb sandisk extreme that acts like usb HDD - Fixed
I had made gpt tests on these ufd devices,
when reverting back from gpt to mbr, windows disk management do not let,
active partition manager could convert mbr fixed disk but not removable one,
partition wizard could convert removable to mbr
(both from gena....launch button ;))
not tested bootice yet but I guess it can do all (it didn't came to my mind at first place)....
Following slowly :turtle:
-
JFX,
btw, since I tried a lot, everytime chkdsk ....
but Win81x64 vhd does not popup chkdsk
only Win71x86 vhd with all re installations...
I "full shutdown" win8, so there should be no dirty bit around...
Well without "full shutdown" , boot bypass "ESC", "Del" .. here to bootmanager ... (where one need to shutdown with power button again to stop bootmanager and get "ESC" work again ...)
Here:
ESC - boot selection
Del - bios
I don't know why, and I don't know if it will break anything, I never let Win71x86 chkdsk to fix anything, and empty reg is safer to me, only informing :)
:turtle:
-
Rufus will format USB MBR and GPT
Put win7x86 VHD on ext hdd and make ext HDD legacy bootable.. Get it off the GPT system disk and off your host bootmgr..
Once on ext HDD - attach VHD - and run > bcdboot V:\Windows /s U: /f BIOS
That command will make your USB HDD - Windows 7 Legacy bootable..
ESC - to change disk boot or set firmware boot1 internal and boot2 external
Menu should show [attach=1]
-
Thanks KYHI,
I already made my usb-hdd-mbr bootable to vhd with WinNTSetup,
to me critical missing with WinNTSetup is gpt support, which is currently not important to me.....
:turtle:
-
Would do you mean with missing gpt support :confused:
BTW: For your chkdsk issues, your really should disable quick boot in any Win8 you have.
-
Hi JFX,
I report that earlier:
I could not get a WinNTSetup boot an empty gpt-fixeddisk... while other utility did nicely..
For GPT you have to create the 100MB system partition yourself and select this one a boot drive.
if there is already an esp partition, there is no letter to it and one can not assign,
see reply 7 second picture http://theoven.org/index.php?topic=1232.msg14476#msg14476
if there is not an esp partition, I create one to be esp later (assigned letter) but WinNTSetup could not get it work (maybe I had forgotten to active again :))
I guess KYHI reported similar...
I am very newly practicing these stuff, I don't know what I am dealing with much,
all I like to have Win7x86 at hand as the result of such spending time..
++
I will chkdsk later with Win81SE,
This did not work with RegTweaks
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager]
"BootExecute"=hex(7):00,00
++
I fixed all my Win71x86 driver stuff,
+ to install usb3 driver, I plug out all devices (vhd on internal disk), and it works now :thumbsup:
+ intel 4000 gpu could not install solved after reading
https://nctritech.wordpress.com/2012/03/15/code-12-on-windows-7-the-device-cannot-find-enough-free-resources/
solutions there did not help,
I decide not to "integrate any driver" to avoid driver conflicts, it workd :thumbsup:
4th time installing, sucked all free times in passing days
now time to copy vhd to usb disk, update Win71x86, some settings .... some hours...
:turtle:
-
You got the wrong picture.
WinNTSetup does nothing with partitions, besides updating boot sector with bootsect.exe.
The complete partition layout is up the the user to be created.
On start WinNTSetup scans all disk for ESP partitions and assigns them a letter.
Even if this not work, can't image a case, but there still mountvol /s to do it.
About "BootExecute"=hex(7):00,00", yes there is bug with empty strings.
-
Thanks KYHI,
I already made my usb-hdd-mbr bootable to vhd with WinNTSetup,
to me critical missing with WinNTSetup is gpt support, which is currently not important to me.....
GPT Support is there in WinNTsetup.. Win7_x64 supports GPT disk and when installed to USB with 2 partitions has its own efi bootmgr > Both WinToUsb and WinNTsetup support selecting an EFI partition and Windows partition...
The issue in your case is Win_x86 on GPT partition and EFI bootmgr..
Winx86 and to my surprise Winx64 boot just fine on single partition USB MBR Hard Disk or USB Flash Drive (No need for GPT Drive Format)
Winx86 and Winx64 can boot using two separate partitions (1 Fat32 and 1 NTFS)
UEFI_GPT x64 Partition Creation
select disk #
clean
convert gpt
== System Partition uefi ==
create partition efi size=100
format quick fs=fat32 label="SYSTEM"
assign letter="S"
=== Windows Partition ===
create partition primary
format quick fs=ntfs label="WIN_OS"
assign letter="W"
BIOS Partition Creatiton x86 / x64
Select disk #
== System Partition ==
create partition primary size=100
format quick fs=fat32 label="SYSTEM" (format quick fs=ntfs label="SYSTEM") either or will work
assign letter="S"
active
== Windows Partition ==
create partition primary
format quick fs=ntfs label="WIN_OS"
assign letter="W"
Notice GPT and Active (I assume one could set EFI partition also as Active) to maybe create a shared x86 and x64 system boot partition
Which just leaves one question > x86 software on GPT partition
JFX, commented you need windows 8 or better to support x86 on GPT (My 8.1 Tablet is x86 on UEFI_GPT)
It depends only some newer uEFI support x86. Also it requires a Win 8 x86.
So once again it comes down to Win7 x86 on UEFI-GPT (or anything prior to windows 8)
Just Better to avoid GPT partition all together - with WinNTsetup the UEFI support comes from within software
-
I will follow and test gpt notes and other stuff in detail in following days....
with better reports :thumbsup:
:turtle:
-
I have used this program, because it seems to work very well with adding boot (BCD) entries for iso, vhd, wim
Nice thing is you may be able to add - OS to ram project > sources\boot.wim (WinPE - WinRE) to BCD entry into USB bootmgr
or visa versa - add vhd to project bootmgr
EasyBCD 2.2 (http://cf.cdn.neosmart.net/software/EasyBCD/community/EasyBCD%202.2.exe?response-content-disposition=attachment%3B%20filename%3D%22EasyBCD%202.2.exe%22&response-cache-control=max-age%3D1209600&Policy=eyJTdGF0ZW1lbnQiOlt7IlJlc291cmNlIjoiaHR0cDovL2NmLmNkbi5uZW9zbWFydC5uZXQvc29mdHdhcmUvRWFzeUJDRC9jb21tdW5pdHkvRWFzeUJDRCUyMDIuMi5leGU~cmVzcG9uc2UtY29udGVudC1kaXNwb3NpdGlvbj1hdHRhY2htZW50JTNCJTIwZmlsZW5hbWUlM0QlMjJFYXN5QkNEJTIwMi4yLmV4ZSUyMiZyZXNwb25zZS1jYWNoZS1jb250cm9sPW1heC1hZ2UlM0QxMjA5NjAwIiwiQ29uZGl0aW9uIjp7IkRhdGVMZXNzVGhhbiI6eyJBV1M6RXBvY2hUaW1lIjoxNDI2MTY2NjE1fX19XX0_&Signature=uyjjIPDSv802Dq7zf~5l1VsWLOmgMgQ~B31XXAhJhISkqvI8KurEwkiHBxAa2TSBZqr2Ymgrd9xKfvf68Yt-YJklRTODSV4ySOZbI7fVcxvsX9z-VeXKlSZ3xtfucRao~TeVfNY7sOvRdjOmLAtfpdK7N8h-FDcwuRKgXSSFiUf2dNOywxhJSQFDktxDsO4y-TOqujt-UURsdTTDg98vjQeTv7iv7RR9xyQ03kNqitbmO7X3HAY7SJc9WFZBYnUltTm7oulC9S8Bt0tnqpHjEBRNg7gZvgqfdLJh14O8Ntphbl5Mjz4oSSlIsbt1QsZlBgYw43fwhxEaPk-OPKSWtQ__&Key-Pair-Id=APKAIPY5GEV5EHVOFFNQ)
[attach=1]
What would be a good Feature in WinNTsetup would be the ability to ADD or USE an existing VHD instead of just creating one..
-
What would be a good Feature in WinNTsetup would be the ability to ADD or USE an existing VHD instead of just creating one..
Just 2 buttons away :whistling:
"VHD >>>" --> "Attach"
-
JFX,
I guess KYHI means only adding bootmanager things without creating a new vhd :wink:
:turtle:
-
Oh, well
common come on guys, just a line in cmd after attaching
Bcdboot Z:\Windows /s Y:
Z: - your mounted VHD
Y: - your boot partition
-
:)
as I wrote, I am very new on this nt6x gems :)
currently writing from new vhd win71x86, syncronised with ff (pw ready), and windows updating :smile
:turtle:
-
What would be a good Feature in WinNTsetup would be the ability to ADD or USE an existing VHD instead of just creating one..
Just 2 buttons away :whistling:
"VHD >>>" --> "Attach"
:white_flag:Oh, well common guy, just a line in cmd after attaching
Bcdboot Z:\Windows /s Y:
Z: - your mounted VHD
Y: - your boot partition
commom guy says >> DUH and asks why I gotta type?? :lamp:
Guess we need to read the instructions - wait men don't need or read instructions.. :w00t:
Our wives tells us what to do and how to do it... :ohmy:
-
Chris got me thinking (bad sign) > How hard would it be to add a partitioning tab or GUI to the current program?
Since I noticed that the program runs a premade diskpart script to create a vhd...
We could add variables to the gui and write a diskpart.txt file that can then run by diskpart as a script to partition a hard disk
-
Or you could simply add bootice next to Winntsetup and will get such a tab.
Puh, with all these question you guys have,
I need to rethink all the features I wanted to put in the next major version :mellow:
-
Not sure that is a good thing or a bad thing JFX..
I believe a script could create a partition script for use with > diskpart /s diskpart_*.txt
-
I was testing this morning this along with the > os to ram > boot.wim
I added sources\boot.wim from project to Win-Usb and added entry with easyBCD
Boot.wim loaded into memory and then fails BCD integrity check written by this program
I can work (still playing with) bootice to get it
SE writes to > windows boot manager > nointegritychecks Yes
SE writes to > windows boot loader > loadoptions DISABLE_INTEGRITY_CHECKS
I know NT was not meant for this, BUT the current win-usb BCD was written by NT
NT writes to > both > integrityservices Enable
The VHD's boot fine as NT has written the BCD -
What I am not sure of is what Option needs to be changed to bypass the checks on boot.wim > just the boot.wim integer or the bootmgr integer or both
-
I made a summary here
http://theoven.org/index.php?topic=1240
:turtle:
-
Got it boot with > legacy x86 and x64 and Win81SE x64 <> EFI x64 and Win81SE x64 (for which win81se uses legacy boot option from bootmgr.efi)
Could not allow NT to write BCD, due to integrity checks.. Choose NONE
Created a Win81SE os-to-ram project to the win-usb, copied WinNTsetup VHD's to win-usb,
mounted x86 VHD and used cmd > bcdboot VHD:\Windows /s USB: /f BIOS
mounted x64 VHD and used cmd > bcdboot VHD:\Windows /s USB: /f ALL
Booted PC both efi and legacy > both booted VHD - due to No display boot menu option in Win81se bcd
Added displaybootmenu option to both bootmgr and bootmgr.efi > bootice = working Win-Usb w/winse
Tweak to SE project = add displaybootmenu yes - to win81se project bcd - timeout is already set by project
Tweak to NT project = use command line bcdboot it does not write in integrity checks in bcd
Next test is to (edit) enable standard mode in win81se bcd entry - to see if win81se can boot in legacy and efi
Success - Booting Win81SE boot.wim into legacy and UEFI
Edited this under SE winloader from > bootmenupolicy Legacy (to Standard)
Tweak 2 for SE project to boot SE in both Legacy Mode and UEFI mode..
A Complete Success!!
Enjoy!!
Kyhi
-
Hi JFX,
a small idea, to add Tweaks,
Gena\Adjunct\MountedDevices Host
since these vhd would be used on personal pc, it would be nice having same driver letters :wink:
->
practical usage is, when drive letter changed for vhd, such feature would make host-os driver letter (Generally C:) same,
which would make symbolic links work...
just an idea :thumbsup:
:turtle:
-
There is already an option to save driveletters.
-
Hi JFX,
Can you point which one ?
http://theoven.org/index.php?action=dlattach;topic=1240.0;attach=2446;image
http://theoven.org/index.php?action=dlattach;topic=1240.0;attach=2438;image
-
http://theoven.org/index.php?action=dlattach;topic=1240.0;attach=2446;image
Every time that VHD is booted that drive letter will be V
Leaving Host OS drive letters un-changed
-
Leaving Host OS drive letters un-changed
well I feel no, windows follows its automatic driver assigning routine, which fits ok if you don't do other drive letter scenarios....
Short story, I accidentally notice this and felt it would be nice feature on WinNTSetup, up to JFX..
In some future, it is good idea to use these .vhd with plugins, where I can use MountedDevices Host plugin too,
not hard, but requires time, much later :thumbsup:
:turtle:
-
All my VHD's booted as pre assigned drive letter M
And my host drives stayed as C windows, D data, E backup
Where as without pre drive letter assignment my C windows was assigned F
-
Than all I can say,
it didn't work here, I asssign my usb-disk S: since the begining,
when vhd booted, and I plugin my usb-disk, it was E: or F:
Anyway, as I say, not much important to me :thumbsup:
:turtle:
-
USB was E or F
VHD windows S ??
Y tag usb
-
no,
vhd when booted V: ;) :great:
usb when first plugged in E: (which is S: on my hostos)
I had written "MountedDevices Host" for that reason in very past (which is a simple plugin), not big deal.
I already changed driver letter from E: to S: on vhd-os, it was a small feature idea for WinNTSetup , that was all :thumbsup:
-
Hmm, yes only logical disk will be saved and of course the new systemdrive.
Well not really worth to add such an option.
-
:thumbsup:
-
JFX,
Change Log for 3.77 ??
-
http://www.winntsetup.com/news/ (http://www.winntsetup.com/news/)
-
Hi JFX,
may I ask how WinNTSetup:
Disable System Restore ?
Shorlty:
Reason Behind:
microsoft.vc80.atl,type="win32",version="8.50727.42",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="x86"
http://social.msdn.microsoft.com/Forums/en-US/vssetup/thread/4cecb2c6-dd5d-440e-8357-8701ac6f302b
:turtle:
-
https://msdn.microsoft.com/en-US/library/ff793976(v=winembedded.60).aspx (https://msdn.microsoft.com/en-US/library/ff793976(v=winembedded.60).aspx)
But indeed, Windows seems to ignore the complete key, wonder when that have changed.
For link, it's properly a AV issue.
-
Here there is no
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\SystemRestore\
DisableSR is at
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SystemRestore
which was 1
I changed to 0, even take a manual restore point, did not help.
+
the link I gave:
I have same trouble (no AV, defender disabled), after digging down I figured out,
trying to install latest vcredist_x86.exe (2005 sp1) failed
I suspected disabled SystemRestore.... well only left suspect a windows update may cause this :smile:
hehe, the Win71x86 vhd I learned creating with all updates etc. now have no use :smile:
I created another quick one (Thanks to WinNTSetup), where vcredist work (without any system tweak, doing things manually after setup),
and application installed to be used nicely :smile:
lots of things to do, lots of things to learn,
hopefully digging more later in summer :thumbsup:
:turtle:
-
JFX,
Pre-Assign Drive Letter " * "
Ex: *:\VHD > Lets windows assign the drive letter ??
Also, to suppress Windows Format Popup during VHD creation - knew the program HAD that issue, may have been corrected already..
TXTAddLine,%vw%,"create vdisk file=%vhd% Maximum=%vp% Type=%Type%",Append
TXTAddLine,%vw%,"attach vdisk",Append
TxtAddline,%vw%,"automount disable",Append
TXTAddLine,%vw%,"create partition primary",Append
TxtAddline,%vw%,"online volume",Append
TXTAddLine,%vw%,"format quick fs=ntfs label=%Volabel%",Append
TxtAddline,%vw%,"automount enable",Append
TXTAddLine,%vw%,"assign letter=%PreAssign%",Append
//TXTAddLine,%vw%,"detach vdisk",Append
TXTAddLine,%vw%,"exit",Append
-
Yes, what else would you expect, a "*" drive in windows explorer :lol:
I never noticed a format dialog, are you sure it was not caused by an other program?
-
Yup, it is your program.. When creating VHD
[attach=1]
I knew a * was wild - just a common guy, verifying the already known
-
What I mean, this is not how diskpart / windows should behave.
Is there any other tool running like "usb drive letter manager" for example?
-
No just your program - as soon as the vhd is created - windows assigns a drive letter and pops up a format windows..
Then your program finishes assign and format.. Even though I pre-assigned N it pops up as Y..
I tested VHD creation many times today with diskpart on Windows 8.1 x64 - my first results where the same as I am reporting to you now..
I was able to over come the issue by using the layout in the codebox.. Formats without windows format popup and assigns my pre-assigned drive letter to the mounted VHD..
I did notice that the BCD "Integrity checks" where removed - But I have to keep adding in "DisplayBootMenu" the "timeout" is already there
And everytime I add a new VHD to the boot drive - I have to re-add DisplayBootMenu, it gets removed or over-written
[attach=1]
-
Hi,
I want to inform I can reproduce on fresh Win81 (emulator) :thumbsup:
( my host do not pop up that message anymore , I don't know what changed ! , maybe "Hide empty drives" disabled ! )
@JFX,
on xp, as you know if you do not click drive letter this message do not pop up,
on w7, I don't know,
on w8, when a new vdisk attached (or when primary partition created ..) , pop up message appears (and stupid message do not disappear after format)
++
it also happened on Fakedisk -> SE http://TheOven.org/index.php?topic=1068.msg13746#msg13746 (also check reply 26)
I had used
automount disable
...
automount enable
to avoid, but this maybe not good for hostos !
well you can easily reproduce on FakeDisk - Win81SE by disabling automount lines :wink:
***
Overall, no big trouble, only informing :thumbsup:
:turtle:
-
automount disable
create partition
online volume
format
automount enable
assign letter
Worked on 8.1 Host..
WinNTsetup format popup with Empty drives - hidden or not..
-
Ok, could reproduce it :thumbsup:
It's a win8 thing, on a quality os like Windows 7, this bug does not exist. :wink:
-
It's a win8 thing, on a quality os like Windows 7, this bug does not exist. :wink:
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: :lol:
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 :wink:
*
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 :cool:
It would be nice to be able to boot 2k3x86 side by side with Win7x86 when needed by a driver/application :smile:
:turtle:
-
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 (http://reboot.pro/topic/18547-vhd-xp-setup-install-xp-in-vhd/)
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 :wink: 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 :smile:
-
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 :thumbsup:
summer :wink:
:turtle:
-
I planned to use with ufd :wink: 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 :wink:
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 :wink:
very sorry, I have very limited time to participate with direct info (how to) around....
:turtle:
-
Right click on VHD button and disable all VHD checks.
I'll will not add winvblock :tongue:
-
Right click on VHD button and disable all VHD checks.
Great I didn't know it was there :smile: :smile: :smile:
Why didn't you write that before :lol:
I'll will not add winvblock :tongue:
I guess !!!! now no problem, adding WinVBlk.INF WVBlk32.sys WVBlk64.sys to add drivers
should work theorically now ?????
for Win7x86
and 2k3 ?????
:turtle:
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 :turtle:
-
New version out, that should fix your VHD format problem.
-
Thanks JFX,
summer :thumbsup:
-
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??
[attach=1]
-
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 :smile:
+
WinNTSetup_x64.exe v3.7.7 work ok on creating VHD, no trouble :thumbsup:
***
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 :thumbsup:
++
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 :wink:
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 :wink:
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 :cool:
******
I hope above helps WinNTSetup development...
:xmas-beer:
-
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:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\DriverSearching]
"SearchOrderConfig"=dword:00000000
-
thanks for the report, i fixed VHD bug, at least i think.
No version change this time.
Just tested,
works nicely now :great:
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.
I feel to open another topic "WinNTSetup Extra Tweaks"
http://theoven.org/index.php?topic=1477.0
This would hopefully help maintaining WinNTSetup,
with not over expanding "WinNTSetup-->Tweaks" :smile:
:turtle:
-
1.
Winntsetup mount Partition should have a judgment mechanism.
The current version of Winntsetup will automatically mount partitions in the BIOS environment. This is wrong.
As shown in the following figure, the BIOS environment loads a hidden partition of a USB stick
2.
The ESP partition is repeatedly loaded and the ESP partition has been loaded as a Z-disk after the WinPE boot, but after running Winntsetup the ESP partition is repeatedly loaded with a W disk.
-
GIF image upload Forum into a static diagram.
Dynamic picture here:
http://bbs.wuyou.net/forum.php?mod=redirect&goto=findpost&ptid=397942&pid=3440328&fromuid=1345
-
1.
Winntsetup mount Partition should have a judgment mechanism.
The current version of Winntsetup will automatically mount partitions in the BIOS environment. This is wrong.
As shown in the following figure, the BIOS environment loads a hidden partition of a USB stick
2.
The ESP partition is repeatedly loaded and the ESP partition has been loaded as a Z disk after the WinPE boot, but after running Winntsetup the ESP partition is repeatedly loaded with a W disk.
-
I take it that you have mounted the boot partitions previously with DG?
This a known problem DiskGenius mount the partition a bit different, so WinNTSetup does not recognize them.
-
GPT partitions are created by Diskgenius
Partitions created by Diskgenius and DiskPart are not significantly different
The ESP partition created by Diskgenius is the FAT format, and the ESP partition created by DiskPart is FAT32 format
Also, the user simply created the FAT partition, without the ESP partition, which can start the system as normal in the UEFI environment. The user's disk partitioning situation is inherently complex.
Winntsetup should be improved in fault tolerance. Determine if the partition is loaded and not be loaded again after loading.
Add a judgment:
UEFI environment, do not load any partitions without GPT disks. There are GPT disks that are loaded by hidden partitions and do not load repeatedly.
BIOS environment, do not automatically load any partitions.
Now there is a situation. Starting from the U disk, Winntsetup will repeatedly load the visible partition of the U disk. Occurs in both the UEFI environment and the BIOS environment.
U disk Boot disk use the program here:
http://bbs.wuyou.net/forum.php?mod=viewthread&tid=349965&extra=page%3D1
is created with a 3 partition boot disk with a hidden partition.
Feedback screenshot here:
http://bbs.wuyou.net/forum.php?mod=redirect&goto=findpost&ptid=397942&pid=3440635&fromuid=1345
-
You now can disable the mounting with an ini file option.
[Options]
NoBootMount=1
-
All right. That's it.
The problem is only circumvented. Doesn't actually solve the bug that's automatically loaded.
Thank you!
-
Tested the INI parameter.
Running Winntsetup will still automatically load the hidden letter to test the ambient BIOS. There are hidden partitions, which are 300MB boot partitions.
It is not known whether Winntsetup automatically unloads the loaded hidden partition when exiting. I use Diskgenius to find that the z disk is still there, but running the mountvol command did not find the z disk?
-
Running the winntsetup388b3 matching INI file is no longer automatically loading hidden partitions.
But there is one problem. The boot part on the Winntsetup interface displays red. UEFI Environment, the EFI part shows red.
This does not install the system properly. Because the Winntsetup Installation Wizard must specify a boot partition. However, you cannot specify the correct boot partition without loading the hidden boot partition. This installs the error.
You can actually use DISM or ImageX to install without specifying a boot partition. For example:
imagex /apply w:\sources\install.wim 1 c:\
bcdboot c:\windows /l zh-cn
After the partition is created, the BCDboot command automatically adds the required files to the hidden boot partition.
-
The result command of the Setup Wizard is not clear, do you know which of the following commands?
-
The BCDboot command is identified, right?
-
Is the final content of the help document duplicated?
In addition, help content feel a bit messy layout, not neat.
-
Take it as it is, I'm not going to change this.
WinNTSetup will require drive letter for both boot and install drive.
It could be done with out letter, but then you would have problems using it in batch files.
-
Ok.
Automatic loading of hidden boot partitions is ok. However, you need to fix bugs that automatically load visible partitions of U disk
-
Is there any way to add a command line option for a basic interface?, for simple windows installs to hard drives?(mbr?)
Kind of like WinNTSetup_x64.exe /legacyinstalliso (See below)
It is a super powerful program and I can appreciate the need for every feature, but a sleeker mode enabled from command line for quick installs to hard disks would be an awesome feature.
If you scripted in something like this:
@ECHO OFF
CLS
ECHO Prepare Hard Disk for WinNTSetup_X64.exe
ECHO ----------------------------------------
ECHO list disk > list.txt
diskpart /s list.txt
DEL list.txt>nul
ECHO.
SET /p disk="Which disk number would you like to prepare? (e.g. 0): "
ECHO.
ECHO --WARNING-- This will FORMAT the selected disk and ERASE ALL DATA
ECHO.
ECHO You selected disk ---^> %disk%
ECHO.
CHOICE /C YN /M "Is this correct "
IF %ERRORLEVEL% == 1 GOTO INIT
CLS
ECHO Preperation Aborted, No changes have been made...
ECHO.
PAUSE
EXIT
:INIT
ECHO sel dis %disk% > init.txt
ECHO clean >>init.txt
ECHO convert mbr >> init.txt
ECHO cre par pri >> init.txt
ECHO for quick fs=ntfs label="Windows" >> init.txt
ECHO assign letter C >> init.txt
ECHO active >> init.txt
ECHO exit >> init.txt
:RUN
CLS
diskpart /s init.txt
DEL init.txt >nul
ECHO.
ECHO This drive is now prepared for WinNTSetup_X64.exe
ECHO.
PAUSE
EXIT
Then after it runs that (or a simple gui version to run those diskpart commands) it would prompt user for ISO and select edition only, then gooo? because with above script install and boot are always C: 100% of the time and always works for MBR install.
Would allow for super simple legacy installs. More people would be able to use. I can use so its not for me but it took me a while to realize what I had and I'd love to put this in peoples hand and make it easier for them to understand what it can do.
-
I think it's easy enough. You can of course create a wrapper and call it by commandline:
WinNTSetup_x64 NT6 -source:I:\sources\install.wim -wimindex:1 -syspart:C: -tempdrive:C: -setup
-
If I make something to do this, is "-wimindex:1" where it gets edition? index:2home, index:3pro etc?
Can command line WinNTSetup use iso or does it have to be mounted first?
I am not trying to hide WinNTSetup if possible I want people to see it. I currently have written instructions already prepared for new people, I was trying to simplify for them. If I make wrapper I will show you and get your approval before I do anything with it..
-
...
-
If I make something to do this, is "-wimindex:1" where it gets edition? index:2home, index:3pro etc?
Can command line WinNTSetup use iso or does it have to be mounted first?
Yes, can use an ISO with the command line and wimindex is usually a 1-based index.
But you can also pass it's name:
WinNTSetup_x64.exe NT6 -source:J:\16299.15.170928-1534.RS3_RELEASE_CLIENTCONSUMER_OEMRET_X64FRE_DE-DE.ISO -wimindex:"Windows 10 Pro"
-
How are you getting the available editions to populate your dropdown after selecting the ISO? I can hardcode "Windows 10 Pro" and other valid names to the wimindex drop section of the wrapper (Basic MBR Install mode) in the dropdown, but if someone downloads an ISO that doesn't have that edition it will error out I'm pretty sure, and very sure it wont work even if it doesn't produce an error. Is it easy to explain where it can be read from?
*** EDIT
Nevermind I found it here: https://winaero.com/blog/how-to-see-which-build-and-edition-of-windows-10-the-iso-file-contains/ (https://winaero.com/blog/how-to-see-which-build-and-edition-of-windows-10-the-iso-file-contains/)
But what are you doing do mount the iso? DISM would take a long time, is there a simpler way you use? I appreciate any guidance and will try to keep the questions to a minimum and simple.
-
...
-
I missed that! Didn't see :grin:
Thank you! Will update soon
just wanted to show some of WinNTSetup's power!!!
I know it is pretty sweet!
-
If I make something to do this, is "-wimindex:1" where it gets edition? index:2home, index:3pro etc?
Can command line WinNTSetup use iso or does it have to be mounted first?
Yes, can use an ISO with the command line and wimindex is usually a 1-based index.
But you can also pass it's name:
WinNTSetup_x64.exe NT6 -source:J:\16299.15.170928-1534.RS3_RELEASE_CLIENTCONSUMER_OEMRET_X64FRE_DE-DE.ISO -wimindex:"Windows 10 Pro"
WinNtsetup3.8.8
Installs the Win7 64-bit system in the WIN10 X64 PE environment. Winntsetup prompts for memory errors during installation and exits.
The win7 system ISO file is WIN10, and the system WIM file is converted to ESD format.
Same environment, same system file, WinNtsetup3.8.7 normal.
-
I need more information on how to reproduce this.
Does it only happens with ESD files?
Is there a difference wimgapi or wimlib?
-
Does the Offreg.dll and WOFADK.SYS replace to the latest version to see if the winntsetup is working correctly?
-
No, you should not update these files. :ph34r:
The offreg.dll v.6.3,9600,17029 is the last one working under WinXP.
Wofadk.sys v.10.0,14393,0 is the last working one that exists currently. Newer ones causes BSoD.
-
Wimgapi V6.2.9200.16384
Winntsetup 3.8.8 in winpe2003 Environment, install WIM and ESD error.
Winntsetup 3.8.7 in winpe2003 Environment, install WIM and ESD normal.
In Win8pe, Win10pe Winntsetup 3.8.8 is normal.
Winntsetup 3.8.8 in winpe2003 Environment, change to use wimlib also normal.
But sometimes there are mistakes:
wimlib_extract_image 0x2: the WIM contains invalid compressed data.
-
Seems the old wimgapi.dll doesn't ignore the new flag. Will be fixed in next version.
For wimlib error, I don't think it's a WinNTSetup problem. The API is very simple and good documented.
-
Fixed version what can be published?
Network access OneDrive in China is difficult
-
Don't have much time, so here you have an unofficial build.
-
Thanks a lot!
Excuse me, is this a formal version or a beta version?
I have forwarded. If there is any problem feedback.
-
Excuse me, is this a formal version or a beta version?
Neither, it's just not tested on all systems.
I don't have any XP/2003 or Vista VM anymore, so can makes sure everything is fine under these systems.
-
Preliminary test. There is no problem in the 2003 environment.
-
So now that awareness for MBR2GPT has been raised.... Will WinNTSetup now add this functionality post setup to support GPT?
http://theoven.org/index.php?topic=2288.0 (http://theoven.org/index.php?topic=2288.0)
-
In WIM format XP Click to start installation will prompt error, Windows source is invalid, need to close prompt, click to start install again to install, and after the desktop will automatically add Microsoft Pinyin, Zheng Code, full spell, intelligent ABC Four Input method
-
Found the bug for the error prompt on first click.
But I have no idea about the IME menu.
-
Feedback:
3.8.7 installing ISO is not a problem.
3.8.8 start, select ISO, match WIM file, install will report error prompt.
-
No problem here with iso.
-
This is the new Chinese language file.
-
- /forceunsigned - (only for installing Windows 7) will let the driver integration accept unsigned drives
Is this correct? I think the following is right?
- /forceunsigned - (only for installing Windows 7) will let the driver integration accept unsigned drivers
-
Hi nttwqz,
thanks for the updated language file :thumbsup:
You are right the is a missing 'r'.
-
thank you
-
This is the new Chinese language file.
Add the following line
- /noapply - does not apply the Wim image.
-
Thanks,
I'm having much less time currently than I hoped I would.
But please continue posting bug reports and translation updates.
-
WinNTSetup 3.8.8.3
Install XP
Check the integration drive, the installation will be stuck in the following figure
Install win7 Integration driver no problem
Winntsetup 3.8.1 Install XP integration Drive No problem
-
Thanks, fixed that and some other bugs with XP install or running under WinXP.
Download link on first Post.
-
add drivers
The message is:
Right-click to enable/disable unsigned driver support
Do not know where to click, did not see any right click after the hint and effect
thanks
-
Test environment
Lenovo Computer
WIN10 PE 64-bit installation win7 system
Winntsetup Eject memory read error during installation
Some user feedback is problematic and somewhat normal. Not sure where the problem is.
Feedback picture is not too clear
-
Do not know where to click, did not see any right click after the hint and effect
Oh, seems I never added this feature to version 3.x.
Will be added to next version.
No idea about that problem with Lenovo Computer.
Maybe a problem with this WinPE or and harware/driver problem.
Also this wimgapi.dll is buggy with esd files, use 15063 version or try wimlib.
-
Feedback installation error. Replace the Wimgapi.dll version of 15063 to be installed.
In addition, Winntsetup is not perfect for high DPI support.
Win7 DPI set to 125%
Show the following figure, some text is not displayed
-
Can't reproduce it. Win7 @ 125 DPI
-
That looks like font scaling ( zoom :confused: ) not DPI... maybe disable simsun font? It may be the default spacing in simsun, I have had issues with it before..
-
The system is a simplified Chinese version of win7
DPI is set to 125% and 150%. Text display is incomplete
-
Yes, the default font on simplified Chinese is bigger. So not really a DPI issue, but I fixed it the same way.
New version is up :smile:
-
Simplified Chinese version win7 system
The computer monitor is 14 inches.
Resolution 1600X900
The DPI setting is 150%. The Winntsetup software interface extends beyond the screen. Unable to click the button to operate.
-
A description revision of the Simplified Chinese language file
-
Removed the DPI fix, it's to much trouble for this one font.
-
I still think I am correct in stating it is the "simsun" font. Maybe freesoft00 can use another in its place by renaming another font to simsuns name and moving it into place or disable it completely. I don't have much experience in simplified Chinese so I'm not sure of the negative effects...
-
Test environment:
The computer is Dell Latitude E5470
Restore the recovery image file from the notebook, the image is Win7 SP1 x64. install.swm, install2.swm, install3.swm
Use the DISM command to restore the system image to normal.
Using Winntsetup recovery, prompt the "0x714" error at the end of the application, "failed to apply the system image. The specified image file does not contain a resource area."
Unsigned:on
Unsigned:off
The newly added language entry is not in the language resource DLL file and is not easy to modify in Simplified Chinese
-
- /forceunsigned - (only for installing Windows 7) will let the driver integration accept unsigned drives
Is this correct? I think the following is right?
- /forceunsigned - (only for installing Windows 7) will let the driver integration accept unsigned drivers
-
@bob.omb
Yes the problem is this font, well more it's default size that is set bigger.
@freesoft00
I have added the Unsigned:on / Unsigned:off to the language resource DLL.
Also added the missing "r" to /forceunsigned english help mentioned by nttwqz
The error 0x714 should be fixed.
About http://bbs.wuyou.net/forum.php?mod=viewthread&tid=404561&extra=page%3D1&page=2 (http://bbs.wuyou.net/forum.php?mod=viewthread&tid=404561&extra=page%3D1&page=2)
This will still not work, as WinNTSetup uses MSSTMake.exe on NT5 for boot critical drivers.
It does not work with firadisk/winvblock or vboot driver.
http://jfx.cwcodes.net/WinNTSetup/Beta/WinNTSetup3.rar (http://jfx.cwcodes.net/WinNTSetup/Beta/WinNTSetup3.rar)
-
I have added the Unsigned:on / Unsigned:off to the language resource DLL.
No xp!
-
Simplified Chinese language file, translated the new section.
-
Beta winntsetup add xp driver feedback normal.
If you have no other questions, you can release the official version. Win10 The new version will also be released.
http://bbs.wuyou.net/forum.php?mod=redirect&goto=findpost&ptid=404561&pid=3518345&fromuid=1345
-
Okay, 1 month no bug report, I agree Final uploaded!
-
Updated Simplified Chinese language files
-
In the XP installation interface, right-click on the dialog box, prompting information or Unsigned:on Unsigned:off The message is in English, not Simplified Chinese.
The description language file does not work here. Win7 Installation interface hint information is Simplified Chinese.
RegTweaks
Using registry Optimization Settings, the dialog box appears without qualifying the *.reg file after clicking the Select button. You cannot select a reg file.
Sorry, post and test again, found the problem.
-
Looking at this situation, 3.8.9.1 will be released shortly :thumbsup:
-
You can't select a reg file, cause you supposed to select a folder (with reg files).
-
Got it.
The corresponding Simplified Chinese translation is changed
---------------------
In the XP installation interface, right-click on the dialog box, prompting information or Unsigned:on Unsigned:off The message is in English, not Simplified Chinese.
The description language file does not work here. Win7 Installation interface hint information is Simplified Chinese.
-
http://bbs.wuyou.net/forum.php?mod=redirect&goto=findpost&ptid=349965&pid=3568390&fromuid=1345
-
Don't know, this is properly buggy hardware.
I've added a few more status messages to Beta 3.
-
I run this cmd file (From a W10 OS or PE that has mbr2gpt.exe included) after using WinNTSetup...... BEFORE I boot into the deployed drive - Make sure not to Reboot when done using WinNTSetup...
Run the below CMD file, and when prompted, select the drive you installed Windows to with WinNTSetup - It takes about 30 seconds to run
[attach=1] <== You can also find this on the SE server in ComponentsY>EasyMBR2GPT
Then I can reboot to the drive UEFI mode with Secure Boot ON and the system will automatically enter the bios key and activate windows. (Assuming you install the correct edition)
Works like a charm for simple UEFI deployment every time...
I wish someone could add this to a checkbox or option to "Finalize with GPT for UEFI Secure boot" in WinNTSetup if MBR2GPT.exe was detected in System32 folder :whistling:
-
FYI a new version of WinNTSetup was posted by JFX (silently :ohmy:) 2 days ago, link in OP...
Looks great but I'm curious about the :( next to uEFI in the title bar.. :confused:
-
"uEFI SecureBoot disabled" was to long for the title, so it became "uEFI :("
Originally I wanted to use a positive smiley if disabled, but MS calls SecureBoot a feature :confused:
-
So now we can do everything - :party_time:
Thank you :thumbsup:
-
"uEFI SecureBoot disabled" was to long for the title, so it became "uEFI :("
Originally I wanted to use a positive smiley if disabled, but MS calls SecureBoot a feature :confused:
I don't think a positive smiley is a bad idea, the sadface makes it seem its not supported, but we know better because we've been using it, someone new wouldn't know...
It seems simple enough to detect: https://docs.microsoft.com/en-us/powershell/module/secureboot/confirm-securebootuefi?view=win10-ps (https://docs.microsoft.com/en-us/powershell/module/secureboot/confirm-securebootuefi?view=win10-ps) through PS - And MSInfo can provide in nfo file.. But its probably a major pain because both of those methods are outside of WinNTSetup..
But I for sure am happy with it, again, thanks JFX you rock..
-
I updated the CMD file I use to prep disks, for doing simple installs with WinNTSetup. (MBR or GPT) It automatically formats and partitions the drive of your choice, then launches WinNTSetup with the prepared drive letters pre-selected. (Made for use with WinPEx64 or on a host x64 system, can be changed to point to x86 exe easily)
Just place this folder inside the WinNTSetup folder and make a shortcut to the cmd file inside :thumbsup:
[attach=1]
-
This one works a little bit better. Drive letters are not hardcoded and it selects from available letters. Available letters are then written to ini and imported into WinNTSetup
Same as the other one just place the "Prep" folder inside the WinNTSetup folder then make a shortcut to the cmd file inside.
[attach=1]
JFX, if lowercase drive letters are used in WinNTSetup.ini they do not work. :wink: They populate but the bottom green light displays red, "Boot Part" and "EFI Part".
Have you ever considered adding formatting? Its actually not that bad I've been playing around a lot with it lately and its pretty straight forward, very small amount of CMDs For MBR and only a few extra for GPT, only thing to add would be error checking and GUI. Its very simple and displayed in this CMD file.
-
Hmm, I can not reproduce your problem with lowercase letters, but I will uppercase them in next version.
About format option, yeah I thinking about that as a command line option.
Maybe:
-format:syspart and -format:tempdrive
-
If you use the cmd I uploaded to prepare disk and change the values to lowercase and run it you will see the error after format.
For format you need one style for MBR(1part is fine, second not needed but can be used for recovery) and another for GPT(needs fat32 boot part, and ntfs, winRE not needed but 3rd partition can be used fo recovery)
So my CMD first asks MBR or GPT? then asks which USB? Then does everything else automatically including importing the drive letters to WinNT for boot and system.
If you had a format option that was that easy you would make a lot of people happy
For me the difficut part is using diskpart without cmd, I know autoit3 can do it but I dont know how yet(testing), so what I do is very ugly with CMD...
You could even allow adding PE ISO's or WinRE.wim as recovery partition later on if you get into formatting..
Its already awesome so no matter what you do... Thanks
-
http://jfx.cwcodes.net/WinNTSetup/Beta/WinNTSetup3.rar (http://jfx.cwcodes.net/WinNTSetup/Beta/WinNTSetup3.rar)
- fixed lowercase Ini file options
- added -format:syspart and -format:tempdrive commandline options
-format:syspart will keep the filesystem
-format:tempdrive will always use NTFS
For more complete partitioning use the Tools\diskpart scripts (command line diskpart:{script name})
-
Sweet! Thanks.. :thumbsup: I will put something together this weekend that utilizes this.. and share if it turns out good..
-
JFX has released a new version of WinNTSetup, version 3.9.1
It can be downloaded here: http://jfx.cwcodes.net/WinNTSetup/Release/WinNTSetup3.rar
(http://jfx.cwcodes.net/WinNTSetup/Release/WinNTSetup3.rar)
-
The download link was killed by Avast and also reported to Win32:Evo-gen[Susp] when opened. This issue was not available in previous versions.
-
Disable Your Avast Software........
Clearly we use software here that is not very common to your everyday PC user...
So some of the programs we use may not have been White Listed... (Due to being a very uncommonly used file)
-
After reporting and updating the Avast, the problem was resolved in a few days.
-
Thanks, that is helpful for everyone :thumbsup:
-
Can the red box be adjusted longer, and the current layout has a lot of information that cannot be fully displayed.
-
The dialog box is adjusted to the following
-
Well that actually looks ugly :huh:
I really don't want to change the layout, but maybe this new beta gives you some more space.
http://jfx.cwcodes.net/WinNTSetup/Beta/WinNTSetup3.rar (http://jfx.cwcodes.net/WinNTSetup/Beta/WinNTSetup3.rar)
BTW: If you add the Build version "1803" your self to the wim description, you may want to delete the file "Tools\Win10Builds.ini".
-
can be displayed correctly. If there is no other problem fix, I think I can change from beta version to stable version.
-
Final version released.
The x86 version still uses older wimgapi.dll, do not update it yourself.
-
Here is my take on Bobs amazing PrepareDiskNT.cmd
@ECHO OFF
CLS
ECHO -----------------------------------------------------------
ECHO Checking to see if the PC is booted in BIOS or UEFI mode.
wpeutil UpdateBootInfo
for /f "tokens=2* delims= " %%A in ('reg query HKLM\System\CurrentControlSet\Control /v PEFirmwareType') DO SET Firmware=%%B
ECHO Note: delims is a TAB followed by a space.
IF x%Firmware%==x ECHO ERROR: Can't figure out which firmware we're on.
IF x%Firmware%==x ECHO Common fix: In the command above:
IF x%Firmware%==x ECHO for /f "tokens=2* delims= "
IF x%Firmware%==x ECHO ...replace the spaces with a TAB character followed by a space.
IF x%Firmware%==x GOTO END
IF %Firmware%==0x1 ECHO The PC is booted in BIOS mode.
IF %Firmware%==0x2 ECHO The PC is booted in UEFI mode.
ECHO -----------------------------------------------------------
CD %~dp0
IF EXIST GPT.ini DEL GPT.ini
IF EXIST MBR.ini DEL MBR.ini
IF EXIST tempgpt.ini DEL tempgpt.ini
IF EXIST tempmbr.ini DEL tempmbr.ini
TITLE Prepare Disk for WinNTSetup3
:PRIVILEGECHECK
NET SESSION >nul 2>&1
IF %errorlevel% == 0 (
GOTO SELECTTYPE
) else (
GOTO GETPRIVILEGE
)
:NOPRIVILEGE
ECHO Prepare Hard Disk for WinNTSetup3 GPT (UEFI) or MBR (BIOS)
ECHO -----------------------------------------------------------
ECHO Warning, Elevated Privilege is Required
ECHO.
ECHO RE-OPEN AS AN ADMINISTRATOR
ECHO THE PROGRAM WILL NOW EXIT
ECHO.
ECHO -----------------------------------------------------------
ECHO.
PAUSE
EXIT
:GETPRIVILEGE
SET "params=%*"
SETLOCAL EnableDelayedExpansion
CD /d "%~dp0" && ( IF EXIST "%temp%\getadmin.vbs" DEL "%temp%\getadmin.vbs" ) && fsutil dirty query %systemdrive% 1>NUL 2>NUL || ( ECHO Set UAC = CreateObject^("Shell.Application"^) : UAC.ShellExecute "cmd.exe", "/k CD ""%~sdp0"" && %~s0 %params%", "", "runas", 1 >> "%temp%\getadmin.vbs" && "%temp%\getadmin.vbs" && EXIT /B )
GOTO NOPRIVILEGE
:SELECTTYPE
ECHO -----------------------------------------------------------
ECHO.
ECHO Prepare Hard Disk for WinNTSetup3 GPT (UEFI) or MBR (BIOS)
ECHO.
ECHO Please note: Only Windows x64 Will work with GPT
ECHO.
ECHO -----------------------------------------------------------
ECHO.
CHOICE /C MG /M "Are you setting up for MBR or GPT "
IF %ERRORLEVEL% == 1 GOTO INITMBR
IF %ERRORLEVEL% == 2 GOTO INITGPT
ECHO.
ECHO Invalid selection! Please choose a valid selection.
ECHO.
PAUSE
GOTO SELECTTYPE
EXIT
:INITMBR
CLS
ECHO Prepare Hard Disk for WinNTSetup3 MBR (BIOS)
ECHO -----------------------------------------------------------
ECHO.
ECHO list disk >> list.txt
diskpart /s list.txt
DEL list.txt>nul
ECHO.
SET /p disk="Which disk number would you like to prepare? (e.g. 0): "
IF [%DISK%] == [] GOTO INITMBR
ECHO.
ECHO --WARNING-- This will FORMAT the selected disk and ERASE ALL DATA
ECHO.
ECHO You selected disk ---^> %disk%
ECHO.
CHOICE /C YN /M "Is this correct "
IF %ERRORLEVEL% == 1 GOTO INITMBR2
CLS
ECHO Preperation Aborted, No changes have been made...
ECHO.
PAUSE
EXIT
:INITMBR2
SET BOOTDRV="S"
SET DATADRV="W"
ECHO sel dis %disk% >> initmbr.txt
ECHO clean >> initmbr.txt
ECHO convert mbr >> initmbr.txt
rem == 1. System partition ======================
ECHO create partition primary size=350 >> initmbr.txt
ECHO format quick fs=ntfs label="System" >> initmbr.txt
ECHO assign letter=%BOOTDRV% >> initmbr.txt
ECHO active >> initmbr.txt
rem == 2. Windows partition =====================
rem == a. Create the Windows partition =======
ECHO create partition primary >> initmbr.txt
rem == b. Create space for the recovery image
ECHO shrink minimum=500 >> initmbr.txt
rem ** Note, adjust the size to match
rem the size of the recovery image.
rem == c. Prepare the Windows partition ======
ECHO format quick fs=ntfs label="Windows" >> initmbr.txt
ECHO assign letter %DATADRV% >> initmbr.txt
rem == 3. Recovery image partition ==============
ECHO create partition primary >> initmbr.txt
ECHO format quick fs=ntfs label="Recovery image" >> initmbr.txt
ECHO assign letter="R" >> initmbr.txt
ECHO set id=27 >> initmbr.txt
ECHO exit >> initmbr.txt
:RUNMBR
CLS
diskpart /s initmbr.txt
DEL initmbr.txt >nul
ECHO.
ECHO This drive is now prepared for WinNTSetup3 - MBR (BIOS)
ECHO.
ECHO The following drive letters have been assigned, and
ECHO will be automatically loaded into WinNTSetup3
ECHO.
ECHO Boot Drive----------: %BOOTDRV%
ECHO Installation Drive--: %DATADRV%
ECHO.
PAUSE
ECHO.
ECHO Please wait while WinNTSetup3 loads...
CD %~dp0
CD ..
IF EXIST WinNTSetup_x86.exe (
START WinNTSetup_x86.exe /cfg:prep\template.ini
) ELSE (
START WinNTSetup_x64.exe /cfg:prep\template.ini
)
GOTO WINRE
:INITGPT
CLS
ECHO Prepare Hard Disk for WinNTSetup3 GPT (UEFI)
ECHO -----------------------------------------------------------
ECHO.
ECHO list disk >> list.txt
diskpart /s list.txt
DEL list.txt>nul
ECHO.
SET /p disk="Which disk number would you like to prepare? (e.g. 0): "
IF [%disk%] == [] GOTO INITGPT
ECHO.
ECHO --WARNING-- This will FORMAT the selected disk and ERASE ALL DATA
ECHO.
ECHO You selected disk ---^> %disk%
ECHO.
CHOICE /C YN /M "Is this correct "
IF %ERRORLEVEL% == 1 GOTO INITGPT2
CLS
ECHO Preperation Aborted, No changes have been made...
ECHO.
PAUSE
EXIT
:INITGPT2
SET BOOTDRV="S"
SET DATADRV="W"
ECHO select disk %disk% >> initgpt.txt
ECHO clean >> initgpt.txt
ECHO convert gpt >> initgpt.txt
rem == 1. System partition =========================
ECHO cre par efi size=100 >> initgpt.txt
rem ** NOTE: For Advanced Format 4Kn drives,
rem change this value to size = 260 **
ECHO for quick fs=fat32 label="System" >> initgpt.txt
ECHO assign letter %BOOTDRV% >> initgpt.txt
rem == 2. Microsoft Reserved (MSR) partition =======
ECHO cre par msr size=16 >> initgpt.txt
rem == 3. Windows partition ========================
rem == a. Create the Windows partition ==========
ECHO cre par pri >> initgpt.txt
rem == b. Create space for the recovery tools ===
ECHO shrink minimum=500 >> initgpt.txt
rem ** NOTE: Update this size to match the
rem size of the recovery tools
rem (winre.wim) **
rem == c. Prepare the Windows partition =========
ECHO for quick fs=ntfs label="Windows" >> initgpt.txt
ECHO assign letter %DATADRV% >> initgpt.txt
rem === 4. Recovery partition ======================
ECHO cre par pri >> initgpt.txt
ECHO for quick fs=ntfs label="Recovery" >> initgpt.txt
ECHO assign letter="R" >> initgpt.txt
ECHO set id="de94bba4-06d1-4d40-a16a-bfd50179d6ac" >> initgpt.txt
ECHO gpt attributes=0x8000000000000001 >> initgpt.txt
ECHO exit >> initgpt.txt
:RUNGPT
CLS
diskpart /s initgpt.txt
DEL initgpt.txt >nul
ECHO.
ECHO This drive is now prepared for WinNTSetup3 - GPT (UEFI)
ECHO.
ECHO The following drive letters have been assigned, and
ECHO will be automatically loaded into WinNTSetup3
ECHO.
ECHO Boot Drive----------: %BOOTDRV%
ECHO Installation Drive--: %DATADRV%
ECHO.
PAUSE
ECHO.
ECHO Please wait while WinNTSetup3 loads...
CD %~dp0
CD ..
IF EXIST WinNTSetup_x86.exe (
START WinNTSetup_x86.exe /cfg:prep\template.ini
) ELSE (
START WinNTSetup_x64.exe /cfg:prep\template.ini
)
CLS
:WINRE
ECHO Configure Windows Recovery Enviroment
ECHO -----------------------------------------------------------
ECHO.
CHOICE /C YN /M "Setup Windows Recovery Enviroment"
IF %ERRORLEVEL% == 1 GOTO INITWINRE
CLS
ECHO Configuration Aborted, No changes have been made...
ECHO.
PAUSE
EXIT
:INITWINRE
ECHO Finding the Windows Drive
ECHO -----------------------------------------------------------
@IF EXIST C:\Windows SET windowsdrive=C:\
@IF EXIST D:\Windows SET windowsdrive=D:\
@IF EXIST E:\Windows SET windowsdrive=E:\
@IF EXIST W:\Windows SET windowsdrive=W:\
ECHO The Windows drive is %windowsdrive%
ECHO.
md R:\Recovery\WindowsRE
ECHO.
ECHO -----------------------------------------------------------
ECHO Finding Winre.wim
@IF EXIST %windowsdrive%Recovery\WindowsRE\winre.wim SET recoveryfolder=%windowsdrive%Recovery\WindowsRE\
@IF EXIST %windowsdrive%Windows\System32\Recovery\winre.wim SET recoveryfolder=%windowsdrive%Windows\System32\Recovery\
ECHO -----------------------------------------------------------
ECHO copying Winre.wim
ECHO.
xcopy /h %recoveryfolder%Winre.wim R:\Recovery\WindowsRE\
ECHO -----------------------------------------------------------
ECHO Register the location of the recovery tools
%windowsdrive%Windows\System32\Reagentc /Setreimage /Path R:\Recovery\WindowsRE /Target %windowsdrive%Windows
ECHO.
ECHO Verify the configuration status of the images.
%windowsdrive%Windows\System32\Reagentc /Info /Target %windowsdrive%Windows
ECHO (Note: Windows RE status may appear as Disabled, this is OK.)
ECHO -----------------------------------------------------------
CHOICE /C YN /M "Would You like To Exit"
:END
-
JFX is the amazing one here... :embarrassed:
The prep cmd does a great job of getting things ready but WinNTSetup is where the real magic happens. :thumbsup:
-
JFX is the amazing one here... :embarrassed:
The prep cmd does a great job of getting things ready but WinNTSetup is where the real magic happens. :thumbsup:
You are 1000% correct. Thank you JFX. Without you where would we be!
-
Updated Simplified Chinese language file
-
Added to Beta 4 :thumbsup: