Whenever attempting to boot unreal engine 5, either through a project, the launcher, or directly by the .exe file in the 5.0 directory, I get the above windows error, that when closed, results in the Unreal crash report also attached. It started when the engine crashed a day ago, working perfectly fine beforehand. At that point I thought nothing of it, and stopped for the day. However when I tried booting it up again today, it gives me this error, every time. I have tried reinstalling, and it still happens.
I am running windows 11, and recently switched over to a new PC (which was also windows 11, upgraded from 10.)
Does anyone have ANY clue what this is? Any help would be appreciated.
Hi,
I am completely new to Unreal but recently encountered a similar problem. After several attemps to resolve this like without success, I fianally traced the dxil.dll file to the Epic Games Launcher. I downloaded a fresh version of Epic Games Launcher and on installation it gave me the option of “Repairing” Epic Games. On completion of this repair Unreal Engine 5.1 ran OK.
UPDATE! Thanks to the previous comments I was able to overcome this new issue by installing the “Epic Games Launcher” as suggested then copy the files found in:
Just leaving my solution here how I fixed this issue, in case anyone else needs it:
Step 1: Delete all files in …\Engine\Binaries\ThirdParty\ShaderConductor\Win64
(Obviously delete engine files at your own risk, I made a backup of them before trying this…)
Step 2: In the Epic Games launcher do a Verify for your engine version.
This downloaded the files for me again and then everything worked as expected.
Just doing a Verify in the first place without deleting the files first did literally nothing for me…
This issue was caused by a Windows 11 update for us.
I just wish Epic Games and Microsoft could work together somehow, so that Windows updates don’t regularly break Unreal Engine. I feel like I’m starting to get too old for having everything break down in the middle of big productions at regular intervals.
Had the similar problem. But I didn’t update Windows. So, in my case, the solve is to update Windows and, after that, rescan required engine (button “verify”). All works fine for now
