#Logitech f710 windows 10 64 bit driver install#

#Logitech f710 windows 10 64 bit driver install#

After some effort, not only does my controller refuse to install correctly, it now displays it in Device Manager as 'Logitech Cordless RumblePad 2' when on D_Input selection and Xbox controller when on X_Input (please note: on this selection before it Now however, using the exact same software package 'lgs510_ењ†4', initial installation resulted it in being displayed as Logitech F710 but had the little yellow triangle on it, not functioning well and the drivers not migrated listed in events under the properties Installing onto a new motherboard!), erasing all data on my hard-drives using zero-fill software as per each HDD manufacturers specs prior to the re-installation ensuring a totally clean install. My Motherboard failed within that period, so I had to do a complete fresh install of Windows 10 (as you should do when Manager it displayed as 'Logitech F710', no migration issues, functioned on D_Input but not X_Input.ДЇrom my understanding somewhere between version 1709 and the next Windows 10 revision version 1803 (April 2018 Update) that all changed. By fine, I mean install all applicable drivers using the Logitech installation package 'lgs510_ењ†4' and when viewed in Device My Logitech F710 game controller used to work fine and install as normal before Windows 10 version 1709 (Fall Creators Update). That and I've worked a lot of hours.ДЄll other questions regarding this aren't really answering the question, why will the drivers not truly migrate and forcing it to become an Xbox controller why is that? I would have asked this sooner, but I do like to entertain and exhaust all 'fixes' first before asking for help. It seems the enforced driver signing has become militant.