Jump to content

JFX

Member
  • Posts

    1,267
  • Joined

  • Last visited

  • Days Won

    6
  • Donations

    0.00 USD 

Everything posted by JFX

  1. SAB tires to start ImmersiveShellController before sending Local\ShellStartupEvent, this can't work in a WinPE. It's ok with a tiny twinui.pcshell.dll, but maybe SAB could ignore this check if: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\MiniNT key exists.
  2. WinNTSetup has an option to save drive letter assignment. If this not works for you, than manually backup the registry value of your Z: under HKEY_LOCAL_MACHINE\SYSTEM\MountedDevices.
  3. It is the same syntax as the ini file uses: WinNTSetup_x64.exe NT6 -sysPart:HDD0:1 -tempDrive:Z: -sysLetter:C: -bcd:EFI -silent -setup
  4. Yes, seems there got something wrong with the rar creation. WinNTSetup 5.4.1 - added missing LANG folder - bootice language files prefer MUI names - disabled multicore apply for x86 version. - removed system menu integration
  5. See first post as usual. Merry xmas and a happy new year to all.
  6. WinNTSetup 5.4 - support for Windows 24H2 and Server 2025 - added arm64 and x86 versions - language files prefer MUI names - support for RTL languages - use only one DISM session - fixed Windows 7 ESP drive mounting - updated Windows 7 USB3 drivers instructions - new disable defender tweak includes Windows Malicious Software Removal Tool
  7. The NTFS permissions comes from the WIM file. MinWin apply only changes the admin rights (MinWin\Default\Options.ini --> AdminAccess = 1) EDIT: I'll disable AdminAccess in next version, it's useful to test and modify MinWin installation, but should not be default.
  8. Did you make any progress on this? Sounds like the USB disk becomes inaccessible during boot. Did you tried different hardware to boot the USB disk? Is there any difference with official Windows To Go setup?
  9. No, it does not touch this value. 0x1C - is the default on Windows 10/11, so I wonder why you have a different one.
  10. WinNTSetup_x64.exe NT6 -sysPart:Q: -tempDrive:Z: -sysLetter:-C: -bcd:ALL -silent -setup
  11. Yes, the currently running system has the correct data in \DosDevices\Z:. The offline system has invalid data in \DosDevices\C:
  12. Mountpoints are calculated, but if you want to do it manually Look up the data of the new partition under HKEY_LOCAL_MACHINE\SYSTEM\MountedDevices and add it to the offline systems registry \DosDevices\C: value. I doubt that. VHDs are unique, you need to updated the BCD for every new VHD.
  13. Fixing mountpoint of system drive is always done, there is no special command line switch needed.
  14. Than maybe something is wrong with the WIM files you have.
  15. @ibay770 WinNTSetup has reach EOL status. You could use it's command line options to automate these steps. @hhui Access denied error is very common with wimgapi or Dism, WinNTSetup already use Trusted Installer rights to overcome some of them. You could try wimlib (top right window icon --> WIM API --> wimlib) for apply instead.
  16. Windows 7 in UEFI mode is a bit picky about partition layout. It only support GPT. The backported driver were update and are now signed with SHA-256. So this method does not work, unless you find the older drivers.
  17. Dunno, maybe a Windows 7 related problem. Try older version like 4.25. Maybe the SWM file is broken, try apply with image.exe.
  18. WinNTSetup 5.3.5.2 - fixed crash with no source selection - removed policy for HiberbootEnabled
  19. Yes, the second policy for HiberbootEnabled has no effect and will be removed. The first one seems to be different between windows versions.
  20. Yes, MinWin focus on deleting files. It's unusual to delete complete folder and than want to keep it. In that case, use wildcard pattern: !\Windows\SysWOW64\WindowsPowerShell\*
  21. It's just a problem with settings app. It properly tries to communicate with Defender and does not get any respond.
  22. Yes, Windows 10 2015 version already uses a 16 MB partition.
  23. Because older Windows versions used a 128 MB MSR partition. The default unattend and diskpart scripts should work for all OS, but you are free to edit them or add your own.
  24. No, <ProductKey> is not supported with WinNTSetup's direct WIM apply. Maybe you can use FirstLogonCommands to run: slmgr /ipk M7XTQ-FN8P6-TTKYV-9D4CC-J462D
  25. I think you can do this. The error your xml generates is very clear.
×
×
  • Create New...