Page 1 of 2
Connecting to windows 11
Posted: Sun Jun 08, 2025 3:21 pm
by Asho88
Hi all I have installed an NVRAM and comms board into my 808 ecu and I'm having dramas getting my PC running windows 11 and my sons running windows 10 to connect really annoying. It's lighting up so connecting ok issues seems to be on the PC anyone had this issue before and able to help out? cheers
Re: Connecting to windows 11
Posted: Sun Jun 08, 2025 4:20 pm
by antus
You need to tell us more detail, there isnt enough to help you there. Windows 10 and 11 are both fine. Are you using tunerpro? with oseplugin? how have you set it up? what com port have you selected? can you see the comport as expected? (last question might answer this too). Have you tried delco ose flash tool? Can it connect? If you cant connect, where in the process are you getting the error? What is the error? If you get as far as 'connecting...' in tunerpro do you see blinking lights on the ecm comms board?
Re: Connecting to windows 11
Posted: Sun Jun 08, 2025 4:25 pm
by Asho88
Hey mate I’m the one that was inboxing you last night and this morning. Yeah trying to use tuner pro. I honestly have no idea what oseplugin is

as I said in the inbox it’s picking it up but with an error so I have no access to it.
Re: Connecting to windows 11
Posted: Sun Jun 08, 2025 4:28 pm
by Asho88
Re: Connecting to windows 11
Posted: Sun Jun 08, 2025 4:30 pm
by Asho88
That’s the error and it shows up in “other devices” but can’t do anything with it. From what I understand it’s in read only will that stop me from viewing what’s on it or is that just to say you can’t make changes?
Re: Connecting to windows 11
Posted: Sun Jun 08, 2025 6:36 pm
by antus
I cant see the error as it looks like you didn't upload the image for that one.
There is a frequently asked questions section here with lots to read about getting started, various tools and terms and some videos that I think will help you understand a bit more about the ecosystem.
viewtopic.php?f=7&t=1396
That error "device descriptor request failed" is a USB error, before it even gets as far as the drivers. That isn't normal and I don't know why that would be happening on your PC. Device descriptor is where the PC asks it for ID numbers which it uses to ID the chip, and download the drivers. Thats a normal USB thing and should succeed as soon as you plug it in then it'd go to the net and get drivers automatically. So it would seem there is something else specific going on here but I have not seen that exact error before. Do both PCs say the same thing?
Re: Connecting to windows 11
Posted: Sun Jun 08, 2025 7:02 pm
by Asho88
Yeah I have seen that unfortunately I struggle to take in a lot of info by reading kinda goes in then straight out. But I’ll have a look and see if I can make sense of it.
Yeah makes sense usually I’d do as you said and auto update or google it and sort it pretty quick but this has been bugging me all day. Yeah they’re pretty much the same slightly different as one is windows 10 the other is windows 11. Cheers
Re: Connecting to windows 11
Posted: Sun Jun 08, 2025 7:33 pm
by antus
Try unplugging any other usb devices, try different usb ports. Those intel drivers and some other usb serial device looks different to what im used to. It might be to do with that or the port not working properly.
Re: Connecting to windows 11
Posted: Sun Jun 08, 2025 7:49 pm
by Asho88
Yeah I tried that it has 3 usb ports tried all 3 there’s nothing else plugged in. I looked at the windows 10 pc and it said there were no drivers available so I might play with a bit more a mate suggest some drivers to download didn’t work on windows 11 pc but maybe might on the windows 10 pc.
Re: Connecting to windows 11
Posted: Sun Jun 08, 2025 7:59 pm
by antus
ftdi ft232rl vcp drivers... should auto install from microsoft though.