Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


JFX

WinNTSetup v4.0

Recommended Posts

@alacran There was no such file. If the Win7 USB tweak don't work for you, than should use usb-boot-watcher.

Edited by JFX
  • Like 1

Share this post


Link to post
Share on other sites

@JFX

Thanks for your quick answer, I think usb-boot-watcher will solve my problem.

alacran

Share this post


Link to post
Share on other sites

Fresh Install of Windows 10 version 1909 on internal SSD is working OK for Capture and Apply using 4.0 RC2. :)

After Windows Update of that version then Capture and Apply results for me in failing logon of Windows 10. :ph34r:

AFAIK the problem is not related to the program, but is caused by Windows Update of version 1909.

 

Edited by wimb

Share this post


Link to post
Share on other sites

WinNTSetup 4.0 Final

- Added Dark Theme support
- Added multicore appling of WIM
- Added wimlib 1.13.1
- Added bottice 1.3.3.2
- Added Disable Reserved Storage tweak
- Added WIM Capture option
- Added apply mode Wimboot:WIMCOPY
- Added Hotfix uninstall option
- Added Driver Export/Import option
- Added LegacyBootMenu checkbox
- Added exclude section to Tools\Win10Builds.ini
- fixed wimlib apply alters WimBootCompress.ini
- Boot code UEFI will be selected as default in case of EFI system partition
- WOF decompression of \Bootmgr, \EFI\boot\boot*.efi, \EFI\MICROSOFT\BOOT\BOOTMGFW.EFI
- WOF decompression of \Boot\BCD, \EFI\microsoft\boot\BCD
- Does not delete MountedDevices key for non sysprep images
- Allow creation of expandable VHD with any size
- Non fitting expandable VHDs will stop from auto expanding on boot
- Workaround wimgapi "PrepopulateList" bug

  • Like 3

Share this post


Link to post
Share on other sites
32 minutes ago, JFX said:

WinNTSetup 4.0 Final

- Added Dark Theme support
- Added multicore appling of WIM
- Added wimlib 1.13.1
- Added bottice 1.3.3.2
- Added Disable Reserved Storage tweak
- Added WIM Capture option
- Added apply mode Wimboot:WIMCOPY
- Added Hotfix uninstall option
- Added Driver Export/Import option
- Added LegacyBootMenu checkbox
- Added exclude section to Tools\Win10Builds.ini
- fixed wimlib apply alters WimBootCompress.ini
- Boot code UEFI will be selected as default in case of EFI system partition
- WOF decompression of \Bootmgr, \EFI\boot\boot*.efi, \EFI\MICROSOFT\BOOT\BOOTMGFW.EFI
- WOF decompression of \Boot\BCD, \EFI\microsoft\boot\BCD
- Does not delete MountedDevices key for non sysprep images
- Allow creation of expandable VHD with any size
- Non fitting expandable VHDs will stop from auto expanding on boot
- Workaround wimgapi "PrepopulateList" bug

Thank you for this update! Looking forward to trying the capture option.

 

When I try to download the new version, it stops halfway thru and says "Failed - Network error"

 

 

The download finally went thru.

Edited by laddanator

Share this post


Link to post
Share on other sites

Got some weird issues with 4.0 and maybe it's me. I tried to read thru all the pages but at 132 pages, it's not enough time in the day! :) 

 

I have a script that I made that automatically does the loads from images depending on what options you need and then the script loads the variables based on that. We still have some MBR computers and a bunch of UEFI stuff.

 

 This is my WinNTSetup command 

 

start WinNTSetup_x64.exe NT6 -source:"%USBDrive%\WINSETUP\%Folder%\%WIM%" -tempdrive:C: -sysletter:C: -bootdest:%BD% -bcd:%BCD% -runafter:"%USBDrive%\WINSETUP\%Folder%\Copy.cmd" -setup

 

With 3.9.4 this command worked fine, and it shows the right image version in the Windows Image box of 1909, and the image starts right away with no hiccups

C8pzXE.jpg

 

But with 4.0 I am getting this error using that same command above. 

 

IH7ty7.jpg

 

If I click OK and exit out, WinNTSetup starts up but list the wrong image version in the Windows Image Box and then I have to manually click setup. Doesn't show any of the green circles beside MBR, BOOTMGR PBR, or Boot Flag.

 

m797Qr.jpg

 

 

 

Edited by laddanator
  • Like 1

Share this post


Link to post
Share on other sites

Thanks for this great update. Thanks also for your tips about the DPI settings, they worked like a charm. I will also mention this update to some buddies, if you don't mind...

Share this post


Link to post
Share on other sites

@laddanator 4.0.1 should fix command line. Alternative download address: http://jfx.square7.ch/WinNTSetup/

@Atari800XL Sure, please mention this update to your buddies :)

Edited by JFX
  • Like 1

Share this post


Link to post
Share on other sites
32 minutes ago, JFX said:

@laddanator 4.0.1 should fix command line. Alternative download address: http://jfx.square7.ch/WinNTSetup/

@Atari800XL Sure, please mention this update to your buddies :)

Thank you for the fast reply!! The switch thing is working great now but it is still showing "Windows 10 Pro v20h1" instead of 1909. That's not a big deal really, just throwing that out there.

 

I added the line 18700= V1909 to the Win10Builds.ini in 4.01 and the right version is showing up now when I choose my image.

 

Edited by laddanator

Share this post


Link to post
Share on other sites

Hmm yes, wimlib will capture a 1909 with 18363 in XML and wimgapi with 18362.

  • Like 1

Share this post


Link to post
Share on other sites
2 hours ago, JFX said:

Hmm yes, wimlib will capture a 1909 with 18363 in XML and wimgapi with 18362.

Gotcha...I use wimlib to capture my stuff so that makes sense. 

Share this post


Link to post
Share on other sites
On 12/9/2019 at 11:43 AM, wimb said:

Fresh Install of Windows 10 version 1909 on internal SSD is working OK for Capture and Apply using 4.0 RC2. :)

After Windows Update of that version then Capture and Apply results for me in failing logon of Windows 10. :ph34r:

AFAIK the problem is not related to the program, but is caused by Windows Update of version 1909.

Same results obtained for Version 4.0.1

What can be the reason that version 1909 after Windows Update followed by Capture and Apply fails for Windows logon (empty taskbar) ?

Edited by wimb

Share this post


Link to post
Share on other sites
25 minutes ago, wimb said:

What can be the reason that version 1909 after Windows Update followed by Capture and Apply fails for Windows logon (empty taskbar) ?

Depends what you mean what that. Does the logon fails or does it takes unusually long.
Or is it more an frozen explorer.exe as you mentioned taskbar?

Can open taskmgr and kill/restart explorer.exe?

Share this post


Link to post
Share on other sites
36 minutes ago, JFX said:

Depends what you mean what that. Does the logon fails or does it takes unusually long.
Or is it more an frozen explorer.exe as you mentioned taskbar?

Can open taskmgr and kill/restart explorer.exe?

Logon takes longer and icons are missing on taskbar.
Windows Start button and My Computer icon on Desktop and Ctrl +Alt + Delete don't react.
No way to get into Taskmgr .....

Finally Desktop screen disappears and I see mousepointer on black screen .....

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...