Diablo Immortal Players Say the Haunted Carriage Sometimes Just Never Shows Up, Which Is a Bold Choice for an Event With “Carriage” in the Name

 

The game announces it. Players run to Ashwold. Then everybody stands there looking silly.

Diablo Immortal has another Haunted Carriage complaint on the board, and this one is almost impressive in how basic it is. In a fresh Blizzard bug report, a player says the game throws up the usual warning that the Haunted Carriage is coming in three minutes, tells everyone to head to Ashwold, and then… no event. No carriage. No boss. No spooky procession. Just a crowd of players showing up on time for a world event that apparently decided not to attend its own appointment.

What players are actually reporting

The report is short, but the hook is clean: this is not being described as a one-off fluke. The player says it does not happen every time, but “like half” of the Haunted Carriage attempts simply do not spawn. That is what makes it a usable story. If the event notification fires and players respond the way the game expects, only for the event itself to ghost them, then the whole loop starts to feel less like scheduled content and more like Sanctuary’s least reliable bus service.

It also fits a broader Haunted Carriage pattern

This is not even the first Haunted Carriage-related headache Diablo Immortal players have been dealing with lately. Blizzard’s own Bug Report board showed multiple Haunted Carriage threads active around April 6–7, including the new non-spawn report and other recent complaints tied to Haunted Carriage progress. There was also a separate March report about the Horrid Haunted Carriage event notification not taking players to the event, which Blizzard marked resolved, plus older threads where players said Haunted Carriage kills or completion were not registering properly. So even if this specific non-spawn issue is new, the broader Haunted Carriage track record is not exactly clean.

Why this matters more than it sounds

A world event bug like this is not as dramatic as a login failure or vanishing paid bundle, but it is exactly the kind of thing that makes a live-service game feel sloppy. Diablo Immortal is built on timers, routines, and quick little loops where players jump in, knock something out, and move on. If the game pings the server with “event’s up” energy and then serves empty cemetery air, people notice fast. And right now, Diablo Immortal is not exactly short on trust issues. We already covered the shop loading bug that keeps blocking rewards, the Battle.net purchase bug where claimed bundles can vanish,  and the Party Finder bug that hides activities. Another event acting weird is not catastrophic on its own, but it absolutely adds to the “what is broken today?” mood.

The weird little problem with event-based games

The funniest part is that this is the sort of bug that makes players feel foolish more than angry at first. They got the prompt. They went where the game told them to go. They did the responsible little live-service thing. And then Diablo Immortal basically left them standing in Ashwold waiting for a ghost cart that never arrived. If more players start reporting the same thing, this could turn from a stray annoyance into a very real event-reliability problem. For now, it is one of those wonderfully dumb bugs that sounds fake right until it wastes your evening.

Read More

Diablo Immortal Players Say Party Finder Is Hiding Activities, Which Is Kind of the One Job Party Finder Has

 

“All Difficulties” apparently means “some of them, probably”

Diablo Immortal has a new bug report making the rounds, and this one is not flashy enough to melt a server or eat a paid bundle. It is just the sort of quietly stupid interface problem that can make a live-service game feel sloppier than it should. In a fresh Blizzard forum post titled The Raid / Party Finder does not properly list all available activities, a player says the Party Finder shows seven activities under All Difficulties, but when filtering by specific difficulty, only three of those activities actually appear. That is less “finder” and more “vague suggestion engine.”

What the report says is going wrong

The breakdown in the report is pretty clean. The player says the full list included activities across Normal, Hell 1–3, and Inferno 1–12. But once they used the difficulty selector, Normal showed only one of the three listed activities, Hell showed none of the one it should have shown, and Inferno showed only one of three. If that is working as described, the filter is not really filtering. It is dropping entries on the floor and hoping nobody notices. Unfortunately for Blizzard, somebody did.

Blizzard has already acknowledged it

This is where the story gets a bit stronger. In the same thread, Blizzard community manager jadaiyuki-1776 replied, called it an “interesting find,” and said they would pass it to the team. That is not a fix, obviously, but it does mean this is already beyond the “one person yelling into the bug-report void” stage. The report is also visible on Blizzard’s current Diablo Immortal bug-report board, where it was listed among the active April 7 topics.

Why this matters more than it sounds

A broken Party Finder is not as dramatic as a login failure or missing paid items, but it is the kind of thing that quietly wastes people’s time. If players are trying to jump into raids or activities and the game is not actually showing the full list it claims to show, then the whole tool becomes less trustworthy. And right now, that is not exactly great timing for Diablo Immortal, considering we have already covered the shop loading bug that keeps blocking rewards and the Battle.net purchase bug where claimed bundles never arrive. A party tool that cannot count properly is not the biggest problem on the board, but it is very much part of the same “why is this so messy?” energy.

A small bug can still make the game feel amateurish

That is really the hook here. Diablo Immortal lives on routines: queue up, group up, get in, get rewards, repeat. So when the interface starts hiding parts of the queue list depending on how you filter it, it makes the whole system feel a little dodgy. Not catastrophic. Just shabby. And in a game this obsessed with frictionless daily loops, shabby is its own kind of problem.

Read More

Diablo Immortal Players Say Battle.net Purchases Are Vanishing After Claim, Which Is About the Worst Bug a Shop Can Have

 

Click claim. Watch it disappear. Receive absolutely nothing. Great system.

Diablo Immortal has a fresh monetization mess on its hands, and this one is about as subtle as a brick through a cathedral window. Across several new Blizzard forum reports, players say they are buying bundles through Battle.net, getting the in-game prompt to claim them, clicking the button, and then watching the purchase vanish without the items ever reaching inventory. That is not a pricing complaint or another argument about value. That is the digital version of paying for a bag of loot and having the cashier eat it in front of you.

The reports are lining up a little too neatly

What makes this story stronger than one angry spender post is how consistent the complaints look. In one bug report about Battle.net purchases not redeeming, a player says they bought bundles, hit claim, and got none of the items. In another thread, a Rift Delver’s Hoard purchase reportedly disappeared the same way. A third report says a Wayfarer’s Crate purchased three days earlier never showed up in inventory or even in the in-game log after being claimed. Different bundles, same magic trick: now you see it, now Blizzard support has a ticket.

This is not stuck on one device type either

That is the ugly part. Blizzard’s current Diablo Immortal bug-report board shows multiple active purchase-delivery threads across both iOS and Android, including “Purchases from battle.net is not delivered in a game!”, “Bundle purchase was not delivered!”, and “Battle store items weren’t added to my inventory.” So this does not look like one cursed phone having a bad week. It looks like a wider claim-and-delivery problem that players are running into across more than one platform.

Players say support knows, but the items still are not there

Several of the follow-up replies are saying basically the same thing: support is aware, but affected players are being told to wait for a developer-side fix and watch the forums or patch notes. That is not a great answer when the missing goods are tied to real-money purchases, with one player claiming they are out around $500 in bundles and another saying their $199.99 purchase simply evaporated after the claim click.

If Diablo Immortal’s shop loading bug already made the store feel shaky, and the recent server-list login issue made access feel unreliable, this one hits even harder: players are now questioning whether paid items will actually arrive at all. That is the kind of live-service headline no game wants.

Read More

Diablo Immortal’s Shop Loading Bug Has Been Hanging Around So Long It’s Starting to Look Intentional

 

The store is loading. It is always loading. It may be loading forever.

Diablo Immortal has plenty of familiar live-service annoyances by now, but one of the stranger ones is also one of the most stubborn: the in-game shop that just sits there and spins like it forgot why it was opened. The bug is not new, and that is exactly why it is suddenly worth writing about. A fresh April 3 bug report says the shop keeps loading long enough to block daily rewards and Prodigy’s Path, while older reports show the same problem has been floating around since at least December and really picked up steam in January.

This is not just a “can’t buy things” problem anymore

That is what makes it a better story than the usual “cash shop broken lol” headline. In the newer reports, players are not just complaining about purchases. They are saying the broken shop is stopping them from collecting things the game itself keeps nudging them toward, including free daily bundles and Prodigy’s Path rewards. In the long-running January shop loading thread, one player flat-out says “all DI users must enter the shop at least once a day” because of the free daily reward flow. That turns the shop from optional monetization window into a weird little mandatory hallway the game keeps forcing people through.

Players say the bug has gone from intermittent to downright petty

The pattern across the reports is not especially flattering. A March technical support post describes the shop loading only around 10 percent of the time on one device, while other players say reinstalling, clearing cache, and restarting the game do little or nothing. In the larger master thread about the shop getting stuck on “Loading…”, one player says the issue used to be random but is now basically permanent, while another says they missed daily rewards completely after the shop stayed broken for 20 hours. That is not a cute glitch. That is the kind of bug that quietly turns routine login habits into a chore.

The really annoying part is how inconsistent it sounds

Some reports are on Android. Others are on PC. One player says the shop fails on PC but works on mobile over the same Wi-Fi, which makes the whole thing sound less like one clean device-side issue and more like a messy backend or client handshake problem that nobody has pinned down publicly. That is an inference, not a confirmed diagnosis, but it fits the reports better than the classic “have you tried rebooting?” shrug. And when a bug hangs around for months in a game this obsessed with daily loops, people are going to notice. Loudly.

A bug like this lands badly in a game built on routine

Diablo Immortal trains players to check in, collect, claim, and move on. So when the shop becomes the jammed front door for that whole ritual, the frustration makes sense. This is not the flashiest Diablo story of the week. It is just one of those classic live-service embarrassments where the thing designed to be opened constantly is the thing that will not open.

Read More

Diablo Immortal Players Say a Login Bug Is Hiding Server Lists, and Blizzard Is Still Investigating

Diablo Immortal has a new kind of problem on its hands, and it is not the fun sort where a boss drops too much loot by accident. Over the past week, multiple players have reported that the game successfully logs them into Battle.net, shows the usual “tap to play” prompt, and then simply refuses to display a server name, which means they cannot get to character select at all. The reports showed up first in late March and were still active on April 5.

What players are actually seeing

The most common version of the issue is brutally simple: the login works, but the server list does not. Players in Blizzard’s Diablo Immortal forums describe restarting the game, repairing the client, uninstalling and reinstalling, and still getting stuck on a blank server section. One player said the issue had dragged on for more than 10 hours at one point, while others said they had lost several days of playtime.

It started looking like an iOS problem

The early reports were heavily tied to iPhone and iPad users. Blizzard’s Technical Support and Bug Report sections both show active iOS-tagged threads for the same issue, and affected players listed devices including iPad Pro, iPhone 15, and iPhone 14 Pro Max. The game versions reported in those threads center on the 4.3.0 branch that followed Diablo Immortal’s recent The Taking update.

The weird workaround makes this even stranger

The most interesting detail is that several players say they can sometimes get in over cellular or by using a hotspot, but not over home Wi-Fi. One player said they could log in on LTE and then switch back to Wi-Fi after getting into the game. Another thread participant suggested the issue might involve how the client reaches game servers after authentication, although that part remains community speculation rather than an official explanation.

Blizzard has at least acknowledged the problem

This is the part that matters. In the forum thread, Blizzard community manager Kalviery asked affected players to provide device, OS version, game version, location, and internet provider details so the Immortal team could investigate. Players in the same discussion also shared a support response saying the issue is known and under investigation, though Blizzard has not posted a public fix yet.

Right now, this is a login problem with real collateral damage

That is what makes it worth watching. A bad balance patch annoys people. A login bug keeps them out of events, battle pass progress, clan activity, and the rest of the daily treadmill Diablo Immortal is built around. When a live-service game cannot reliably get players from login to character select, that is not background noise. That is the game failing at the front door.

Read More

Diablo Immortal Players Are Still Reporting Shop and Gem Issues After Patch 4.3

Diablo Immortal Patch 4.3 brought in The Taking, a new story chapter, PvP updates, Rocky Waste, new Legendary Gems, and a long list of feature changes. But while the official spotlight is all about content, Blizzard’s current support and bug-report forums suggest some players are still dealing with a more frustrating side of the update: missing gems and shop-loading problems that have not gone away yet.

The reason this is worth a fresh follow-up is simple. This is no longer just a “post-patch hiccup” angle from launch day. Blizzard’s Diablo Immortal forum listings on March 22, 2026 are still showing active threads like “Lost at least 4 legendary gems after patch,” “Shop tab won't load,” and “Shop still will not load please help.” That makes this feel less like one isolated complaint and more like a continuing support-cluster story.

What players are reporting right now

The current Android-tagged Blizzard forum page is a pretty blunt snapshot of the problem. On the same March 22 listing, it shows “Lost at least 4 legendary gems after patch” under Technical Support, “Shop tab won’t load” under Bug Report, and “Shop still will not load please help” with activity from March 21. It also shows another related gem complaint, “Gem disappeared after gem power transfer,” which suggests the gem side of the problem is not limited to one exact scenario.

That does not prove all of these reports share one cause. It also does not prove every affected player is experiencing the same issue in the same way. But it does support one careful conclusion: fresh, current Blizzard forum traffic is still surfacing gem-loss and shop-access complaints after Patch 4.3 went live.

Why this matters more than a normal support thread

Some support stories stay small because the underlying issue feels minor. Gem complaints usually do not.

Legendary Gems are one of Diablo Immortal’s most important progression layers, and Patch 4.3 itself added new Legendary Gems like Leviathan Tomb, reinforcing how central gem systems remain to the game’s current design. That means a player report about gems vanishing after the patch naturally lands harder than something like a misaligned tooltip or a cosmetic glitch.

The shop complaints matter for a different reason. Even players who are not actively trying to buy something tend to read a broken or non-loading shop tab as a sign that the client is unstable in visible, user-facing ways. When those complaints sit next to gem-loss reports on the same current support pages, the overall picture starts to look rougher than “one unlucky bug post.” This is an inference based on the forum pattern and the types of systems involved.

Patch 4.3 is clearly live, but so are the complaints

Blizzard’s official Patch 4.3 article confirms the update is now live and frames it as a major 2026 content step, centered on The Taking, the Rocky Waste, PvP refreshes like Siege of Corvus and Challenge of Equals, new Legendary Gems, and multiple events and quality-of-life updates.

That is what makes the support angle more interesting, not less. On paper, Patch 4.3 is a big content push. In practice, at least some current forum users seem more focused on whether their gems are still there and whether the shop loads at all. That disconnect is often what defines a rough patch rollout: the official headline says “look at all this new stuff,” while parts of the player base are stuck asking why core interfaces and progression items feel unreliable. This is an inference based on the official patch scope versus the current support listings.

This still looks like a support-cluster story, not a confirmed universal failure

It is important to keep the framing clean.

The evidence here supports multiple fresh player reports on Blizzard’s own forums. It does not support saying Blizzard has confirmed a universal gem-loss issue across all players, nor that every shop-loading problem is tied to one single verified root cause. The right read is narrower: the complaints are still visible and current after Patch 4.3, and they span both gem-related progression concerns and storefront access.

That is still enough for a useful article, especially because readers care about whether the issue is still active. In this case, the answer appears to be yes: these threads are still sitting in Blizzard’s March 22 forum listings, which is a stronger signal than a one-day flare-up that vanished immediately.

Why this is worth a late-night follow-up

This kind of follow-up works because it answers a practical question players often have after a patch story: did those issues fade out, or are they still happening?

Based on Blizzard’s current support pages, at least some of the gem and shop complaints are still there right now. That makes the angle timely and useful without overstating what Blizzard has or has not formally acknowledged.

If Blizzard resolves these quickly, they may end up as short-lived Patch 4.3 footnotes. If not, they risk becoming part of the update’s reputation, especially because gems and shop access are exactly the kind of high-visibility systems players notice immediately when something feels off. 

Read More

Diablo Immortal Players Are Reporting Fresh Gem and Shop Problems After Patch 4.3

 

Diablo Immortal Patch 4.3 added plenty of new content, but the technical support and bug-report forums suggest some players are having a much less exciting experience with the update. Alongside the PC client issues already making the rounds, a separate cluster of fresh reports is now pointing at missing gems, gem-related inventory problems, and shop access failures.

The most notable part is that these are not all the same complaint. Blizzard’s Diablo Immortal support listings from March 20–22 currently show threads titled “Lost at least 4 legendary gems after patch,” “Lost All 2 Star Gems,” “My gems are gone afrer replaced it,” and “Shop still will not load please help,” along with a fresh bug-report entry called “Shop tab won't load.” That does not prove one giant shared bug, but it does show that post-patch support traffic is surfacing multiple gem and storefront issues at the same time.

What players are reporting

The current technical support page is doing a lot of heavy lifting here. Blizzard’s own listing shows an Android support thread titled “Lost at least 4 legendary gems after patch” from March 20, while the PC-tag listings show “Lost All 2 Star Gems” on the same date. On the bug-report side, there is also a March 20 topic titled “My gems are gone afrer replaced it.”

Meanwhile, the shop side of the equation is not looking much cleaner. The technical support listings show “Shop still will not load please help” from March 21, and the bug-report forum now also includes “Shop tab won't load” dated March 22. Those titles alone do not tell us every device condition or exact failure mode, but they are clear enough to establish the main point: some players are reporting that either the storefront itself is inaccessible, or key parts of it are not loading as expected.

This looks like a support-cluster story, not one single confirmed bug

That distinction matters.

Right now, the evidence supports a cluster of fresh player-reported issues rather than one neat official diagnosis. The gem reports are not all worded identically. One says legendary gems were lost after the patch. Another says all 2-star gems were lost. A third suggests gems disappeared after a replacement action. The shop complaints are also split between a general “still will not load” support post and a bug-report thread specifically about the shop tab failing to load.

So the cleanest framing is not “Patch 4.3 deleted everyone’s gems and broke the store.” The cleaner framing is that Blizzard’s own forums are showing several fresh post-patch support complaints around gems and shop access, and together they paint a rough picture of technical friction that goes beyond one isolated thread.

Why gem complaints hit especially hard

Not all support stories carry the same weight. Gem-related complaints tend to hit a nerve faster than many other bugs because Legendary Gems are one of the game’s most valuable progression layers.

When players think gems have vanished, even temporarily, that feels a lot more serious than a broken tooltip or a UI hiccup. Some gem systems in Diablo Immortal are tied directly to upgrades, long-term builds, and in some cases monetized progression decisions. That means even a relatively small number of gem-loss reports can feel much bigger in community terms because the perceived stakes are higher. This is an inference based on the role Legendary Gems play in Diablo Immortal progression and the way the reports are titled.

The shop complaints land similarly hard for a different reason. Even if a player is not trying to spend money, a store tab or shop feature that fails to load makes the game feel unstable in a very visible way. And if players are trying to claim, buy, or check something specific, a dead shop interface becomes more than an annoyance very quickly. This is also an inference based on the type of issue being reported.

This fits a broader post-patch pattern

These gem and shop reports do not exist in isolation.

As of March 20–22, Diablo Immortal’s current forum listings also show other fresh technical and bug-report issues around PC client behavior, missing NPCs, event progression, and performance hiccups. That does not mean everything is connected to one root cause, but it does suggest Patch 4.3’s rollout period has been noisy on the support side. In that environment, gem and shop complaints feel even more important because they stack on top of an already messy player-support picture.

No clear public fix yet

Based on the sources reviewed here, there is not a visible official Blizzard post that cleanly says these gem-loss or shop-loading issues are resolved, nor one that groups them into a confirmed known-issues notice. That means the safest and most accurate read is still the cautious one: these are fresh player-reported post-patch support problems visible on Blizzard’s own Diablo Immortal forums.

That may sound like a small wording choice, but it is important. There is a big difference between “players are reporting this right now” and “Blizzard has confirmed a broad failure.” The current evidence strongly supports the first statement. It does not yet fully support the second.

Why this is worth covering

This is the kind of story that tends to matter more than its forum size suggests.

A flashy patch feature gets the headlines, but support-cluster issues are what shape how a patch actually feels for the people logging in. If a player thinks they lost valuable gems, or cannot even get the shop to load, they are probably not spending much time admiring the finer points of the update’s design. They are just trying to figure out what broke and whether it is safe to keep interacting with the system. That is an inference based on the kinds of issues being reported.

If Blizzard clears these issues up quickly, this may end up as a short-lived support spike. If not, it risks becoming one of those awkward post-patch footnotes where the content itself looked solid, but the technical side kept stealing the spotlight.

Read More

Diablo Immortal Players Say They Cannot Claim Midnightmoon Rewards After Completing the Required WoW Quest

Diablo Immortal’s latest crossover-style reward tie-in is generating a small but notable wave of frustration, with fresh player reports saying they completed the required World of Warcraft quest but still cannot claim the related reward in Diablo Immortal.

The clearest examples are two Blizzard forum bug reports from March 21. One PC-tagged topic is titled “Cant claim the Event ‘Midnightmoon’ with finished World of Warcraft Quest,” while a second iOS-tagged thread says the player completed the Paved in Ash quest in WoW but gets the message: “This account does not meet the unlock criteria. Please try again later.” when trying to claim Harbinger of Darkness in Diablo Immortal.

That does not prove a broad system-wide failure affecting every eligible player. But it does make this one of the more interesting fresh Diablo Immortal stories because it hits a very specific promise: do the required thing in one Blizzard game, get the reward in the other. When that chain breaks, players notice fast.

What players are reporting

The current public reports are fairly consistent in tone.

In the PC-tagged Blizzard forum listing, a fresh March 21 bug post says the player cannot claim the Midnightmoon event reward despite having finished the required World of Warcraft quest. Separately, the iOS-tagged bug report gives more detail, saying the player completed Paved in Ash in WoW but still cannot unlock Harbinger of Darkness in Diablo Immortal because the game says their account does not meet the unlock criteria.

That wording matters because this does not sound like a player being unsure where to click. It sounds like the reward handoff itself may not be recognizing completed eligibility in at least some cases. That is still a player-reported issue, not a confirmed Blizzard diagnosis, but it is a more specific complaint than a vague “event is bugged.”

The crossover requirement seems clear enough

While Blizzard’s own Diablo Immortal news feed visible in search results does not surface a dedicated official Midnightmoon article in the sources reviewed here, secondary coverage from late February described the promotion as a crossover unlock tied to World of Warcraft. MMORPG.com reported that players with access could log into WoW and complete a quest in Midnight’s hub, Silvermoon City, to earn Harbinger of Darkness in Diablo Immortal. Reddit discussion around the reward also centers on Harbinger of Darkness as the Midnight Moon event reward.

That does not replace a primary-source Blizzard step-by-step guide, and I would not lean on it to prove every exact requirement. But it does support the basic shape of the player complaint: this appears to be a cross-game reward flow, and players believe they completed the WoW side correctly before the Immortal claim failed.

Why this kind of issue lands harder than a normal event bug

A regular event problem is annoying. A cross-game reward issue feels riskier because it asks players to spend time in one ecosystem while trusting another one to honor the reward.

That is the core frustration here. If a player completed a quest in WoW specifically to unlock something in Diablo Immortal, and the claim button then tells them they do not qualify, the problem is not just inconvenience. It creates doubt about whether the promotion is tracking correctly at all. That is an inference based on the structure of the reported issue and the wording in the bug reports.

It also creates a more stressful kind of uncertainty than a normal in-game quest bug. The player in the iOS-tagged report explicitly says they cannot redo the quest in WoW, which raises the obvious follow-up question: if the requirement only happens once, what exactly is the recovery path when the linked reward does not trigger?

This looks like a fresh support angle, not a giant meltdown

The scale matters here.

Right now, the evidence supports multiple fresh official-forum bug reports, not a confirmed widespread event collapse. The Midnightmoon issue appears in Blizzard’s current bug-report listings and PC-tag listings for March 21, but it is not sitting at the center of a huge public acknowledgment or a major official warning in the sources reviewed here.

So the cleanest framing is this: some Diablo Immortal players are reporting that the Midnightmoon reward claim is failing even after they believe they completed the required WoW quest, and those reports are now visible on Blizzard’s own bug forums. That is enough for a fresh article. It is not enough to claim Blizzard has confirmed a large-scale event failure.

Why this is worth covering now

This is exactly the kind of Diablo Immortal story that can get overlooked because it is smaller than a major patch headline and less flashy than a new PvP system or class reveal.

But reward-claim problems tied to outside requirements tend to matter a lot to the players affected by them. They are also the kind of issue that can spread quickly through community discussion because the complaint is easy to understand: I did the thing in WoW, so why won’t Diablo Immortal give me the reward? That is an inference based on the nature of cross-game promotions and the current bug reports.

If Blizzard resolves it quickly, this may end up as a short-lived support hiccup. If not, it could become one of those awkward crossover stories where the promotion itself sounds cool, but the handoff between games becomes the part people remember. 

Read More

Diablo Immortal Players Are Reporting Fresh PC Client Problems After the March 18 Patch

Diablo Immortal Patch 4.3 brought a lot of new headline features, from The Taking story content to PvP updates, new Legendary Gems, and quality-of-life changes. But while most of the official coverage has focused on what was added, some players are already talking about something less exciting: the PC client itself.

Over the last day, fresh Diablo Immortal forum posts have pointed to a small but notable cluster of post-patch PC problems, including keyboard controls failing to initialize properly, multiple in-game issues after the March 18 release, and even reports of the PC client trying to re-patch itself with a very large second download. None of that automatically proves a single widespread PC meltdown, but it does suggest that Patch 4.3’s rollout has not been completely smooth for everyone on desktop.

The cleanest new complaint is a keyboard controls bug

One of the clearest current reports comes from a March 20 Diablo Immortal bug thread titled “Keyboard bindings not initializing.” In that post, a player says that after the recent patch, their keyboard controls are not being initialized when the game starts. According to the report, opening the in-game settings and visiting the controller tab temporarily fixes it, which makes the issue sound less like a permanent total failure and more like a broken startup state on PC.

That may sound minor compared with a crash or a hard disconnect, but control initialization bugs are the kind of issue that instantly make a PC client feel shaky. If players have to poke around menus just to get their basic inputs working properly, the patch starts to feel a lot less polished than the feature list suggests. This is an inference based on the type of bug being reported.

Another player says the March 18 patch brought multiple in-game PC issues

The keyboard report is not standing alone.

A separate forum thread posted after the March 18 patch release is titled “Multiple InGame issues - PC Client - Post March 18 Patch Release (Americas).” The available forum snippet shows the player saying the problems persisted even after both a Battle.net Scan & Repair and a game load screen repair, which suggests they had already tried the most obvious first-line fixes before posting.

The snippet does not expose every listed problem in full, so it would be overstating things to claim Blizzard players are all seeing the exact same symptoms. But the thread is still useful because it shows that at least some PC users are treating the post-patch problems as more than a one-off local setup issue. They are specifically tying them to the March 18 patch window and to the PC client.

There is also a strange re-patching complaint

One of the more awkward reports involves patching itself.

In another recent Diablo Immortal PC forum thread, a player says the client downloaded the initial update, then later attempted to apply another much larger patch after they exited the game. The post describes a second update ballooning into a 15.19 GB re-patch after the first installation. That is just one report, so it should not be treated as a confirmed universal launcher issue, but it is the kind of thing that tends to get player attention quickly because it feels so obviously wrong when it happens.

If a content update is supposed to get players into the game faster, a surprise giant second download is pretty much the opposite experience.

The forum activity suggests this is part of a broader PC-side rough patch

The strongest reason this story feels worth covering is not one thread by itself. It is the pattern.

The Diablo Immortal PC and bug-report forum listings from March 20–21 show a cluster of fresh PC-related topics, including the keyboard bindings thread, the multi-issue post-patch thread, the re-patching thread, tooltip behavior issues, and a shop problem thread. That does not prove one shared root cause, but it does show that desktop users are actively surfacing a number of current problems in the same immediate post-patch window.

That makes this a better story than a plain “one angry player had a bad time” post. The available evidence supports a more cautious conclusion: some Diablo Immortal PC players are running into fresh issues after Patch 4.3, and those complaints are visible across multiple current forum topics.

This is not the same as saying Patch 4.3 is broken

That distinction matters.

Officially, Patch 4.3 is still a major content update centered on The Taking, the Rocky Waste zone, PvP revisions like Siege of Corvus and Challenge of Equals, new Legendary Gems, and other system changes. Blizzard’s own announcement is focused on those features, not on a public warning that the PC client is unstable.

So the careful read here is that the content update itself is real and live, while some players are also reporting fresh desktop-client problems around the same release. That is a more accurate framing than jumping straight to “Patch 4.3 broke the PC version.” The forum evidence supports the existence of current complaints, but not a confirmed Blizzard statement that the PC client is broadly compromised.

Why this overlooked angle matters

This is exactly the kind of post-patch story that often gets missed because it is less glamorous than new content and less explosive than a major monetization debate.

But for players on PC, these issues can matter more in the short term than whatever new activity or event just went live. New quests and PvP updates are great. They matter a lot less when your controls are not loading correctly or your client is acting like it wants another double-digit gigabyte snack before you can play. That last part is an inference based on the player reports and the kind of friction they describe.

If Blizzard responds quickly, this may end up being a brief rollout stumble that fades by next week. If not, it could become one of those quiet PC-client frustration stories that does not dominate the patch headlines but absolutely shapes how the patch feels for the people actually trying to log in and play it. 

Read More