This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
For the past few days when I load my PC up, a pop-up will appear saying "a driver cannot load on this device". I have done countless things like updating my PC seeing if that works, uninstalling those updates, trying to relocate the file in C:\Windows\System32\drivers which doesn't show at all and going through troubleshooting. None of these things have been able to work and the error still pops up. Please could I have help on what to do I have have hit a dead end on what to do. The error is shown on the top.
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
I have been using this driver for 3+ years. Why is it suddenly a problem after a highly problematic Windows update that currently has me on my knees for multiple reasons? Why is this particular driver suddenly a problem, after 3+ years of usage?!!? And, don't give me the non-answer response that is 99% the case on this Microsoft Community. Either answer my question or move on.
Thanks Rick - a much more effective and simpler quick fix than the BS being put around and I get to keep using the RGB driver.
Much appreciated
So really the solution is to get your RGB software updated.
Hm .... which mine is, and I still get the error.
Using ASUS ROG stuff myself.
hi ppl with same error as myself. Did you find a solution to the ene.sys driver?
And the most annoying thing is that it was not possible to set the windows update back to the last working version!!!!
renaming it is virtually removing the risk - if the ene.sys driver is operating as a driver, it is a vulnerability risk. Of course, renaming it doesn't help your RGB software work properly either. Proper way is an updated, signed version of the driver. If you need it, you can turn off driver blocking in settings, but it won't help if a particularly vulnerable driver update happens.
