Hi
I’m getting this error when trying to launch the game after today’s update “The procedure entry point CreateDXGIFFactory2 could not be located in the dynamic link library dxgi.dll”
Just before the update the game was running fine
My OS is Windows 7
Jeez… Widows 7 might be your issue there…
But try this…
https://www.reddit.com/r/FortNiteBR/comments/zllkb8/possible_fix_for_createdxgifactory2dxgi_dll/
Windows 7 is below the min specs. Can you upgrade to a newer OS?
Thank you for reply, unfortunately OW2 folder doesn’t have Binaries\Win64 subfolder as this reddit thread suggests.
As I wrote OW2 was running fine on Win7 just yesterday before the update despite the system requirements stating otherwise already for 2 years, I do have a Win10 installation through dual boot, I assume that there is no issues, but I prefer to find a bypass for this issue on Win7 because my pc is too old to run Win10, hopefully someone will find a bypass soon, as there always were bypasses so far.
Getting this same error on Win 7 today too 
Please update if you find a workaround, nothing I’ve tried has worked yet but it ran perfectly before the update.
(Upgrading isn’t an option in the short term unfortunately)
edit: well, I tried to do a reinstall but after I uninstalled the game, it won’t let me reinstall it on my Win7 machine. Not sure what to do now, that’s frustrating.
Would imagine the new patch has something that kills it on win7.
Try upgrading to a newer windows see what happens.
Hi. This is a directX file. The company released 12 directX for Windows 7. Try installing it. The site says that it does not support all games. And just in case, make a Windows “checkpoint”. Write if you succeed.
Yes, this is most likely a DirectX related issue. I am also experiencing this on a Win7 machine, which until yesterday ran OW2 much better than Win10 on the same machine. The sad thing about this is that this issue does most likely not have to be there. It is most likely just some dev who did not pay attention not to use some unnecessary functionality, that will not run in Win7 but is not really required. Through playing with DLLs, I got it to the point where OW2 starts again and shows no issues at first, but freezes and crashes about a minute after starting the game. This happens regardless of if you are idling in the main menu or playing in a game. Sometimes the game crashes and must be closed by windows and sometimes it is able to send an error report first.
Jeez… Didn’t realise Windows 7 was still so popular…
Same problem. I think the problem is with Microsoft Vusual C++
What did you do? Others might benefit from your knowledge and be able to help.
Downloaded ReShade and extracted ReShade64.dll from the installer via 7-zip.
Then renamed the file to dxgi.dll and put it into the same directory as Overwatch.exe.
This produced different error messages about missing files (api-ms-win-core-libraryloader-l1-2-0.dll, api-ms-win-core-file-l2-1-2.dll, api-ms-win-core-file-l1-2-2.dll), which I then acquired the 64 bit versions of and put into the same folder.
Although this solves the original issue, it might well be that the game crashes later, are caused due to OW2 classifying ReShade as some cheating tool. This might be caused by any alterations to the DirectX files, which result in file signature mismatches.
On the other hand, the fact that this workaround works to this point means that there is no technical reason, this issue could not be fixed by Blizzard. And it would be a minimum effort fix.
Edit: I did some further analysis and the programmatic fix for the issue would be as simple as just calling the function “CreateDXGIFactory1” instead of “CreateDXGIFactory2” in Windows 7.
Hey, same problem here, game doesn’t work anymore after the update on Win7. Today’s little “update” didn’t fix anything. I don’t know what they did cuz there is no info if they wanted to stop supporting game on Win7 (as it was with LoL).
“I did some further analysis and the programmatic fix for the issue would be as simple as just calling the function “CreateDXGIFactory1” instead of “CreateDXGIFactory2” in Windows 7.” You mean Blizzard should do it? Because in my dxgi.dll file I have only CreateDXGIFactory1. I just really hope they’re gonna fix it, because it was working fine on Monday and stopped working after this update.
Hi. Same problem with the same error. After 8 years the OW stopped running on Win7. Well, that day has come.
Hello. They write at startup. “We do not service Windows 7 and recommend installing W10.” You click “Ignore and continue startup.”
The thing is that in Windows 7, compatible versions of the dxgi.dll do not contain the CreateDXGIFactory2 function because it is a DirectX 12 function. The Windows 10 versions of the dxgi.dll have that function, but do not work in Windows 7. Windows 7 does not support DirectX 12, although rudimentary support may be hacked in. However, Overwatch2 works perfectly while using only DirectX 11 functions. So if Blizzard did just call the DirectX 11 function CreateDXGIFactory1 when in Windows 7, it will work perfectly fine like it did until now.
I think it is highly likely that any attempt to inject a wrapper into the pipeline that re-routes the CreateDXGIFactory2 function call to CreateDXGIFactory1, will most likely trigger the OW2 anti-cheat measures.
So let’s hope they will fix it. It would be really bad if it stopped working after that many years, especially that it worked fine.
I hope a fix for this is found. For those suggesting to “upgrade” to win 10/11, that is not a solution. My system is stable and well configured to suit my needs. I’ve seen plenty of issues on 10/11 and I’m in no hurry to subject myself to them on a daily basis.
Besides, that is not what we are trying to accomplish.
“Just upgrade” is not the answer to the question we are asking.
I did some further testing an discovered that two of my Windows 10 machines are also experiencing issues since the problematic update. They do not show the same error message, but occasionally crash upon start and in-game with no error message at all. At least the behavior of crashing upon starting the game can be solved by applying the same trick as on the Windows 7 machine, but also triggering the same game crash after a minute of being in the game. So not really a solution there either. However, this strongly suggests that the issue are related.
I just tried to bring the issue to Blizzards attention by creating a ticket and got a response that suggests that they are not aware of any players experiencing the same issue. So maybe it could help that anyone experiencing this issue creates a ticket (just posting in the forum will not really help). Ticket creation is hidden under the “Get Help” button in the support section of your account here.
The version that broke things here was 2.14.1.0.134326.