Patch 2.0.1 Bugs and Known Issues
The new patch brings new bugs and oddities
With Diablo III patch 2.0.1 now live around the world, there are the inevitable bugs, issues and oddities to deal with. Any patch can introduce bugs, and one the size of this patch has brought more than a few. Here are some issues being dealt with in hotfixes or an upcoming small patch, and the official known issues list.
Just found the answer. Aparently it's a known issue: http://us.battle.net/d3/en/forum/topic/11883998315
Thanks for the link! We're testing a hotfix for this right now. I don't have an ETA on when the hotfix will be deployed (or even if it will pass testing), but I still wanted to communicate that we're not only aware of the issue, but actively working to address it.
If we are able to hotfix, we'll be sure to communicate that information via forum post, or even a front page blog post (as we've often done in the past).
For repetition sake, this is the issue in question:
Thanks Lylirra! Logged in right now and it seems to work now. Couldn't reset my wiz quests and now I just did it.
Can confirm that the hotfix is now live!
Error 300006 - Reset Quest
There is a new option in the patch to Reset Quests, which starts the campaign over entirely for a character, like it was their first time through it. Using that button if you had already pre-ordered the Reaper of Souls Expansion gave error 300006. That has now been taken care of, with a hotfix.
Post by Blizzard (Blue Tracker, Official Forum)
Just found the answer. Aparently it's a known issue: http://us.battle.net/d3/en/forum/topic/11883998315
Thanks for the link! We're testing a hotfix for this right now. I don't have an ETA on when the hotfix will be deployed (or even if it will pass testing), but I still wanted to communicate that we're not only aware of the issue, but actively working to address it.
If we are able to hotfix, we'll be sure to communicate that information via forum post, or even a front page blog post (as we've often done in the past).
For repetition sake, this is the issue in question:
Quests
- The "Reset Quests" button will return an error when pressed by players who pre-ordered Reaper of Souls.
Thanks Lylirra! Logged in right now and it seems to work now. Couldn't reset my wiz quests and now I just did it.
Can confirm that the hotfix is now live!
Mac Client Crash
There have been multiple issues with the Auction House after the patch landed, but one of the more serious was that the OS X Diablo III client sometimes crashes when the player tries to access the AH. Check out this thread on the Mac Technical Support forum for details.BoA Items on Auction House
All newly obtained Legendary and Set items in patch 2.0.1 are now Bind on Account, and can only be traded for 2 hours with other characters who were in the game when the item dropped. There was a bug that allowed some of those items to be listed on the Auction House, including crafted legendary items. That has been hotfixed so those items cannot be sold, and other fixes will take care of the items that were already sold.
Post by Blizzard (Blue Tracker, Official Forum)
Let me jump in really quickly on this. :)
The ability to list Bind on Account items on the auction house was not intended and most certainly a bug. Early this morning, we implemented a hotfix which now instructs the auction house to reject all Bind on Account items, including those that currently have a 2-hour (or less) trade timer active.
Here’s some additional info:
We'll be sure to keep you all updated on any further changes, should they come through. Thanks for your reports!
The ability to list Bind on Account items on the auction house was not intended and most certainly a bug. Early this morning, we implemented a hotfix which now instructs the auction house to reject all Bind on Account items, including those that currently have a 2-hour (or less) trade timer active.
Here’s some additional info:
- As a result of this hotfix, players who attempt to list an account-bound item on the auction house will now receive an error ("[Item Name] Auction Failed (32105)") as soon as they hit the "Create Auction" button and the item will be returned to the player’s stash or inventory unchanged. Since deposits are only taken on a successful sale and not for simply posting an auction, players won’t lose any gold or real money for attempting to list account-bound items.
- Account-bound items that are currently listed on the auction house will not be taken down. Instead, we’re letting those auctions sell or expire naturally.
- As we speak, we’re looking at making any account-bound item that’s been sold on the auction house BoA for the player that purchased it. This would apply retroactively. Our desire is to avoid taking anything away from players if possible, but still ensure that our goals for items in patch 2.0.1 are being met. This particular solution seems to be best of both worlds.
We'll be sure to keep you all updated on any further changes, should they come through. Thanks for your reports!
Crash on Windows XP
Another technical issue can come up with the Diablo III client on PCs running the old Windows XP operating system. This can cause the dreaded Blue Screen of Death (BSOD). This may also be an issue in newer versions of Windows if the client has been changed to Windows XP compatibility mode. The technical support team is looking for feedback to help track this bug down.
Post by Blizzard (Blue Tracker, Official Forum)
Greetings Diablo Community,
We're aware of an issue that occurs for some Windows XP users, where running the Battle.net App may cause a system crash (blue screen). Please use the workaround below while we work on addressing the issue in a future update:
If this issue persist after deleting systemsurvey.exe, please let us know here.
Update:
We are looking for more information about this error, and we would greatly appreciate it if you could submit the error logs related to this error. The error log is located here:
XP: C:\Documents and Settings\<username>\Local Settings\Application Data\Blizzard Entertainment\SystemSurvey\log.txt
Vista+: C:\Users\<username>\AppData\Local\Blizzard Entertainment\SystemSurvey\log.txt
Please email the log file to forumtech@blizzard.com
If you are willing to test some new files, please let us know as well.
Update (2/28):
Thanks to those of you who have sent the log files! Our developers are additionally requesting the mini dump of the crash. The mini dumps can be found in the Windows folder here:
C:\Windows\Minidump
Thanks very much for your help!
We're aware of an issue that occurs for some Windows XP users, where running the Battle.net App may cause a system crash (blue screen). Please use the workaround below while we work on addressing the issue in a future update:
- 1. Close any Battle.net and World of Warcraft related programs.
2. Delete systemsurvey.exe. Below are the default installation locations.
C:\Program Files\Battle.net\
C:\Program Files\World of Warcraft\
Note: If you installed Battle.net or World of Warcraft in different location, systemsurvey.exe will be in the main Battle.net or World of Warcraft folder of the custom location. 3. Run Battle.net as normal.
If this issue persist after deleting systemsurvey.exe, please let us know here.
Update:
We are looking for more information about this error, and we would greatly appreciate it if you could submit the error logs related to this error. The error log is located here:
XP: C:\Documents and Settings\<username>\Local Settings\Application Data\Blizzard Entertainment\SystemSurvey\log.txt
Vista+: C:\Users\<username>\AppData\Local\Blizzard Entertainment\SystemSurvey\log.txt
Please email the log file to forumtech@blizzard.com
If you are willing to test some new files, please let us know as well.
Update (2/28):
Thanks to those of you who have sent the log files! Our developers are additionally requesting the mini dump of the crash. The mini dumps can be found in the Windows folder here:
C:\Windows\Minidump
Thanks very much for your help!
No Gold Sales on RMAH
The Auction Houses are still open, although they will be closing entirely on March 18. Right now, gold can't be sold or purchased on the Real Money Auction House, because of a bug that will require a small patch to fix. We can expect to see something like a patch 2.0.1a in the near future, to take care of this bug and other issues that can't be dealt with via a hotfix. Here's the current news on the issue:
We've investigated various different options for fixing the issue that's causing players to be unable to buy or sell gold on the real-money auction house. Unfortunately, this issue cannot be hotfixed and will require a small client-side patch to resolve fully. We are working developing that patch as we speak, but do not have an ETA to share at this time.
Known Issues for Patch 2.0.1
Finally, here's the latest list of major bugs and issues that the Technical Support team is tracking. Some of these will be cleared up via hotfix, and others will take a patch to fix.
Post by Blizzard (Blue Tracker, Official Forum)
Hello everyone, and welcome to Patch 2.4.1! Below you will find the Known Issues list for our 2.4.1 patch. Please do not report bugs that you see on this list, as we already know about them, and help out other players reporting bugs by referring them to this list.
As a reminder, this list will not list every bug that is active in the 2.4.1 patch. What it is listed here are a select few issues -- chosen due to visibility and impact -- that are active and confirmed as bugs by Quality Assurance with verifiable steps and (in most cases) an expected fix. Just because a bug is not on this list does not mean we don't know about it! In addition, potential exploits and the like will never be listed here.
Please note that documented bugs may not always be fixed in the order in which they were reported. In some cases, we may not have a timeline for a when a bug will be fixed and some bugs may not be able to be fixed at all. If we are able to verify that a documented bug cannot be fixed, it will be removed from this list.
Thank you for your continued reports, and enjoy Diablo III!!!
Achievements
As a reminder, this list will not list every bug that is active in the 2.4.1 patch. What it is listed here are a select few issues -- chosen due to visibility and impact -- that are active and confirmed as bugs by Quality Assurance with verifiable steps and (in most cases) an expected fix. Just because a bug is not on this list does not mean we don't know about it! In addition, potential exploits and the like will never be listed here.
Please note that documented bugs may not always be fixed in the order in which they were reported. In some cases, we may not have a timeline for a when a bug will be fixed and some bugs may not be able to be fixed at all. If we are able to verify that a documented bug cannot be fixed, it will be removed from this list.
Thank you for your continued reports, and enjoy Diablo III!!!
Achievements
- The icon art is not displaying correctly for multiple achievements. These achievements can still be completed normally and the rewards correctly delivered.