The board looks slick and seems to run well... Except for trying to install an OS from a USB drive. In my case I had the latest BIOS revision F7, a Samsung 512GB NVMe SSD, and a USB 3 32GB drive with Windows 10 Enterprise 1703. Installation media was created with Rufus and boot tyoe was created as UEFI only. This drive worked to install on 3 other PCs without issue.First was getting the USB drive detected. It just wouldn't. No matter my BIOS settings it just couldn't find the USB drive. After much peripheral switching, disconnecting items from the motherboard, etc... The only way I got it to work was waiting j til the machine was already one to connect the USB drive. I found connecting it at the splash screen when you can enter BIOS, press F12 etc... was the only way to get it to see it. Once it did, I was able to boot from it and install windows. The USB drive remained detected after I rebooted.However, windows would crash after installation and first reboot at about 23% during the initial setup. Every, single, time. Seems it was detecting something that wasn't compatible or otherwise didn't like. I need to troubleshoot more to determine if it's the motherboard or other hardware related issues. Frankly I don't really to have to.Either way the damn USB detection was an hour ordeal and many a Google searches later with a long history of this issue and Gigabyte motherboards. Shame too, I wanted to like this motherboard, however, it'll likely be returned and get something else. Maybe it's a lemon, maybe it's not. Never had this much trouble getting a system up and running.If I can get it fixed or find a smooth solution, I'll happily change this review.18DEC2017 UpdateI attempted a 2nd go at this and swapped M.2 slots. No change. Attempted to use a few 2.5" SSD in RAID 0 on the SATA ports, no change with the windows installation being a failure but it seemed to go less further in the installation process and would fail before the first reboot at about the 20% mark. Tried just a single 2.5" SSD in AHCI mode. No change in the result. I created a new USB boot drive with Rufus on an older USB 2 drive and set it to be bootable with UEFI or MBR this go round. Tested on another machine the drive worked like the previous one. Used on this combination, and same installation error. I was attempting to move either USB boot drives into different ports to see if that would make a difference and I accidentally left them both connected and the installation processed passed, I was able to boot windows and write this review.Overall I'm unsure what the issue was definitively, but considering all the problems I had with just recognizing the USB boot drive in the first place and having tested it out on other machines to know it was working, I'd have to say there's something "wonky" with this motherboard and USB drives, maybe just limited to the boot process. If I figure this out I'll update this review again.Beyond that, windows is speedy compared to the previous machine but the VR was a great improvement. Now that it's working well enough to use, I'll put the stars at a 3, but for a new system builder this would've been a pretty tough challenge to overcome.18JAN2018ISSUE: Having intermittent issues of USB power surge warnings when booting into windows.TL:DR - Turned off windows fast boot and it seems to have stabilized.Normally I'd say this is a windows issue but considering the previous issues I've been looking into this issue for about a month now. Could never get the issue to remedy for more than 1 or 2 boots so I started with disconnecting everything USB related, both internal and external. No luck. Still getting the issues. This also prevented me from using some USB ports, both USB3 and 2. I also notice windows was giving me the "new device connected" sound when I booted up. Like it was discovering a new device every single time. Since it prevented me from using the ports or devices connected to them, I had to see if it was at the BIOS level or Windows. So... I took a USB boot drive and connected it to each port and booted.BIOS saw the drive on all ports. Cool, thats great. Feels like a windows issue. Booted next and luckily I had windows repeatedly displaying the error today, as in every 3 seconds it would notify me. This gave me an opportunity to test disabling usb hubs and try to narrow it down. I disabled my root hubs and reinstalled one by one. Tried older drivers, factory motherboard drivers, intel drivers....Nothing corrected the issue. Though I did notice I was getting a different amount of hubs reported in device manager vs what was being reported in the BIOS. Huh. Weird. After some internet sleuthing, it turns out the fix wasn't driver related at all, but windows power setting called "fast startup." It's in control panel (Not settings) -> All control panel items -> power options -> choose what the power buttons do -> change settings that are currently unavailable (link) -> uncheck the "turn on fast startup (recommended)" option. Now I didn't recognize any noticeable boot time change, but what I did notice was all my USB root hubs and devices were there once I was at the login screen and NO more new device sound at login. Whoop! All my ports now work and all my devices are recognized at startup. Damn weird windows issue. All in all I hope this helps someone who might think it's a Gigabyte issue.