SumAussieCobber Posted July 27, 2017 Share Posted July 27, 2017 I just updated and now my macros for my scimitar not working at all.. I have a screen shot and i have tried repair and full reinstall and nothing.... I have tried older ones and still nothing and now my profiles wont load they just stay the spiral one.... http://imgur.com/tkTsiFU What can i do as i need them for my game i play as its to hard hitting keys miles away that is why i bought this mouse.. Not happy at to be honest!! Really and now i cant even get my Star Wars Boba Fett to work..... No profile will work... Just the ones you have in drop down bar! Link to comment Share on other sites More sharing options...
Corsair Employees Corsair James Posted July 28, 2017 Corsair Employees Share Posted July 28, 2017 Check your device manager and see if the Corsair virtual input driver has an error. If it is, its most likely Code 52 and you need to update your Windows with a patch. Link: https://technet.microsoft.com/en-us/library/security/3033929.aspx Link to comment Share on other sites More sharing options...
SumAussieCobber Posted July 28, 2017 Author Share Posted July 28, 2017 Corsair virtual input driver isn't anywhere in device manager and windows 10 is up to date. Link to comment Share on other sites More sharing options...
Toasted Posted July 29, 2017 Share Posted July 29, 2017 Try reinstalling the driver. You can find it in the driver/hid folder. C:\Program Files (x86)\Corsair\Corsair Utility Engine\driver\hid Right click CorsairVHidDriver.inf > Install and see whether that helps. Link to comment Share on other sites More sharing options...
SumAussieCobber Posted July 30, 2017 Author Share Posted July 30, 2017 Try reinstalling the driver. You can find it in the driver/hid folder. Right click CorsairVHidDriver.inf > Install and see whether that helps. Nope didn't work thanks though Link to comment Share on other sites More sharing options...
Comet 1626864951 Posted July 30, 2017 Share Posted July 30, 2017 Try reinstalling the driver. You can find it in the driver/hid folder. Right click CorsairVHidDriver.inf > Install and see whether that helps. It didn't help, even though the installation said it was successful. Link to comment Share on other sites More sharing options...
SumAussieCobber Posted July 30, 2017 Author Share Posted July 30, 2017 It didn't help' date=' even though the installation said it was successful.[/quote'] Yeah first time i tried said successful then i tried going back to 2.14.67 then failed now back at 2.15 and successful again Link to comment Share on other sites More sharing options...
Comet 1626864951 Posted July 30, 2017 Share Posted July 30, 2017 Check your device manager and see if the Corsair virtual input driver has an error. If it is, its most likely Code 52 and you need to update your Windows with a patch. Link: https://technet.microsoft.com/en-us/library/security/3033929.aspx Microsoft Security Advisory 3033929 Availability of SHA-2 Code Signing Support for Windows 7 and Windows Server 2008 R2 Published: March 10, 2015Version: 1.0 This security advisory does not appear to be for any issue on Windows 10. Link to comment Share on other sites More sharing options...
Toasted Posted July 30, 2017 Share Posted July 30, 2017 Try this temporary "fix" from another user who has the same issue. http://forum.corsair.com/v3/showthread.php?t=155288 Link to comment Share on other sites More sharing options...
SumAussieCobber Posted July 30, 2017 Author Share Posted July 30, 2017 Try this temporary "fix" from another user who has the same issue. http://forum.corsair.com/v3/showthread.php?t=155288 tried that it never comes up and i am running windows 10 Link to comment Share on other sites More sharing options...
SumAussieCobber Posted July 31, 2017 Author Share Posted July 31, 2017 Ok so i did a system restore for over 3 weeks ago and everything back to normal but i cant use any profiles or the macro's stop working... Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.