wimb

Thanks, Crash Fix of WinNTSetup4 Beta 4 is working OK

Wrong type of wim file like boot.wim gives now when pressing Setup - Warning Windows Source invalid So the crash is gone and this solution is OK. There is another problem present in 4.0 Beta3 and Beta4 In case wimlib is used and Mode Wimboot Selected then After pressing Setup the program crashes. Using WimGAPI (all cases) Or wimlib with Mode Wimboot Unchecked Or other Mode are working OK. In version 4.0 Beta1 and Beta2 this problem did not yet occur.

Selecting a wrong type of wim file should be refused by the program. Now boot.wim can be selected as installation file and then pressing Setup results in program crash.

For Install of XP in VHD Download VHD_XP_Setup with Support Topic VHD_XP_Setup

I found a bug in WinNTSetup4 Beta 2 After launching WinNTSetup, then I can Load a previously Saved .ini file with Settings to overrule the default WinNTSetup.ini It turns out that the Tweaks from that previously other saved .ini file are not taken into account to switch off tweaks, allthough the switch offs are present correctly in that saved .ini file. Also the program WinNTSetup crashes when a wrong type of wim file like boot.wim is selected. May be for the unexperienced user it is good to give WARNING - This WIM file is Not Valid as Installation file

You might consider to Add in the Download of WinNTSetup4 some useful Tools, so that they are ready to be used by the program: - wimlib files libwim-15.dll - BOOTICE v1.3.3.2 - some sample unattend.xml files for Unattended Install of Windows 10 - the slightly modified WimBootCompress.ini file as used in VHD_WIMBOOT - some extra DiskPart scripts as given in VHD_WIMBOOT to make UEFI/MBR based portable SSD

Perfect - WinNTSetup4 is a very Powerful Program

What do you use in WinNTSetup4 that allows to capture wim file from running Windows ?

Sure, I know, and I said that I might change that behaviour of the program. Then I will change VHD_WIMBOOT so that the wim files captured with WinNTSetup4 can be used. So it is not a good idea to use wimlib's --snapshot ...... Thanks for the Warning But, what is then the best way to make and use VSS snapshot .... May be then best is to rely on WinNTSetup4 for Capture of wim file from running System

The Captured wim file without the wimboot compatible mark is not (yet) accepted by my program VHD_WIMBOOT. But I might change that behaviour. The advantage of your Program is that VSS Snapshot is used so that Capture of a running Windows system is possible. I don't know (yet) how to add VSS to my AutoIt VHD_WIMBOOT Program. EDIT: Actually I see it is not that difficult to use VSS, since wimlib has build-in parameter --snapshot for VSS support Anyway I would like also to use in VHD_WIMBOOT the wim file Captured with your WinNTSetup program. wimboot capture can be combinesd with XPRESS and LZX https://wimlib.net/man1/wimcapture.html In wimlib-imagex.exe capture the --wimboot parameter automatically involves XPRESS 4K compression and for LZX I have used as parameters --wimboot --compress=LZX --chunk-size=32K So wimboot option is not a weak compression ....

Thanks for Adding WIM Capture and Driver Export Option, which are both very useful to me. In WIM Capture the wim file is not marked to be wimboot compatible, allthough the file can be applied for wimboot mode. Can you add a checkbox to select Capture in wimboot mode, so that the wim file is marked as wimboot compatible ? In the Boot code dialogue can you Add option to choose for BootMenuPolicy Legacy Or Standard ? BootMenuPolicy Legacy is often preferred since it allows in Multiboot to boot straight with the selected option, without the reboot that otherwise occurs. In the Boot code dialogue in case of EFI Boot Drive, the preferred setting should be UEFI instead of ALL, since BIOS cannot be used in this case. It would be nice if these settings can be saved in the WinNTSetup.ini file by using Save Ini Option. In Create VHD the preset filename is still Windows7.vhd, which nowadays should be Windows10.vhd The Menu Item for the new options is now named Offline Windows, whereas these new options can be used also with Online Windows. May be a better name would be Windows System The Driver Export function is also quite useful to collect the drivers that can be used with the Add Drivers option for a much faster clean install of Windows 10. I have used WinNTSetup4 also in Win10XPE environment. The Hotfix Uninstall Option is then available. There were no Hotfixes available for selection, allthough Windows 10 1903 Installation was Updated with 6 Updates. Is the Hotfix Unistall Option not suitable for these Updates ? The preferred WIMAPI wimlib Setting is Not saved in the WinNTSetup.ini file by using Save Ini Option. It would be nice if also this setting can be saved in the ini file. Anyway the new options are a good improvement of the already very good WinNTSetup Program

For support of 32-bits version System_Info_x86.au3 Disable Windows Defender - Realtime-Security Please Download and Install AutoIt https://www.autoitscript.com/site/autoit/downloads/ You can Run the au3 Script Or Compile Script to .exe (x86) to get executable Program System_Info_x86.exe Defender will remove System_Info_x86.exe as Trojan horse, which is however a false positive action

Thanks for using System_Info and for your approval

Install Windows 10 Unattended using WinNTSetup Using an unattend.xml file saves time and you don't need to answer all kind of questions during Install of Windows 10. In WinNTSetup you can select an unattend.xml file that you can edit using right-click on the checkbox. The unattend.xml files provided in the Attachment are modified versions as originally given by alacran - Replace My-PC with your ComputerName - Replace TimeZone value with your TimeZone e.g. W. Europe Standard Time - Replace InputLocale 0409:00020409 of VS International Keyboard with your Language and Keyboard code e.g. 0413:00020409 - Replace 4x en-US with your Language code e.g. nl-NL Keyboard and TimeZone - TimeZone - see also Wikipedia ========================================================================= A. Unattended with Local Account - use unattend_local_account.xml - Replace Vx64W in Username and Name with your UserName for Local Account - Password = admin This method is completely unattended. After Install of Windows 10 you can switch to MS Account. After Install you can switch Settings > Privacy > Diagnostic Feedback to Basic for reduced Telemetry After auto Install of all drivers then use Settings > Update > Windows Update to Search and Install Updates This method is working best and used for Install in VHD to be used for booting from USB Portable SSD on various equipment ========================================================================= B. Unattended with Microsoft Account - use unattend_ms_account.xml During Install give MS Account with e-mailadres and password You need to answer 4 questions: PIN code for Logon, Synchronisation, Phone, OneDrive After Install you can switch Settings > Privacy > Diagnostic Feedback to Basic for reduced Telemetry After auto Install of all drivers then use Settings > Update > Windows Update to Search and Install Updates This method is Not completely unattended and is Not preferred by me ========================================================================= How does it work ? In WinNTSetup you select an unattend.xml file e.g. unattend_local_account.xml or unattend_ms_account.xml WinNTSetup will copy that file as unattend.xml in folder Windows\Panther on the installation drive. During Install of Windows 10 then file Windows\Panther\unattend.xml is used to give answers .... More Info: Windows Unattended Setup Reference - Download PDF Telemetry is minimized by using the CEIPEnabled = 0 and ProtectYourPC = 3 settiings. Telemetry is maximized by using the CEIPEnabled = 1 and ProtectYourPC = 1 settiings. Download: Unattended_Eng.zip

Install Windows 10 from USB after booting with WIM or VHDX and UEFI_MULTI are both designed to give Booting and Install from USB with BIOS + UEFI support using UEFI/MBR-based portable SSD having FAT32 + NTFS partition. Win10_Inst_Eng.pdf

HP System Diagnostics and Save HWIDs have been Added to System_Info 4.0 program. More Info: System_Info

System_Info Updated to Version 4.0 - Added 4 new buttons for HP System Diagnostics + Save HWIDs + Windows Settings + Control Panel More Info: Devcon Commands

Download HP System Diagnostics - HP_Sys_Diag_col1832.exe

Download - SaveHwids.exe

VHD_WIMBOOT - Apply and Capture of WIM Files for OS in VHD Reserved Space for future use Download and Manual: VHD_WIMBOOT

VHD_WIMBOOT - Apply and Capture of WIM Files for OS in VHD Manual: VHD_WIMBOOT.pdf Step 1 is use WinNTSetup to do Fresh Install of Win10x64 in VHD located on your Internal System Drive C: according to page 2 of the pdf Manual Step 2 is use VHD_WIMBOOT to CAPTURE WimBoot modeNew WIM file from that VHD so that the capture is WimBoot compatible and contains only 1 Index Step 3 is use VHD_WIMBOOT to APPLY WimBoot mode that Captured WIM File to New VHD on NTFS System Drive of USB Portable SSD Step 4 is Boot Portable SSD with that New VHD from Boot Manager Menu as FILEDISK - do Windows Update and Add Programs + Drivers e.g. SVBus driver Step 5 is use VHD_WIMBOOT for CAPTURE and APPLY to Regain Free Space Or APPLY to 3.9 GB Expand VHD for booting with Grub4dos from RAMDISK FILEDISK / RAMDISK is a Preset to get desired values for VHD Type (Fixed / Expandable) and VHD Size (25 / 3.9 GB) - FILEDISK - Use Fixed VHD 25 GB booting with Boot Manager Menu and with Free space to add drivers for new hardware, to allow Windows Update and to add Programs - RAMDISK - Use Expandable VHD 3.9 GB to allow Fast loading into RAM from Grub4dos Menu and using SVBus Driver for booting from RAMDISK The Buttons WIM Info and VHD Info will give useful info about your WIM and VHD file The Button Upd WimBOOT can be used after copy of VHD + WIM to other drive to make the set bootable again The Button Make Boot will make the boot entries on Target Boot Drive for VHD located on NTFS System Drive - VHD boot entry in Boot Manager Menu for booting as FILEDISK - in BIOS mode and in UEFI mode - VHD boot entry in Grub4dos Menu for booting VHD from RAMDISK using SVBus Driver - in BIOS mode only - For booting from USB with Portable SSD - After BIOS beep press F8 Or F11 to arrive at BIOS Boot Menu and select your boot device WimBoot LZX Compression can be used in CAPTURE to make WIM files of smaller size. Roughly with LZX the time to CAPTURE is doubled and the WIM Size is 30% smaller so that it saves for a 9 GB WIM file about 3 GB. More Info is in UEFI_MULTI topic and is given by alacran in WIMBOOT Topic and Compression and RAMBOOT Topic ==

VHD_WIMBOOT - Apply and Capture of WIM Files for OS in VHD Download: VHD_WIMBOOT-53.zip at GitHub APPLY of WIM File in wimboot mode to VHD gives Operating System with only variable and boot essential files total about 1 GB in VHD. The VHD contains also pointers to the non variable files in the WIM archive, so that it seems that the complete OS is present in the VHD. The VHD content can be generated in 2 minutes from the WIM archive of about 9 GB, so that a backup of the system is always available. The VHD + WIM set can be copied to any drive so that we have a portable Operating System. The WIM file cannot be changed by viruses or other malware so that the system is reliable and if needed it is easy to generate new VHD. The VHD can boot as 25 GB FILEDISK from Portable SSD to allow changes, but also booting always Fresh from 3.9 GB RAMDISK is possible. VHD WIMBOOT has support for Office and Printer and any program can be installed, which is all not possible in case of WinPE In case of VHD WIMBOOT on each machine it takes extra boottime and space to adjust the drivers for that machine The VHD WIMBOOT solution is Portable, but not as flexible as Win10XPE, where boottime is not dependant on machine hardware Credits and Thanks to: Microsoft for making WIMBOOT - https://msdn.microsoft.com/en-us/library/dn631793.aspx and https://docs.microsoft.com/en-us/windows/win32/w8cookbook/windows-image-file-boot--wimboot- synchronicity aka Eric Biggers for making wimlib - https://wimlib.net/ schtrom for making SVBus Virtual SCSI Host Adapter for GRUB4DOS - http://reboot.pro/topic/21787-svbus-virtual-scsi-host-adapter-for-grub4dos/ alacran for support and info - http://reboot.pro/topic/21957-making-the-smallest-win10-install-wimboot-mode-on-512-mb-vhd/ and http://reboot.pro/topic/21972-reducing-wimboot-source-wim-file-using-lzx-compression-and-vhd-using-gzip-or-lz4-compression-to-save-room-and-also-load-faster-on-ram/ JFX for making WinNTSetup to Install Windows 2k/XP/2003/Vista/7/8/10 x86/x64 - https://msfn.org/board/topic/149612-winntsetup-v394/ Uwe Sieber for making ListUsbDrives - http://www.uwe-sieber.de/english.html Pauly for making BOOTICE - available via http://reboot.pro/files/file/592-bootice-v1332/ and https://sites.google.com/site/gbrtools/home/software/bootice-portable/bootice-downloads chenall, yaya, tinybit and Bean for making Grub4dos - http://grub4dos.chenall.net/categories/downloads/ Thanks to karyonix, alacran, Wonko the Sane, tinybit, yaya, chenall, cdob, JFX, steve6375, ReTokener, synchronicity, schtrom and Microsoft Development is described here - http://reboot.pro/topic/18182-uefi-multi-make-multi-boot-usb-drive/page-5 The program is released "as is" and is free for redistribution, use or changes as long as original author, credits part and link to the reboot.pro support forum are clearly mentioned VHD_WIMBOOT - http://reboot.pro/topic/21977-vhd-wimboot-apply-and-capture-of-wim-files-for-os-in-vhd/ Author does not take any responsibility for use or misuse of the program.

Thanks for the Info. Latest version will use RegRead Or your AutoIt code. System_Info will find the value of Hardware UUID as tested in Windows 7/8/10 and Windows 10XPE

System_Info Updated to Version 3.2 - Added code to determine Hardware UUID

System_Info is working OK in Windows 7/8/10 and in Win PE. It was just about the extra option to show UUID, where the very useful RegRead solution does not work in Win 7