Rufus works if you set it up properly, but the rufus driver doesn't support secureboot - because MS won't sign it. If you turn secureboot off for the installation, it should work fine.
Otherwise if you want to use fat32, you can split the wim. I would use wimlib-imagex for that. It is in the BIN folder.
wimlib-imagex split install.wim install.swm 4000
note the word split is lower case.
Last edited by SIW2; 24 Mar 2019 at 21:04.
This is an alternative method:
How I make an NTFS UEFI Bootable USB with No Rufus = Works with Secure Boot
Another option is to use Windows 7 Component Removal download | SourceForge.net to remove componenets from the image - before updating it.
Seems to work fine.
There is also another tool - but when I tested it the ie8 removal is too aggressive. The linked one above is probably better.
Didn't work for me.
"Bootsect not recognized as an interal or external command"
My new plan is to study hard in hopes of becoming proficient enough at using Windows 8 and/or Windows 10, that I eventually accumulate the expertise to install a copy of Windows 7 on my computer so that I can use that instead of Windows 8 or 10.
In what way didn't it work? If the fat32 partition has the correct files, it should boot up boot.wim. The instructions at the linked article are not very clear. Efi bcd store points at [boot]\sources\boot.wim. So you would need to create a sources folder on the fat32 and copy boot.wim into it.
Windows 7 is not digitally signed, so again secure boot needs to be turned off.
In a nutshell -
1. Copy all the folders and their contents ( EXCEPT the sources folder ) from the win7 installation media onto the 2gb fat32 partition. Then create a folder on the fat32 partition and name it sources. Copy only boot.wim from installation media sources folder to fat32 sources folder.
2. Copy ALL contents of win7 installation media ( including the sources folder) onto ntfs partition.
If you have created the partitions as per instructions at the linked article, that should work fine.( bootx64.efi file was already created when you ran 7updater.)
Last edited by SIW2; 23 Mar 2019 at 16:29.
I just checked, there is a typo in 7updaterv21.
You can fix it manually. After running 7updater, the installation media should contain the file efi\BOOT\bootx64.efi
The typo missed off the file extension, so you can just rename efi\BOOT\bootx64 TO efi\BOOT\bootx64.efi
Will fix that typo and reupload.
Bootsect is not included in your current windows system32 by default. You can just copy it in from the installation media boot folder - you can copy the mui as well if you like. Files in system32 are by default "in the path", which means you don't need to tell windows where they are. In which caseDidn't work for me.
"Bootsect not recognized as an interal or external command"
Bootsect /nt60 g: /force
should work
Alternatively, if you don't have a copy of bootsect "in the path" you can tell command prompt where bootsect.exe is, for example:
C:\extracted-iso\boot\bootsect.exe /nt60 g: /force
Last edited by SIW2; 23 Mar 2019 at 16:56.
SIW2,
- setEXTRACTpath.cmd can't be found on Bin folder (7UPDATERv21)
- Does 7UPDATERv21 has the ability to split Install.wim?
check for the getextractpath.ini file in the BIN folder- setEXTRACTpath.cmd can't be found on Bin folder (7UPDATERv21)
getextractpath.zip
It is best to select a drive to extract to - rather than a folder.
No, but it is easy to add an extra .cmd file to do it.Does 7UPDATERv21 has the ability to split Install.wim?
Thanks
Quote