Jump to content

JFX

Member
  • Posts

    1,247
  • Joined

  • Days Won

    6
  • Donations

    0.00 USD 

Everything posted by JFX

  1. Found a solution. Next version will respect this setting.
  2. There is no option. Disk index is a file property, thus it is saved inside the WIM file. Maybe, I can alter the attributes during apply. But has this disk indexing setting still any effect since Vista?
  3. No, i should be OK, wimlib is recommended library for creating a WIM file. Just wonder why wimgapi has a trouble with that WIM. Never had any compatibly problems. Expect the LZMS WIM/ESD created by earlier version of WinNTSetup, but they would cause a crash or freeze of the program.
  4. How was this WIM file created?
  5. During this error display there should be a log file: %Temp%\WinNTSetup\Logs\wimgapi_error.log Maybe better to switch to wimlib with (Ctrl + Shift + W) and see if it can apply the WIM.
  6. Is there any problem? You need at least build 25324 as host and source to install.
  7. Sure, please share, when ready.
  8. No, WinNTSetup only applies to one partition. What you are looking for is mklink. Move C:\Windows\Microsoft.NET to d:\Microsoft.NET than create symlink or junction.
  9. Yes, you can specific the drives with letter: WinNTSetup_x64.exe NT6 -syspart:S: -tempdrive:W: or with drive and partition number WinNTSetup_x64.exe NT6 -syspart:HDD1:1 -tempdrive:HDD1:4 Eventually you will need a timeout after diskpart to have drive letter available on system. ping 127.0.0.1 -n 2 > nul
  10. There are all the GUI options you can save with CTRL+S and the 26 hidden option mentioned in the WinNTSetup.ini.txt. Do you need anything in particular? Links are on the first page, do you need another mirror?
  11. No, I mean you can use multi threaded WIM apply also with image.exe or DISM.exe on command prompt by just setting WIM_FileData_Number_Workers environment variable. WinNTSetup will load an existing WinNTSetup.ini on start. This .ini can be loaded or saved with Ctrl + L and CTRL + S hotkey and holds most GUI settings. WinNTSetup.ini.txt describes hidden feature than can be added to WinNTSetup.ini. like: [options] UseMultiCore=1
  12. That's the thread count used by wimgapi. See WinNTSetup.ini.txt, by default if uses half of CPU physical cores. You can uses this with imagex.exe or DISM.exe, too. set WIM_FileData_Number_Workers=8 Imagex /apply ...
  13. Yes, sample.ini is just there to give you an idea of the feature, you supposed to create your own *.ini file based on it.
  14. Yes, create your own RemoveAppx.ini inside DISM folder. Sample.ini is just an example how the .ini it should be formatted.
  15. Seems, I missed adding this to the F1 Help, there is a -dism: switch taking a file name relative to the DISM folder WinNTSetup_x64.exe NT6 -dism:Sample.ini
  16. Yeah this tool is dead. there is simply no need for it anymore. Stick with older version or use adksetup.exe with terrible 45 MB download. If you have a current OS, why would you need them anyway?
  17. If you like, but not sure what difference it would make.
  18. 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
  19. 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.
  20. 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
  21. 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
  22. 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.
  23. 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.
  24. 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.
  25. 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'
×
×
  • Create New...