Jump to content

JFX

Member
  • Posts

    1,254
  • Joined

  • Days Won

    6
  • Donations

    0.00 USD 

JFX last won the day on October 25 2022

JFX had the most liked content!

About JFX

Profile Information

  • OS
    Windows 10 x64

Recent Profile Visitors

28,379 profile views

JFX's Achievements

420

Reputation

  1. Than maybe something is wrong with the WIM files you have.
  2. @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.
  3. 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.
  4. Dunno, maybe a Windows 7 related problem. Try older version like 4.25. Maybe the SWM file is broken, try apply with image.exe.
  5. WinNTSetup 5.3.5.2 - fixed crash with no source selection - removed policy for HiberbootEnabled
  6. Yes, the second policy for HiberbootEnabled has no effect and will be removed. The first one seems to be different between windows versions.
  7. 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\*
  8. It's just a problem with settings app. It properly tries to communicate with Defender and does not get any respond.
  9. Yes, Windows 10 2015 version already uses a 16 MB partition.
  10. 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.
  11. 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
  12. I think you can do this. The error your xml generates is very clear.
  13. @xiaoyue it does work as expected, ignored by older Windows versions, and converted to registry by newer ones.
  14. Adding dark mode for current Windows 10/11 builds, was already several month of work. I don't do this for deprecated windows versions. As for your mistakes: 1) It now longer loads ADK, if the current windows don't needed it. 2) Version display was removed, because some people carelessly updated and just broke supported OS versions, for no reason. 3) That's wanted, looking more current system conform. Re-uploaded, you now can disable these 3 options in WinNTSetup.ini. [Options] NoDownload=0 ShowEngineVersion=1 NewIcons=0
  15. WinNTSetup 5.3.5.1 - fixed language file creation failed with 5.3.5 - fixed capture of mounted VMware disks - added support for multi language WIM files
×
×
  • Create New...