We have published article on. That guide is useful if you want to make yourself free from need of dual boot. Now here is another scenario what if you don’t have DVD-ROM and you are running Windows XP, you might have guessed in this case we can’t install windows 7.
Since so its obvious that you will need to burn windows 7 iso on DVD and another issue is you can’t start windows 7 installation by mounting ISO file on windows XP as Windows XP upgrade to windows 7 is not allowed. In such situation installing windows 7 from USB pen drive is feasible solution. Here is small guide on how to install windows 7 from USB flash drive or USB pen Drive for Windows XP users. How to Install Windows 7 from USB Flash Drive Requirement: USB Pen Drive (Min 4 GB) (32 bit or ) MBRwiz and Extract it on your hard drive (Diskpart utility for Windows XP doesn’t detect USB drive as Disk hence we need to use this free utility to make bootable USB drive). Connect your USB Flash Drive to your computer Format USB drive 2. To Format USB Flash Drive Go to My Computer - Right click on USB drive and select Format from context menu. Now go to Start Menu-run-cmd (Open Command Prompt) and Type following command convert i: /fs:ntfs (Where “I” is your USB drive latter) 4.
Mount Windows 7 iso as drive (You can use ). Type Start-run-cmd Now dir to directory where you have extracted MBRWiz and run following commands mbrwiz /list (note down disk number of your USB Pen drive) mbrwiz /disk=X /active=X (X is Disk Number of your USB Drive) exit 6. Now open another command window and type following command J: (Drive letter of Windows 7 iso mounted with demon tool) CD boot bootsect /nt60 Y: (Y is drive latter of your USB drive ) 7.
Now copy all files from drive where you have mount Windows 7 iso 8. Now reboot your computer and press F9 to get your BIOS screen and s elect USB drive as your boot drive. If every thing goes fine, Your Windows 7 Installation should start from your USB drive.
So I figured out how to install Win 7. I installed onto my partitioned D drive and it worked like a charm. No.iso mounting needed. I’ve spent about 2 hours checking out and installing codecs and drivers.upon trying one of the games, windows 7 offeres to test your machine. And afterwards seemed to mock my graphics card. So to shut it up, I installed the latest nvidia driver from my external hard drive,cause I don’t use internet at home, get plenty of internet use at work.(which the driver works on xp) and now I some how broke windows 7 beta.
It continues to go to a blue screen and reboots. I had to reformat my D drive and now here I sit, waiting on a fresh install of windows 7.
Windows 7 Iso Usb Download
@Wayne – I gave it one more try. I figured out that it may be required to run the 64 bit version of bootsect so I planned to following: 1. Download VMWare Server (it’s free) 2. Mount the 64 bit ISO in a virtual machine 3.
Install Windows 7 x64 within a VM 4. Add a virtual USB controller to the virtual machine 5. Prepare the USB stick as described in this article 6. Install Win7 from the USB stick for real:) Using VMWare Server 1.08, step 4 doesn’t work. I can choose from 3 USB devices but neither can be ‘mounted’. Ejecting or unmounting in the host OS (safely remove device in windows) Doesn’t help. VMWare’s log keeps saying: USBG: Removing stale connect request.
For those that diskpart won’t recognize your usb, it’s about “flipping the removable bit”. LEXAR brand drives have an executable app that works on their own drives, and a few others. For all other usb’s it can be done in notepad and put in registry. Then usb’s show up with “local drives” instead of showing up with cd drives @ the bottom. GUARANTEED.sometimes you can go to properties of usb drive ie “policies” and click on optimize for performance, not quick removal and that works, sometimes.
You can google “flipping the removable bit” and find the info since i don’t have it in front of my face at this time.btw-i boot WINse7en off a 2G/B lexar 360 jump drive (my iso is only 1.43G/B’s, thanks to vlite WIN7 release 7127 Written by Michael. I have recently tried to use this method and i have done everything correct so far. I set my flash drive to active and then rechecked to make sure it was active with the mbrwiz/list command and it is active. I then proceed to the next step J: (Drive letter of Windows 7 iso mounted with demon tool) CD boot bootsect /nt60 Y: (Y is drive latter of your USB drive ) and when i do this the drive is no longer active!!!! MAKING ME MAD I then copied all the files over to the flash drive and tried booting and no luck. I then reactivated the drive and tried again with no luck. For some reason my flash drive will not stay active HELP PLEASE.
First of all, thanks for this. Secondly, i have a problem.
I’m using windows 7 rc1 32bit at the moment (and installed it by using this article). I downloaded windows 7 64bit (higher version of rc1). I’ve done what you wrote step by step but when i got to the “bootsect /nt60 e:” part, i’m having an error like this: the version of f: boot bootsect nt60 e: is not compatible with the version of windows you’re running. Etc etc well i can understand what i read but my dvd rom device is broken and i want to try 64 bit out. Is there no way at all for me to boot my 64bit w7 on a 32bit w7 system? I want to write a summary to all helpful comments above, emphasizing on the OP serious mistakes.
Without these comments, it would have been impossible for me to install Windows 7 on a USB drive. These two mistakes are as follows: NOT: mbrwiz /disk=X /active=X (X is disk number of your USB drive) but instead: mbrwiz /disk=X /active=1 (active argument MUST be 1, it is NOT the disk number) NOT: bootsect /nt60 Y: (Y is the drive letter of your USB drive) but instead: bootsect /nt60 Y: /mbr (where Y is the USB drive letter). Kek and evry1 elese having issues, not to insult the poster of this guide but a MUCH simpler way to install Windows 7 via USB is using the freeware program WinSetFromUSB. I have used it multiple times, for Windows Vista Installations and Windows XP installations via flash drive and I can assure u that its GREAT! Here’s a download link: Now here’s a STEP-TO-STEP guide on setting up ur installation USB.
What you’ll need: Windows 7 ISO, flash drive bigger than 2 GB, WinSEtupFromUSB, PowerISO or any other ISO program that can mount ISOs. Download & install the program from the link provided, and plug ur USB flash drive into ur comp (make sure its big enough to fit the Windows 7 installation-at least 2 GB.) Find ur windows 7 ISO on ur hard drive and mount it as a virtual drive (Use power ISO or any other ISO program). Open up the program WinSetUpFromUSB. Note that it was designed for Windows XP USB installations but works fine for Windows Vista AND windows 7 as well. Now, make sure that under “USB Disk Selection” the flash drive u intend to use is recognized and selected. MAKE SURE U BACKUP UR DATA, BECAUSE THE PROGRAM WILL FORMAT IT.
Click on the button “RMPrepUSB”. A window should pop up. In the RMPREPUSB window under FileSystem & Overrides”, select NTFS (this makes setup go MUCH faster). Also under “BOOT Options” “WinPE/Vista v2 Bootable (BOOTMGR)”. Now click PREPARE DRIVE (light blue button).
A command promptish window should appear, wait for it to finish. After it is done click EXIT in the RMPREPUSB window. In the program Windows look under “You may also add:” and check the second bullet “Vista/7 setup/PE/Recovery ISO”. Click the the “” button next to the selection to browse for ur mounted ISO.
Select the virtual drive its under and click OK. Now ur ready to make the installation USB! Click GO in the program Window. A little into the process u might get an error saying: “Could not install grub4dosector”. Just click OK and it’ll continue just fine, or if u don’t it’ll bypass the message and continue with the process anyway. Wait for the program to copy all the files on ur flash drive (should take 5-10 minutes).
When it’s done, click EXIT. Now your flash drive is ready. Safely remove, re-boot, then boot from USB and install Windows 7 as u usually would!
Im a Technology Support Specialist for a large software company. We’ve used this exact technique before obviously with the change of: mbrwiz /disk=X /active=X (X is Disk Number of your USB Drive) should be: mbrwiz /disk=X /active=1 (X is Disk Number of your USB Drive) as pointed out earlier. Most of the people complaining baotu it didnt work in this thread will find that thats because this is an XP ONLY process and that if you use Vista, it’s totally different!! Good job bringing this knowledge to the masses.
Thanks everyone. Managed to install Windows 7 64 bit edition first time using the USB method. The DVD upgrade disk didn’t work well with my DVD drive when I tried to boot from it and the installation kept crashing but using your outlined procedure I was able to create a 4Gb partition on my USB drive (80Gb), turn it into a Windows 7 64 bit install disk and get my machine to boot from that. One key point is when performing “bootsect /nt60 X: /mbr” from the 32 bit command prompt, use the 32 bit disk. When copying the files, if you want the 64 bit edition, change the disk over to the 64 bit version and copy that to the USB drive. I was tearing my hair out till I read this article and all the postings.
Windows 7 Install Usb Stick
Hi, Replying to late to this, but for someone’s help I think it would be okay. I could NOT use the following command: mbrwiz /disk=X /active=1 (X is Disk Number of your USB Drive) INSTEAD mbrwiz /disk=X /active (X is Disk Number of your USB Drive) (Note =1 is removed for /active) Maybe it is because of mbrwiz version but anyhow, I was able to run this command successfully this way.
Now I’m getting Cannot find operating system error, trying to work it around bt using the bootsect /mbr method. Will post again for any progress made.
This is a discussion of making a bootable Windows 7 Installation USB-stick Media. It might apply to making other USB connected 'Disks' like Smartcards bootable too. I recently had to do this (a Laptop with no build-in DVD drive and no USB DVD drive around). And it turned out to be surprisingly simple, using nothing but build in Windows tools from the Disk.
![Starter Starter](/uploads/1/2/3/9/123922552/356542323.jpg)
I only found and nothing in english (but I might just have searched after the wrong terms, google has been wierd regarding langauge lately), so I thought I write it up (along with some problems I ran into). Making a USB-Stick into a bootable Windows 7 (and propably Vista) Media is a 3 step process: 1. Create a Active, Primary, FAT32 Partition of 4+ GB on the stick 2. Use bootsect.exe from Windows Disk to create the MBR and Partition Boot Record for that Partition 3. Copy all files from the Disk to said Partition 4. Test if it boots Detail analysis: Step 1 is so simple I doubt it needs explanations. Create enough free space on the USB disk (at worst delete all previous Partitions).
Make a Priamry Partition of 4+ GiB. Mark it as Active. Format it in FAT32. The Guide used Diskpart, but this step can be done with any Partition Tool under any Windows, Linux, UNIX or DOS. While the choice of FAT32 seems a bit outdated, theye propably did not gave the relevant bootlaoder the ability to read NTFS.
Or maybe they just though FAT32 is enough for a media that is mostly read. I have not tried what happens if I format it in NTFS, but it might be possible. Step 2 was the only tricky part. You need the programm 'boot bootsect.exe' from the Installation Media. It also must be run on a non-UEFI booted OS (otherwise it cancels out). I had a Windows 8 on a new Laptop so I had a UEFI booted system.
Luckily I also had a VMWare Windows 7 lying around. I just assigned the Windows 7 ISO image to the Windows 7 VM, then connected the USB drive to the host. Advanced things: Need to check if the partition could be formated as NTFS. I prefer a Journalling Filesystem for my USB-sticks.
Windows 7 can be installed on a (U)EFI system, but I have not checked if I can use the boot from teh stick on such a Computer. Latest for Windows 8 Media UEFI compatibilty is nessesary. I converted the stick to NTFS using the convert.exe and it continued booting. So chances are high they only choose FAT32 in the example because no feature of NTFS was per nessesary in a 'almost only reading' scenario like installation media. The second part depends on the BIOS. I have a more advanced one where I can choose legacy boot options (like USB stick) in the boot option menu even when the default setting is UEFI, as long as I don't need Secure boot (wich I do not).
Another question arose: Windows 7 has the Kernel/BCD level ability to boot from.VHD Files. The only thing preventing version below corporate from using this feature is a license check that is run just before the login (so way after the booting has been completed). Starting with 3.0 Windows PE is based on the kernel of Windows 7. So the instlaltion system might have the ability to boot from.VHD too and might have no such check in place. If so, I could put both versions of the Windows 7 installer into.VHD, reducing the need to have physical primary partitions for those.
Windows bootprocess vs. Linux boot process under BIOS: The BIOS goes over all the boot media.
Menggunakan Wizard Subtitle Translation, Anda dapat melakukan terjemahan srt atau sub translaton dalam dua klik dan Anda dapat memutar subjudul untuk beberapa film yang tidak memiliki subjudul atau Anda dapat memainkan segala jenis subjudul yang Anda inginkan. Subtitle translation wizard patch. Ketika otomatis srt terjemahan atau terjemahan sub dilakukan, Anda dapat secara langsung dan secara manual mengedit subtitle diterjemahkan dengan menampilkan subjudul asli.
If it finds one with a MBR, that one is executed and the BIOS part of the boot process is officially over. Under Windows the MBR contains the 'generic boot loader'. A simple piece of code as old as BIOS (25 Years) that looks for the primary partition with 'Active' Flag on 'it's' disk. If it finds one, the Partition Boot Record of that parition is executed. The MBR has done it's part - NTLDR (NT too 2000), this one reads the boot.ini file and gives/executeds apropirate options - BOOTMGR (Vista, 7), this one reads the BCD files - Since Windows 7 BOOTMGR can also chainload the Partition Boot Record that is inside a.VHD File - Wicher was used in Windows 3.X/95/98/ME Higher versions can chainload lower versions, but must be designed for this and (re)installed in the proper 'order'. The sometimes odd behavior that Windows 7 tries to keep 100 MiB in a seperate primary partition is there to have proper places for later additions to the BOOTMGR settings. Specifically it allows multiple BOOTMGR OS to use/edit the same BOOTMGR instace without running into problems with 'whose partition is active?'
(since it is always the System Reserved one). It's not disimilar to having an extra /boot partition in Linux or how a GRUB's stage 2 works. Under a typical Grub Legacy the MBR contains the Stage 1. It directly reads the Stage 2 from the proper partition/file system with a hardcoded path, but due to size limit of the MBR cannot do more. In some cases it starts a stage 1.5 wich has more space to do work (63 sectors between MBR and first partition), but I never used this Setup - Stage 2 loads the Grub Configuration from the disk. From here it depends on what OS you want to boot.
For Linux or Unix the kernel is started directly. Any Windows OS up to 7 can be booted using the chainloader command. For the OS this is identical to having the partition choosen by the Generic Bootloader.
While it can be chainloaded by the Generic Bootloader from the active primary partition, GRUB and thus Linux has no requirement for any Primary Partitions. Stage 1 is designed to directly access the specific File System containng the Stage 2. In fact it does not even need to reside on the same disk (as the Generic Bootloader has to). If one does not need the Active Flag to control the Generic Bootloader (because a proper Stage 1 is installed in MBR) it is adviseable to mark wichever Windows Partition is chainloaded as active (up to Vista at least I had very odd behavior if the Windows boot partition was not marked active, down to randomly shredded Partition boot managers).
After running a Windows Setup usually the Stage 1 has to be restored, as Windwos Setup will always write it's Generic Bootloader in the MBR. In order to get 'rid' of a Grub all one has to do is overwrite the MBR with the Generic Bootloader and set the active flag properly. Let's talk about MVVM: Please mark post as helpfull and answers respectively.
This process has them galore: Apparently I do have to use FAT32. While it does boot and run from NTFS on BIOS computers without hitch, Setup won't be able to find the disk if I boot from NTFS on a EFI computer. And I have no idea how this could even be possible. Second problem is that for some reason MS thought nobody ever would need more then 1, non-hidden primary partition per USB stick (it will simply not detect others as Volumes to mount). On top of that while the active flag seems nessesary, just switching it and the hidden flag around does not seem to work to boot from variable partitions. So much for using GRUB to just switch between the partitions.
That leaves me two (maybe three) evenues to put multiple Windows onto one stick: Integrating the other Windows into the sticks instal.wim. Wich is an issue as it is 1.9 GiB large for Windwos 7 x32 without service pack and FAT32 has a file size limit of 4 GiB. Or try my luck with the 'boot from VHD approach' and hope Windows PE and it's bootmanager can deal with it. There might be a third way using sub-directories if BCD can chainload into the directory structure (one dir per DVD-content, properly setup BCD config). Let's talk about MVVM: Please mark post as helpfull and answers respectively. Anoter day, another insight.
There are 3 parts of interest for making the stick/a custom DVD: 1. Bootability 2. The version of the Setup/PE you use 3. The contents of the sources install.wim 1. The partition can be NTFS or FAT32.
![Ei.cfg Ei.cfg](https://www.lidux.de/images/anleitungen/xvirtual-box-machine-usb-boot-9.gif.pagespeed.ic.GKwC0-5BqY.jpg)
It must be marked active. You have to write a BCD bootsector using 'boot bootsect.exe' onto it.
Once that is done you can simply copy the contents of any DVD (Vista, 7, 8, 8.1) into the root of the stick. As long as it uses BCD at it's core the setup will start, without any extra work. If Win 9 uses BCD too, it will propably work too. So you can switch out wich version setup/file contents you are installing via Copy&Paste or Move.
And with the ways to modify the install.wim you don't even need seperate media for x32 and x64 version. That one is tricky. You want to choose one from a x32 DVD.
You don't need the x64 Setup to install a x64 version and the x32 setup is downward compatible. The Windows 7 PE/Setup will on certain computers, under certain BIOS/EFI settings and with a NTFS formated USB-Stick Parition not be able to work.
It will start but once you try to install setup.exe will claim it 'could not find a device' and won't let you proceed to the Version selection. It does have full access to the Disk, DVD and USB stick in my tests - it just won't continue and I have no idea how to fix that. The Windows 8.1 x64 Setup does not seem to have the issues with NTFS+certain BIOS/EFI settings.
But with it's own pitfalls: First, I have to try to get a x32 version of the disk. I am not sure they even exist. Second you need a specific ei.cfg. (instead of no one) to be able to select the version without having to enter the Key during install.
Windows 7 Starter Download
Also the Enterprise version of 8.1 again seems to need a seperate medium so I could not test it as well. The setup can instal any version that has a image for in the instal.wim file. Bitnumber of setup and the image in the wim File does not need to match up. Propably the version of the Installed Windows and the Setup do not need to match up either (you might use the Vista PE/Setup to install a 8.1), but I would prefer the most current setup (it's job is to write/edit the boot manager). The install.wim can be edited using the ImageX tool of the WAIK (Vista/7) and WADK for Win 8.1 The compression is outright impressive. I put every version (Starter too Ultimate) of Win7 SP1 (except for Entperprise, had none around) in both x32 and x64 into a single.WIM file and it is only 3,707,791,694 Bytes (3,28 GiB) small. Unfortuantely the Filesystem can dictate stuff about the.wim file.
FAT32 has a 4 GiB File limit. There seems to be a way to split.wim files using the.swm format and ImageX, but not sure the setup would continue to work then.Version selection without nessesary key entering seems to work with a sources ei.cfg looking like this: Channel Retail Let's talk about MVVM: Please mark post as helpfull and answers respectively.