Hi

Using a friends laptop, I tried to create a bootable Windows 10 Pro, 64-bit USB drive.

Installation went ahead as usual, but after booting from the drive, and going through some of the normal setup stuff, Windows asked for a login password. There was already a user account. At no point did I set such a password. What causes this, and how can I get around it?

It should be noted that the laptop itself already had that that exact same version of Windows 10, installed internally. But there was no password set on the internal installation.

I also tried to boot a WinToUSB disk I had previously created on another computer, one with Windows 8 on it, and that one booted perfectly here.

Has anybody seen this problem before? Does anybody know how to get around it?

Hi

My only Windows system is a WinToUSB, and I'm trying to create another bootable USB from this system. I'm creating it from an ISO file.

When I try to install, I get this error message: Failed to run system API.(0x00130015011F4000)

Installing to the same USB, with the same ISO, and the same version of the program has worked fine in the past when using a computer in which Windows is running from the internal HDD.

Why is this happening? Is it not possible to create another bootable USB when you are already booting from a WinToUSB created disk?

I've also tried cloning the current system, but that didn't work either.

I've tried using WinToUSB on both a 32 GB USB 3 flash drive and a really old 160 GB  mechanical (spinning) drive.


I've tested both, and the flash drive has much faster read/write speeds than the spinning drive. It can do like 130/60 MBps, while the spinning drive is more like 27/27.

Yet, when I tried to install Windows 10 on the flash drive, and booted from it, it was painfully slow. It froze all the time, and was basically useless.

Running from the (8 year old) mechanical drive, it works just fine! It's probably not at optimal speed, but it's just fine for my needs.

I remember getting a warning while installing to the flash drive, saying that it might not work very well on that drive. But why is that? Isn't read/write speed the most important thing? What limitations are there on the USB 3 flash drive that made running Windows from it not work? I mean, it's read/write speeds are so fast!

Hi

The internal HDD of the computer I'm booting WinToUSB drive on does not appear in Windows Explorer. How can I make it appear?

I'm running Windows 10 Pro, 64-bit. I just made a fresh installation using WinToUSB.

I remember it working before. But I was using Windows 8, 32-bit back then. It was the same computer.

What can I do to make the computer's internal HDD appear in Windows Explorer?

Hi Guys,
I have a broken W10 install and want to create a NEW Clean install and slowly migrate everything across. I'm a very busy user and have lots of bits of software to re-install and setup once installed (custom layouts of screen environments etc etc)

I guess I need a dual boot system for a while?

Is this something you can help with?

I'm a new user and want to try out the product. I might purchase a license in the future, but I can't get my first try to even start as the free/trial version is giving me the following message:

"The free/trial version doesn't support Windows Enterprise/Server operating systems.(0x0000010708AB0000)"

I'm just trying to install Windows 7 Pro.....is that supposed to be restricted in the free/trial version?

Am I doing something wrong?

Screenshot attached of page where I'm selecting the version to install: hitting the next button gives a dialog with the message above.

Thanks for any insight or tips to get it to work.

Attached Files

Thumbnail(s)
   

when i try to install windows 10 PRO on kingston data traveler G4 usb3.0 128gb i with drive partition and virtual space 14gb i get en error disk on partition space is insufficient: (0x000000c2094B0000) when i increase the virtual space 20gb click next the windows is at 0% and all of the USB ports disconnect and cannot be found.

Attached Files

Thumbnail(s)
       

Failed to extract file from WIM file using Win10 x64 ENT VL ISO to Kingston DT Workstation 64GB USB.

Attached Files

  user.log.1.txt (Size: 7.41 KB / Downloads: 1)
  user.log.2.txt (Size: 155.85 KB / Downloads: 1)
  user.log.3.txt (Size: 97.63 KB / Downloads: 2)

This has happened to me twice now cloning Window 8.1 to Extreme usb 3.0 works 100%, however it seems when the space is getting low on the 64GB stick windows decides to use the paging file on the local internal drives & also changing the boot menu thinking it shouldboot from D drive & not  drive C.

Does the autounattend.xml file work with a New Installation to a HDD? If so where do I put the file?