1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

UOSteam Intel ICD OpenGL Driver Error

Discussion in 'Guides' started by parsnip, May 21, 2017.

  1. HibbiGibbi

    HibbiGibbi New Member

    3
    4
    3
    Jul 23, 2017
    Hello everyone, I'm back again.

    So last night (November 15, 2017) my computer downloaded a windows update....."Windows 10 Fall Creators Update". I thought to myself at the time "This better not screw up my openGL Driver thing again!"

    Guess what? It did.

    However, armed with the knowledge of my 8 month journey before- I went strait to the culprit.

    It appears my overwritten entry for the folder "0001" was reverted back to say the false location again- so I yet again manually changed it following the instructions from the guide posted above. Restarted my computer and received the same error message.

    So I went back into regedit and this time looked into the "0002" folder and changed those values to mirror those in the "0001" folder and restarted my computer. It fixed it!

    So I'm back up and running again- but thought I'd post a little update for anyone who may stumble upon this at a future date.

    Regedit After.png
     
    parsnip likes this.
  2. iDzk

    iDzk Member

    8
    1
    3
    Mar 15, 2016
    High Troika
    The first solution didn't work for me aswell, but i did as @HibbiGibbi said, and edited my 0001 folder aswell, copying the steps from the 0000 folder, and it worked! :)
     
    parsnip likes this.
  3. Iniak

    Iniak Member

    22
    27
    13
    Oct 17, 2017
    Iniak
    Downloading the updated Intel driver and then installing it via the Update Driver fixed this problem for me too. Thank you to everyone who spent time figuring out the different fixes for people.
     
  4. TwistedSix

    TwistedSix Well-Known Member

    75
    9
    8
    Dec 11, 2013
    upload_2018-9-12_17-40-25.png

    Just ran into this issue... Tried the method outlined in the thread without any success. Updated the driver through the Device Manager and everything works well now.
     

Share This Page