Jump to content

JFX

Member
 View Profile  See their activity

  • Posts

    1,277

  • Joined

  • Last visited

  • Days Won

    7

  • Donations

    0.00 USD 

 Content Type 

Posts posted by JFX

    WinNTSetup v5.4.2

    in Install Windows from USB

    Posted

    16 minutes ago, click-click said:

    FYI  - Newer version of IMDisk available: 2.1.1 vs. 2.0.10

    Yes, but IMDisk 2.1.1 no longer supports unpatched Window7 (which include all Win7PE based WinPE and the Windows 7 WinRE).
    If you only use it on updated Windows 7, you can replace the 2 IMDisk files in Tools\imdisk.

    1

    WinNTSetup v5.4.2

    in Install Windows from USB

    Posted · Edited by JFX

    On 8/16/2022 at 4:18 AM, alacran said:

    By the way only fixed size VHDs are capable to Ramboot by means of grub4dos for UEFI + SVBus driver, unless there is new info I'm not aware.

    Last time I checked, SVBus was supporting dynamic VHDs. No RAM saving, but faster loading than fixed VHDs.
    Separate ESP partition does not make much sense here. It depends on Grub2 and this one can load a NTFS driver.


    Hope someone figures how to setup the native vhdramdiskboot from bootmgr.efi.
    If this one support differencing VHDs, I might get some interest in RAM booting again.

    As for your profile, nice one. You could get rid of this WUB, as Windows Update is removed in MinWin anyway.

    0

    WinNTSetup v5.4.2

    in Install Windows from USB

    Posted

    Yeah, there i no wimboot switch, cause wimboot actually means a weeker compression form of xpress.

    Image_path is the name MS choose in imagex.exe

    Quote

     

    Captures a volume image from a drive to a new WIM file.

      image_path - The path to the volume image to be captured.
      image_file - The path of the new WIM file.
      image_name - The unique name for the image being captured.
      description - The text that provides additional reference information.

     

    As for your command line there is no equivalent to "--include-integrity" and you should set "-wimlib" to make sure you actually capture with wimlib and not wimgapi.

    WinNTSetup_x64.exe CAPTURE-CLI J:\ "D:\Wimboot\MinWin-10x64-LZX.wim" "MinWin-10x64-LZX_220803_044206" "MinWin LZX WIMBOOT IMAGE" -compress lzx -config wimscript.ini -wimlib

    0

    WinNTSetup v5.4.2

    in Install Windows from USB

    Posted

    Normally Windows 10 systems above build 17000 don't need any WOF exclusion.

    But there were some reports that it don't work for some people (maybe hardware related).
    None of them told if they used BIOS or UEFI booting. This also makes a difference!
    EFI bootmgr has reading support for compressed files, BIOS bootmgr has not.

    You can set SkipBuildsAbove17000 in Tools\Compact\WimBootCompress.ini if you sure you don't have
    this problem with your machines.

    0

    WinNTSetup v5.4.2

    in Install Windows from USB

    Posted

    There is bit more to translate now in:

    WinNTSetup 5.2.6

    - fixed Feeds did not got disabled on Windows 10
    - added log files wimgapi_error.log and wimlib_error.log
    - added VHD-DIFF option
    - added commandline option VHD-DIFF -file:{file} -parent:{file}
    - added commandline switch for VHD-CREATE -mbresp
    - added commandline switch for VHD-CREATE -vhdbootletter:{0|1}
    - added commandline switch for NT6 -vhdbootfiles:{0|1}
    - new commandline switch -syspart and -tempdrive support VHD(X) files
    - workaround: added AMD's Shadercache to wimscript exclusion (buggy SecurityDescriptors)
     

    3

    WinNTSetup v5.4.2

    in Install Windows from USB

    Posted

    1 hour ago, alacran said:

    --recover-data parameter emulates the way Dism works during apply.

    No, --recover-data ignores data corruption. That's not something that should be simply ignored.
    Wimlib has an error output. Don't know why I have not add this. Will be available in next version.

    BTW: DISABLE_INTEGRITY_CHECKS is useless in BCD loadoptions.

    0

    WinNTSetup v5.4.2

    in Install Windows from USB

    Posted

    Yeah, I guess this is the problem. You change the system disk to be a RAMDisk,
    Windows reacts like this is a full hardware change and will need same SysWoW64 files to be signed.

    You can edit Tools\CATTrim.ini and add the lines: 

    ..\SysWOW64\basesrv.dll
..\SysWOW64\bcryptprimitives.dll
..\SysWOW64\csrsrv.dll
..\SysWOW64\ntdll.dll
..\SysWOW64\kernel32.dll
..\SysWOW64\kernelbase.dll
..\SysWOW64\gdi32.dll
..\SysWOW64\gdi32full.dll
..\SysWOW64\ucrtbase.dll
..\SysWOW64\winsrv.dll
..\SysWOW64\win32u.dll
..\SysWOW64\normaliz.dll
..\SysWOW64\advapi32.dll
..\SysWOW64\bcryptprimitives.dll
..\SysWOW64\cfgmgr32.dll
..\SysWOW64\clbcatq.dll
..\SysWOW64\combase.dll
..\SysWOW64\comctl32.dll
..\SysWOW64\coml2.dll
..\SysWOW64\crypt32.dll
..\SysWOW64\cryptbase.dll

    BTW: there is a newer SVBUS available.

    1

    WinNTSetup v5.4.2

    in Install Windows from USB

    Posted

    Interesting, maybe Tools\CATTrim.ini is still missing some important file that needs to be signed.
    I'll will take a look at some full windows installations. The current file list is only based on my Win10PE research.

    BTW: It should be run against a fully installed Windows,
    cause during setup some SysWoW64 files are scanned and needs to be signed.

    0

    WinNTSetup v5.4.2

    in Install Windows from USB

    Posted · Edited by JFX

    Hi alacran,

    just run it from command prompt:

    WinNTSetup_x64.exe NVRAM 

    NVRAM 1.00

Usage:
NVRAM option [ID|DisplayName]

Options:

 (A)dd      "full_path_to_EFI_File" "DisplayName"
 (D)el      [ID|DisplayName]
 (S)etfirst [ID|DisplayName]
 BootNe(x)t [ID|DisplayName]
 (E)num

 E(n)ter UEFI on next boot

    It's a command line modification of the boot entries and boot order stores in UEFI NVRAM.
    Kinda a command line version of BOOTICE UEFI options.

     

    WinNTSetup_x64.exe CATTRIM 

    CatTrim 1.00 - Only use with WinPE or MinWin installations!

This Will delete "non essential" catalogs in \System32\CatRoot folder!

Usage: CatTrim "Windows directory"

    CatTrim will remove most catalogs in \System32\CatRoot and delete or rebuild the cached database in \System32\CatRoot2 folder.
    That would be fatal for any full windows, but will save some space for a MinWin or WinPE installation.
    It uses Tools\CATTrim.ini as a list of critical files and lookup what *.cat files hold their signature.

    It support online or offline installations.

    3

    WinNTSetup v5.4.2

    in Install Windows from USB

    Posted

    Nothing was changed with VHD creation, maybe your system has a problem with VDS service.
    I will add differencing VHD creation option to next version.

    Don't run it from something else that a NTFS formatted drive, that not fully supported.

    1

    WinNTSetup v5.4.2

    in Install Windows from USB

    Posted

    WinNTSetup 5.2.5

    - updated ADK tools to version 22621.1
    - disables DumpStack.log.tmp file creation
    - disables network requirement for Windopws 11 (disconnected devices only)
    - Logs are saved in \Windows\Log\WinNTSetup\%Date%_%Time%
    - added NVRAM log
    - added NVRAM tool: WinNTSetup_x64 NVRAM
    - added CatRoot trimm tool: WinNTSetup_x64 CATTrim

    2
×
×
  • Create New...