Is there a particular problem that you are trying to solve? Because as I see it you just got an extra option which causes no problems and which you do not have to use.

@Hennes I'm used to see the icon only when there is an actual USB flash drive plugged in. Seeing the icon gave me extra information. Now it doesn't, and if by accident I click the Host Controller instead of the USB drive, I have to reboot (or do some trick to disable/enable the controller so that it's detected again). Not cool.

@guest-vm The W7 driver won't install, I tried the modded W10 one but Windows still says his driver is more recent for some reason. I tried to force it and... my USB stopped working. No way to boot W10 in safe mode without doing Shift+Shutdown or going into the Settings but lucky me, my Asus Strix motherboard has a PS/2 port (not sure why but I'm so happy it does) so I was able to reverse the change easily (and save myself from booting on USB sticks to debug or just reinstall). That modded driver might be outdated for the Z270 chipset, I'm not sure.

@guest-vm Did you delete your comment? Can't see the link anymore. But yes I don't mind posting in that specific thread and try to work a solution out.

Run in command prompt reg query HKLM\SYSTEM\CurrentControlSet\Enum\USB\ROOT_HUB30 /s /v Capabilities, report any found value to me.

3 matches found. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USB\ROOT_HU‌​B30\4&1dc5b97&0&0‌​, 5&25605cf7&0&0 and 5&930df50&0&0. I have an ASUS Z270G STRIX, it does have an additional ASMedia USB 3.1 Controller for the USB 3.1 Type-C port.

All the same: 0x80.

damn, then what is described here won't work...

Have you tried the Intel® Driver & Support Assistant to check for Intel drivers? This utility might suggest the Intel® Chipset Device Software or you could try to install it manually. Updating the BIOS is another possibility, but check very carefully that it matches your motherboard.

@harrymc Already tried the Intel utility and installed the Intel chipset driver from their website. Also updated my BIOS from ASUS website. The closest I can get to a driver on Intel's website is here: downloadcenter.intel.com/product/65855/… However Windows keep saying my driver is already up to date and won't use that driver since it's for Windows 7 or outdated. I didn't try to force it.

The driver might still work on Windows 10, but ensure that the files needed to undo it are not on a USB 3 device, for obvious reasons. If by any chance this works, you will need to block Windows from updating it back (but that's for later).

Tried to force it, it says it's not a "compatible software driver for your device", Windows won't let me install it. I tried all *.inf files for x64, there were 3.

@guest-vm Yes. I had the same issue with the ASMedia controller while I was using Microsoft's own driver. But ASMedia still develops drivers for its controller even for Windows 10 (Intel doesn't), so I was able to just update the driver to ASMedia's driver and it removed it from the USB eject menu (it also explicitly said it was ASMedia's controller).

There were 4 Hub entries in the removable drive section, updating the Microsoft driver to ASMedia's removed half of the entries. I added a full picture of what's in my Device Manager for clarity sake.The Intel host controller, if disabled, also removes the bottom entry and both removable devices.

BTW, did you import Win-RAID CA Certificate and use DPInst.exe when you tried the modded Intel drivers? As there is a feedback that it worked for a B250 mobo with Windows 10 1709 x64, can't see why it didn't work for your Z270.

I have exactly the same device with exactly the same installed driver, and the device does not show up as removable. The problem might be a remnant from some past installation, perhaps from when Windows was upgraded to Windows 10. I suggest the old method of deleting the device in Device Manager and reboot, to reinitialize the device to a clean state. Otherwise, there have been reports about such problems being solved by a clean install of Windows. But if your device is functioning correctly, I do not think that the problem warrants such a radical solution.

@harrymc I installed Windows 10 from scratch last week. In fact, I created this post right after the installation as I wasn't able to fix this.

@guest-vm Windows 10 1709 fall update wouldn't go through at first, it failed every time, and suddenly for no reason, the update decided to install correctly. It's not the first time I see this after a clean W10 install. Now that the update went through, I will do some more tests tonight about this because no, as far as I know I didn't import any certificate last time I tried the modded driver (all I had to do was confirm I was sure I wanted to install non-approved driver or whatever).

@guest-vm The Windows 10 ISO (downloaded from Microsoft website with my key before installing) didn't have the 1709 update pre-installed. I have Windows 10 Pro (not sure that it matters but just in case). winver.exe currently shows 1709, I didn't check pre-update what it was.

If modded drivers still fail, try them on a clean reinstalled 1709 (eg. on a spare small partition) when you have time, for "debugging" sake.

All in all it just seems like there is no thing as a simple fix for this and I'm honestly very surprised. The issue is documented online but barely, it doesn't receive a lot of attention. It seems like it's just an acceptable behavior for most. Both my keyboard and mouse stop working if I accidentally hit that button with no other fix than hard resetting the whole PC if I don't have a PS/2 keyboard already plugged in (it doesn't work if it's not plugged in before POST). I'm surprised this is deemed as acceptable. It's not like I'm really going to ever misclick (I probably won't) but still.

@dnLL Have you re-tried the drivers yet?

@guest-vm no sorry, not yet, I don't have the time right now. It's more time consuming than I anticipated.