Retroarch: retroarch.exe stopped working (intel HD 3000)

[eMSX]

Hello guys, i am having trouble with the latest version of Retroarch.

Retroarch 1.4.1 crashes directly when opened.
Error message retroarch.exe stopped working.

Version 1.3.6 runs fine and reconizes the HD 3000 graphics drivers.
When i run 1.4.1 it crashes immediatly

I am running Windows 10 home 64 bit.
I have tested both the 32bit and the 64 bit versions, makes no difference.
I am running it local, not using RDP.

The hardware is an Acer W700 tablet running Windows 10 home 1607 with all updates

Intel(R) Core(TM) i3-2375M CPU @ 1.50GHz
Intel HD Graphics 3000
Driver version 10.17.10.4229
Also tested with version 9.17.10.4229 same issue

Here is the debug log.

Intel(R) Core(TM) i3-2375M CPU @ 1.50GHz
RetroArch [INFO] :: This is RetroArch version 1.4.1 (Git ba98ecd)
RetroArch [INFO] :: === Build =======================================
Capabilities: MMX MMXEXT SSE1 SSE2 SSE3 SSSE3 SSE4 SSE4.2 AVX
Built: Feb 2 2017
RetroArch [INFO] :: Version: 1.4.1
RetroArch [INFO] :: Git: ba98ecd
RetroArch [INFO] :: =================================================
RetroArch [INFO] :: Loading default config.
RetroArch [INFO] :: Environ SET_PIXEL_FORMAT: RGB565.
RetroArch [INFO] :: Redirecting save file to "C:\emulation\retro arch 1.41\saves.srm".
RetroArch [INFO] :: Redirecting savestate to "C:\emulation\retro arch 1.41\states.state".
RetroArch [INFO] :: Version of libretro API: 1
RetroArch [INFO] :: Compiled against API: 1
RetroArch [INFO] :: Set audio input rate to: 29970.03 Hz.
RetroArch [INFO] :: Video @ 960x720
RetroArch [INFO] :: Found GL context: wgl
RetroArch [INFO] :: Detecting screen resolution 1920x1080.
RetroArch [ERROR] :: [WGL]: wglCreateContextAttribsARB not supported.
RetroArch [INFO] :: [GL]: Vendor: Microsoft Corporation, Renderer: GDI Generic.
RetroArch [INFO] :: [GL]: Version: 1.1.0.

Here is the log of the working 1.3.6 on the same system.

RetroArch [INFO] :: === Build =======================================
Capabilities: MMX MMXEXT SSE1 SSE2 SSE3 SSSE3 SSE4 SSE4.2 AVX
Built: Aug 4 2016
RetroArch [INFO] :: Version: 1.3.6
RetroArch [INFO] :: Git: 62281f8
RetroArch [INFO] :: =================================================
RetroArch [INFO] :: Config: loading config from: C:\emulation\retro arch 1.36\retroarch.cfg.
RetroArch [INFO] :: Resetting undo buffers.
RetroArch [INFO] :: Environ SET_PIXEL_FORMAT: RGB565.
RetroArch [INFO] :: Version of libretro API: 1
RetroArch [INFO] :: Compiled against API: 1
RetroArch [INFO] :: Set audio input rate to: 29975.00 Hz.
RetroArch [INFO] :: Found shader "C:\emulation\retro arch 1.36\shaders\retroarch.cgp"
RetroArch [INFO] :: Found shader "C:\emulation\retro arch 1.36\shaders\retroarch.glslp"
RetroArch [INFO] :: Video @ 960x720
RetroArch [INFO] :: Found GL context: wgl
RetroArch [INFO] :: Detecting screen resolution 1920x1080.
RetroArch [INFO] :: [WGL]: wglSwapInterval(1)
RetroArch [INFO] :: [GL]: Vendor: Intel, Renderer: Intel(R) HD Graphics 3000.
RetroArch [INFO] :: [GL]: Version: 3.1.0 - Build 9.17.10.4229.
RetroArch [INFO] :: Querying GL extension: ARB_ES2_compatibility => doesn't exist
RetroArch [INFO] :: Querying GL extension: ARB_sync => exists
RetroArch [INFO] :: Querying GL extension: ARB_texture_float => exists
RetroArch [INFO] :: Querying GL extension: EXT_texture_sRGB => exists
RetroArch [INFO] :: Querying GL extension: ARB_framebuffer_sRGB => exists
RetroArch [INFO] :: [GL]: Supported extensions:

If more info is required i am happy to help.

---

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

[twinaphex]

I think the problem is on your end -

"RetroArch [INFO] :: [GL]: Vendor: Microsoft Corporation, Renderer: GDI Generic.
RetroArch [INFO] :: [GL]: Version: 1.1.0."

If it shows that then it means it can't find a REAL GL driver on your system and it instead resorts to a Microsoft-provided software rendered implementation of OpenGL, which utterly sucks. Don't even bother trying to use it since it will suck majorly, and find valid video drivers instead so that you can get a real GL driver for Windows.

[Brawl345]

Can confirm, have the same problem with Intel HD Graphics 3000. v1.3.6 works fine. I dunno how to get logs, retroarch_debug.exe also crashes on start (and I can't find any log files?). Setting
menu_driver = "rgui" in retroarch.cfg fixes it and uses the older GUI. My drivers are up-to-date and I'm on Windows 10 Pro 1607 64 bit.

[ghost]

i can guess 2 reasons:

1. hd graphics 3000(sandy bridge) do not have official windows 10 drivers
2. retroarch 1.4.1 seems to have increase gl-feature requirements, #2 may
   have only installed basic dx drivers but not full gl.

On Wed, Feb 8, 2017 at 12:55 AM, Andreas Bielawski <[email protected]

wrote:

Can confirm, have the same problem with Intel HD Graphics 3000. v1.3.6
works fine. I dunno how to get logs, retroarch_debug.exe also crashes on
start (and I can't find any log files?). Setting
menu_driver = "rgui" in retroarch.cfg fixes it and uses the older GUI. My
drivers are up-to-date and I'm on Windows 10 Pro 1607 64 bit.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/libretro/RetroArch/issues/4580#issuecomment-278063313,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AWPDtiKYyJC75lBCoALbhhCtDUI3bDBQks5raKICgaJpZM4L4nf2
.

[eMSX]

I have also tried it on my Laptop an Acer V571G (also featuring a Sandy bridge cpu with GMA 300 HD. When i disable the Nvidia GPU it is giving the same error als the tablet.

It is failing the reconize the Intel 3000 adapter.
The drivers are the ones installed by Windows 10 by default.
9.17.10.4229 on Windows 10 home 1607

Here 1.3.6 also works fine on the intergrated gpu.

[gouchi]

You may try the latest driver version 9.17.10.4459 available for Win10.

Source

[eMSX]

I have installed that driver but Retro Arch still crashes directly when started.

[Mohamed28]

I also did the installation and stillI have same issue.

[gouchi]

Can you try to install Win8 driver ?
Thank you.

[Mohamed28]

Man, install newer driver, older driver it's all same. This error persist.

[Mohamed28]

@loganmc10 There's anything I cany do? I am sorry, I am just a noob.

[bparker06]

Can someone with an affected system try this MSVC build and see if it works any different?

From the previous log, the line:

RetroArch [ERROR] :: [WGL]: wglCreateContextAttribsARB not supported.

is very peculiar since 1.3.6 also uses this function and it appears to work fine there. The entire reason for the crash is due to the failure to look up the pointer to that function in the OpenGL library. Since an OpenGL context cannot be created with the missing function, any further attempts to call a GL function will crash.

At first I would have also suspected a system driver issue, but I don't think this can be if 1.3.6 works.

[Mohamed28]

@bparker06, thank man, it does works but doesn't load any core and any game.

[bparker06]

Then I suspect the issue may be related to some GL code that gets compiled on msys2 builds that doesn't on msvc, like glslang or something.

[twinaphex]

You'll have to start bisecting.

loganmc10 pushed through some extensions in RA that enable certain graphic features but this apparently was not properly tested against most common hardware as we can already see certain iGPUs no longer working on Windows.

[bparker06]

@Mohamed28 The build I linked you to is 32-bit, so it will only load 32-bit cores.

Can you also try the 32-bit version of the current msys2 build and see if that works?

Until someone with the same/similar hardware, and the knowledge, time and patience to be able to bisect this comes forward, I don't think a whole lot of progress can be made, simply because we cannot reproduce it elsewhere.

[sm199]

@bparker06 version 1.4.1 x86 working fine...thnx man...
I tried latest nightly but with same error...

[bparker06]

@sm199 Were you trying an x86 nightly or was it an x86_64 one that didn't work? Trying to narrow down exactly what versions work and what doesn't.

[sm199]

@bparker06 i tried both versions...recently downloaded both versions but they are not working...

[bparker06]

So neither nightly works, and 1.4.1 x86 works, what about 1.4.1 x64? And have you tried the MSVC build I linked to? That one is more recent than 1.4.1 as well.

[sm199]

I tried your MSVC build so x86 version worked...before it was not working...
x64 build not working...xmb menu successfully opened but no cores are working because that exe belongs to x86...

[sm199]

Sorry for bad english...

[bparker06]

I found a machine here with an hd3000 and tried it myself, and it is working here: https://i.imgur.com/YdBYAZe.png

This is the latest 64-bit nightly also. Driver version is 9.17.10.2932 on Windows 7 with i7-2600k.

[sm199]

I don't know mine is intel hd 3000 or not...how to check it...???

[sm199]

I tried both latest nightly builds on windows 10 64 bit...with latest video driver installed...

[bparker06]

@sm199 Right click on the desktop -> Display settings -> Advanced display settings -> Display adapter properties

[sm199]

Okk i will check it and post screenshot here...

[Mohamed28]

@bparker06 I tested here, version 86x with your file works fine, the cores and games also worked. I used the yabause_libretro.dll to do the test.

[bparker06]

@Mohamed28 Are you saying the 32-bit MSVC build works or the 32-bit msys2 one works? And have you tried both?

[eMSX]

I have also being testing. the 32 bit MSVC works perfect, the 32 bit msys2 gives the same eror.
Also the nightlys of 10-2 are giving the same error.

[sm199]

@bparker06 It is not showing anything about 3000.it is showing intel hd graphics only....u can see screenshot here...
http://imgur.com/a/ivFe6

[hizzlekizzle]

@sm199
HD3000 was the built-in IGP for the Sandy Bridge line of i-series CPUs. If you can look up what series your CPU came from, that should tell you.

[Mohamed28]

@bparker06 Yes man, actually I tried your file in both x86 and x86_64 in both it makes the GL works, but only in x86 runs cores and games.

[sm199]

@Mohamed28 did you try 32 bit msys2...???

[Mohamed28]

@sm199 Yes, I did sir, it's working. I did as @bparker06 has requested.

[sm199]

U mean u tried latest nightly not v1.4.1,right...???

[Mohamed28]

@sm199 Yes, sir. The latest nightly from yesterday.

[sm199]

Okk now nightly is working fine for you but i am having the same error...only MSVC 32 bit build working fine... :(

[bparker06]

I have an automatic msvc build setup here:

https://s3.amazonaws.com/retroarch/RetroArch-x86-msvc2005.exe

Works on all Windows versions from 98 and up.

It rebuilds every hour if there's any code changes on the master branch. At least it is something until we can figure out what's going on with the msys2 builds.

[sm199]

Thanks @bparker06 but how to use it...??? Should i have to copy this in current nightly build...???

[bparker06]

You can run the exe by itself anywhere, or you can put it in an existing folder that you had from a nightly, sure.

[sm199]

So you mean all the nightly buids will work now...??? :D

[sm199]

And will i have to download it everytime when i will download latest nightly or upcoming stable build till it fixes...and thank you so much @bparker06 ...

[bparker06]

I don't quite follow what you're saying but, whenever you want a newer build you can just re-download that same exe, and keep it in the same folder, overwriting the old one. You don't have to re-download any actual nightly stuff from the buildbot, just my exe.

[fr500]

@eMSX can you just build from source?
it takes a while, and bisecting is a PITA I know, but it's the only way to get to the bottom of it.
Build guide
https://bot.libretro.com/docs/compilation/windows/

Once you can build you have to bisect
https://git-scm.com/docs/git-bisect

[eMSX]

I'm able to complile retroach, but i am experiencing some black blocks in front of the menu's.

The bisecting doesn't go according to plan.

I am receiving some errors:

$ git bisect bad
': is geen geldige naam: regel 88: export: 'dashless
Bisecting: 2949 revisions left to test after this (roughly 12 steps)
error: Your local changes to the following files would be overwritten by checkout:

but even if i say bisetct bad, is doesn't give me less revisions te test.

[bparker06]

That error is telling you that you have modified the source of the current commit you're on, so the bisect will not continue until you remove those changes.

[eMSX]

I have been bisecting till there isn't a single version left to test, with no luck, it still crashes directly after loading, while on my nvidia machine's it runs without issue. Even the 1.3.5 which i build crashes.

$ git bisect bad
7191465dcb038ce77991238a24e01bc91901cbfe is the first bad commit
commit 7191465dcb038ce77991238a24e01bc91901cbfe
Author: Mikael Brunnhede [e-mail]
Date: Sun Jul 17 12:15:44 2016 +0200

Fix bug in calculation of blocksize for savestates.

:040000 040000 0f8cef8d38a74224f54e36cbc31f971bab36059c e923966015f4721398342eea3f536d7901ff9fc6 M managers

Has there been a change in the way retroarch is compiled since 1.3.6 ?

Please note that i am by no means a programmer, just a guy who read the above tutorials to compile his first program since "the game of life" in turbo pascal at school.

[bparker06]

@eMSX If the bisect is done correctly then the commit right before "the first bad" one should work. Can you confirm this?

[bparker06]

Also, how is it that you narrowed done a commit from July if 1.3.5 crashes too?

[Nickelbawker]

I have a intel3000-Windows10ProX64, with the issue here. Let me know if I can help test whatever is wrong. I changed video driver = d3d in the cfg and it doesn't have any graphics like PSP's XMB but the program opens up. It plays VBA-M games just fine the GUI is fairly non-existent or not pretty in d3d mode though.

The .4229 is the latest driver from intel direct, what ever is on microsofts site isn't officially supported for my i5-2520m. I tried the newer one above with no luck the installer prompts to allow, then quits itself realizing that my version is the MS approved one.

[bparker06]

This is a confirmed issue only on Windows 10. Other OpenGL programs besides RetroArch are having similar problems.
https://bugreports.qt.io/browse/QTBUG-42240

[sm199]

@bparker06 someone posted this WTFI.exe in retroarch forums.
https://github.com/alexey-lysiuk/tools/raw/master/wtfi/Release/wtfi.exe
It removes the Windows10 supportedOS GUID line from the xml manifest and now v1.5.0 working without any error.
https://forums.duke4.net/topic/8383-win10-hd3000-32bpp-crash-on-4897/

[bparker06]

Just FYI I have also added MSVC builds to the buildbot so it will create nightlies for it from now on:

http://bot.libretro.com/nightly/windows-msvc2010/

These should work fine without any changes on HD3000, and supports XP and up (the msys2 builds no longer support XP).

[Camui87]

First of all, thanks for your awesome work, Retroarch in generell and also all about this thread and to make Retroarch work again on Intel HD Graphics on Win 10.
Just a small thing I noticed about the MSVC2010 build: Retroachievements are missing, I loved that this feature was implemented, but was still a bit buggier in the 1.3.6 version which is working with HD3000. The new standard version on my other pc works fine now, but on that one I have to use the msvc2010 version, the achievements part is completely missing. Would it be possible to include this? :-)

Best regards!

[kingkork]

Sm199: can you advise how to use that wtfi.exe? I used it with retroarch.exe as the target with no luck.

[kingkork]

I am having this same issue. New build. Msi motherboard with a GeForce gtx 1050 card with nvidia driver installed. Windows 10. I've downloaded the last few stable retro arch releases (starting with 1.5) and the last two nightlies. Although I have a 64bit OS I also tried x86 with the same results. Retroarch crashes at a white screen right upon load. The debug gives me the same output as OP. Would love any ideas or suggestions!

[Microscoft]

I have come here from a YouTube channel called "Simply Austin". And he explained you can make ps1 look better with Beetle. And I have gotten the main menu to work, it just crashes when I try to play a game. Vulkan is not supported, GL crashes, and all other video drivers just give me a C++ runtime error. Has anyone found a fix for this issue? (I was going to update the driver but, I don't know if I should. I don't want to take a chance of it installing the driver and then my hunk of shit pc not working. My current driver version is 9.17.10.4459)

[Brawl345]

Problem still exists in v1.6.0. Driver version is 9.17.10.4459 on Windows 10 1703 x64

[aidenn]

Hi,

It seems this is an issue with Intel's drivers and Windows 10. Intel isn't going to fix this, but a few kind souls hacked the drivers to think they're running on an older OS version here: https://github.com/LWJGL/lwjgl/issues/119

My path:

1. Installed 64-bit 4229 drivers from Intel - same as default W10 drive, OGl doesn't work at all.
2. Tried the patcher from the link above - didn't work at all.
3. Tried https://github.com/LWJGL/lwjgl/files/620292/Intel_OpenGL_Win10_9.17.10.4459_Fix_x64.zip - a different error in RetroArch
4. Tried https://github.com/LWJGL/lwjgl/files/661125/OpenGL_Fix_PHDGD_Omega_5.0.zip - RetroArch finally works (and other OGl stuff up to 3.1)

Where the files should go:

• x86 Systems
  /System32/ig4icd32.dll
  /System32/ig7icd32.dll

• x64 Systems
  /System32/ig4icd64.dll
  /System32/ig7icd64.dll
  /SysWOW64/ig4icd32.dll
  /SysWOW64/ig7icd32.dll

Everything on W10 Home 64-bit and SB 2500k.

[2V3EvG4LMJFdRe]

I have this problem on Windows 8, with both and old build and the latest one. My computer used to have a second AMD GPU, but it broke so now I'm stuck with an integrated Intel HD 4000. Should I follow the solution mentioned above?

edit: nevermind I had to change it to D3D.
edit2: actually, that didn't fix it either. I made the menu show up, but games wouldn't launch. I had to install the latest .exe driver from Intel rather than the default Intel HD 4000 one and the one provided by HP for my laptop because that one wouldn't work either.

[aidenn]

I think that solution is only for HD3000.

[RobLoach]

This should be fixed.

:stop_sign: Close.

[Xebozone]

I have strugged with this too...
Now I finally have RetroArch 1.7.0 working on my Intel HD2000
I followed what aidenn said by installing this:
https://github.com/LWJGL/lwjgl/files/661125/OpenGL_Fix_PHDGD_Omega_5.0.zip

However, I got the following:

C:\Users\Owner\AppData\Roaming\RetroArch>[INFO] RetroArch 1.7.0 (Git 4b68a21a7)
[INFO] === Build =======================================
Capabilities: MMX MMXEXT SSE1 SSE2 SSE3 SSSE3 SSE4 SSE4.2 AVX AES
Built: Dec 25 2017
[INFO] Version: 1.7.0
[INFO] Git: 4b68a21a7
[INFO] =================================================
[INFO] [Config]: Loading default config.
[INFO] [Config]: loading config from: (null).
[INFO] Environ SET_PIXEL_FORMAT: RGB565.
[INFO] Redirecting save file to "C:\Users\Owner\AppData\Roaming\RetroArch\saves\.srm".
[INFO] Redirecting savestate to "C:\Users\Owner\AppData\Roaming\RetroArch\states\.state".
[INFO] Version of libretro API: 1
[INFO] Compiled against API: 1
[INFO] [Audio]: Set audio input rate to: 29970.03 Hz.
[INFO] [Video]: Video @ 960x720
[INFO] [GL]: Found GL context: wgl
[INFO] [GL]: Detecting screen resolution 1440x900.
[ERROR] [WGL]: win32_set_video_mode failed.
[ERROR] [Video]: Cannot open video driver ... Exiting ...
[ERROR] Fatal error received in: "init_video()"
[ERROR] This core requires a content file.

I ran the Manifest updater (WTFI.exe) linked above and pointed it to Retroarch...
I then reverted the drivers back to the originals... it still works?!
So, I'm not sure if the WTFI program made a difference, the updated drivers, or they both needed to work together... but I'm using the original drivers and everything is working now, so I believe the WTFI program did its job.

C:\Users\Owner\AppData\Roaming\RetroArch>[INFO] RetroArch 1.7.0 (Git 4b68a21a7)
[INFO] === Build =======================================
Capabilities: MMX MMXEXT SSE1 SSE2 SSE3 SSSE3 SSE4 SSE4.2 AVX AES
Built: Dec 25 2017
[INFO] Version: 1.7.0
[INFO] Git: 4b68a21a7
[INFO] =================================================
[INFO] [Config]: Loading default config.
[INFO] [Config]: loading config from: (null).
[INFO] Environ SET_PIXEL_FORMAT: RGB565.
[INFO] Redirecting save file to "C:\Users\Owner\AppData\Roaming\RetroArch\saves\.srm".
[INFO] Redirecting savestate to "C:\Users\Owner\AppData\Roaming\RetroArch\states\.state".
[INFO] Version of libretro API: 1
[INFO] Compiled against API: 1
[INFO] [Audio]: Set audio input rate to: 29970.03 Hz.
[INFO] [Video]: Video @ 960x720
[INFO] [GL]: Found GL context: wgl
[INFO] [GL]: Detecting screen resolution 1440x900.
[INFO] [WGL]: wglSwapInterval(1)
[INFO] [GL]: Vendor: Intel, Renderer: Intel(R) HD Graphics 2000.
[INFO] [GL]: Version: 3.1.0 - Build 9.17.10.4459.
[INFO] [GL]: Using resolution 960x720
[INFO] [GL]: Default shader backend found: glsl.
[INFO] [Shader driver]: Using GLSL shader backend.
[INFO] [GLSL]: Checking GLSL shader support ...
[WARN] [GL]: Stock GLSL shaders will be used.
[INFO] [GLSL]: Found GLSL vertex shader.
[INFO] Shader log: No errors.

I still get crash though when launching Mupen64, which makes me sad. I haven't tried any other cores.
I noticed that the xmb wave effect is also blown-out. The effect is that the wave is much brighter, kind of like over-exposure of an image. I think transparency is not working correctly, but I'm not really sure.

WTFI is open source:
https://github.com/alexey-lysiuk/tools/blob/master/wtfi/wtfi.cpp
I checked what it does, and basically, it just removes the "compatibility" section of the exe's manifest, which removes this in retroarch.exe 1.7.0

  <compatibility xmlns="urn:schemas-microsoft-com:compatibility.v1">
    <application>
      <!--The ID below indicates application support for Windows Vista -->
      <supportedOS Id="{e2011457-1546-43c5-a5fe-008deee3d3f0}"/>
      <!--The ID below indicates application support for Windows 7 -->
      <supportedOS Id="{35138b9a-5d96-4fbd-8e2d-a2440225f93a}"/>
      <!--The ID below indicates application support for Windows 8 -->
      <supportedOS Id="{4a2f28e3-53b9-4441-ba9c-d69d4a4a6e38}"/>
      <!--The ID below indicates application support for Windows 8.1 -->
      <supportedOS Id="{1f676c76-80e1-4239-95bb-83d0f6d0da78}"/> 
      <!--The ID below indicates application support for Windows 10 -->
      <supportedOS Id="{8e0f7a12-bfb3-4fe8-b9a5-48fd50a15a9a}"/> 
    </application>
  </compatibility>

I have confirmed that the patched exe works on my hardware now while the unpatched exe with the compatibility section in the manifest still included is not working.

More info on manifests:
https://msdn.microsoft.com/en-us/library/windows/desktop/aa374191(v=vs.85).aspx

How to check a manifest (I just open the exe in 7zip):
https://blogs.msdn.microsoft.com/patricka/2009/12/09/answers-to-several-application-manifest-mysteries-and-questions/

External vs internal priority (on XP, external takes priority):
https://stackoverflow.com/questions/17853304/manifest-embedded-and-external-which-has-priority-can-one-override-other

[ComputerNovice]

I'm was experiencing the same issue mentioned, with one main difference... My laptop has a Intel 4000 HD integrated graphics chip... Anyways everytime I attempted to load RetroArch (x64 version) it would start to open up the interface and then immediately crash...

So I then decided that I would attempt to uninstall the application from my laptop... I uninstalled it using revo-uninstaller and made sure that everything was totally removed... I then reboot and installed the app again

However the issue still persisted ...

I then remembered I had changed/updated the driver for my Intel 4000 HD over the weekend. So I opened up my device manager and rolled back my driver version after doing so the app began working again. So now my Intel HD 4000 is running the version listed below ... and for right now everything is working fine again. Not sure though why the newer driver doesn't work at all. Just wanted to provide this bit of info
Provider: Intel Corporation
Version #: 10.18.10.4358

Anyways ever since I rolled my graphics driver back to the version above everything started working again... So a graphics driver change may fix the issue for some of you ...

[oltolm]

I have Windows 10 64-bit with an Intel i5-2500 with an Intel HD Graphics 2000. RetroArch 1.7.1 crashed on start. This post helped to fix the problem. I used wtfi to patch retroarach.exe and it started to work.

Apparently the Intel driver checks if you are running Windows 10 and actively prevents you from running OpenGL applications. They do it because Intel HD 2000 does not support Windows 10, in theory. In practice it work very well on Windows 10, or it would if Intel itself did not create problems on purpose.

Please add the solution to documentation, it was not easy not find it.

[Kikuchef]

Just about 2 hours ago i used the wtfi patch on the retroarach.exe im using the stable 1.7.1 windows 10 64 bit

[Pat86]

Any chance this will be fixed officially? I still cant use Retroarch on my laptop. :(

[bparker06]

@Pat86 We cannot fix broken GPU drivers, and the other solutions that involve modifying the manifest are not acceptable for us to add for everyone. Unless you have some other ideas, all you can do currently is use either one of the d3d video drivers in RA, or gdi.

Is there a good reason you cannot use any of the solutions posted here?

[Pat86]

@bparker06 patching the retroarch.exe with wtfi did the trick, thanks.

its just that i prefer a "clean" solution that doesnt require modifying files. ;)
but it works fine this way too, so its ok. :)

[fishcu]

I'm running into exactly the same problems/issues as @Xebozone described in the last comment in this thread.
My system is a Chromebox with an Intel HD 3000 iGPU.
I tried both with Windows 10 and now Windows 8.1, with exactly the same result. Because of BIOS issues, I cannot install & test Windows 7 unfortunately
1. Would running Windows 7 make a difference?

While I can boot RetroArch, I cannot launch Mupen64 (retroarch.exe has stopped working). Parallel works, but it has somewhat slower performance still, so I'd prefer to use Mupen64.
2. Any workarounds for running Mupen64 on Intel HD3000 and Windows (8, 10)?

This issue is so annoying, because Mupen64 runs just fine under Linux (Ubuntu, Lakka). The only reason I switched to Windows is to have better Xbox 360 wireless controller drivers...

[bparker06]

Did you try patching the driver with wtfi?

[fishcu]

My problem is that Mupen64 crashes; Retroarch works with Parallel currently.

I have followed @Xebozone 's steps (https://github.com/libretro/RetroArch/issues/4580#issuecomment-358012766) and have encountered the same successes, but also failures. Thus I am asking about Mupen64 finally.

If by "patching the driver" you mean running wtfi.exe on the *.dlls, that doesn't work.

Is there a way to get mupen64 running?
Would it run on Windows 7 instead of Windows 8.1 / Windows 10 that I'm currently using?

[bparker06]

@fishcu I believe mupen requires OpenGL 3.3 which your GPU probably doesn't support.

[fishcu]

I see. Any recommendations (emulators, plugins, settings) for the best compatibility and speed on my old toaster? I would like to run the likes of Mario Tennis 64, Majora's mask, Smash Bros., and the Mario Parties on it.

Mario Tennis especially seems challenging, I could either get good graphics (framebuffer effects, etc.) but choppy, or full speed with lots of visual glitches.

BTW, I had Mupen64 running inside retroarch under Ubuntu Linux, so definitely also lazy Intel is to blame for not supporting drivers a bit longer...

[13ondy]

Hi Guys, I have a hp 8200 i7 2600 3.4ghz with 8gb of dd3ram, I have intel hd graphics 2000, running windows 10 pro. The problem I'm having is when I open retroarch it goes to open then just shuts straight away, I tried the wtfi patch but it didn't seem to do anything, and retroarch is still doing the same thing opening then shutting straight away. Can anyone help me or give me some advice or other ideas of what I can do please.