Jump to content

JFX

Member
  • Posts

    1,239
  • Joined

  • Days Won

    6
  • Donations

    0.00 USD 

Everything posted by JFX

  1. WinNTSetup.ini.txt only show the hidden options. Most of them are uses in initialization and can't be changed later while loading a new ini file. if you want to document the normal GUI options, sure do and I will add it.
  2. WinNTSetup 5.3.2 - native ARM64 code for WIM apply and capture - WIM apply and capture will be executed as "trusted installer" - WIM capture UI adds compression level, defaults to wimlib's LZX Fast - wimlib wimboot apply - changed overlay type to WIM_BOOT_OS_WIM - wimlib capture WIM - deletes incomplete WIM after operation cancel - wimlib smooth progress bar for appending operation - using customized wimlib.dll (do not update!) - automatically switch to wimlib, if wimgapi can not load WIM file - fixed cancel setup was ignored during DISM operations - fixed WinCopy Volume mode problems - fixed some issues with ARM64 sources - added advanced VHD creation options - respect NTFS indexing option on target partition - no longer downloads ADK files on Win10/11 Host
  3. A warning, yes that should be added. But more options will not be added. It's just a simple action like get used clusters and copy them. Adding exclusions would require complete MFT parsing, what I don't have the time to implement.
  4. Mount the VHD and than create backups like you do on every other normal disk system. Either a disk imaging software like Acronis TI, Macrium Reflect or a file backing image like a WIM backup.
  5. Yes, it working for me, using it from time to time. But the grow rate is quite high. Just booted a diff and shutdown after 3 minutes it grow to 1.42 GB. You could simplify this without editing BCD. Just rename the VHD to let's say Base.vhd and create a diff with the old name. Also make sure that parent and diff vhd are in the some folder.
  6. Maybe, differencing VHDs are not the best choice for you Have not seen that 0xC0000000f error. Could be a problem coming from Bootice edit.
  7. No, but {default} is the correct one. "bcdedit -v -store Q:\Boot\BCD" would show the correct GUID, but you can use symbols like {default} or {current}, too.
  8. "bcdedit -store Q:\Boot\BCD" should print something like this:
  9. Yes, that would require to do all steps manually. Update BCD with bcdedit.exe: Get the %GUID% form bcdedit -store S:\EFI\Microsoft\Boot\BCD than update device and osdevice: bcdedit -store S:\EFI\Microsoft\Boot\BCD -set %GUID% device vhd=[C:]\diff.vhd bcdedit -store S:\EFI\Microsoft\Boot\BCD -set %GUID% osdevice vhd=[C:]\diff.vhd
  10. No, you have to do this manually.
  11. You create a diff.vhd and use this for everything (mounting or booting via BCD). If you make any changes to the base.vhd the diff will be invalid.
  12. Hi dimo70, if the selected boot partition is GPT, WinNTSetup automatically switch to UEFI only for bcdboot.exe. unless BCD option is set by ini or command line. This was requested years ago and actually makes sense. But if you use legacy boot with a GPT hybrid MBR, this causes promlems. Makes sure you set BCD option to "ALL".
  13. Yes, simple use a filename with .vhdx extension and it will create a VHDX file.
  14. Just guessing will not help much. WinNTSetup already uses these 2 commands. bcdboot.exe W:\Windows /s S: /f ALL bootsect.exe /nt60 S: /mbr Were W: is the Windows installation drive and S: is the selected boot partition. Only difference I see is the missing /force switch on bootsect command. But this is done on purpose, also diskpart does write bootable MBR and PBR. If you encounter the problem again try 1 of these command from a WinPE, to find out witch one makes a bootable again.
  15. That sounds like a problem with the MBR of the boot disk. By default WinNTSetup uses bootsect to update the boot sectors. bootsect.exe /nt60 S: /mbr The first 2 green lights are only using simple checks, there is no way to tell if the code is actually bootable. To limit the problem, it depends on what repair you do with bootice.
  16. Wimlib is only faster for capture. For apply there actually more or less equal. Just wimgapi can use more than 1 CPU core, so it can speed up quite a bit.
  17. Thanks, it looks good One thing, if I use "UEFI original Script" it ends up selecting the MSR partition as boot drive.
  18. Found a solution. Next version will respect this setting.
  19. 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?
  20. 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.
  21. How was this WIM file created?
  22. 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.
  23. Is there any problem? You need at least build 25324 as host and source to install.
  24. Sure, please share, when ready.
  25. 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.
×
×
  • Create New...