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
Sorry to hear you are having issues. What error message popup when you launch those games?
Thanks
Basj,
Stardock ♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥.
Sorry to hear you are having trouble.
Can you give us an example of what game will not launch and a few that do?
For the ones that do not, does Steam report them as 'running'?
Sean Drohan
Stardock Product Lifecycle Manager
I realize we are asking you to do some (much appreciated) work here but can you find more games for us in your library that do *NOT* work?
Furthermore, it's likely that 2042 did 'run' but crashed. If so, the crash would appear in the Windows Event viewer, for example:
https://cdn.stardock.us/support/uploads/mmc_2023-02-21_09-30-59sdrohan.png
This is some work but if you were willing, and if you can see that it is indeed crashing, this process would capture it:
https://support.stardock.com/space/SHC/1444478977/Manually+Collecting+WindowBlinds+Crash+Dumps
As noted in it, the resulting file will likely be VERY large. Zip it, upload it to a cloud drive service of your choice, and post a shared link here.
If its any consolation, that crash catcher (WinDBG) could help you henceforth diagnose other issues for you in the future.
Thanks, OniKenji.
Sean Drohan
Stardock Product Lifecycle Manager
Thank you, OniKenji. Looking forward to what you can provide next.
Sean Drohan
Stardock Product Lifecycle Manager
0:000> .dump /mf C:\Users\final\Desktop\CODBlackOPS3_03012023.dmp
Creating C:\Users\final\Desktop\CODBlackOPS3_03012023.dmp - mini user dump
GetContextState failed, 0x8007001F
Unable to get event thread context, Win32 error 0n31
GenGetProcessInfo.Start(0x7cbc) failed, 0x8007012b
Dump creation failed, Win32 error 0n299
"Only part of a ReadProcessMemory or WriteProcessMemory request was completed."
GetContextState failed, 0x8007001F
Unable to get current machine context, Win32 error 0n31
To be clear:
-WinDBG is installed and set to the default postmortem debugger:
https://cdn.stardock.us/support/uploads/DbgX.Shell_2023-03-02_09-02-11sdrohan.png
-A WindowBlinds Skin is applied
-You try to run the game but it fails to load
-After the game does not load (crashes), WinDBG pops
Is that the case, those conditions result in WinDBG popping, yes?
Sean Drohan
Stardock Product Lifecycle Manager
I suspect that any game that fails also has anti-cheat (AC) mechanisms in them - COD \ BF 2042 certainly would. It is also likely why it wont allow WinDBG to capture a dump - they don't want people being able to see how the AC is working at that level.
This may be difficult for you to determine, if a game has AC or not, but if my theory is correct, all the ones that do will fail and all the ones that do not will work. Again, that's some work but can you confirm that?
Assuming it's true, that game with AC will fail, a workaround would be to 'disable' the WB service, reboot (logging out \ in may suffice), and run the game.
https://cdn.stardock.us/support/uploads/mmc_2023-03-03_09-08-27.png
Its not ideal (at all) but its better than having to uninstall \ reinstall WB.
In the end, this would not be the 1st time AC has caused issues with 3rd party apps and services.
Sean Drohan
Stardock Product Lifecycle Manager