We have updated our Community Code of Conduct. Please read through the new rules for the forum that are an integral part of Paradox Interactive’s User Agreement.
You are using an out of date browser. It may not display this or other websites correctly. You should upgrade or use an alternative browser.
Found this on a couple other sites, and it worked for me to fix the error (I also have an older computer still running Windows 7 too)
Go to (by default) - C:\Windows\SysWOW64. From there, copy the dbghelp.dll file. Then paste it into Steam/steamapps/common/Victoria 3/binaries. Then launch as normal.
For me it doesnt work. The error message is the same you´ve got with CK3 (caused by the avx problem) until paradox released a "beta" launch version to fix that.
The "dll solution" seems only to work for some Windows 7 user.
Found this on a couple other sites, and it worked for me to fix the error (I also have an older computer still running Windows 7 too)
Go to (by default) - C:\Windows\SysWOW64. From there, copy the dbghelp.dll file. Then paste it into Steam/steamapps/common/Victoria 3/binaries. Then launch as normal.
That's actually interesting. I bumped into this problem myself. Starting vicky3 outside of the launcher revealed it was missing an entry point in that specific .dll file.
Since syswow64 contains (unlike the name suggests) the 32-bit system dll's, and is normally part of the search path for locating dll's, this would imply that vicky3 is a 32 bit application (or tries to spawn a 32 bit child process), and that there is a different version of this specific dll in the search path before it searches the syswow64 folder, which is missing the needed entry point.
I'll take a look on my own Windows 7 system later tonight.
Update : You don't even need to copy the dbghelp.dll file. Just delete (or rename) the one in the binaries subfolder of vicky3 fixes the problem.
Which means the dbghelp.dll file that got installed together with the game itself is a faulty one (because it's missing at least one function the game engine wants to call).
I have this issue in Parallels (virtualized arm64 Windows running on macOS) on a 2021 M1 Macbook Pro.
Victoria 3 launches and runs fine on native macOS (I've only launched it from the Steam -> Paradox launcher). But I get the OP error when trying to launch the game from virtualized arm64 Windows inside Parallels. Launching the vic3 binary from the /binaries folder seems to no-op just like OP said.
A clean install of arm64 Windows inside Parallels has this issue even after installing the latest Microsoft Visual C++ Redistro. This is probably the simplest repro step for the developers.
Removing/copying dbghelp.dll doesn't seem to change the problem for me.
Crusader Kings 3 also runs on both macOS and inside arm64 Windows via Parallels (where I get much better performance in Windows hosted on macOS than on macOS alone). That's why I tried running Victoria 3 there as well.
Fortunately I can play Victoria 3 on macOS, so it's not a show-stopper, but maybe this info can help somehow.
Found this on a couple other sites, and it worked for me to fix the error (I also have an older computer still running Windows 7 too)
Go to (by default) - C:\Windows\SysWOW64. From there, copy the dbghelp.dll file. Then paste it into Steam/steamapps/common/Victoria 3/binaries. Then launch as normal.
I have no idea how the original person figured it out, I saw it suggested in a few places when googling the problem, so I tried it, and it worked for me, so I figured it was worth sharing to try to help someone else also.
That's actually interesting. I bumped into this problem myself. Starting vicky3 outside of the launcher revealed it was missing an entry point in that specific .dll file.
Since syswow64 contains (unlike the name suggests) the 32-bit system dll's, and is normally part of the search path for locating dll's, this would imply that vicky3 is a 32 bit application (or tries to spawn a 32 bit child process), and that there is a different version of this specific dll in the search path before it searches the syswow64 folder, which is missing the needed entry point.
I'll take a look on my own Windows 7 system later tonight.
Update : You don't even need to copy the dbghelp.dll file. Just delete (or rename) the one in the binaries subfolder of vicky3 fixes the problem.
Which means the dbghelp.dll file that got installed together with the game itself is a faulty one (because it's missing at least one function the game engine wants to call).
I'm glad some people were helped by the solutions suggested in this thread. Kudos for sharing them!
It is clear my computer is not going to run Victoria 3 in the current setup, so I'm going for an upgrade. A necessary one anyway, just found out that my motherboard dates from 2008. Hopefully I'll be able to run the game soon!
(I also have an older computer still running Windows 7 too)
