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.

[bacevs]

[quote="admin" pid="10634" dateline="1762408827"]
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.

I’ve had similar, not identical, issues. For me, WinToUSB creation succeeds about 99% of the time, but instability shows up after booting the VHDX and sometimes during build updates.

My setup

• Enclosure: Simplecom SE538 uses a Realtek RTL9220 USB–NVMe bridge
  
• Tooling: WinToUSB or WinToGo v9.x, sometimes the WinToGo Upgrader
  
• Hosts: Rock solid on HP Elite desktops at work. Problems only on my AMD X570 board, ASUS ROG Crosshair VIII Hero, so the host USB controller seems to expose the bridge quirks.
  

Symptoms

• During updates: the upgrade often fails near the end, rolls back, and breaks boot
  
• Normal use: after running fine for a while, a later reboot can randomly throw BSODs with missing vital drivers, Explorer corruption, or “missing system files”
  

What fixed it
I stopped using the NVMe enclosure and switched to a self-contained portable SSD, Crucial X10 Pro (uses a native USB controller Silicon Motion SM2320). Same ISO, same tool, same steps, upgrades complete, no rollbacks, and no post-boot corruption since.

Things to try before replacing hardware

• Update the enclosure or bridge firmware
  
• Short USB 3.x cable, plug directly into the host, no hubs or docks
  
• Avoid front-panel ports when possible
  

TL;DR
My problems were not just the Upgrader. I also saw random BSODs and missing files on normal reboots. The common factor was the Simplecom SE538, Realtek bridge, on an AMD X570 system. Switching to a Crucial X10 Pro portable SSD solved it, however it was never an issue on HP Elite desktops.

[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.

I’ve had similar, not identical, issues. For me, WinToUSB creation succeeds about 99% of the time, but instability shows up after booting the VHDX and sometimes during build updates.

My setup

• Enclosure: Simplecom SE538 uses a Realtek RTL9220 USB–NVMe bridge
  
• Tooling: WinToUSB or WinToGo v9.x, sometimes the WinToGo Upgrader
  
• Hosts: Rock solid on HP Elite desktops at work. Problems only on my AMD X570 board, ASUS ROG Crosshair VIII Hero, so the host USB controller seems to expose the bridge quirks.
  

Symptoms

• During updates: the upgrade often fails near the end, rolls back, and breaks boot
  
• Normal use: after running fine for a while, a later reboot can randomly throw BSODs with missing vital drivers, Explorer corruption, or “missing system files”
  

What fixed it
I stopped using the NVMe enclosure and switched to a self-contained portable SSD, Crucial X10 Pro (uses a native USB controller Silicon Motion SM2320). Same ISO, same tool, same steps, upgrades complete, no rollbacks, and no post-boot corruption since.

Things to try before replacing hardware

• Update the enclosure or bridge firmware
  
• Short USB 3.x cable, plug directly into the host, no hubs or docks
  
• Avoid front-panel ports when possible
  

TL;DR
My problems were not just the Upgrader. I also saw random BSODs and missing files on normal reboots. The common factor was the Simplecom SE538, Realtek bridge, on an AMD X570 system. Switching to a Crucial X10 Pro portable SSD solved it, however it was never an issue on HP Elite desktops.

Thank you for sharing your experience. Yes, using a self-contained portable SSD does offer better compatibility.

[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.

I’ve had similar, not identical, issues. For me, WinToUSB creation succeeds about 99% of the time, but instability shows up after booting the VHDX and sometimes during build updates.

My setup

• Enclosure: Simplecom SE538 uses a Realtek RTL9220 USB–NVMe bridge
  
• Tooling: WinToUSB or WinToGo v9.x, sometimes the WinToGo Upgrader
  
• Hosts: Rock solid on HP Elite desktops at work. Problems only on my AMD X570 board, ASUS ROG Crosshair VIII Hero, so the host USB controller seems to expose the bridge quirks.
  

Symptoms

• During updates: the upgrade often fails near the end, rolls back, and breaks boot
  
• Normal use: after running fine for a while, a later reboot can randomly throw BSODs with missing vital drivers, Explorer corruption, or “missing system files”
  

What fixed it
I stopped using the NVMe enclosure and switched to a self-contained portable SSD, Crucial X10 Pro (uses a native USB controller Silicon Motion SM2320). Same ISO, same tool, same steps, upgrades complete, no rollbacks, and no post-boot corruption since.

Things to try before replacing hardware

• Update the enclosure or bridge firmware
  
• Short USB 3.x cable, plug directly into the host, no hubs or docks
  
• Avoid front-panel ports when possible
  

TL;DR
My problems were not just the Upgrader. I also saw random BSODs and missing files on normal reboots. The common factor was the Simplecom SE538, Realtek bridge, on an AMD X570 system. Switching to a Crucial X10 Pro portable SSD solved it, however it was never an issue on HP Elite desktops.

Thanks a lot sharing your setup and advice , will consider them. 

However, I was just able to get it to boot up properly using a powered SuperSpeed USB 3.0 hub by Kensington, the Windows 11 did work too

[bacevs]

Thanks a lot sharing your setup and advice , will consider them. 

However, I was just able to get it to boot up properly using a powered SuperSpeed USB 3.0 hub by Kensington, the Windows 11 did work too

Hey KKBS, just a heads-up: if it ends up being a chipset issue like I had with mine, a powered hub can help smooth things out but won’t necessarily solve it for good. The reason is that the bridge chip inside the enclosure is what actually handles all the data communication and UASP protocol with the computer - the hub only cleans up power and signal quality, it doesn’t change how the bridge itself talks to the host. So if the bridge firmware or timing isn’t fully compatible with your system’s USB controller, the same kind of issues could still appear down the track. If that ever happens, switching to an enclosure with a more stable bridge (like ASMedia ASM2362/2364) or a native USB SSD might save you some headaches.

Just curious, were you runnng into issues on an Intel or AMD host computer and/or using front panel ports?