Jump to content

JFX

Member
  • Posts

    1,238
  • Joined

  • Days Won

    6
  • Donations

    0.00 USD 

Posts posted by JFX

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

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

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

  5. Hi Atari800XL,

    I don't know why Microsoft releases this Validation OS. Seems to be a very bare bone version of windows.

    It's not a WinPE, but seems to have far less features.
    So I failing to see the point of it. Why would anyone use this instead of a normal boot.wim or ADK WinPE :dubbio:

  6. 1 hour ago, Tihiy said:

    - Workaround Windows bug resulting in too wide taskbar buttons

    Seems to ignore MinWidth.

    Windows Registry Editor Version 5.00
    
    [HKEY_CURRENT_USER\Control Panel\Desktop\WindowMetrics]
    "MinWidth"="250"

     

  7. Hmm, I'm not so sure I know what you mean.

    I guess you now have 2 option in boot menu - your old installation and the new one that is ready to setup?
    What the system you wanted to installed a NT6.x one (Win Vista - Win11) or NT5 one?

  8. WinNTSetup 5.2.4

    - fixed Regimport did not support multi line binary data with inline comments
    - MinWin: added support for Unicode / UTF-8 text files
    - MinWin: added support for subfolders
    - MinWin: text files can have condition on first line to enable/disable the entire file
     

  9. Most of these log files can simply be disabled in the registry, but yes I'll should add a "dummy file" feature.
    Dxdiag.exe should be deleted. There are some hundred of *.exe files that could also be deleted,
    but I did not want to make a choice for default profile.

×
×
  • Create New...