2.4.3 Known Issues List - Updated 1/6/17

  • Hello everyone, and welcome to Patch 2.4.3! Below you will find the Known Issues list for our 2.4.3 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.3 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 that are under investigation and (in most cases) are expecting a 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!

    • Newly created characters are not receiving Angelic Wings or Infernal Helms on log in
      • Please note: the Angelic Wings will now be found in the Cosmetics section of your Inventory if any characters had them in their Inventory or Stash prior to the patch. Additionally, any Infernal Helms in your Inventory or Stash prior to the patch will still be there

    • Players with large friends lists may occasionally only see game icons in their chat feed instead of full names when multiple friends come online
  • The following issues should now be resolved and have been removed from the above list:

    • Players may experience a crash upon game launch when a large number of friends are online on PS4

    • Players are experiencing lag/framerate/crashes with the 64-bit client
      • Changing to the 32-bit client or leaving the chat channels for your communities may temporarily resolve this issue