This board does not have an FTDI chip -- they replaced that with another USB bridge (atmega16u2). Some details can be found here:
http://learn.adafruit.com/arduino-tips-tricks-and-techniques/arduino-uno-faq
From that link, it is indicated that Arduino started using their own USB vendor ID (VID), so the device will not be identified as nor work with anything related to FTDI.
64-bit Windows has been a lot more picky about unsigned USB drivers than prior versions. While I haven't done anything with Arduino yet, there are a few things I can suggest.
1) Get Windows to disable device driver signature enforcement. Windows 8 apparently does this differently than before -- it used to be that hitting F8 on boot would get to a menu that would allow this, but apparently now they have brought that control up into the OS. Have a look here:
http://www.howtogeek.com/126016/three-ways-to-access-the-windows-8-boot-options-menu/
Historically, when you disable the driver signature enforcement, Windows re-enables it on the next reboot. Not a great or permanent solution, but if you're just trying to get something done, it may be an option.
2) Try to coerce Windows into loading the driver. If you go into the device manager and tell it to load the driver, it may force you to browse to the location of the .inf file with the Arduino VID/PID (probably provided with whatever you installed for the kit). It may then allow you to use this if you suffer through enough warning dialogs first. This may work better under 32-bit than 64-bit (where I believe the enforcement is more severe). This might need to be done in conjunction with option #1 above.
3) Windows is the only OS that requires a special driver file to use the new board (notwithstanding reports of OSX Mountain Lion above -- not sure about that). You might be able to get an Ubuntu Linux on a USB flash drive that allows you to use the same tools without installing anything permanently on your PC. However, that is likely to have its own learning curve.
4) Buy a USB Vendor ID for yourself ($5K), get the device driver professionally tested (~$400 just for Windows 8 64-bit based on my experience) and signed ($250). This is what Microsoft thinks you should do.
I think that some combination of #1 and #2 will get you past this.
