Unable To Locate Hardware

[ParkerSL]

So i have just bought and received my Pro TOols Express and Avid Fast Track Interface. I have registered and downloaded everything including the Instruments and have updated to the more recent update for my interface but every time i go to open Pro Tools Express a message comes up saying "Unable to Locate Hardware" i have no idea what to do at this point. I have checked as many forums as i could find but still can not find an answer to this issue. if someone could help that would be amazing, thank you! also i do have the interface and usb iLok plugged in while trying to open Pro Tools

[YYR123]

You need to post your computer specs operating systems and the ProTools version that you were using for a more detailed response and help

[ParkerSL]

I am using a Mac Book Pro 13' and Pro Tools Express

[YYR123]

Originally Posted by ParkerSL

I am using a Mac Book Pro 13' and Pro Tools Express

Sorry to be a downer but u say mb and I think 10.6.8 - right???

U say PTE and I say ver 3.5 right?

[ParkerSL]

2.9 GHz dual core intel Core i7 with 4MB L3 cache

8gb of 1600MHz DDR3 SDRAM

750gb 5400 rpm hard drive

any of that help? im not that ig into computers so im not to sure what to post

[Southsidemusic]

We need:

OS version
Pro tools version
Driver version for your Avid FT interface
Other useful info found here

http://duc.avid.com/showthread.php?t=300050

Please provide ALL the info we ask for in one clear concise post so we don't have to ask several times for your OS version for example

Thank you
Christopher

[skugger]

FYI, I just ran into this issue with my brand-new M-Track Plus. I only had to download and install new drivers for it, at www.m-audio.com, in order to get this error to go away. the new drivers are dated May 2013.

[apoltorak6]

Originally Posted by skugger

FYI, I just ran into this issue with my brand-new M-Track Plus. I only had to download and install new drivers for it, at www.m-audio.com, in order to get this error to go away. the new drivers are dated May 2013.

From what it seems I had the same exact problem, and this was the answer. I looked all over the forums and nothing helped...then I saw this post, downloaded the most recent driver, and now everything works!!!