The main Demonbinder bug thread now contains more than 60 replies and close to 6,000 views. Players across PC and PlayStation describe essentially the same experience: Demonbinder drops, often from Grigoire or the Hall of the Penitent, but using the item does nothing. It remains in the inventory or stash instead of being consumed and added to the Stable's Mount Armor collection. Some players have found two copies. Others have collected three. One particularly patient player reported having five Demonbinders sitting in the stash. At that point it stops being a cosmetic reward and begins resembling an unusually specific storage problem.
Demonbinder Drops Normally — Then Refuses to Unlock
The basic failure is remarkably consistent. A player defeats Grigoire, sees Demonbinder appear among the rewards, picks up the Mount Armor and attempts to use it. The usual sound or interaction may occur, but the cosmetic is not consumed and nothing new appears in the Stable. Players have tried restarting Diablo IV, relogging, moving the cosmetic through the stash, switching between mouse and keyboard and controller, and simply waiting for the game to reconsider its position. None of those methods appears to provide a reliable fix.
The first large thread began on May 5 when a PC player said Demonbinder had dropped but could not be added to their collection. They checked whether it had perhaps already been unlocked under another name and found nothing. More importantly, Demonbinder itself did not appear among the Mount Armor entries available to collect. Other players immediately confirmed the same behaviour, including somebody who had obtained the cosmetic from the Hall of the Penitent. By May 23, the original poster had accumulated five copies without being able to learn a single one. ([us.forums.blizzard.com](https://us.forums.blizzard.com/en/d4/t/cannot-add-demonbinder-mount-armor-to-collection/250329))
It is difficult to imagine a cleaner demonstration of a broken reward loop. Kill boss. Receive cosmetic. Cosmetic does not unlock. Kill boss again. Receive same cosmetic. Cosmetic still does not unlock. Continue until stash begins looking like Demonbinder's regional distribution warehouse.
Some Players Say They Already Owned Demonbinder — Then It Vanished
The stranger part actually predates those unusable drops. On April 28, a separate player reported that Demonbinder had disappeared from their Mount Armor collection despite previously owning and regularly using it with the Brimstone horse. Other players quickly confirmed that they remembered having Demonbinder unlocked and could no longer find it. Within days, that same thread began attracting players who had newly obtained the cosmetic and discovered they could not learn it either. ([us.forums.blizzard.com](https://us.forums.blizzard.com/en/d4/t/demonbinder-mount-armor-no-longer-appearing-in-collections/246533))
That combination suggests something more interesting than a simple broken “Use” button. We cannot see Diablo IV's internal collection data, and Blizzard has not publicly explained the cause, so it would be premature to declare exactly what went wrong. But players reporting that an existing collection entry disappeared at approximately the same time new Demonbinder items became impossible to register raises the obvious possibility that the underlying cosmetic entry itself became disconnected or unavailable. The physical reward still exists in the loot table. The Stable appears to have forgotten what it is supposed to do with it.
This fits uncomfortably well with the broader cosmetic problems we have already been tracking. Earlier this year, Diablo IV's Wardrobe began producing another round of transmog and cosmetic complaints, including problems with mounts, trophies and appearances. We also covered players unable to claim the Herald of Hatred pet despite the reward appearing available. Those are not necessarily the same technical bug, but they live in the same rather untidy cupboard: Diablo IV occasionally seems less reliable at remembering cosmetic ownership than it is at remembering how many demons you killed three months ago.
The Bug Is Not Limited to PC
Although Blizzard's largest thread sits in the PC Bug Report section, console players have reported the same problem. A PlayStation-tagged thread from May 3 describes Demonbinder refusing to unlock on console as well as PC, with additional players confirming the issue. Another European forum report from June says a PS5 player received the cosmetic but could not use the item to add it to their account. That makes this considerably harder to dismiss as a local installation issue or one corrupted PC client. ([us.forums.blizzard.com](https://us.forums.blizzard.com/en/d4/t/demonbinder-mount-armor/249287))
Reports continued through July and August. Players were still obtaining Demonbinder from Lair Bosses at the end of July and discovering that it could not be learned. On August 7, one player noted that they had received another copy in Season 14 after already reporting the same problem in Season 13. On August 17, yet another player said a freshly dropped Demonbinder remained stuck in their stash because right-clicking it did nothing. The main Blizzard bug index now shows the original thread with activity as recently as September 7.
Cosmetic Bugs Matter More When Cosmetics Are Part of the Endgame
It is tempting to rank Demonbinder somewhere below a broken Unique, missing Paragon Points or a quest that prevents progression entirely. Nobody loses damage because their horse is insufficiently intimidating. But Diablo IV deliberately treats cosmetic collecting as one of its long-term reward systems. Bosses drop mount trophies and bardings, seasons offer appearances, the shop sells elaborate armor sets, events hand out cosmetics and players spend hundreds of hours gradually filling their collections. Once the game turns cosmetics into rewards, those rewards need to remain collectible.
We saw the opposite side of that equation recently when some Diablo IV players began finding surprise free cosmetics in their personalized shops. A free weapon appearance is fun because the act of receiving it creates permanent ownership. Demonbinder currently performs only the first half of that transaction. The game congratulates you on the drop and then apparently asks you to keep the receipt in your stash indefinitely.
It also creates an ugly incentive around repeat drops. Normally, seeing a cosmetic you already own is largely irrelevant. With Demonbinder, affected players may not technically own it according to the Collection, so another copy looks like another chance to finally unlock the appearance. Then it fails. Then another drops. Before long, the player is preserving multiple copies because nobody knows whether salvaging or discarding them could mean losing the cosmetic permanently if Blizzard eventually repairs the collection state.
There Is No Reliable Workaround Yet
The community has tried the obvious fixes. Restarting the game has not consistently worked. Relogging has not consistently worked. Controller versus mouse makes no difference in the reports we found. Moving Demonbinder into and out of the stash does not suddenly remind Diablo IV that it is Mount Armor. Obtaining another copy also appears useless for many affected accounts. Players who already owned Demonbinder before it disappeared seem to have even fewer options because there is nothing meaningful they can do to recreate the original unlock.
For now, the safest approach is probably to keep at least one unusable Demonbinder in the stash rather than throwing it away. That is not an official Blizzard recommendation, and we cannot guarantee a future fix would require the item to remain present. It is simply the cautious response when the game has successfully awarded a cosmetic but failed to register that award permanently. Inventory space is annoying. Farming the cosmetic again after a fix would be more annoying.
Diablo IV's inventory has already been asked to babysit enough broken rewards recently. Yesterday we looked at Charm Slots that can visibly exist while refusing to accept Charms, while Treasure Breach players have been forced to choose which loot to leave behind when town teleporting fails. Demonbinder contributes its own wonderfully modest variation: please reserve one stash slot for the horse armor you already earned but are not currently allowed to possess.
Four Months Is a Long Time to Keep a Horse Waiting
The scale of Demonbinder's forum history is what makes the problem worth revisiting now. This is not one player who misread a tooltip. The largest thread has accumulated dozens of confirmations, nearly 6,000 views and reports stretching through multiple seasons. Separate threads cover PlayStation, missing previously unlocked copies and new drops that cannot be consumed. The bug has survived from spring into September with no visible Blizzard response or documented fix that we could find.
That does not make Demonbinder the most serious bug in Diablo IV. A Secret Cow Level quest that can stop before delivering the Hadopelagic Key is considerably more damaging to progression. A broken defensive item can kill characters. Missing rewards can affect actual power. Demonbinder merely prevents your horse from wearing an especially nice piece of armor.
But four months is an impressively long time for something this simple to remain broken. The boss knows how to drop Demonbinder. The player knows how to pick it up. The inventory knows how to store it.
Only the Collection seems unaware that Demonbinder exists.
