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)
       

I tried to clone my Win8.1 system to a USB disk, but it fails with the error Operation failed.(0x0000000200F70000). WinToUSB is version 2.4 Beta, build sept 18, 2015. USB stick is Sandisk Extreme 32GB.

Any idea how to get this working?

Relevant part of user.log:

2015-09-26 16:24:05 T:000010A8 OS Name:Microsoft Windows 8.1 with Bing Version:6.3.9600 Build 9600 Bits:64
2015-09-26 16:24:05 T:000010A8 WinToUSB Version:2.3.2.2
...

Could I do things normally on a usb 2.0 port assuming I was on a fast/good computer? how slow would it run? I don't need a 3.0 flash drive do I? I only have 2.0 usb port...

I got a 16 gb flash for 5 dollars, doesn't it seem bad to set the memory requirement at 16gb? i mean 16gb should be enough for windows 7 and a few gb left over right? a 16gb stick only has 14.5 memory so it's certainly not enough

if i used the computer for an hour and a half each day on a windows 7 flash drive, how many years would the flash drive last? i know flash drives have a limited number of write cycles etc, some sites say it won't last long, but i think they should last several years because they have so many cycles

thanks

@admin:

Nice to see a new beta-version (2.4).

Can we support developing?

What features are new or have been changed?
What should we test and what kind of feedback information is required?

BR
Andre

I have an UEFI and use Windows 10. I used the "Clean" function of EasyUEFI in order to clean unused entries from my UEFI boot partition. However, this seem to damaged my UEFI somehow. I cannot longer login into my UEFI with F2. When I press F2 at boot, it says "Wait please ..." but I get directly moved to the boot loader instead into UEFI settings.

I tried reflashing my UEFI but this didn't changed anything. Running Windows Repair with BootRec.exe /FixBoot, /FixMbr and /RebuildBcd did not helped either. I cannot access UEFI anymore.

I am now scary to reinstall Windows to not brick my Laptop (Samsung Series 7 Chronos 700Z3A-S02DE, UEFI Version 15FD (newest)).

Any suggestions? Thank you!