I have a TerrMaster D8 Hybrid USB 3.2 Gen 2 external enclosure where I have 4 HDDs and 2 NVMEs within it.

When I connect to the USB C 3.2 Gen 2 connector on the back of my Gigabyte X570 Aorus Master motherboard I get this issue where it does not recognise the device and it Device Manager it states the below:



When I Right Click > Properties, it says this:



This is on a fresh install of Windows 11 Pro, and I even tried reinstalling and it was still the same.

However, when I use the same cable and connect to my laptop, it works immediately and without issue, so there is nothing wrong with the enclosure nor the cable (I don't think). I only have the one USB C port on my desktop and so can't try the cable in another port. However, when I plug my Audient ID14 MkII into the desktop's USB C port, it works fine, so it doesn't appear there is anything wrong with the USB C port.

I read somewhere it may be due to not being ejected properly, but it was disconnected when the PC was powered down. Also, when connecting to the laptop, I had no issues and ejected it properly there before disconnecting to see if it resolved the issue to no avail.

Anyone got any ideas or come across anything like this or any ideas on how to resolve?!?!

 

Last edited: Oct 11, 2024

i had major usb issues with overclocked ram.
disabling onboard usb audio also helped

 

Too many variables to randomly guess at. Start with the gpt suggestions, save some typing. I would probably jump to 7 and 8 based on your post. Everything else is more basic and time consuming.




Windows has stopped this device because it has reported problems. (Code 43). The USB set address request failed.
ChatGPT said:

The error message "Windows has stopped this device because it has reported problems (Code 43)" typically indicates that there is an issue with a connected USB device or its driver. In your case, the additional message "The USB set address request failed" suggests a problem with the USB device's ability to communicate properly with your system.

Here are some steps to troubleshoot and resolve this issue:

1. Unplug and Replug the USB Device

• Disconnect the USB device from the computer.
• Wait for a few seconds, then reconnect it.
• Check if the error persists.

2. Try a Different USB Port

• Connect the USB device to another USB port on your computer to rule out any problems with the current port.

3. Restart Your Computer

• A simple reboot can sometimes resolve temporary issues with device recognition.

4. Check Device Manager

• Press Win + X and select Device Manager.
• Look for any devices listed under Universal Serial Bus controllers with a yellow triangle or error icon.
• Right-click on the problematic device and select Uninstall.
• After uninstalling, disconnect and reconnect the USB device to allow Windows to reinstall the drivers.

5. Update or Reinstall USB Drivers

• Right-click the problematic device in Device Manager and select Update driver.
• Choose Search automatically for updated driver software.
• If the update doesn’t work, download the latest drivers from the manufacturer’s website, uninstall the current driver, and reinstall the new one.

6. Check for Windows Updates

• Sometimes, driver updates are included in Windows updates.
• Go to Settings > Update & Security > Windows Update, and check for updates.

7. Test the Device on Another Computer

• To determine if the issue is specific to your computer or the USB device itself, try connecting the device to another computer. If the problem persists, the device may be faulty.

8. Disable USB Selective Suspend Setting (Optional)

• Open the Control Panel and navigate to Power Options.
• Click on Change plan settings for your active power plan, then choose Change advanced power settings.
• Expand the USB settings and then the USB selective suspend setting.
• Set it to Disabled.
• Click Apply and OK to save the changes.

9. Check for Hardware Issues

• If none of the above steps resolve the issue, the USB device may be physically damaged and may need to be replaced.

These steps should help you troubleshoot the "Code 43" error. Let me know if you need further assistance!

 

Already tried all of this.

 

My RAM isn't overclocked and all onboard audio disabled already as I use an audio interface.

 

Last edited: Oct 12, 2024

I am now suspecting the USB C port/circuit may have shorted somehow. Having thoroughly gone through, it seems like it is just the USB C port that doesn't work, but when connecting to one of the four four USB 2.0 or other USB A type ports devices load up.

Does this seem like a legit explanation?

I'm contemplating ordering an add in PCI card for USB 3.1 Gen 2 ports and seeing if that works as a solution. Anyone got any experience with these?

Otherwise I may be needing to buy an entire new motherboard....which will then lead me down to upgrade the entire system, which I don't wanna do just after the expense of buying a new home!

 

Last edited: Oct 12, 2024

I've recently come across similar thing, turned out Microsoft Windows Security was stuck in block loop because the USB device contained bootable partition/code Microsoft decided not to like

 

That may be the issue and will try that as one of the drives is my old OS drive that I'm yet to format.

Not sure why it wouldn't also do it on my laptop too though if this was the issue?!

 

Try other peripheral on those ports (mouse, usb key with a cable ...) and see if they work.

Even if ports "burned", it is 9 times on 10 a soldered fuse.
As each port have is own ... probably not your case

May be a security update not on laptop, or different security setting

 

Last edited: Oct 12, 2024

Just tried my Push 2 and my Audient ID14 MkII connected to the USB A ports and they all get recognised fine by the PC. It may be the boot drive issue, so am next gonna try to connect to my laptop, use that to reformat the old OS drive in there, and then see what happens.

The TerraMaster D8 Hybrid setup is currently:

HDD1 - 18TB Seagate IronWolf Pro (in RAID0 with HDD2 via hardware RAID controller on the enclosure)
HDD2 - 18TB Seagate IronWofl Pro (in RAID0 with HDD1 via hardware RAID controller on the enclosure)
HDD3 - 8TB empty drive
HDD4 - 5TB empty drive
NVMe1 - 2TB old OS drive with old OS boot data still on it
NVMe2 - 2TB empty drive
NVMe3 - unoccupied
NVMe4 - unoccupied​

When I connect, it tries to connect the drives but almost like it can't work out what should be happening as they aoppear and disappear for a couple of minutes and then the empty NVMe becomes visible, the old OS NVMe becomes partially visible but not fully accessible (and can't format as it seems the connection with the device isn't stable enough so it crashes), and the 2 empty HDDs become visible, and it's the RAID drives that seem to trigger the unrecognised device error and are not visible at all.

PS - The RAID0 etup is because this is my hot drive. I also have a cold enclosure with 2 x 18TB Seagate IronWolf Pro drives in RAID0 too and the 2 RAIDs are mirrored, meaning I have duplicates, as well as cloud version, so have backups, before anyone comments on the absurdity of having 36TB of data in RAID0

 

I would scan all hard disks for errors with the command chkdsk and have them repaired immediately!

It is best to unplug all the connectors and plug them back in when switched off, of course. Sometimes there is still voltage in the cable. Please also always use the “ Safely remove hardware button in the taskbar.

I have read that if you have NVMe1 it will take up one free SATA port! So if you have 6 free SATA ports - 1 SATA port goes to the DVD/writer drive, that leaves five for the hard disks including the NVMe's!!!! Please check!
I wouldn't install so many hard disks, it's better to have a few external hard disks for storage or as a backup.

EXTERNE SDD/HDD List:
Inateck USB 3.0 zu SATA Konverter Adapter - 20.04.2024 - 19,95 €
https://www.inateck.de/collections/...aufwerke-hdd-ssd-mit-12v-2a-netzteil-ua1001-1

DELOCK 83119 Slotblech - USB 2.0 2x Port Low Profile
https://www.reichelt.de/slotblech-u...delock-83119-p180130.html?&trstct=pol_6&nbc=1

LOGILINK UA0041A externes 2.5" SATA, HDD/SSD Gehäuse, Alu, USB 2.0, silber
https://www.reichelt.de/de/de/exter...-2-0-silber-logilink-ua0041a-p317457.html?r=1

 

Last edited: Oct 12, 2024

The NVMe's are in an external enclosure, so SATA port allowance isn't an issue. My internal NVMe's and SSDs are working fine.

I've also unplugged everything except for keyboard and mouse and the enclosure with no success. And used the Eject Safely options.

I think your links are misunderstanding the issue maybe?!

All the above drives are in an external enclosure, being the TerraMaster D8 Hybrid. It is a USB C.3 Gen 2 10Gbps enclosure, and you can find the product page here: D8 Hybrid (terra-master.com)

The firs two HDD bays are RAID-configurable with the device's onboard hardware RAID controller, which I have set to RAID0. The other 2 bays are just independet hard drives, as are any NVMe's you put in the 4 slots (of which I am only using 2). The enclosure then connects as a DAS to your device via USB 3.2 Gen 2, meaning you can RAID0 HDDs and use NVMe's in the same enclosure for fairly zippy performance to utilise that 10Gbps bandwidth.

My issue here is that when using the specific, and only, USB C 32 Gen 2 port on the back of my desktop, I am getting the device connection issues detailed above.

 

This is what I see in disk management, meaning it is the RAID drives that aren't showing up and seemingly causing the issue in connecting:

Disk 2 = 2TB NVMe OS drive
Disk 3 = 4TB internal NVMe drive
Disk 4 = 4TB internal NVMe drive
Disk 0 = 4TB internal SSD
Disk 1 = 4TB internal SSD​

All the above from the above list are internal and working fine, so no issues with these.

The list below, from the Disk Management panel below, are the other drives in the external enclosure. I have now been able to use my laptop to Delete Volumes and used DiskPart to clean them, meaning they are now empty with no data and unallocated, so no previous OS boot information on any of them:

Disk 5 = 8TB HDD (drive bay 3 on TerrMaster D8 Hybrid external enclosure)
Disk 6 = 5TB HDD (drive bay 4 on TerraMaster D8 Hybrid external enclosure)
Disk 7 = 2TB NVMe (NVMe bay 1 on TerraMaster D8 Hybrid external enclosure)
Disk 8 = 2TB NVMe (NVMe bay 2 on TerraMaster D8 Hybrid external enclosure)​

However, my 36TB RAID0 using the external enclosure's hardware RAID in HDD drive bays 1 and 2 are seemingly the ones causing the connection/device issues and not visible at all.

 

Thanks Bunford for the summary, in my opinion you have too many hard drives, hence the links to make some hard drive external.
My idea for a stable system goes like this: 2 NVMe internal (fast access times) , 3 x SSD (fast access times) the rest as external via the as data storage movies - large files. Nevertheless, I would check all the hard disks with “ Properties --> Tools ”

Windows: Error Code 43 - how to fix the problem

The Windows error code 43 indicates a problem with connected or installed devices such as USB hard drives. Several solutions are available.

- In most cases, simply restarting your PC will do the trick . This will usually resolve any driver issues quickly .
- External USB devices may also be defective , such as a broken cable. Try using a different device to see if the error occurs again. If not, you will need to replace the cable or device.
- It is also possible that either Windows, certain drivers or components require an update . These include, for example, SATA , the USB controller , BIOS or your mainboard . After the update, you often no longer have to worry about the error message.
- You may also want to perform a system restore , especially after installing new drivers. You may be using an incompatible driver that is causing the problem.

Windows Error 43: Update device drivers

Sometimes it may be necessary to update the device drivers .

1. To do this, open the Device Manager on your PC. You can find this via the Control Panel .
2. Look for the device in the Device Manager. If Windows has detected a driver problem , this will be indicated by a yellow exclamation mark. If not, it is still worth updating the driver.
3. Right-click the device and click Properties from the drop-down menu .
4 Navigate to the Driver item . Within this menu you will find Update driver . The update is started via the Search automatically for updated driver software item . The most recent driver software will be installed, if available, to solve the problem.

Windows Error 43: Reconnect devices via Device Manager

In addition to the option to update drivers, Device Manager also offers another method to solve error 43.

- To do this, select the respective device, such as the USB port, again in the Device Manager. Then click on the Disable device option .
- Then turn off your PC and restart it. The computer will now automatically reconnect the deactivated device.
- This will resolve any software and connection issues . Updating drivers is not always necessary.

 

seeing your setup, also do note Windows decides (and remembers) on drive letters and the mappings (which might explain why your other Windows device behaves different), also do note Windows is not able to properly operate drives which have exactly same names (for ex. you cannot have two Ventoy drives attached)

 

one option I'd also try is, plug the device via some properly powered USB hub/dock - because it's also possible your AHCI/xHCI BIOS config is corrupt, or BIOS/OS power delivery being corrupt, USB selective suspend etc...

 

It's a fresh install of Windows though, so there would have been nothing to remember as it happens on first connect of the external enclosure.

 

Unfortunately I do not have a powered USB hub with a USB C port to try this. But is there any other way to check for the corruption?

 

@Bunford
you can definitely go through BIOS settings and check AHCI/xHCI settings, also check its "handoff" (whether you should enable or disable it is a discussion for you can find online),
if it's fresh Windows install, you might want to reinstall drivers by those provided directly from your motherboard manufacturer, Windows is terrible picking random drivers from Microsoft database,
last but not least, check if you're using Maximum Performance mode in Windows power settings, and also make sure USB Selective Suspend is disabled there (because by default it never is)

 

Will check the BIOS later today.

Already use regedit to unlock the Ultra Performance power mode, which I always do. USB suspend is also disabled as one of the default first OS tuning things I do as per all the DAW tweaks recommended.

I haven't yet tried to install the drivers direct from the motherboard vendor, but will try that today too, but have tried separate things to pick hó drivers like using IObit Driver Booster etc.