Clean WIM: Code: Obtaining list of 3rd party drivers from the driver store... Driver packages listing: Published Name : oem0.inf Original File Name : prnms001.inf Inbox : No Class Name : Printer Provider Name : Microsoft Date : 6/21/2006 Version : 6.1.7600.16385 Published Name : oem1.inf Original File Name : prnms001.inf Inbox : No Class Name : Printer Provider Name : Microsoft Date : 6/21/2006 Version : 6.1.7601.17514 With nvme updates only: Updates: Code: Command line that ran is dism.exe /image:"c:\mount" /Add-Package /PackagePath:"J:\Simplix_Batches_Win7\Win7\(W)Lan+WAT+NVMe_x86\Updates_WinPe" Deployment Image Servicing and Management tool Version: 10.0.17763.1 Image Version: 6.1.7601.17514 Processing 1 of 2 - Adding package Package_for_KB2990941~31bf3856ad364e35~x86~~6.1.3.0 [==========================100.0%==========================] Processing 2 of 2 - Adding package Package_for_KB3087873~31bf3856ad364e35~x86~~6.1.2.0 [==========================100.0%==========================] The operation completed successfully. 3rd Party Drivers: Code: Obtaining list of 3rd party drivers from the driver store... Driver packages listing: Published Name : oem0.inf Original File Name : prnms001.inf Inbox : No Class Name : Printer Provider Name : Microsoft Date : 6/21/2006 Version : 6.1.7600.16385 Published Name : oem1.inf Original File Name : prnms001.inf Inbox : No Class Name : Printer Provider Name : Microsoft Date : 6/21/2006 Version : 6.1.7601.17514 So the mentioned nvme drivers must have been integrated by SiMPLiX
What's weird to me is that I don't see any Micron NVMe drivers in the /get-drivers list(from earlier). Also, I saw some OpenFabrics Alliance (OFA) generic NVMe drivers on win-raid.
Great tool! I created my x64 AiO just under 1.5 hrs and it's 2.83GB in size with .net4.8, visual cpp redists and directX integrated along with the drivers. Thanks!
Later today i will release the updated tool, i have to test some things first, after the Easter dinner
Updated the bare tool: https://forums.mydigitallife.net/th...with-install-esd-creation.79421/#post-1516361 Changelog: Code: - Added code for host OS architecture detection for wimlib-imagex use on x86 or x64 OS. - Added new cmd's: W7_x64_HomeBasic_Only.cmd W7_x64_HomePremium_Only.cmd W7_x64_Professional_Only.cmd W7_x64_Ultimate_Only.cmd W7_x64_Enterprise_Only.cmd W7_x86_Starter_Only.cmd W7_x86_HomeBasic_Only.cmd W7_x86_HomePremium_Only.cmd W7_x86_Professional_Only.cmd W7_x86_Ultimate_Only.cmd W7_x86_Enterprise_Only.cmd W7AIO_x86_WIth_Enterprise.cmd W7AIO_x64_WIth_Enterprise.cmd The cmd's with Enterprise need the Win 7 Enterprise iso inside "SOURCE_ISOs\7_x64_Enterprise\" or "SOURCE_ISOs\7_x86_Enterprise\".
Great tool! I created my x64 AiO just under 2.5 hrs and it's 2.83GB in size. But i don't know ISO to usb. Can you help me? Thank you.
I'm talking about PCs with no UEFI support. I have an old Core2Quad PC with Intel G41 chipset motherboard lying around and I did try that method but it didn't work for me until I manually did it using NTFS and made it bootable by using bootsect. Code: BOOTSECT.EXE /NT60 X: That always worked for the manual process on my older PC. Of course the tools work too if I properly specify what type of BIOS I have but your suggested method only works for my newer Ryzen PC and a laptop (also UEFI/CSM based) both in Legacy and UEFI mode. Just sharing my experience.
I just format the usb FAT32 and extract the iso to it, on my old 775 intel platforms all works fine (Core2DUO and QUAD core and all sorts of systems i assembled for my friends and family.