Instalar Steam
iniciar sesión
|
idioma
简体中文 (Chino simplificado)
繁體中文 (Chino tradicional)
日本語 (Japonés)
한국어 (Coreano)
ไทย (Tailandés)
български (Búlgaro)
Čeština (Checo)
Dansk (Danés)
Deutsch (Alemán)
English (Inglés)
Español - España
Ελληνικά (Griego)
Français (Francés)
Italiano
Bahasa Indonesia (indonesio)
Magyar (Húngaro)
Nederlands (Holandés)
Norsk (Noruego)
Polski (Polaco)
Português (Portugués de Portugal)
Português - Brasil (Portugués - Brasil)
Română (Rumano)
Русский (Ruso)
Suomi (Finés)
Svenska (Sueco)
Türkçe (Turco)
Tiếng Việt (Vietnamita)
Українська (Ucraniano)
Informar de un error de traducción
what a shame.
Thank you!
*Make a new windows login*
I had to run the game on a secondary windows login and somehow that worked. I even tried to use Regedit after finding out a new windows account helped but still couldn't fix it. But some how, running the game on a blank new log in always worked while my regular login doesn't.
I tried to reverse the setup: installed Steam under another account and tried to start the game under my own main one. It didn't start. It looks like the game doesn't start under my main Windows account regardless of the way it is installed.
Some kind of a magic...
P.S. I don't have a folder "_CommonRedist" under "Deus Ex Mankind Divided" in Steam directory :(
The issue is its not as simple as releasing a patch. The are no currently known major bugs stopping the game from running, which means the issues is on your end.
There is no real way for the devs to know what background programs you have running on your machine, what file could be missing/corrupt or if you have an incompatible driver/software installed without actually looking at your machine.
All you can do is try the various fixes listed on the forums and hopefully one of them will get it running.
This is a perfect example, Clearly there is a fault in their original user somewhere, a corrupt setting/files somewhere which is stopping the game from running, but it runs with another account, which proves its not the game directly causing the issue, as the same machine is clearly running it fine on another user account.
However tracking down that fault could take a while and would need someone who knows what they are doing being heavily involved whether remotely or at the computer itself.
Edit
===
Whoops I missed this was kind of a resurrected thread........
FYI - using bitdefender
This might not be a magic bullet for everyone but if you've tried everything else, try that too just in case your root cause is the same as mine.
I know that isn't really helpful but it's still an option.
In my case, the Application Access feature was blocking DXMD.exe - presumably because it was trying to modify my Documents folder.
Adding an exception for the program under that feature allows it to run.