Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Something on your system is blocking the user interface from starting. Could be a firewall blocking connections to localhost (127.0.0.1) - ad-aware for example is know to do that.
Alternatively something is blocking the UI process from starting.
To know for sure, I'd need trace logs from the run. Add startup option: --trace to 3DMark on Steam then try starting, once it has failed, look up 3dmark.log and 3dmark-native.log in Documents/3DMark/ folder and email those to info@futuremark.com and also mention a link to this thread or explain your issue in the email so I know what do those logs refer to.
If no logs show up, then Documents/3DMark/ cannot be written to or there are some other file permission issues.
Viele Grüße, Michael
GL
Also, wichtig ist das der Dokumente Ordner nicht in der Onedrive Cloud ist. Am besten darauf achten! War bei mir der Fall. Falls ein 3dmark Ordner in den Windows Dokumenten Ordner besteht,