Question in USB installation via ISO, creating using Rufus and I assume that since this is Window 7 we must choose MBR or is that incorrect? What are most using MBR or GPT? I am looking to dual boot Windows 7 and Windows 10 from an Samsung NVMe Also when the USB boots then I assume once chooses the UEFI prefixed one from boot list. Is that correct?
Windows 7, 8 &10 can handle both MBR & GPT. As you are looking on this thread, you should be having a very modern pc. These machines normally come or have internal disk(s) partitioned as GPT though you may convert the disk from GPT to MBR If your BIOS supports /allows! but ... if its a Pre-build / Pre-installed pc / laptop with a single internal disk & installation, you will lose the installation (OS) as you change from GPT to MBR Or you have to properly migrate the OS from GPT to MBR. When the USB is prepared and booted, You have to choose UEFI if you are heading with GPT partition scheme. MBR follows Leagcy BIOS or UEFI-CSM. As it is out of the scope of this thread, Make a new thread if you still have doubts. Thanks. ...
I used mbr because I used w7 on a b450 mobo and needed to use legacy/csm. I used Rufus on the usb stick again to make sure it is formatted ntfs and mbr, BIOS (or UEFI-CSM). I do this because it makes using daz loader super easy, just need to run it, and because I have a ssd just for the OS which is less than 2tb in size. For other drives you would want to use GPT to get past the 2tb limit of mbr. Be aware I didn't use this tool but rather a different one for getting a new PC up and running on w7. You can see what I did here to see if it helps you any. https://forums.mydigitallife.net/th...ates-up-to-01-2020.78722/page-14#post-1566177
Four weeks ago, I used this tool to generate a USB-bootable installation ISO for Win7 Pro sp1. It worked perfectly and I used zrufus to create the bootable image on a USB thumb drive. Today, four weeks later, I tried to generate another USB-bootable installation ISO from a clean Win7 iso file. Same tool, unchanged. Now, I see these ERRORS: ----------------[ UPDATING WuaCpuFix64.dll ]---------------- [2020-03-23 1314] Sending request to xxxx://codeload.github.com/p-lider/WuaCpuFix/zip/master [xxx=https] [2020-03-23 1314] ERROR! NO CONNECTION. --2020-03-23 14:03:14-- (try:12) xxxx://download.windowsupdate.com/msdownload/update/software/updt/2011/06/windows6.1-kb2547666-x64_28b78926b1b1a04a9867050ecb5e81857ebd5d66.msu [2020-03-23 14:03:14] Connecting to download.windowsupdate.com (download.windowsupdate.com)|23.59.182.19|:80... failed: Bad file descriptor. --2020-03-23 14:03:44-- (try:15) xxxx://download.windowsupdate.com/msdownload/update/software/updt/2011/06/windows6.1-kb2547666-x64_28b78926b1b1a04a9867050ecb5e81857ebd5d66.msu [2020-03-23 14:03:44] Connecting to download.windowsupdate.com (download.windowsupdate.com)|23.59.182.19|:80... failed: Bad file descriptor. That last message is repeated for about an hour, then the tool gives up. It cannot progress past that first failed kb2547666-x64 file Anyone know what may have happened, please ?
I just came back to say this..I saw the archive was updated and tried it again..May be my experience alone..This s**t never worked for me ..Considering the time i wasted for this to complete..Every time there is no ISO created..But ATAK..Thanks a lot for the drivers..I integrate them them to make my on ISO..U rock
OK, I guess I will look for another solution. I have tried 5 different Windows 7 x64 ISO and probably a dozen times and the current version of the tool seems to be broken. I wish I had not deleted the older version that I had that was still working correctly. The process ends prematurely with no error message and no ISO file is created.
Hello there, thanks for this tool which is great. I have an issue though. I'm using this tool to install Win7 on a laptop with a Celeron N3350 CPU, 4 Gb of RAM and a 2"5 ssd drive (i disabled the eMMC drive in bios). The laptop can only boot in UEFI mode (no CSM option in bios unfortunately). Secure boot is disabled. I use the generated iso on a Zalman VE350 drive which can emulate a cdrom drive from an iso file. My issue is that I can access to the Windows 7 install menus (Region selection, version of Win7, partitions edition menu,...) Then the installation is beginning but it stops on a random basis... The installation goes sometimes to 2%, 5%, 22% or even 85%. But it never goes to the end though. I have finally tested the installation with a usb key made with Rufus tool but the problem is the same.... I never had errors in the logs of the updater tool. I checked all the options when creating the iso (integrate updated installer, integrate updates & drivers, downloading missing updates, apply to all editions) Do you have an idea ? thanks
Hi Atak_Snajpera, first thanks for this utility. I have been reading up on it and trying various other ways to update my windows 7 iso(s) i have in the hopes to get an install for a z370 board and nvme drive. so far i'm not successful. This seems the most promising but I keep hitting road blocks. I've been at it for two days now. I am trying to create a usable win7 x64 iso on my current machine which is running win7 x64 sp1. Originally i tried to use the asus ezinstaller to put it on my usb, iso, etc.. to no avail, same with Gigabyte's version of ezinstall. Anyway, I was reading through this thread and it looks like I have to have powershell 4.0, in order to install adk 8.1 for windows 8, which will run under 7, in order to make your utility work. Is this correct? Well I don't have adk, so i downloaded it, but the ms site says, i need powershell 4.0, i have powershell 2.0. they don't offer 4.0 for download anymore... I can't find it anywhere. It looks like both your utility and the simplix one require it. Even if I did it on my own, it appears i would need adk to have the updated dism utilities, in order to slipstream the usb3.0 drivers and nvme drivers in. Could you help me out?
I guess I got confused when reading about the MDL tool for simplix requiring ADK, I had the windows 7 img updater running when I had posted earlier, but decided to let it continue even though I had thought it would fail. Glad I did, cause it worked fine with out error. My bad.. It makes a really nice ISO thanks so much, you saved me a lot of headache! I did have some issues installing, mainly with my bios, after the first or second reboot, somehow secure boot got turned on. My bios gave me some boot warning saying that the install changed a bunch stuff, and I had to go in and delete all the keys to get it to turn off.
This worked for me although I had a version I downloaded in December that I used. My ports worked with a PCIE USB card but none of the other ports work, it said that in the post before. However now I no longer see any mention of this.
I used your program, everythings looks to work but no ISO is created ?! :O Does it happened to someone ? I tryed during like 4-5 hours.
Install windows 7 fully updated on virtual machine , Use dism++ to clean reduce windows 7 iso size Sysprep And capture with dism++ Choose wim recovery max compression After that you have an iso with 7gb size maxi
Yes, i capture it later on...It's way big tho....other tools or manual after full update, never seen such huge WIM?! I have one updated to 2020-08 = 3.22 GB (3,466,658,623 bytes This one = 10.5 GB (11,313,093,722 bytes) (no drivers etc..) just the updates, used on: en_windows_7_ultimate_with_sp1_x64_dvd_u_677332 ps: Rebase also failed btw... on/offline on this image. Then again,all works just fine.
My AiO x64 en-US ISO without any added drivers, except the USB3.x generic driver, and containing install.wim: Code: Name: Win_7_AiO_x64_en-US_SiMPLiXED_2020-11-18.iso Size: 5549279232 bytes (5292 MiB) Does the script rebuild or optimize the wim files?