Hi all,

I am trying to make a live windows iso file from 2018 13"MBP on a samsung X5 (1TB).

I understand to use a thunderbolt drive you need to purchase the professional license however when I run the formatting I recieved the following error message (API error (0x0571001501210000)) I couldnt find documentation for the installer that pointed to this error. I understand an external library is used for the boot driver is it possible the call to the API is in error. Any help would be appreciated.

I used disk utility to format the drive on a parralels desktop.

Thanks all.

Hey Guys

I'm trying to convert an exisiting Windows installation on a M.2 SSD NVMe to a Windows to Go version. The disk size is 256GB and 192GB of the disk is free. When I run WinToUSB I get in the dropdown for the destination disk my internal SSD (there is no other HDD attached to that laptop, so only the internal one can show up in the dropdown). 
Here a screenshot:
   
As far as I understand you can't convert a internal HDD or SSD. According to the instructions it must be in a external closure. 
I would love to know if, 
a) Is it possible to convert a running Windows System?
b) If it isn't possible, how am I meant to convert a Windows which is on a M.2 NVMe SSD (hardly any external disk enclosures for NVMe form factor...)? (The purpose of that conversion is to build out the SSD and then place it into another machine which also has a M.2 slot)

Your response is greatly appreciated

Thanks in advance

The pagefile.sys, refues to be created even after changing virtual memory settings to 0 and back and I'm stuck with 0MB, so basically nothing, windows is virtually unusable. No solutions have worked as I have tried for 24 hours, I reinstalled windows three times, with different iso's, editions and settings but I get the same error. I'm running it off of an external hard drive and no internal hard drive, if that information matters. Can someone help so I can actually use windows again, I've been stuck without a computer for three weeks.

Hi im trying to put windows 10 home x64 on my 32gb usb but I keep getting this error once it gets to around 90 something % .


The system cannot write to specified device (0x000000630BCA002F)

Attached Files

Thumbnail(s)
   

Actually, I have made a windows 7 bootable MBR-UEFI USB with the help of wintousb software but that bootable USB have not worked for my PC, so again with the help of wintousb software I tried to make Windows 7 bootable usb in MBR-BIOS but that operation was not completed as the pendrive automatically disconnects.

After that I've tried formatting, deleting volume and creating new volume from Create and format Hard disk partitions and also tried cleaning from CMD, but the same things happens like pendrive disconnects automatically and one message appears (screenshot attached). I am not worried about the data in it (cause it's the images of OS only), but I want to make this USB to work as usual. Please revert.

Attached Files

Thumbnail(s)
   

Hello everyone,

I recently created a Windows 7 bootable USB and was able to reach the boot screen, at which point the system would eventually show a strange red bar at the top of the screen, then crash. I unfortunately had the same experience when trying to boot to safe mode, and thus was unable to generate a log file. Has anyone else experienced this?

Hi

I have created a WintoUSB Windows 10 OS on a Sandisk Cruzer Blade USB stick, and have a separate USB stick (same make and model) which I use for moving files from PC to PC.    However, when I put the USB stick I use for moving files in the PC with the WintoUSB OS, it does not get recognised.  I presume this is because the PC can't distinguish between the WintoUSB USB stick, from the other USB stick, as they are the same make and model -  despite them being two different USB sticks used for different purposes (hope that makes sense).  Does anyone know any way to fix this?

Regards

I am running Windows 7 on a Thinkpad x230. I am trying to create a Win to Go USB from the internal drive. I have removed the drive, placed it in an external enclosure, plugged in a 128 GB Sandisk Extreme Go USB and followed the directions under the Tools-> Windows to go Conversion. The drop down menu shows and allows me to pick the Sandisk USB and the Convert Local Disk to Windows radial button is chosen. I click Okay and a pop up windows says "This may take several minutes..." flashes for about a second and then another window opens saying the Operation was completed successfully, but USB is still blank. I tried this on a Dell computer running Windows 10 with the same result. Please advise.

I bought the professional version of WintoUSB and created a USB that runs Windows 10 using a Windows 10 ISO. It works great. What i would like to know is some information on the options. I tried three different Sandisk USBs and all were successful; an Ultra 3.0 256GB (100MBps), an Extreme Go 3.1 SDCZ800 64GB (150MBps) and Extreme Go 3.1 SDCZ880 128GB (380MBps). The all loaded with no issues, however the Sandisk Ultra 3.0 ran much slower and was not really a viable choice. I also settled on using the Extreme Go 3.1 SDCZ880 128GB (380MBps)

I created these with the same default setting of VHD mode, which creates a virtual hard drive. My question what would be the difference if I used legacy or VHDX? My other question is how would I clone the USB I am using so I can save the changes I have made?

I'm getting this error right now while trying to install using the Professional v5.1 from an ISO onto a 250GB drive. The drive was partitioned into 249.90 GB and 100 MB partitions. I've tried all 3 installation modes.