WinNTSetup

- /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
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

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

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

 EasyMBR2GPT.7z (1.77 kB - downloaded 64 times.)  <== 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 

FYI a new version of WinNTSetup was posted by JFX (silently ) 2 days ago, link in OP...

Looks great but I'm curious about the :( next to uEFI in the title bar.. 

"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 

So now we can do everything -

Thank you

"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 

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

 Prep.zip (2.93 kB - downloaded 58 times.)

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.

 Prep_v2.7z (2.2 kB - downloaded 80 times.)

JFX, if lowercase drive letters are used in WinNTSetup.ini they do not work. 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.