Windows 10: Windows 10 Creators Update bug: USB 3.1 Port shown as Unspecified

You are probably right. I did not realize you had done a fresh installation. That is the nuclear option and eliminates a lot of possible problem/solutions.
Most likely growing pains with Manufacturer drivers not keeping up with Windows builds, or Windows builds not being backward compatible with old drivers.

 

Have you considered trying the F20 BIOS?

The statement: "version F21 it is required to install USB 3.1 drivers" sounds like the solution here. The question then becomes why the F21 BIOS version wont work.

BIOS upgrades add new features and functionality. They don't list all of the changes made in each version on the download page, just the "most relevant" ones. So it doesn't matter, in most cases, that you don't need the featured upgrades, there are often others and bug fixes that you can use. In general it is always best practice to run the most recent BIOS made for your motherboard, but there are exceptions.

It sounds like you ran a BIOS update from within Windows. While this method has greatly improved over the years it can still be problematic in some cases.
Do you know if there is an option to flash the BIOS from within the BIOS?

Your USB 3.1 ports are probably running in USB 2.0 mode. Maybe 3.0

 

It is always helpful if we know what hardware you are working with. If you fill out your system specs then we could see that info.

 

Here is the BIOS method: Q-Flash

http://www.gigabyte.com/MicroSite/12...ios_qflash.pdf

How to Update Your Gigabyte Motherboards BIOS | tonymacx86.com

 

This is a solution but didn't work for me, You can test it anyway:
Fix USB 3.0 HUB not working in Windows 10 Creators Update | Microsoft Surface tablet

 

Had something of a similar issue as posted in the Gigabyte forums at overclock.net. However mine didn't arise until after I updated my BIOS to F21, before the Creator update!

That said, if the board supports Thunderbolt, make sure you install both driver and firmware update. And as many have said both chipset drivers and SATA drivers. Once this is done, reboot, than after that, if the issue is still there... completely power off the machine, to include removing the power cord! Wait about 30 seconds, power back on and see what happens.

Let us know.

And yeah, for some odd reason the F21 BIOS causes some weird issues with the some USB ports. Gigabyte is clueless here, and claim they know nothing about the issue. I know because I called them on this. They promised to get back to me on it but they never did. That was 3 weeks ago. Anyway have a look at my post for clarity. And let me know if this helps.

Peace *Cool

 

The F21 BIOS is not beta.

And yeah, it is unusual for a "stable" BIOS to cause issues, but somehow Gigabyte managed to accomplish this, at least on some machines. The big issue is that F20 and up BIOS's completely changes the look and features of the old BIOS since it's main purpose is to add Kaby lake support to their (gigabyte) Z170 boards. That said, you are warned that updating to these BIOS won't let you "downgrade" to your previous one.

Prior to the F20's, most all of Gigabyte's Z170 boards had sub 8 BIOS's. That is most of the BIOS's were in the F7ish range. Prior to updating my Z170X Gaming GT board I had an F7c Bios. After these, Gigabyte jumped to the 20's where they added support for Kaby Lake processors to most their Z170 boards.

The first Kaby BIOS's had over-volting issues with Sky Lake processors. The fix was the F21/F22 BIOS (some boards have an F22 BIOS) which "adjusts" the V-Core voltages. Current BIOS for the OP's and my board is F21.

Anyway, I too had weird issues when I upgraded to the F21 BIOS such at that of the OP's issue as well as a TPM module issue. The TPM issue seems have sorted itself out so.

That said, I've been updating BIOS's since I got into PC's, always opting for the latest one, and this is the first BIOS I've ever had issues with in my 20 years of PC building.

At any rate all this is just FYI.

Peace *Cool

 

Yikes!
Another Seagate saga? Et Tu Gigabyte?

 

Ok after flashing my BIOS back to F5 version, btw really worry about it because maybe it could break my BIOS, now except for the USB issue everything is working properly, no more bsod or instabilities, but not USB 3.1 either.
Now after flashing my BIOS back I lost my Mac address in the BIOS(out off topic if anyone knows how to fix this)
Gigabyte state I need BIOS version F21 to be able to install USB 3.1 drivers, but I can't use this one because It gives me issues to boot into window
Do you think flashing the BIOS up and back can be safe?
I tried all the solutions provided here, none of them have worked. Thanks very much for all your help anyway.
By the way between those BIOS flashing I was able to install thunderbolt but when I started the computer say I need an update and open a web site to download it but my motherboad is not listed there.
Identify your product, then click on the link below to go to the product page. Click on “Support and Downloads”. Choose “Utility” under Download Type and follow all directions. Remember to install the Thunderbolt driver before installing the Thunderbolt FW Update Tool.

GIGABYTE - GA-Z170X-Gaming G1
GIGABYTE - GA-Z170X-Gaming GT
GIGABYTE - GA-Z170X-Gaming 7
GIGABYTE - GA-Z170X-Gaming 7-EU
GIGABYTE - GA-Z170X-UD5 TH
GIGABYTE - GA-X99P-SLI

- See more at: Thunderbolt™ Updates | Thunderbolt Technology Community

 

Try grabbing the modded USB 3.1 drivers from Fernando's exellent Win-Raid Forum: USB 3.0/3.1 Drivers (original and modded). I've found them to be uncommonly helpful in dealing with odd or interesting USB 3.0 and 3.1 driver issues on Windows PCs.
HTH,
--Ed--

 

My reply replies in red. The links are to the Gigabyte forums over at overclock.net.

Peace *Cool

 

It still would be nice to see what hardware we are dealing with.

 

anyone test it ?

 

What's wrong with the drivers that comes with the boards???

 

I've modded my own high-end desktops with these win-raid drivers and they work better than the stock MS drivers supplied by default.
HTH,
--Ed--