| Crashes launching RoS since launcher update(1) | Category: Technical SupportAugust-8-2014 11:30 AM PDT (8 years ago) ![]() | |
| Hello, Ever since the most recent Battle.net launcher update went live (1.1.7.4906) recently, I cannot launch Diablo III: Reaper of Souls through the launcher. When launching, it pops up the following error immediately before it even appears that the game is cached into memory. "This application encountered an unexpected error." To help us identify the problem, please describe what you were doing when the error occurred. 3FC4EB9D-FFF1-4E16-B0D8-9AA31AD92E3A http://i.imgur.com/sZfsVy3.jpg I have not made any system changes (e.g. driver updates, pc config/hardware settings) at all before and after the bug started. - The game works fine if I run directly from the executable (//Diablo III.exe -launch). - Uninstalled battle.net launcher and re-installing still gives the same error - This does not happen on my Surface Pro, that I have; the only difference beside the hardware are the additional language packs are not installed on that computer. | ||
| Crashes launching RoS since launcher update(2) | August-8-2014 11:36 AM PDT (8 years ago) ![]() | |
| sojourn, In your Desktop App, under the Game settings, do you happen to have the option to use additional command line arguments enabled and if so do you have anything specified? If the answer is yes, try removing whatever you have on the line or disable the option altogether and try it again. _________________________________________________________ I'm available in the forums Tuesday - Friday, 11 am - 8 pm Pacific Time Saturday 10 am - 7 pm Pacific Time Feedback? - https://www.surveymonkey.com/s/Omrakos | ||
| Crashes launching RoS since launcher update(4) | August-8-2014 1:01 PM PDT (8 years ago) ![]() | |
| sojourn, We discovered the same thing yesterday. Dankorii had -locale in his options too and it was causing the crash. If you had the complete option which specified a locale to use, it wouldn't cause a problem, but removing the country code does this. We've already reported it and it ought to be fixed in an upcoming Battle.net Desktop update. _________________________________________________________ I'm available in the forums Tuesday - Friday, 11 am - 8 pm Pacific Time Saturday 10 am - 7 pm Pacific Time Feedback? - https://www.surveymonkey.com/s/Omrakos | ||
