@Gigi20 is normal that i made some test to try to solve the problems before I understand that it’s normal to test when it didn’t work, but you need to understand that neither I nor anyone else on the forum is seeing what you’re doing, it’s not obvious that you modified it, because I don’t know what your level of knowledge is, because I don’t I know you and you didn't make that clear. Please understand that you need to make everything you did completely clear, when you say that you have not modified anything (totally clean), and in fact you have modified something (either for testing or whatever), you are interfering with the result , and who loses is you! so I tried the manual setup connection you suggested but without success! You once again did not make it clear: What exactly did you try? What commands did you use? What are the results of the commands? What errors were returned? I repeat: what seems obvious to you, is not obvious to anyone who is trying to help you on the forum. I can cite as an example a user who (with knowledge) was facing difficulties in an advanced configuration, which, it was OBVIOUS that he knew how to do, but, he missed a character in a command, and the error was so simple and so OBVIOUS , but he didn't see it. That's why for you to get help, you need to describe every detail, even if it seems obvious: it is often insignificant details that affect the result drastically. Now if there is not a software bug... I'll buy a new controller Without the information above, I cannot say whether you did the procedure correctly or if there is still something you can do, so I am not sure it is a driver incompatibility. I would not classify it as a bug, but "incompatibility", in case it doesn't really work.