![]() ![]() Since a lot of replicating and testing needs to be done, it’s difficult to give an exact time frame at this time. It can be a lengthy process, but we want to make sure the fix in place does resolve the issue before it’s pushed out. If they can test and verify the fix in place works, an update or hotfix will be pushed to the live servers. Once a fix is in place, our QA and compatibility teams need to make sure the fix works. Our team needs to run through testing and replicating the issue to find the cause, then work on a fix for the issue. It’s a frustrating issue and these types of compatibility issues can take a bit of time to resolve. Our team is still investigating the issue and they believe they found the source of whats been causing the issue. The other option is to roll back to the previous build of Windows 10 while we work on this. This will result in playing without sound however. The most successful options currently are temporarily disabling sound outputs on your PC. We’ll let you know as we get more insight into the problem, but for now, there are some work arounds posted in this thread. The devs are aware and looking into the issue now. ![]() You are welcome to continue reporting issues or work arounds that you discover, but you can save yourself some time and stop gathering the previously requested logs now. I’m editing the other messages to indicate that we no longer need more data. Thanks for answering the call to action and getting us those DXDiags/Error reports. We’ve synced with the devs and it looks like we’ve got enough reports now. Could I point out that a week ago the US Technical Support forum acknowledged that these freezes are due to an issue between the interaction of Diablo III’s sound system and Windows 10 version 2004 and the developers are working on a fix… ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |