Jump to content
MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. ×

JFX

Member
  • Content Count

    892
  • Joined

  • Last visited

  • Days Won

    4
  • Donations

    $0.00 

JFX last won the day on February 17

JFX had the most liked content!

Community Reputation

186 Excellent

About JFX

Profile Information

  • OS
    Windows 10 x64

Recent Profile Visitors

10,655 profile views
  1. Glad it works now. The command window is separate process you can close WinNTSetup while it's running. The Wofcompress.exe tool is merge in and can be also used from command line: WinNTSetup_x64.exe wofcompress.
  2. WinNTSetup 4.6.0 - fixed vhd detection regression - fixed dism dowload was missing logprovider.dll - fixed possible freeze caused by PathCompactPath - fixed possible freeze with "-noapply" mode - fixed some High DPI issues - fixed commandline iso attach did not return errorlevel for driveletter - dismount of vhd with hidden bootpart will force remove all it's drive letters - driver integration now uses dismapi, trys to avoid adding drivers of different architecture - driver export now sorts by driver class - move Tools\WimBootCompress.ini to Tools\Compact\ - logging co
  3. Hi Renodos, not really, WinNTSetup needs an WIM or ESD image to work with. However, you could capture this WTG to a WIM file and use this - let's call it backup.wim - as source. Only downside with this is that no Recovery menu option (WinRE) will be created.
  4. Yes, but you should focus more on your system: Check if there is a image in: %AppData%\Microsoft\Windows\AccountPictures that matches HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\AccountPicture, SourceId. Clear thumbnail cache. Try to temporary chance the picture.
  5. There is no problem with avatar here, 19043.844 with SIB 2.9.8.
  6. WinNTSetup 4.5.1 - VHD GUI will be saved to ini - ini option BootMountExclude supports DiskID - fixes listview font on non darkmode
  7. Right, for 2 equal disk vendor name is useless here, next version will support disk id.
  8. Run from admin cmd.exe: WinNTSetup_x64.exe disks
  9. WinNTSetup 4.5.0 Final - Dropped 32-Bit version, system requirements are now Windows 7x64 + - VHD functions no longer uses diskpart.exe - VHD Attach / Detach supports ISO files - VHD Creation supports GPT Partitionsttyle - VHD Install will always create internal boot files depending on partition style - new default VHD creation type MBR - BIOS/UEFI - added VHD command line options /gpt and /mbr - fixed instant VHD creation cylinder bug - fixed iso mount does not select install.swm - Fixed open file dialog pattern not working on default WinPE 3.x + - Fixed wimgapi captu
  10. RC3 is out, if there no bugs anymore, this one will be final soon.
  11. RemoveBootMountsOnExit does remove the mounted boot partitions (active primary or ESP) usually mounted as Z:. There was a bug with this option, you will need the re-download RC2.
  12. WinNTSetup 4.5.0 RC2 - new ini option "RemoveBootMountsOnExit" - rewrote all file and registry recursion functions to use iteration - command line VHD creation uses expandable by default - command line VHD ignores disk size for expandable type - fixed iso mount does not select install.swm
  13. WinNTSetup 4.5.0 RC1 - ini option BootMountExclude supports Vendor name - fixed VHD drive letter assignment - fixed Windows 7/8 compatiblity
  14. They have an EFI folder on the second partition. Hidden Sectors should be equal to diskpart now. Both use the offsets from HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\vds\Alignment I guess this is a Grub problem, they booting attach to VMWare in BIOS and UEFI mode.
×
×
  • Create New...