Jump to content

JFX

Member
  • Posts

    1,254
  • Joined

  • Days Won

    6
  • Donations

    0.00 USD 

Posts posted by JFX

  1. Drive letter assignment is really simple stuff.

    WinNTSetup will calculate and write \DosDevices\C: to HKLM\SYSTEM\MountedDevices
    On first boot Windows will recognize a different drive letter and does all the work. 

      

    On 3/4/2024 at 1:35 PM, wuliyen said:

    There is still a problem that needs to be fixed
    Windows\Boot\PCAT\zh-CN\bootmgr.exe.mui
    This file needs to be kept

     This version will add logging for black and whitelist as well MUI and MUN file removal.

  2. 3 hours ago, click-click said:

    The apply image is not broken because it installs fine to a partition. What could be the problem with the install to vhd and how to fix?

    Start by looking at the log files: \Windows\Panther.
    Maybe your BCD is a bit unusual are edit it to much with bootice.

    Maybe you some alternative boot manager.

  3. 6 hours ago, sakatgg said:

    But the folder is deleted in both Server 2019 and Win11

    If there is a way to make the filter work in NetFX.txt? Thank you.

    Are you sure you don't delete it somewhere else. Lines that get skipped will be logged:

    \Windows\Logs\WinNTSetup\*\MinWin_WimHost.log

  4. On 2/19/2024 at 1:06 PM, dimo70 said:

    Maybe better include ability scanning for sources in next version of WinNTSetup?

    I don't plan any new version. Create your own tool for scanning or modify the scanfiles.cmd to your need.

     

    16 hours ago, Antonino said:

    sorry about changing the subject - would anyone tell me how to change the default x: vhd drive into any other one when creating it in winntsetup? me, I would be better off having i: as the default vhd drive instead.

    Change it with Disk management or bootice and hit F5 in WinNTSetup.

  5. I would say steve6375 has already given the right answer.

    WinNTSetup only applies the WIM to the VHD and create boot files.
    The image is still in sysprep phase and therefor will try to "specialize" the BCD store on first boot.

    If he immediately boot that VHD with Ventoy it will cause that error.
    I don't know how Ventoy boot it, but i guess it uses a virtual boot drive like NTBOOT.
    And that can't be seen later in the boot process.

    For the "hidden menu" he will need to use newer version.

  6. WinNTSetup 5.3.4

    - fixed problems starting as TrustedInstaller on some machines
    - fixed rare heap corruption
    - fixed CompactOS was ignored for Windows Server versions
    - Removed offreg.dll (will be downloaded for older Windows)
    - MinWin uses build number from registry rather than WIM
    - MinWin removed hard coded pathes
    - MinWin WinSxS.ini - can use "!" to avoid old components removal
    - MinWin WinSxS.ini can be deleted
    - MinWin fixed wincopy mode bug

  7. 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.

     

  8. 2 hours ago, mrjonnyHello said:

    (continue from post 1) The options I used at build time (S and X were partitions 1 and 2 on vhd)

    Not sure what to try next 😟

    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).

×
×
  • Create New...