Jump to content

WinNTSetup v5.3.5.1


JFX

Recommended Posts

  • JFX changed the title to WinNTSetup v5.3.1

WinNTSetup 5.3.1

- updated wimlib to version 1.14.1 (faster wim capture)
- fixed GUI capture may ignores WimScript.ini
- fixed wimlib LZMS capture did not used solid compression
- fixed auto format option should disable free space warning
- fixed wincopy/wimcapture could not be canceled during VSS creation
- fixed Win7-11-Select.xml required all fields to be set
- added some support for MinWin with ARM64 sources
- added commandline switch: -NoTweaks
- much faster wincopy (wimlib mode)
- changed wimboot/compact mode don't use exclusion for GPT formated disk
 

Edited by JFX
Link to comment
Share on other sites

On 4/28/2023 at 9:27 AM, JFX said:

Re-uploaded with wimlib v1.14.1.

I did a wimlib capture on a generalized sysprep partition both with wimlib 1.3.4 and 1.4.1. Your change.log indicates a faster capture with 1.4.1. My times don't agree with that. 1.3.4=15 min. and 1.4.1=18 min. In what way is 1.4.1 supposed to be faster? I used the following command each time:

u:\$W0\Wimlib\WimCapture.cmd q: u:W81ProWMC_04Rebase.wim "Windows 8.1.1 Pro with Media Center" --config=u:wimscript.ini

Link to comment
Share on other sites

3 hours ago, click-click said:

In what way is wimlib 1.14 supposed to be faster?

New wimlib has a (more) optimized SHA-1 hashing.
During a wimcapture operation all files are being hashed, thus hashing speed makes difference.
Even more if you are appending a WIM, were only new files are being compressed.

However, you need a recent CPU to notice any difference.

Link to comment
Share on other sites

  • 2 weeks later...

caveat for those of u who use drivergenius. here below is a list of syswow64 files (most of them dlls, for that matter) that let it work even in miniwinned versions:

!\Windows\SysWOW64\advapi32.dll 
!\Windows\SysWOW64\advpack.dll 
!\Windows\SysWOW64\AppResolver.dll 
!\Windows\SysWOW64\BCP47Langs.dll 
!\Windows\SysWOW64\bcrypt.dll 
!\Windows\SysWOW64\bcryptprimitives.dll 
!\Windows\SysWOW64\cfgmgr32.dll 
!\Windows\SysWOW64\clbcatq.dll 
!\Windows\SysWOW64\combase.dll 
!\Windows\SysWOW64\coml2.dll 
!\Windows\SysWOW64\CoreMessaging.dll 
!\Windows\SysWOW64\CoreUIComponents.dll 
!\Windows\SysWOW64\crypt32.dll 
!\Windows\SysWOW64\d3d11.dll 
!\Windows\SysWOW64\DataExchange.dll 
!\Windows\SysWOW64\dcomp.dll 
!\Windows\SysWOW64\devobj.dll 
!\Windows\SysWOW64\dnsapi.dll 
!\Windows\SysWOW64\dwmapi.dll 
!\Windows\SysWOW64\DWrite.dll 
!\Windows\SysWOW64\dxgi.dll 
!\Windows\SysWOW64\edputil.dll 
!\Windows\SysWOW64\FWPUCLNT.dll 
!\Windows\SysWOW64\gdi32.dll 
!\Windows\SysWOW64\gdi32full.dll 
!\Windows\SysWOW64\iertutil.dll 
!\Windows\SysWOW64\imm32.dll 
!\Windows\SysWOW64\IPHLPAPI.dll 
!\Windows\SysWOW64\kernel.appcore.dll 
!\Windows\SysWOW64\kernel32.dll 
!\Windows\SysWOW64\KernelBase.dll 
!\Windows\SysWOW64\mpr.dll 
!\Windows\SysWOW64\msasn1.dll 
!\Windows\SysWOW64\msctf.dll 
!\Windows\SysWOW64\msimg32.dll 
!\Windows\SysWOW64\msvbvm60.dll 
!\Windows\SysWOW64\msvbvm60.dll 
!\Windows\SysWOW64\msvcp_win.dll 
!\Windows\SysWOW64\msvcrt.dll 
!\Windows\SysWOW64\mswsock.dll 
!\Windows\SysWOW64\msxml6.dll 
!\Windows\SysWOW64\msxml6r.dll 
!\Windows\SysWOW64\netutils.dll 
!\Windows\SysWOW64\nsi.dll 
!\Windows\SysWOW64\ntdll.dll 
!\Windows\SysWOW64\ntmarta.dll 
!\Windows\SysWOW64\ole32.dll 
!\Windows\SysWOW64\oleacc.dll 
!\Windows\SysWOW64\oleaccrc.dll 
!\Windows\SysWOW64\oleaut32.dll 
!\Windows\SysWOW64\oledlg.dll 
!\Windows\SysWOW64\olepro32.dll 
!\Windows\SysWOW64\OnDemandConnRouteHelper.dll 
!\Windows\SysWOW64\OneCoreCommonProxyStub.dll 
!\Windows\SysWOW64\OneCoreUAPCommonProxyStub.dll 
!\Windows\SysWOW64\profapi.dll 
!\Windows\SysWOW64\propsys.dll 
!\Windows\SysWOW64\rasadhlp.dll 
!\Windows\SysWOW64\rpcrt4.dll 
!\Windows\SysWOW64\scrrun.dll 
!\Windows\SysWOW64\sechost.dll 
!\Windows\SysWOW64\setupapi.dll 
!\Windows\SysWOW64\SHCore.dll 
!\Windows\SysWOW64\shell32.dll 
!\Windows\SysWOW64\shlwapi.dll 
!\Windows\SysWOW64\slc.dll 
!\Windows\SysWOW64\sppc.dll 
!\Windows\SysWOW64\srvcli.dll 
!\Windows\SysWOW64\sspicli.dll 
!\Windows\SysWOW64\stdole2.tlb
!\Windows\SysWOW64\sxs.dll 
!\Windows\SysWOW64\TextInputFramework.dll 
!\Windows\SysWOW64\TextShaping.dll 
!\Windows\SysWOW64\twinapi.appcore.dll 
!\Windows\SysWOW64\ucrtbase.dll 
!\Windows\SysWOW64\urlmon.dll 
!\Windows\SysWOW64\user32.dll 
!\Windows\SysWOW64\userenv.dll 
!\Windows\SysWOW64\uxtheme.dll 
!\Windows\SysWOW64\version.dll 
!\Windows\SysWOW64\win32u.dll 
!\Windows\SysWOW64\Windows.StateRepositoryPS.dll 
!\Windows\SysWOW64\windows.storage.dll 
!\Windows\SysWOW64\WindowsCodecs.dll 
!\Windows\SysWOW64\winhttp.dll 
!\Windows\SysWOW64\wininet.dll 
!\Windows\SysWOW64\winmm.dll 
!\Windows\SysWOW64\winnsi.dll 
!\Windows\SysWOW64\winspool.drv
!\Windows\SysWOW64\winsta.dll 
!\Windows\SysWOW64\wintrust.dll 
!\Windows\SysWOW64\WinTypes.dll 
!\Windows\SysWOW64\wldp.dll 
!\Windows\SysWOW64\ws2_32.dll 
!\Windows\SysWOW64\ws2help.dll 
!\Windows\SysWOW64\wshom.ocx
!\Windows\SysWOW64\wsock32.dll 
!\Windows\SysWOW64\wtsapi32.dll 

 

I checked the list with process explorer while driver genius was still on, so these are the files that the sofware "invokes" or expects to find in syswow64.
 

 

Edited by Antonino
Link to comment
Share on other sites

  • 2 weeks later...

In Win7-11-Select.xml added launch FirstLogon.cmd but the commands don't work. Does WinNTSetup v531a support FirstLogon.cmd?

SetupComplete.cmd works immediately, by default, did not edit anything, Win11 22H2 22624.1680

      <FirstLogonCommands>
        <SynchronousCommand wcm:action="add">
          <CommandLine>C:\Windows\Setup\Scripts\FirstLogon.cmd</CommandLine>
          <Order>1</Order>
        </SynchronousCommand>
      </FirstLogonCommands>

P.S.
The start of firstlogon.cmd is obtained if you register in SetupComplete.cmd

reg add HKLM\Software\Microsoft\Windows\CurrentVersion\RunOnce /v firstlogon /t REG_SZ /d %windir%\Setup\Scripts\firstlogon.cmd /f


Still, it is interesting through Win7-11-Select.xml, is it possible to start and work firstlogon.cmd?

Edited by sakatgg
Link to comment
Share on other sites

12 hours ago, sakatgg said:

Still, it is interesting through Win7-11-Select.xml, is it possible to start and work firstlogon.cmd?

No problem here, just adding a SynchronousCommand to Win7-11-Select.xml.

<?xml version="1.0" encoding="utf-8"?>
<!--

[WinNTSetup]
process=1

;process 1 - asks for user input and replaces all 4 %variables%
;process 2 - don't ask and only replaces %WinNTSetup-Arch%

;WinNTSetup-Arch
;WinNTSetup-User
;WinNTSetup-PC
;WinNTSetup-Group

-->
<unattend xmlns="urn:schemas-microsoft-com:unattend">

  <settings pass="specialize">
   <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="%WinNTSetup-Arch%" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
     <ComputerName>%WinNTSetup-PC%</ComputerName>
   </component>
   <component name="Microsoft-Windows-UnattendedJoin" processorArchitecture="%WinNTSetup-Arch%" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
     <Identification>
       <JoinWorkgroup>%WinNTSetup-Group%</JoinWorkgroup>
     </Identification>
   </component>
  </settings>


  <settings pass="oobeSystem">
    <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="%WinNTSetup-Arch%" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="NonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
      <UserAccounts>
        <LocalAccounts>
          <LocalAccount wcm:action="add">
            <Name>%WinNTSetup-User%</Name>
            <Group>Administrators</Group>
            <Password>
              <PlainText>true</PlainText>
              <Value />
            </Password>
          </LocalAccount>
        </LocalAccounts>
        <AdministratorPassword>
          <Value />
        </AdministratorPassword>
      </UserAccounts>
      <AutoLogon>
        <Password>
          <Value />
        </Password>
        <Enabled>true</Enabled>
        <LogonCount>1</LogonCount>
        <Username>%WinNTSetup-User%</Username>
      </AutoLogon>
      <OOBE>
        <NetworkLocation>Home</NetworkLocation>
        <HideEULAPage>true</HideEULAPage>
        <HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE>
        <SkipMachineOOBE>true</SkipMachineOOBE>
        <SkipUserOOBE>true</SkipUserOOBE>
      </OOBE>
      <FirstLogonCommands>
        <SynchronousCommand wcm:action="add">
          <CommandLine>net accounts /maxpwage:unlimited</CommandLine>
          <Order>1</Order>
        </SynchronousCommand>

        <SynchronousCommand wcm:action="add">
          <CommandLine>C:\Windows\Setup\Scripts\FirstLogon.cmd</CommandLine>
          <Order>2</Order>
        </SynchronousCommand>
      
      </FirstLogonCommands>
    </component>
  </settings>
</unattend>

If I see this right, FirstLogonCommands are actually converted to RunOnce registry values.
So there is no logging, if something goes wrong. They are only mentioned in \Windows\Panther\UnattendGC\setupact.log:

2023-05-18 15:23:26, Info                         [Shell Unattend] LogonCommands: Set command 'net accounts /maxpwage:unlimited' 
2023-05-18 15:23:26, Info                         [Shell Unattend] LogonCommands: Set command 'C:\Windows\Setup\Scripts\FirstLogon.cmd' 

 

Edited by JFX
Link to comment
Share on other sites

Using a unattend.xml, you can launch programs, just before desktop icons and taskbar appears.
WinNTSetup's tweaks are limited, but FirstLogonCommands do run with admin rights, so you can do any customization in these scripts.

Link to comment
Share on other sites

JFX, Now firstlogon.cmd starts normally via Win7-11-Select.xml. Thank you.

And in general, thank you for such a wonderful program. :worship:

Edited by sakatgg
Link to comment
Share on other sites

  • 3 weeks later...

Integration of drivers for USB controllers, scanners, printers on WinNTSetup_v531a is going well.
But when the MinWin mode is enabled, the drivers are not integrated.
Is it possible to do driver integration in MinWin mode? Thank you.

Link to comment
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   1 member

×
×
  • Create New...