I just installed Win10 PRO x64 on SanDisk Extreme 64 as a Windows to go, but it generated two disks out of it. C: 14GB, which only has 500MB left after all the updates, and another one D: with 58.5GB, that only has one 14GB strange file. As you can tell, I'm extreme noob at this.
This is not good.

Is there a guide on how to install it and use all the space on my drive? Thank you

I get the following message when starting WinToUSB 2.4:Failed to run System api 0x00000015002E0000

After the message the application seems to run fine but when creating a Windows 10 on an USB then during formatting the USB a BSOD occurs

WinToUSB runs on Windows Vista Ultimate 64x English (4GB memory, enough Diskspace on SATA disks)

The log:
2015-10-28 10:26:51 T:00000564 OS Name:Microsoft® Windows Vista™ Ultimate  Version:6.0.6002 Service Pack 2 Build 6002 Bits:64
...
2015-10-28 10:32:35 T:00000564 .\main.cpp main 178 End...

I receive the following error when I attempt to install windows 7 to my usb.

Unable to run System API.(0x0005001501AF0000)

Here is the User Log
user.log

I found nothing about compatibility for Win8.1 32bit system that my Dell Venue 8 Pro has. Unfortunately it isnt bootable now and I'm asking if the bootstick would be compatible to the 32 bit WIN8.1 if I installed EasyUEFI on a similar Win8.1 System 32bit? Every time I build it with a 64bit system it gives me only the x64 efi file in EFI/BOOT and no x32 efi bootfile. Seems that no one has thought about win8.1 systems with 32bit as other Boot tools have the same problem when making a USB-stick. DOES EasyUEFI support Win 8.1 32bit UEFI Boot via USB stick?
PS: for other users with the same problem: MistyPE is the only tool I know that is running on my 32bit Dell on usb-boot-stick with WINPE cause it has a x86 option and a flat boot option. The Bios is only capable of switching secure boot, no legacy option.

Good morning,

for a few days now, I try to install either Windows7 or Windows10 in legacy mode to a 64G Toshiba usb stick via USB3, all done from within Virtualbox5 running a Win10 VM.

The first time I did so - using an ISO of Win7 x86 - everything worked flawless and I was able to boot the usb stick on my real machines.

Trying to create a working device after that however always failed by various error messages that either tell to turn off the AV software (which doesn't exist, Windows Defender is completely turned off during the process) OR that certain files from the WIM files couldn't be copied over OR also having only VHD creation as an option to choose from.

Eventually, the typical Windows FS hierarchy with it's directories and files exist but necessary files for a proper boot do not.
To choose partitions does not work either as only one is shown unless I try to create a USB from the apparent existing "HDD" install that exists in Virtualbox but again, this will also fail due to missing boot files.

So my question is, what can I do to make things working again?
To use a computer with native WinNT install is not an option as I know noone myself around me who has a computer that runs Windows.


Kind regards,
MOS6510

I have successfully installed the Windows 7 SP1 64 system on my pendrive (Sandisk ultrafit 3.0 16gb, also a Samsung Evo 16gb microsd gives the same error). Everything is working except that i cannot install WIndows .net. I have tried the offline installer for the 4.0, 4.5 and 4.6, All of them fail on the end, saying "User canceled installation". It is the same situation on W7 ultimate and home editions.
Anyone has any idea how i can install it?



Also, totally unrelated: I think it would be useful if we could use WinToUSB to install windows on an internal hard drive/partition.

Press Ctrl+Alt+Delete to restart

This is the loop I get when i try to boot up my external SSD. What can I do to fix this. The installation said installed successfully.

Hello,

For reason I can't explain in brief, I have to update BIOS of a notebook. Is it safe to do this on a WinToUSB drive?

Thank you

Installed W10 32-bit on USB3 stick. All goes well. However, in the system property, It says "Installed Memory 16GB(usable 1.6G)". Why there is 1.6GB limit? It should be about 3.x GB for 32-bit system.

Use version easy UEFI 2.3. Windows 10 RTM x64
There are 2 "Windows Boot Manager" with exact same information. The only different is the GPT partition GUID
The first entry refers to Disk 0 partition 2 with a red rectangle
The second one also refers to Disk 0 partition 2 and is without the red rectangle
If I delete the second one and reboot. It will again re-created.

Why are there 2 entries ? Please advise.

Attached Files

Thumbnail(s)