Logitech F710 Software & Drivers Download, Manual, Setup Guide for Windows & Mac OS – Logitech F710 Wireless Gamepad Software practically started gamepads for the COMPUTER.Nowadays we have complete compatibility with the Xbox360 gamepad which’s what most video games focus on. Install the Logitech F710 Gamepad within Windows 7 & 8. Posted on October 31, 2013 January 29, 2015 by Matt I’m posting this is because every time I wipe my PC, I have a nightmare figuring out how to re-install my beloved Logitech F710. May 14, 2016 In this video I will show you hot to get your Logitech F710 Controller to work! To record my video's I use a program called ACTION! I like it and it's easy to use. My new Discord server! Play console ports with their native-style controller or adopt a more relaxed position while enjoying PC games. F710 is easy to set up and use with your favorite games thanks to XInput/DirectInput—the two most common input standards.
It seems the enforced driver signing has become militant.
I would have asked this sooner, but I do like to entertain and exhaust all 'fixes' first before asking for help. That and I've worked a lot of hours.
All 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?
My Logitech F710 game controller used to work fine and install as normal before Windows 10 version 1709 (Fall Creators Update). By fine, I mean install all applicable drivers using the Logitech installation package 'lgs510_x64' and when viewed in Device Manager it displayed as 'Logitech F710', no migration issues, functioned on D_Input but not X_Input.
From my understanding somewhere between version 1709 and the next Windows 10 revision; version 1803 (April 2018 Update) that all changed. My Motherboard failed within that period, so I had to do a complete fresh install of Windows 10 (as you should do when 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.
Now however, using the exact same software package 'lgs510_x64', 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 tab. 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 would disconnect from the PC), the drivers appear to be installed and working at this point. Device Manager now reports this device is working properly, but when you delve deeper it really isn't. The driver package hasn't migrated at all as listed under the events tab in properties. Also to note under the Details tab listed property No install class = <true>
Device HIDVID_046D&PID_C2196&265274ac&3&0000 was not migrated due to partial or ambiguous match.
Last Device Instance Id: HIDVID_05A4&PID_9860&MI_01&Col028&1396a20&0&0001
Class Guid: {745A17A0-74D3-11D0-B6FE-00A0C90F57DA}
Location Path:
Migration Rank: 0xF000FC00FFFFF102
Present: false
Status: 0xC0000451
After much web searching I came across the fact the Enforced Driver Signing will be potentially blocking the installation of these drivers, which I really believe to be true now. No matter what I do I cannot get the current driver package to install correctly and never migrates.
Things I've tried:
1: Updating via the update driver tab in properties, full auto mode and manually searching.
2: Uninstall and reinstall of driver package plus reboot.
3: Download the driver package again and tried steps 1 -3 several times (definition of insanity)
4: Disabling enforced driver signing via the F7 Recovery troubleshooting option upon restart, it does nothing.
5: Disabling enforced driver signing in the actual elevated administrators account(why is this even a thing) using an elevated command prompt 'BCDEDIT /set nointegritychecks ON' , it always states the operation has completed successfully, it does nothing.
How do I fix this?
How do I migrate the drivers that existed before and are now installed along side with the software package, and get Windows 10 to actually use them?
Then there's my internal card reader...