Ethernet Connection for Avid C24

Update:  Don't know if this is going to fix the issue but . . . Sweetwater Tech found that the Pro Tools Control drivers are unsigned so Windows 10 won't load them. The set the bios to disregard the fact that it is unsigned but it still didn't load it so, they think that is where the issue lies and have requested Avid to see if they can resolve it from that angle.  The other option might be to go to an older windows version like 8 and see it it will load the drivers but they feel that since my version of Pro Tools is so new, the same issue may arise and they said that my combination of hardware and software is a low percentage of systems out there that it may not get alot of attention from Avid. So, I'm hoping that they will take it seriously enough to help me resolve it, it that is indeed the problem.

There are ways to get around the unsigned drivers. 

This site shows two ways. (1) Permanently and (2) temporary 

https://www.top-password.com/blog/how-to-disable-driver-signature-enforcement-in-windows-10-8-7/

---

@gary_keslingwrote:

1. Update:  Don't know if this is going to fix the issue but . . . Sweetwater Tech found that the Pro Tools Control drivers are unsigned so Windows 10 won't load them.

2. The set the bios to disregard the fact that it is unsigned but it still didn't load it so, they think that is where the issue lies and have requested Avid to see if they can resolve it from that angle. 

3. The other option might be to go to an older windows version like 8 and see it it will load the drivers but

4. they feel that since my version of Pro Tools is so new, the same issue may arise and they said that my combination of hardware and software is a low percentage of systems out there that it may not get alot of attention from Avid. So, I'm hoping that they will take it seriously enough to help me resolve it, it that is indeed the problem.

---

1. Now you are getting somewhere.

This is more inline with what you have been describing (ie ... not the fault of the Area51-R5). But, we will see once it's fixed.

2. I'm not sure that is how you do it. Also, the drivers must be "64 bit" because the Operating System is.

3. No, that is not really a solution. The latest version of Windows-8 *IS* Windows-10 (64bit) :Smile:

4. The fact is that Pro-Tools and the Avid-C24 need to run on Windows-10 64-bit. This requirement has been relevant for many years now already.

thanks, gonna give it a try

---

@gary_keslingwrote:

1. Sweetwater Tech found that the Pro Tools Control drivers are unsigned so Windows 10 won't load them.

2. they said that my combination of hardware and software is a low percentage of systems out there that it may not get alot of attention from Avid. 

---

1. I think another way to test this theory is to simply run Pro-Tools (and therefore, also the Avid-C24) from a different computer with Windows-10 64bit installed on it. It would prove it has nothing to do with the Area51-R5.

2. How do they figure that ? ... Windows-10 64-bit has been shipping for many years now. 

while waiting to get a call from Avid, I tried the above steps and I guess I'm not experienced enough. 

when I go to Command Prompt, the I enter bcdedit /set testsigning on I get this,  "The boot configuration data store could not be opened. Access is denied.

It has been years since I worked in basic so I'm scratching my head.

I would have used Option 2 in the procedure, which is temporary but enough to try installing the unsigned AVID driver.  

and yes, I used method No. 2 of your advice!

Ok guys,

Here goes.  I found that my new PC had not been "verified" with Microsoft yet. Not sure why that mattered but I stumbled across this and I had Microsoft text me a code that I entered and verified who I was on this PC.

After that was done, It allowed me to run certain functions or commands as Admin that it wouldn't allow before.

Then I went back in and tried to disable the Signed driver enforcement to no luck. So I tried the trouble shooting method for a 1 time disabling for testing and it let me in. After taking the F7 option to disable Enforcement of Signed Drivers. I rebooted and launched Pro Tools. This time, on Setup of Peripherals, it scanned for devices and found both my Bluetooth network and my hardwired Ethernet. I chose the Ethernet and it found my C24. I chose it and it connected to it. 

So I did a restart just to test it and it dropped it so I had to follow the same steps again and it again connected. So, I need to either get the permanent method to work or not shut my computer down or . . . . Avid could get the Driver signed and approved by Windows 10 and that will fix the issue for good but . . .  Whew, I now have control of my console.

Thanks to all you guys, the guys at Avid and also the guys at Sweetwater.  My wife has put the gun away that she was about to  use to shoot me over this expensive upgrade that was going south for the past 16 days. 

I will update this thread as I get the final fix in place. Thanks Again. 

---

@gary_keslingwrote:

 

1. I found that my new PC had not been "verified" with Microsoft yet. Not sure why that mattered but I stumbled across this and I had Microsoft text me a code that I entered and verified who I was on this PC.

2. After that was done, It allowed me to run certain functions or commands as Admin that it wouldn't allow before.

3. This time, on Setup of Peripherals, it scanned for devices and found both my Bluetooth network and my hardwired Ethernet. I chose the Ethernet and it found my C24. I chose it and it connected to it. . .  Whew, I now have control of my console.

4. Avid could get the Driver signed and approved by Windows 10 and that will fix the issue for good but .

5. Thanks to all you guys,

---

1. I've never heard of that. The only thing remotely close to that is that your copy of Windows-10 must be Activated. That should have already been the case.

2. When you setup Windows as the first user, your User should have been granted Administrator privileges.  

3. That is good news.

4. Right. Like every other company on the planet, selling hardware designed to run on Windows-10 64bit.

5. You are welcome.

Yes, keep us updated.

Method 2 is temporary but proved what Sweetwater said about the unsigned driver appears to be the problem.  Method 1 is a "permanent" solution but I wouldn't want to use that permanently.  Maybe use it, in your case, until AVID issues a signed driver and then go back to the Windows default.  Its a "safety" item so you don't want to permanently run with it disabled.

Thanks for the Kudos, too.  

The C24 is not a Dell Product and NOT supported here.

There are too many numerous problems with windows 10 and pro tools.

• Windows 10 requires Pro Tools 12.5.
• Please see Pro Tools 12 System Requirements
• and Pro Tools HD 12 System Requirements for full details.
• Pro Tools | First is not supported

http://avid.force.com/pkb/articles/en_US/compatibility/Windows-10-OS-Support-for-Avid-Products

Pro tools is also not supported here.

http://www.avid.com/products/C24

The version of pro tools is also not trivial

Windows non 10 computer running Pro Tools 9 or higher software

There is NO UPGRADE PATH from 9 to 12.

 Pro Tools 9 Frequently Asked Questions

• Pro Tools Updates and Pro Tools CS Updates

Pro Tools 9 software upgrade requires both of the following:
Your Pro ToolSCore card serial number
Your Pro Tools 7 or 8 iLok license (Earlier versions do not qualify)

Update! first, thanks to all that helped. I was able to use the c24 after disabling driver enforcement but never could get the Secure boot disabled. It would loop through a re-boot, over and over.  But I was content to run sessions with the work around and then . . . .

I did 9 successful days of recording with the work around and on the 10th day, I'd get the BSOD each time I launched Pro Tools at the step where it "initializes" the hardware. I talked to Sweetwater Tech support and Avid and they felt the HDX card had failed and sent me a new one. That did not fix the problem. I am very confused as to why the system worked from the beginning with out the C24 and then 9 days with it working and then began crashing. I disconnected every single USB device and all other devices, trying to find the problem. I even reset the pc to it's factory settings, since it worked when right out of the box.  I am stumped. I have techs from Avid and Sweetwater working on it.  I had asked Dell about returning the machine, if it is never going to work with Pro tools but they said I have had it too long and I understand that but I had to wait 7 extra weeks to get the hardware from Sweetwater, after being told it would take 2 weeks and then worked on getting the "bugs" out for another month. Then had it work great for 9 days. Seems like if it worked for those 9 days, I should be able to find what changed and get it back up and running and this is killing my business. I planned on a week or so of down time to make the upgrade but now it has been over 2 months with a small 9 day window of success.

Very bummed but not giving up.

---

@gary_keslingwrote:

I even reset the pc to it's factory settings,

---

That seems extreme for something that just "quit working". Did someone advise you to do that?

And finally, how exactly did you do it, and what steps did you take to get the machine's OS, drivers, and software rebuilt back up?

Are you still using the StarTech-NIC? If so, is the on-board Killer-Networking NIC still disabled?

According to your posts, it was never a fault of the Area51-R5 in the first-place, so not sure why you inquired about returning it.