JFX

July 4, 2023

You can edit DISM\Sample.ini or better create your own lets say RemoveAppx.ini.

Remove the netfx3 under [EnableFeature], as it takes some space.
After using DISM option with WinNTSetup, a list of APPX packages the are not removed.

Dism /Image:X:\ /Get-ProvisionedAppxPackages

Add what you want to be removed under [RemoveAPPX] of your ini.

As for space warning, only compact:none has one

July 3, 2023

17 hours ago, Antonino said:

yes, there is one, provided ur disk or vhd has enough space for the initial installation proper, as it is impossible to compact while installing.

:blink: Using mode Compact:XPRESS*K or LZX do compress while extracting the WIM file. Free space check is disabled for these modes.

However to survive setup, tweaks like pagefile and hibernate removal might be necessary.
Using DISM option to remove APPX will also save a lot space.

June 20, 2023

Yeah, that evil thing does not want to stay disabled.
To get back build-in Spyware, save this as .cmd file and run it as admin.

reg delete "HKLM\Software\Policies\Microsoft\Windows Defender" /v DisableAntiVirus /f
reg delete "HKLM\Software\Policies\Microsoft\Windows Defender" /v DisableAntiSpyware /f
reg delete "HKLM\Software\Policies\Microsoft\Windows\System" /v EnableSmartScreen /f
reg delete "HKLM\Software\Policies\Microsoft\Windows Defender\SmartScreen" /v ConfigureAppInstallControlEnabled /f
reg delete "HKLM\Software\Policies\Microsoft\Windows Defender\SmartScreen" /v ConfigureAppInstallControl /f

reg add HKLM\Software\Microsoft\Windows\CurrentVersion\Run /v SecurityHealth /t REG_EXPAND_SZ /d ^%%windir^%%\system32\SecurityHealthSystray.exe
reg delete "HKLM\Software\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\MpCmdRun.exe" /v Debugger /f
reg delete "HKLM\Software\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\MsMpEng.exe" /v Debugger /f
reg delete "HKLM\Software\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\smartscreen.exe" /v Debugger /f

start %windir%\system32\SecurityHealthSystray.exe

June 8, 2023

Interesting, I can't integrate this driver from a German Windows, but no problem with English one.
However I still could not reproduce your problem with minwin :dubbio:

June 8, 2023

It does not seems to be MinWin related. Printers\hplj1020.inf_amd64_5ffa82d4dfa98331 is failing in normal mode, too.

Neither dism nor Dism++ can install this driver.

June 8, 2023

16 hours ago, sakatgg said:

Is it possible to do driver integration in MinWin mode? Thank you.

Yes, it should work in most cases but scanner and printers support is removed in MinWin\Default\Remove\DrvStore_Inf.txt.
Edit or delete the file should help.

@LiveFreeDead No problem here.

from \Windows\Panther\UnattendGC\setupact.log:

2023-06-08 09:17:40, Info                         [Shell Unattend] TimeZone: Time zone set to 'AUS Eastern Standard Time'

@kocoman There is no support for txtsetup.oem. MSSTMake.exe has problem with some SATA drivers, so better integrate them with nLite or Drivepacks.

May 18, 2023

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.

May 18, 2023

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'

April 30, 2023

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.

April 28, 2023

Re-uploaded with wimlib v1.14.1.

April 24, 2023

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

April 13, 2023

Firefox download windows, show the same problem as growing titlebars here.

A sudden jump of NONCLIENTMETRICS caption font from -12 to -16.
Programs that draw their own title like VMware Workstation will be the first that show big titles.
At some point DWM picks this up and all titlebars will be drawn with big fonts.

Don't know if it's related to SAB, but I'm seeing this since October 2021,
so it has nothing to do with a specific version.

April 12, 2023

With version 3.6.3.4670 Start_ShowNetConn no longer fits in any style:

April 8, 2023

I added some log lines for WinNTSetup.log: https://mega.nz/file/KWgX2JKS#liM5r1_ONwfMdUu7Od2xx3rkcDNiRgDUeiufXW2nbMg

April 8, 2023

On 4/7/2023 at 7:48 AM, GT500s said:

I put *.reg files in a folder WinNTSetup\RegTweaks\Win10 (i selected this folder in Tweaks > RegTweaks)

Yes, it should work that way. NT6Only.txt is only there to hide in for XP installs.
A log file is created \Windows\Logs\WinNTSetup\%Date%\WinNTSetup_RegImport.log.
Maybe there is a parsing error.

@Sonic Wimscript folder was moved to out of Tools, but there is also another bug with it.

March 13, 2023

Somehow you overused my mind reading capability, it's not working anymore.
Please ask questions in a way that someone else than you can understand them.

March 13, 2023

If you want classic drive grouping, try this:DriveTypeCategorizer.zip

March 10, 2023

Maybe, you disabled notifications system wide than SIB/SAB updater does not do anything.

March 9, 2023

No, svbus only interprets a loaded image (from grub4dos or grub4efi) as physical disk.

March 9, 2023

It does not support upgrade or repair installation.
You actually overwrite an existing Installation.

March 3, 2023

"VSS ERROR: 80042302" yeah the '0x' is missing. There might be a better message, thought.

March 3, 2023

@Antonino Online capture uses VSS, properly you broke that or optimized it away. Anyways there should be an error message.

March 3, 2023

No idea what your are trying to ask with the first question.
As for ESD apply yeah I have seen a few crashes and dead locks while applying a wimlib captured image with wimgapi or dism.
So switch to wimlib (Ctrl + Shift + W) and apply this ESD.

March 2, 2023

@Antonino Only The Windows11.txt got a new line for windows dev explorer.

March 1, 2023

WinNTSetup 5.3

- compiler updated to PureBasic 6.00 C-Backend
- updated wimlib to version 1.13.6
- right-click on apply mode combo opens Tools\Compact\WimBootCompress.ini
- fixed errors with native 4K drives
- fixed VSS error not displayed
- fixed Bootice Mod always starts in darkmode
- fixed capture problem with OneDrive On-Demand files
- fixed error message on FormatEx failures
- fixed inaccessible devices were listed in drive combo boxes
- fixed offline windows scan may not detect Windows 10/11 builds correctly
- fixed internal VHD boot files option may create duplicate BCD entries
- fixed auto format may not work if drive is in use
- fixed loading ISO with relative path may create duplicates in source combo box
- added commandline switch for VHD-CREATE -uuid:{UUID} (simular to VBoxManage internalcommands sethduuid)
- added WinCopy option (copy Windows from one partition to another)
- added WinCopy and WinCopy-CLI command line
- added ReFS support for Windows 11 23H2
- added combobox script selection to diskpart window
- added -diskpart command line switch to bring up diskpart window
- added WIM_MSG_ERROR and WIMLIB_PROGRESS_MSG_HANDLE_ERROR Messagebox choice
- added Remove OneDrive tweak
- added DISM feature enable/disable and APPX removal
- added possability to disable SFX detection with file: "nosfx" next to WinNTSetup_x64.exe
- new right-click on tweaks button to quickly disable all tweaks
- changed wimlib is the default compression engine
- changed Unattend: Win7-11-Select.xml disables 42 days password expire
- changed rearrage folder layout
- MinWin: support inline comments (//)
- MinWin: grant full admin access to files
- MinWin: fixed VCRuntime 2008 installer needs sxsstore.dll and config\TxR
- MinWin: fixed diskpart shrink needs defragproxy.dll
- RegImport: added support for [?HKEY_LOCAL_MACHINE\...] (only processed if key exists)
- workaround windows 7 Dism /add-driver bug 30 (AMD, NVIDIA drivers with LZSS compression)
- workaround EFI NTFS driver bug

Sign In

JFX

Posts

Joined

Days Won

Donations

Content Type

Profiles

Forums

Events

Posts posted by JFX

WinNTSetup v5.3.4

WinNTSetup v5.3.4

WinNTSetup v5.3.4

WinNTSetup v5.3.4

WinNTSetup v5.3.4

WinNTSetup v5.3.4

WinNTSetup v5.3.4

WinNTSetup v5.3.4

WinNTSetup v5.3.4

WinNTSetup v5.3.4

WinNTSetup v5.3.4

StartAllBack for Windows 11

StartAllBack for Windows 11

WinNTSetup v5.3.4

WinNTSetup v5.3.4

WinNTSetup v5.3.4

Classic Drive Grouping feature in SAB

StartAllBack for Windows 11

WinNTSetup v5.3.4

Error: Entpacken des Installationsarchiv fehlgeschlagen

WinNTSetup v5.3.4

WinNTSetup v5.3.4

WinNTSetup v5.3.4

WinNTSetup v5.3.4

WinNTSetup v5.3.4

Activity

Browse