Unknown error while Creating Win 11 To Go and cloning old Win 10 created with Hasleo

[KKBS]

Hi Team,
We are currently using the Halseo WinToUsb Pro Version 9.5 (Build: Jan 6 2025) and facing problem while cloning and creation of Win 11 ToGO Drive.

1. Cloning :
Previous systems created can no longer be cloned as the tool takes forever (~ More than 3 hours) and crashes without any error.

2. Win 11 To Go Creation:
The operation was not successful after 99% completion which failed with an Unknown error 0x003100B2000001B1 (ErrorWin11.jpg)
The ISO file that was used : en-us_windows_11_iot_enterprise_version_25h2_x64_dvd_67098cd6.iso [Downloaded from Microsoft Visual Studio marketplace]

However after failure the device was not recognizable on the laptop and had to be removed and connected back.

The contents on the drive (ErrroWin11_Contents.jpg)
The size of the created contents (ErrorWin11_Size.jpg)

Wanted to know if Win11 To Go can actually be created with the version 9.5 being used, or any changes to procedure needed due to reported error.

Thanks

[KKBS]

Quick update.

I tried the below few settings to enable creation of WindowsToGo Drives.

1. Launch Halseo with Admin priv
2. Uncheck "Offline internal disks when booting into Windows To Go"

Resulted in following observations:

Windows 10:

1. Creation completed successfully
2. Booting for the first time caused a BSOD with BUGCODE_USB3_DRIVER
3. Rebooted again after the BSOD was able to boot to Windows

Windows 11:  (Also checked "Bypass Microsoft account requirements")

1. Creation completed successfully
2. First boot taking forever (Stuck in windows boot animation) (Win11_Stuck.jpg)

Thanks

[KKBS]

Update 2:

For Windows 11:

1. Unchecked even "Bypass microsoft account requirements"
2. Connected to internet for Windows installation , could be due to new Windows 11 requirements.


Observation:

1. First boot we have the the new windows BSOD with the same error BUGCODE_USB3_DRIVER [Win11_BSOD.jpg].
2. The second boot result in the restart Windows pop up [Win11_RestartWindow.jpg]


Thanks

[admin]

Regarding the BUGCODE_USB3_DRIVER BSOD issue, we recommend that you try updating your motherboard and USB drivers. And hardware compatibility issues may also cause this problem, so using a new USB cable and USB enclosure may also help.

[KKBS]

Regarding the BUGCODE_USB3_DRIVER BSOD issue, we recommend that you try updating your motherboard and USB drivers. And hardware compatibility issues may also cause this problem, so using a new USB cable and USB enclosure may also help.

Any recommendations on USB cables and enclosures or SSDs ? Using M.2 NVME SSD enclosure from ORICO

[admin]

Regarding the BUGCODE_USB3_DRIVER BSOD issue, we recommend that you try updating your motherboard and USB drivers. And hardware compatibility issues may also cause this problem, so using a new USB cable and USB enclosure may also help.

Any recommendations on USB cables and enclosures or SSDs ? Using M.2 NVME SSD enclosure from ORICO

I'm sorry we don't have any specific enclosures or cables to recommend, as we typically purchase Portable SSDs directly, such as the Samsung T7. Do you have any other USB drives on hand that can be used for testing? Do they all have the same problem? The problem could also be caused by compatibility issues with the computer.