I was running Win7 64 bit with the Intel driver...I believe thier eXtensible host controller works fine. Windows 7 will do security updates until 2020 and most raid controllers drivers are built in ( most have been around for a few years and load third own BIOS anyways) You should be good to go...If you want to run a NVMe SSD drive for your windows 7  that may be a little trickier but doable 
 

Be vary of RAID controllers on newer chipsets (all which are pure UEFI). There is no guarantee whatsoever from any of the vendors that RAID/HBA card will work properly. Most consumer boards don't support Int15 which is required for normal operation. Only server grade chipsets are supported like e.g. C6xx family. 
 
I felt this rubbish myself when 7 series outright refused to work, nobody cared about fix. 6 series also for most part didn't worked properly on X99. 8 series Adaptecs work on X99 100%, I know that most of LSI cards are trouble free. I haven't got a clue about Z270 tho, but like I've said be very vary of RAID controllers on UEFI powered consumer boards. Old school BIOS retained irq, int and all addressing stuff in same space for decades. With "invention" of UEFI, outside basic ground work supplied by Intel (or AMD) there are NO rules. Every UEFI detection procedure is different across the range. What will work on EVGA may or may not work on other vendors boards. It's that stupid. No other word for it.
 
"No int13 drive found" is normal in two cases:
 
1. You haven't defined any arrays on the controller (it doesn't matter if volume is bootable or not)
2. Using RAID controller in HBA mode and in this mode you can't create Int13 volumes - all drives are detected as a singular devices, like using ordinary SATA ports off the motherboard.
 
My current main workstation running in HBA mode (drive pool as RAID is by now totally archaic) and I get "no int13 drive found - bios not installed" every time when PC is POSTing. 
 
32b driver won't work on 64b system. I don't know if KL is limited only to 64b, but 32b is by now prehistoric. Monitoring suite from Adaptec requires about 800MB-1GB of RAM just to run in the background. Accommodating this inside 32b system is not possible. 
 
If you planning to install OS on normal SSD (recommended) please remove everything from the system except SSD and CD drive. You can install controller later. I don't recommend installing RAID card during OS installation process. Sometimes controller forces itself on booting process and you'll end in world of pain. When system is installed and running controller can't takeover Windows Boot Manager.

Well installing Win7 from USB pendrive is potential minefield. I got bored with all the hassle. Returned to good old DVD, plug it for 10-15 minutes, all goes smoothly. Problem solved. 

Well after learning how to extract the CD key from one of my other win 7 systems, giving Microsoft the key in exchange for a Win 7 64 *.iso download and learning how to burn an *.iso DVD with IMGBurn I managed to replace my lost 64 bit DVD.
 
Now the original problem I had with all of this is not being able to get the controller to work. So I went out and got a SATA drive hoping to use it to load an OS on the SAS drive.
 
The disc does get past all the earlier problems I had with the USB. But once you load the Win 7 xHCI USB 3 driver I lose all USB functionality including the mouse and keyboard. That leaves me no choice but to reinstall. I tried the USB 2 headers and 3 different drivers. Is there not any other way to keep at least the keyboard working? Seriously considering a retail Windows 10.
 
Meanwhile I got with Adaptec/Microsemi support and they are replacing the controller. That problem is at the BIOS/UEFI level and has nothing to do with the operating system. Looked at LSI controllers - very similar. If Adaptec was not sending me another board and refunded instead I would probably get the LSI 9300-4i. New builds are tough.

I am pushing SAS for 3 reasons. One is 12Gb/s I/O speed, two is MTBF an order of magnitude better than SATA, and three; downward compatibility with SATA. I also like the controllers ability to perform independent operations on and management of many drives from it's own BIOS.
 
The controller has a legacy Ctrl-A BIOS that you can use to manage drives like old SCSI but it also has a UEFI mode which I hope might work when I get the new one.
 
 

Well another 2 weeks have gone by. Sent the controller to Microsemi/Adaptec and they sent me another under warranty. Same thing - "no logical drives found" etc... Since abandoned trying to install Windows 7 (way to many problems and I can't get through the xHCI issue). Went and got a retail W10 on USB. But I have also learned a lot and sorted out all the individual problems to get this issue down to what I believe is the core problem.....and that I am saving for a new thread as this one is no longer applicable. The new thread is "Adaptec 1000 series SAS UEFI incompatibility with EVGA UEFI". See you there.