![]() Well, in case it helps, here's the last log entry:ĭPI registry setting, HKEY_CURRENT_USER\Control Panel\Desktop\LogPixels:0.ĭPI registry setting, HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\FontDPI\LogPixels:96. And this all ran fine prior to me having to reinstall Windows 10 for completely separate reasons.įwiw does \logs\exceptionlog.txt give you anything more than the screenshots?, probably not, but worth eyeballing if you haven't yet. I'm running an AMD Ryzen 7 3700X processor with 32 gigs of RAM so clearly everything is 64 bit on my machine. Sounds logical - the error text does point to a 32-bit vs. Just a thought should the usual attempts (dependencies,corrupted dependency or system file somewhere,AV,Viddrv,permissions,etc) fail to point toward the problem. I wonder if some unusual pathing order or environmental issue is going on making cmo attempt to load a 圆4 version of a dependency (or dependency of a dependency doing such) that it's expecting to be an x32 version. x001c is usually ERROR_BAD_EXE_FORMAT, and commonly a bitness issue like trying to load a 圆4 dll into x32 process (or the reverse). It might in terms of what version of the frameworks\dependencies\etc are installed and the overall environment perhaps. Net Frameworks, but I still have the same problem. I had to resort to installing 3.5 via the Windows Feature app, and then in a last-ditch attempt tried using Visual Studio 2019 Community Edition to install all the 4.x. ![]() Also eyeball \logs\exception.log for any additional info that might be logged, probably the same info as your screenshots but might have more.Īs I suspected, I'm still getting the same errors. I doubt that has anything to do with this though. I do have Visual Studio 2019 Community edition installed along with all the DirectX programming items, as well as all the different variations of the. Thank you for your continued help with this! Going to do a fresh Steam Install, then try these out, and will report back. FYI the post being quoted refers to a "PreRequisites" folder that doesn't exist - at least in the Steam installation. I've tried this as well, but I will give it another go. This does appear to be tied to the Prerequisites somehow, and from what we've been able to see so far, installing them individually should resolve this issue. Once that's complete you should also use Steam to verify your Game Cache's integrity via Steam. Please run those individual exes indicated in this topic. This thread details the best approach for resolving that: ![]() The errors you're experiencing appear to relate to that. I've passed this along to the team, and they've informed me that there is a common issue with fresh installs that precludes the prerequisites from installing fully during the base install process.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |