Possible fix for 'Couldn't find TESV.exe (self.enderal) submitted 2 years ago by ThatOneGuy1294 So the latest version of Enderal Launcher (1.1.0.4) seems to have problems finding TESV.exe. Jan 22, 2018 - Invalid application name TESV.exe, version: 1.9.32.0, timestamp: 0x51437ce5. Timestamp: 0x59b94abb Exception code: 0xc0000005 Error offset. Yeah, I saw that, but we can't fix this, because it's not caused by Enderal.

Hey Guys, so I just started playing Skyrim again because i got a new computer and i wanted to try out a bunch of mods. With Sky UI being one of them i downloaded SKSE and installed it according to this video i followed everything to the letter and when i tried to run the skse loader it spits out a 'couldn't find TESV.exe' which is crap because its right there. I tried searching for someone having the same issue but i cant find anything. If anyone could tell me what i'm doing wrong or what the issue is i would appreciate it. I should have mentioned in the first post that i tried that too.

I just went back in and double checked everything and i found where i messed up. Where did you mess up. I had this problem. What I found I'd done wrong was I was pointing the shortcut at the skse loader in the unzipped folder. Since that's about as clear as mud do this: right click your desktop shortcut choose properties in 'target' make sure the correct file path is there, for me it's 'C: Program Files (x86) Steam steamapps common Skyrim skse_loader.exe' (include the ') hope this helps •.

I'm suffering the same error, also on Windows 10, as of just a few days ago. It's definitely related to ENB - launching Skyrim without ENB does not trip the error, and launching it with the ENB d3d9.dll invariably does, regardless of whether it's through MO or not. I've also been able to use a SweetFX d3d9.dll just fine. The problem for me started when my computer installed the Windows Creators Update, which is (as far as I can tell) the only thing that could have caused the game to stop working for me literally overnight. It seems that that error code relates to the program not being able to access a resource it needs, so that update must have changed or moved some component that ENB is expecting. And since Boris isn't interested in working on compatibility for Windows 10, it may well be borked forever, unless someone can identify what got screwed up. I'm suffering the same error, also on Windows 10, as of just a few days ago.

It's definitely related to ENB - launching Skyrim without ENB does not trip the error, and launching it with the ENB d3d9.dll invariably does, regardless of whether it's through MO or not. I've also been able to use a SweetFX d3d9.dll just fine. The problem for me started when my computer installed the Windows Creators Update, which is (as far as I can tell) the only thing that could have caused the game to stop working for me literally overnight. It seems that that error code relates to the program not being able to access a resource it needs, so that update must have changed or moved some component that ENB is expecting. And since Boris isn't interested in working on compatibility for Windows 10, it may well be borked forever, unless someone can identify what got screwed up. Same issue and the ONLY thing I've added to Win 10 is the new update from last week for 'creators'. Wonder if Microcough broke something with DX9 games.