Back to Blog
VMware
Linux
"Did They Just Kill It Overnight?" The Quiet Panic Around VMware Photon's Disappearing Act
April 24, 2026
4 min read
# “Did They Just Kill It Overnight?” The Quiet Panic Around VMware Photon’s Disappearing Act
## When a 404 Feels Like a Funeral
It starts small. A simple download attempt. A link that used to work suddenly throws a 404. Then another. And another. That’s how the panic creeps in—not with an announcement, but with silence. One user described trying to grab VMware Photon OS, only to find every official link dead, even update repositories returning nothing.
That’s the kind of moment that makes engineers uneasy. Infrastructure tools aren’t supposed to just vanish. They’re supposed to be stable, predictable, boring. When they aren’t, people start asking bigger questions: Is it broken, moved, or quietly abandoned?
And in the absence of clear answers, speculation fills the gap fast.
## “They Killed Everything” vs. “It’s Still There”
The reactions split almost immediately. One side doesn’t hesitate: “Did they kill everything? Yes.”
It’s blunt, emotional, maybe exaggerated—but it captures the mood. For many, this isn’t just about one Linux distribution. It’s about a broader fear that everything under VMware is being reshaped, cut down, or deprioritized.
But then there’s the other side, calmer and more measured. Some users point out that Photon isn’t gone—it’s just moved. The URLs changed, now pointing to Broadcom-hosted infrastructure instead of VMware domains. Swap out the old links, and things start working again.
From that perspective, nothing died. It just relocated. Messy? Sure. But not catastrophic.
The problem is, both sides are reacting to the same experience—confusion.
## Migration Without a Map
Here’s where things get tricky. Even if Photon OS still exists, the transition hasn’t exactly been smooth. Links breaking without redirects, repositories going dark, documentation lagging behind—it creates the impression of abandonment, even if that’s not the intention.
One user casually noted, “all the URLs got moved over,” as if it’s obvious.
But for anyone outside that loop, it’s anything but obvious. There’s no big banner saying “we moved.” No clear migration guide. Just trial and error, guesswork, and community breadcrumbs.
And in enterprise environments, that kind of ambiguity isn’t just annoying—it’s risky. Teams rely on these systems for production workloads. They need clarity, not detective work.
## The “It Was Already Dead” Argument
Then there’s a third angle that’s less emotional and more technical: maybe Photon wasn’t in great shape to begin with. Some voices suggest the project has felt stagnant for a while, pointing to slow development or lack of visible progress.
“It’s been dead for a while,” one comment claims, referencing stale activity.
But even that gets challenged. Others counter that active branches still show recent commits, meaning development hasn’t stopped—it’s just not happening where people expect to see it.
This creates a weird split perception. Depending on where you look, Photon is either quietly maintained or slowly fading away. Same project, different signals.
## The Trust Problem Nobody Talks About
Underneath all of this is something bigger than Photon OS itself: trust. When a company changes hands, users expect changes. But they don’t expect confusion.
One sarcastic comment nails the tension: “why would the company who bought another company keep the name the same?”
It’s a joke, but it points to a real issue. Branding, URLs, infrastructure—these aren’t just cosmetic details. They’re how people navigate and trust a platform. When they shift without warning, it feels like the ground is moving under your feet.
And once that trust starts to crack, every small issue feels bigger than it is.
## Exit Strategies Start Quietly
While some are still trying to figure out what’s going on, others have already made a decision: move on. A few users mention switching to alternatives like Flatcar, Fedora CoreOS, or even Amazon Linux.
Not because Photon is definitively dead, but because it feels uncertain.
“Our dev-ops guys felt that Photon wasn’t being maintained,” one comment explains, describing a quiet migration away from the platform.
That’s how these shifts happen. Not with dramatic announcements, but with gradual exits. One team leaves, then another, until the ecosystem starts to thin out.
## So… Is Photon Actually Gone?
Here’s the honest answer: no, it doesn’t look like it’s gone. The files exist. The repositories still function, at least in some form. Development hasn’t completely stopped.
But that’s not really the point.
What matters is how it feels to the people using it. Right now, it feels uncertain. It feels harder to access, harder to trust, and harder to understand. And in tech, perception can be just as powerful as reality.
Because once people start asking, “Did they kill it?”—even if the answer is no—you’ve already lost something important.
Clarity.
Keep Exploring
We Knew This Was Coming: The Quiet Collapse of VMware Loyalty Turns Into a High-Stakes Exit
There's something oddly emotional about ripping out infrastructure that's been around since the late '90s. One engineer described starting a migration away from VMware as...
1,500 VMs, One Wrong Move: The Brutal Reality of Escaping VMware Without Breaking Everything
There's a big difference between migrating a handful of VMs and staring down a number like 1,500. At that scale, this isn't a project—it's a gamble with real consequences. The...
"We're Finally Leaving… But At What Cost?" The Raw, Messy Reality of Breaking Up with VMware
There's something oddly honest about week one of a migration. No polished case study, no vendor-approved success story—just a running list of things that worked, things that...
It Was Supposed to Be Fine: Inside the VMware Renewal Rollercoaster No One Can Predict
There's something oddly revealing about relief. Not excitement, not satisfaction—just relief. One IT admin summed up their renewal experience in a way that feels almost too...