Hey guys, I've searched the forums here and didn't find anyone else having my specific problem so I'm sorry if it's been posted already!

I have a v2 accessport for my 2006 AT. I've been using it with a windows 7 PC and have had no issues. Got a new laptop running Windows 8.1, installed the same version of AP Manager, plugged in the AP, and got an error message stating the firmware of the AP wasn't updated enough to be compatible with Windows 8.1, and would have to be updated on an older PC. So, plugged my AP back into my old laptop, tried to update it, and it tells me that my current version is the most updated version! Not sure what to do here, need help!

Current AP firmware is v1.6.1.1-13820, running AP Manager 2.1.1.8 on both PCs.

 

Our AP does not work with windows 8.1. It's a connection issue and Cobb no longer supports the rx8, so they will not update the firmware. Windows 8 works, but not 8.1.

 

Oh crap.
My new laptop is 8.1

Glad I've still got an old Windoze 7 desktop PC around ... humphf

 

No love here.
I went and installed the latest AP Software from Cobb Tuning on my new Win8.1 laptop

AP would not connect. Failed with following message.


So off to my Win 7 box --- plug in, fire up AP Manager, get updates including setting the option for beta updates. Everything good.

Plug in to my Win 8.1 laptop and fail.

I even tried the compatibility modes and running as Admin

 

Exactly what happened to me wcs....... Oh well

 

Hmmm, maybe my firmware was never updated. I guess I won't mess with it,

 

You suck 9k! Lol

 

sorry, gonna call BS ...

ATR is fine, AP Manager cannot find/communicate with the hand-held device on W8.1+ OS


.

 

Well, I guess I better check and make sure the last time I transferred a tune 8.1 was installed but I am pretty sure it was. I will check when I get home.

 

should only work on 8.1+ if you have virtual machine running an earlier Windows OS since there never was a firmware update for our AP devices to make them 8.1 compatibile

 

I may have it running in compatibility mode.

 

That doesn't work. The issue is the hand-held AP firmware .... but don't be afraid to correct my noobish ways if you mastered it somehow ....


.

 

<waits intently for 9k to skool us>

Hope you've figured out a work around Scott.

 

forgot all about it damn it.

 

I figured this went the same way as the aluminum exhaust thread ....

 

Damn you guys are right. I opened AP manager and immediately got an option to update and after the update I just get this, it never changes and no matter how I run it, it doesn't work. I waited a while to go from 8.0 to 8.1 and I guess Steve and I have not done a tune change since I was on 8.1. Time to reformat my laptop and go Windows 7 for tuning duties.

 

Thanks 9k

I was hoping you had found a work-around whether it was by accident or on purpose.

I'll try it today using a VM of Windoze 7 ... it should work.

VM Player is free and if I can find a free to use copy of Windoze maybe easier than a reformat and install. Then all the dreaded updates.

 

Hmm, I am pretty sure I have some Windows 7 discs laying around, I will check out VM player. but I also have an extra laptop I don't use, might as well install it on that. Thanks.

 

Probably the signature on the driver. I've had that issue on friends computers running old hardware. The OS is capable of loading the driver it just refuses because the driver is unsigned or an old signature. Here is a workaround that might do the trick:
How to Disable Driver Signature Verification on 64-Bit Windows 8.1 (So That You Can Install Unsigned Drivers)

Sorry if this isn't the problem, I'm completely speculating because I won't let windows 8 anywhere near my machines.

 

Tried it, no go. Thank for the tip though.

 

His theory doesn't account for it being a firmware issue in the handheld device.

 

If the firmware works on one OS but not another then it is a driver issue. Either the OS isn't loading the driver properly, or it isn't letting the driver do something required to function. If it was firmware it wouldn't work regardless of the OS. Windows 8 is having a lot of these issues with older hardware. New firmware might be able to work around this issue (with a new driver as well) but that's a bandaid around Microsoft imposed incompatibility.

 

Just checked some Subie forums. New firmware does solve the problem with them. So it's probably some sort of low level access that window 8 won't allow. Probably used to verify the AP is what it claims to be (or for the AP to verify the computer is what it claims to be). Wouldn't want people to be able to unmarry their AP from their PC after all...

Edit straight from the horses mouth, it's a windows issue:
"In Windows 8.1, Microsoft changed how the drivers communicate with programs. Therefore, older Accessports must be updated on a non 8.1 computer before being able to communicate with Windows 8.1"
https://cobbtuning.zendesk.com/hc/en...ws-8-1-Support

 

Yes, but Cobb is not motivated to update the firmware for discontinued devices. Therefore it only works in a pre-W8.1 environment.

theories always look great when you don't understand that the basis of your assumptions are all wrong ...

 

You miss the point again. This is a Microsoft imposed restriction on hardware causing incompatibility, nothing more. There are probably a few people with similar hardware problems and some of them may have found a solution. Saying "it's just incompatible" and waiting for an update that will never happen is silly.