First time here? Check out the FAQ!
THIS IS A TEST INSTANCE. Feel free to ask and answer questions, but take care to avoid triggering too many notifications.
Ask Your Question
0

Popup Notification: CreateDXGIFactory2 could not be located in the dynamic link library dxgi.exe

  • retag add tags

Hello Techies I ran into a problem while trying to set up "From what I believe" is WireShark 40. 64 Bit. The popup notification goes like this. The procedure entry point CreateDXGIFactory2 could not be located in the dynamic link library dxgi.exe. I found this file in the system32 directory. Can anyone give me a hand in correcting this problem? J

JWanner's avatar
1
JWanner
asked 2022-10-06 19:47:01 +0000
Guy Harris's avatar
19.9k
Guy Harris
updated 2022-10-07 05:32:52 +0000
edit flag offensive 0 remove flag close merge delete

Comments

What operating system is the install running on?

Chuckc's avatar Chuckc (2022-10-06 20:36:15 +0000) edit
more
  • delete
add a comment see more comments

2 Answers

0

Do you have SweetFX installed? A Google search for CreateDXGIFactory2 finds a number of pages that suggest that it might be a problem with SweetFX.

Some other pages it found suggest it might be a problem with some Ubisoft software; for example, a comment on this Reddit thread mentions some Ubisoft issues.

Guy Harris's avatar
19.9k
Guy Harris
answered 2022-10-07 05:26:48 +0000
edit flag offensive 0 remove flag delete link
more

Comments

add a comment see more comments
0

I think from the duplicate question from the OP they were running Win 7 which is no longer supported. They'll have to use Wireshark 3.2 or earlier (officially supported, 3.4 & 3.6 may still work).

See the LifeCycle wiki page for more info on OS version support.

grahamb's avatar
23.8k
grahamb
answered 2022-10-07 09:18:06 +0000
edit flag offensive 0 remove flag delete link
more

Comments

Ok, So the version of Windows that I am running is Win 7 Ultra. Thanks. I tried using version 3.4 at one time but when it updated it no longer worked. I was hoping WS 4.0 would have corrected the problem. I see now that isn't the case. So, it looks like I have to uninstall 4.0 and reload 3.4. If I have to do the update again and it crashes again. Whats my remedy? Thanks guys

JWanner's avatar JWanner (2022-10-07 16:59:41 +0000) edit
more
  • delete

As noted in my answer the last version to officially support Win 7 was 3.2

grahamb's avatar grahamb (2022-10-07 18:53:42 +0000) edit
more
  • delete
add a comment see more comments

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account. This space is reserved only for answers. If you would like to engage in a discussion, please instead post a comment under the question or an answer that you would like to discuss.

Add Answer