Hello i wanna ask about installing windows from created USB with WinToHDD
I went trought all steps and at screen where Disk partitions its so confusing here what i did first time but i think i messed something i posted a photo what i did first time when i installed windows 10 from it i think i tick something wrong on that photo i did all that but now second time i miss some partition FAT or so dont remember?

Can someone help me with it, what did i tick wrong if so how to fix that and what is correct system and boot partition to tick in my case ?

Thanx.  

Attached Files

Thumbnail(s)
   

I’m using a Macbook Pro 2017 and worked with WTG drivers for months. Recently i bought NVIDIA RTX graphic cards but my older version 1703 doesn’t work with RTX. I have to upgrade my Windows into 1809 so I chose WinToUSB to do that. I erased and formatted my drive and installed WTG correctly, but after I successfully booted the first time into WTG and installed the Boot Camp drivers and restarted, the WTG cannot be booted anymore. I erased again and clean installed again and things are the same. I want to know what’s the problem here, thank you!

The drive I am using is a Sandisk SSD with a SATA USB C case. I also tried to connect to the SATA port of my eGPU case and use the Thunderbolt 3 as I used to do, but didn’t work as well.

The latest one is unable to make Multi-Installation USB on Windows-10 64bit system.

It always fails after reaching till 95% with a very common error code and status (which unfortunately elaborates NOTHING): Failed to run system API.

Worth to be mentioned, the Firewall/Antivirus/Administration Privilege all have been enabled/disabled/tested gradually, but the result remained the same as it is. Same case with different Device/Computers but with same Windows-10.

But with Windows-8/8.1 the situation is totally different. Everything works fine with no issue at all. Same system I've re-installed Windows-8.1 Enterprise replacing of Windows-10 Enterprise, and it worked like charm!!!

Please fix it guys, no log to be attached for this, as it seems to be a very common issues from very beginning. And please make some changes in your error logs, which just prompts but explains nothing!

Another issue was found while making Multi-Installation USB HDD. It never shows that Format Checkbox, due to that the NTFS Drive just gets the data copied but doesn't get linked with UEFI Partition. Same had been tested with both Windows-8.1 & Windows-10 as well.

Again, no Log file is required to upload to describe these kinda issues, as these seems to be very common bugs which could be fixed easily enough.

Cheers.

Hello,
I have wintousb installed as vhdx.
when native booting the system starts without problems, but always comes with the Windows performance optimization, since no paging file can be created. What have I done wrong. Please help.

The changes made so that 1809 works seem to be reversed when sfc /scannow is run. I was attempting to fix an issue where Legacy booting worked but EFI would hang on loading everytime, recreated the boot partition with bcdboot, didn't work, tried sfc /scannow and now the system blue screens every time I boot legacy or EFI.

Just something for others to take note of.

Hello. I hope I'm posting in the proper thread.

It would appear after 4 days of trying to determine the issue I'm experiencing that your product will not work with a PNY Turbo 256GB USB 3.0 Flash Drive.

I have an Asus ROG G75VW it only has USB 3.0 ports. I was attempting to install Windows 8.1 from a verified working ISO.
My PNY Turbo 256GB USB 3.0 Flash Drive keeps throwing a BSOD USB 3.0 BUG error code.

I used a micro SD card after my 4th day of process of elimination and it works fine!

So it's not user error. Can you please tell of a remedy for the issue other than to insert a USB 2.0 stick or port?

If not I'll look elsewhere for a product that can suit my needs.

Thanks for your time.

Hi all, brand new here. Got a problem that might be related to WinToUsb and hope to get some help.

Today I successfully installed a win10-1803.iso on an external/usb drive using WinToUsb (latest version).
I can boot the drive and Windows 10 starts, logo appears, then the spinning dots appear and the logo disappears, and then...... the dots just keep spinning for hours and set up does not continue.

What could be the cause?

(BTW: It's a 1TB drive, which I had to split into 2 smaller drives bc WinToUsb would not proceed in the installation set up.)

Can't clone to go USB HD, using Legacy option. Source is win10 x64 1809 with disabled appstore. Same Boot/System drive, BIOS only.

Last log lines:

2018-12-29 17:01:02 T:00000EE0 .\DiskIOWin32.cpp 61 nRet=0x00020066003C0000 \\.\PhysicalDrive31
2018-12-29 17:01:02 T:00000EE0 .\DiskTypeWin32.cpp 47 nRet=0x00020066003C0000 \\.\PhysicalDrive31
2018-12-29 17:01:02 T:00000EE0 .\SelTargetPage.cpp 346 DiskNumber:0 DiskType:3 CHS:38913*255*63 SectorSize:512 Sectors:625137345 Readonly:0 Removable:0 USB:0
2018-12-29 17:01:02 T:00000EE0 .\SelTargetPage.cpp 346 DiskNumber:1 DiskType:3 CHS:77825*255*63 SectorSize:512 Sectors:1250258625 Readonly:0 Removable:0 USB:1
2018-12-29 17:01:02 T:00000EE0 .\SelTargetPage.cpp 448 ====================Usable Disks:====================
2018-12-29 17:01:02 T:00000EE0 .\SelTargetPage.cpp 476 DiskNumber:1 DiskType:3 CHS:77825*255*63 SectorSize:512 Sectors:1250258625 Readonly:0 Removable:0 USB:1
2018-12-29 17:01:02 T:00000EE0 .\SelTargetPage.cpp 496 PartNumber:1 PartType:2 FsType:10 DriverLetter:M StartSector:2048 EndSector:122881184
2018-12-29 17:01:02 T:00000EE0 .\SelTargetPage.cpp 496 PartNumber:2 PartType:2 FsType:10 DriverLetter:N StartSector:122881185 EndSector:1250258624
2018-12-29 17:01:17 T:00000EE0 .\DosDeviceEx.cpp 106 nRet=0x0002000600690000
2018-12-29 17:01:19 T:00000EE0 .\LicenseKeyRegEx.cpp 154 dwErrNo=0x2
2018-12-29 17:01:19 T:00000EE0 .\LicenseKeyRegEx.cpp 156 nRet=0x00000013009B0000
2018-12-29 17:01:19 T:00000EE0 .\LicenseMgr.cpp 167 nRet=0x00000013009B0000
2018-12-29 17:01:23 T:00000EE0 .\FilePublic.cpp 1356 C:\Recovery
2018-12-29 17:01:23 T:00000EE0 .\FilePublic.cpp 1389 C:\Recovery\Logs\Winre.wim
2018-12-29 17:01:23 T:00000EE0 .\FilePublic.cpp 1389 C:\Recovery\WindowsRE\Winre.wim
2018-12-29 17:01:23 T:00000EE0 .\FilePublic.cpp 1401 C:\Recovery\WindowsRE\Winre.wim
2018-12-29 17:01:23 T:00000EE0 .\FilePublic.cpp 1418 C:\Recovery\WindowsRE\Winre.wim
2018-12-29 17:01:30 T:0000119C .\DosDevice.cpp 85 nRet=0x0000000600540000
2018-12-29 17:01:30 T:0000119C .\DosDevice.cpp 85 nRet=0x0000000600540000
2018-12-29 17:01:49 T:0000119C .\FilePublic.cpp 650 nRet=0x0003001502890000 D:\INST\WinToUSB\WinToUSB_x64\x64\*.*
2018-12-29 17:01:49 T:0000119C .\BuildWinpeWimgapi.cpp 410 nRet=0x0003001502890000
2018-12-29 17:01:49 T:0000119C .\BuildWinpeWimgapi.cpp 126 nRet=0x0003001502890000
2018-12-29 17:01:59 T:0000119C .\BuildWinpeDlg.cpp 252 nRet=0x0003001502890000
2018-12-29 17:02:00 T:00000EE0 .\SelTargetPage.cpp 3261 nRet=0x0003001502890000
2018-12-29 17:02:00 T:00000EE0 .\SelTargetPage.cpp 3298 nRet=0x0003001502890000
2018-12-29 17:02:00 T:00000EE0 .\SelTargetPage.cpp 3514 nRet=0x0003001502890000
2018-12-29 17:07:15 T:00000EE0 .\main.cpp main 264 End...

So according to the website, I can use the free version of wintohdd to clone my system
Yet when I try it says my trial version is not able to do this?
Does this mean the trial version is completely useless? or am I missing something?

Hi,

I'm trying to install Windows 10 1809 (from an ISO downloaded using Microsoft Media Creation Tool) on an external SSD (it's actually an internal one connected through a USB enclosure), but I'm getting the error: "The operation may damage the current Windows installation". I'm attaching a picture of the error below. I'm running WinToHDD from a Windows Pro machine registered using a Microsoft Dreamspark (student) key.