Jump to content

JFX

Member
  • Posts

    1,238
  • Joined

  • Days Won

    6
  • Donations

    0.00 USD 

Everything posted by JFX

  1. \windows\system32\config should never be deleted. If it happens without you using telling it to do, then it's a bug.
  2. Good you remind me about CompactOS and Server. It works so I'll remove this limitation. ! for WinSxS.ini will be supported. I think about making this ini optional. That should make things easier for people that just want to remove some files.
  3. They were actually test versions for some problems that I could not reproduce. As there was not much feedback, i have to assume that all is fixed now. I will release an update, maybe next week.
  4. Hi, no it's not a BETA version. It's the latest stable.
  5. There is a command line tool for Group Policy: LGPO.exe. It should be possible to restore a saved backup in setupcomplete.cmd or FirstLogonCommands.
  6. Nope, it's not possible to do this with registry.
  7. That error means you did not run _DeltaPatchWinXP\FixWinXP.cmd.
  8. Than use 3.8.6. Legacy version will not get any updates or fixes.
  9. I would say that the problem, you create the boot files inside the VHD. You should select the bootable partition on local disk (I guess on disk 0).
  10. The one in system32 folder is to old for users of Windows 7 or 8, so a newer version needs to be downloaded. Current ADK does not support Windows 7 therefore the files will be patched.
  11. There is nothing I can do about. Looks like MS did only update the ReFS driver, but forgot to update the boot loader.
  12. Good, next check if the service (WLANSVC) is running. and check wlan interfaces. netsh wlan show interfaces Maybe reapply reg file for classic taskbar flyout: MinWin\Default\Reg\SysTray_Network_Flyout.reg @wuliyen There will be only a few bug fix releases, but I don't plan to add any new features. WinNTSetup development is more or less frozen, but not yet discontinued.
  13. @wuliyen Oh, right I was thinking about WinSxS folder, but you showed WindowsApps. It does work here and keeps all 5 folders. Maybe it's Windows setup that removes them depending on the "scale factor" of the newly installed Windows. @dimo70 You need to use GPT format for UEFI boot only and select the FAT32 ESP partition as boot drive.
  14. @Antonino Blindly add files may not be the best way. First make sure you can install the driver and it show's correctly in device manager. @wuliyen That's a feature, read from here.
  15. @Atari800XL I don't get any error message from Setup, if WinRe.wim is deleted. (at least not from 22631.2861.231204-0538.23H2_NI_RELEASE_SVC_REFRESH_CLIENTBUSINESS_VOL_x64FRE esd files) BTW: if I also delete the ReAgent.xml there is no error in the log file, only warning. @Antonino Lines beginning with ; or # are ignored and reserved for comments. You can also rename all the *.txt files inside Remove folder to *.ini. This should give comments a different color depending on the Editor you use.
  16. Could it be you booted into this new windows and forgot to select "show hidden files" in folder options?
  17. No, problem with Win11 23H2 v2 ISO. Also I don't no what to do about. If files are applied correctly and Windows Setup is deleting them, than it's not a bug of WinNTSetup.
  18. Seems we lost some posts here. Reattach last WimHost fix. WIMHost_1.0.0.7.zip
  19. Not, possible with the WinSxS.ini. These folder are always deleted: \Windows\servicing\LCU \Windows\WinSxS\Temp\InFlight \Windows\WinSxS\Temp\PendingRenames \Windows\WinSxS\Backup \Windows\WinSxS\FileMaps They should be only needed by Windows Update. I'll rethink the last 4, maybe add an option for this.
  20. Yeah, installing optional components isn't supported with default minwin profile. Replace Tools\x64\WIMHost.exe If you add a ! at line begin it should keep all version.
  21. The filter \Windows\WinSxS\Manifests\amd64_microsoft.activedirectory.management_31bf3856ad364e35_10.0.17763.* matches for both: \Windows\WinSxS\Manifests\amd64_microsoft.activedirectory.management_31bf3856ad364e35_10.0.17763.1_none_095c3cc5ce4cc481.manifest \Windows\WinSxS\Manifests\amd64_microsoft.activedirectory.management_31bf3856ad364e35_10.0.17763.1490_none_6621891b47f3382c.manifest Every wildcard filter will only keep the newest component (17763.1490), all older we be removed. Whats are you trying to accomplish with all these files?
  22. Hmm, WimBoot wasn't supported by Server version, so I skipped the the apply modes. But it seems that Compact mode works. I'll check more Server version and remove this restriction in next version. Good, question with Win10/11 this is no longer a problem. You can try with bootice, it can partition the flash drive with multiple partitions. It allows you to assign a drive letter to only 1 partition at the time. Not sure how WinNTSetup's drive letter assignment will behave in this case Will have to check this out ...
  23. Yeah, this is a problem with obsolet version removal. This filter \Windows\WinSxS\%ARCH%_microsoft-windows-d..erservice.resources_31bf3856ad364e35_10.0.17763.*_%LANG%_* matches both, so only one remains. For now you could solve it with 2 filters: \Windows\WinSxS\%ARCH%_microsoft-windows-d..erservice.resources_31bf3856ad364e35_10.0.17763.*_%LANG%_3a6bba1e80fb955e* \Windows\WinSxS\%ARCH%_microsoft-windows-d..erservice.resources_31bf3856ad364e35_10.0.17763.*_%LANG%_7226aa566821f809*
  24. You should format the boot partition with FAT32, not the entire disk. create a small let's say 500 MB FAT32 partition for the boot files and use the remaining space as you want
×
×
  • Create New...