Jump to content


  • Posts

  • Joined

  • Last visited

  • Donations

  • Country

    United States

About laddanator

Profile Information

  • OS
    Windows 7 x86

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

laddanator's Achievements



  1. Gotcha...I use wimlib to capture my stuff so that makes sense.
  2. 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.
  3. 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 But with 4.0 I am getting this error using that same command above. 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.
  4. 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.
  5. Yes, this is my point. wimgapi is faster at apply than wimlib (Or so on my test machine). I plan to test on an older system with low ram to see if the time gap between the two will change.
  6. Not that this info really makes a huge difference to this topic but I ran a little test applying a wimlib capture image (29gigs but 12gigs compressed). I applied the image with wimgapi in 10mins25secs and 11mins27secs with wimlib on the same exact test machine I use to test my images.
  7. Curious if you used "Wimlib" to make the wim would the results be different?
  8. @JFX what command are you using to update the boot record with bootsect and bcdboot when ALL is selected? Are these the commands? bootsect /nt60 C: /force bcdboot C:\windows /s C: /f UEFI
  9. I have a weird error. I am still running 3.8.9 and decided to upgrade to the 3.9.2. I have been starting 3.8.9 from a cmd file for months no problem. I deleted the 3.8.9 files out of the folder and copied in the 3.9.2 and didn't change nothing else and the 3.9.2 will not start from the same cmd line that has worked for months. This is the cmd line that I am using but this has me puzzled. I can double click on the 3.9.2.exe and the program runs fine. WinNTSetup_x64.exe NT6 /Runafter:%LaddsUSB%\WINSETUP\%Folder%\Copy.cmd /cfg:"%LaddsUSB%\WINSETUP\%Folder%\%INI%" /setup Never mind, figured it out. I didn't have libwim-15.dll copied into the new 3.9.2 tools folder as I have that set in my ini.
  10. Thanks for your help! My command lines are much cleaner now! WinNTSetup_x64.exe NT6 /cfg:"%LaddsUSB%\WINSETUP\%Folder%\%INI%" /setup
  11. Ohhhhhhhhhhh! Sorry, I thought the ini set the NT5 or NT6. I will give it another try. Thank you so much for the help.
  12. WinNTSetup_x64.exe /cfg:"D:\WINSETUP\Win7x64Pro\Win7x64Pro.ini" /setup This how I run it, but setup will not start automatically.
  13. I did try that, but didn't work, as in the first part of the setup loaded all the settings, but didn't start the process with both switches. Let me double check myself.
  14. Oh, ok. Anyway I can manually add to push the setup button to my ini?

  • Create New...