Leaving VMware Just Got Harder After Broadcom Pulled VDDK Downloads

Just when we thought that Broadcom wouldn’t be able to slow down customers moving off of vSphere to another platform. They may just now have done something that will have that net effect. This time it involves VMware’s Virtual Disk Development Kit, which we have always known as the VDDK. Broadcom has just killed the download of this library, and it will have far reaching consequences if this is a permanent move. Let’s see why this is a cause for alarm and why the VDDK is so important. What is the VMware VDDK? If you have never personally downloaded the VDDK you might assume this is some obscure VMware developer package that most just won’t ever need. And, you are right to some extent if you have no need to use the VDDK directly. However, what you might not realize is just how many tools that you probably ARE using that make use of it. Like what? Well, here is the kicker. This library is central to many of the migration tools that are used to migrate from VMware to other platforms. It is used by tools like Microsoft Azure Migrate, Red Hat’s Migration Toolkit, Nutanix Move, VMware to KVM migration products, and other tools like virtv2v and nbdkit. So, for VMware customers who are trying to figure out what life after Broadcom looks like, this is yet another unexpected roadblock to leaving the platform. What exactly did Broadcom change? The reason this suddenly matters is that Broadcom has removed the normal publicly accessible VDDK download pages, and affected customers are reporting that Broadcom support has told them VDDK is no longer available for general use or download. See the Reddit thread here: Broadcom VDDK links : r/sysadmin. If you now navigate to the link of the VDDK download where it was previously, you will see the following 404 page: Even stranger as it would seem, I have been unable to find a traditional Broadcom announcement explaining this change. So far, there has been no transition notice, deprecation announcement, or replacement tool or library announced. Instead of this, many migration vendors and customers have seen in the last few day that links they have been pointed to are suddenly returning errors. This is much more interesting than an SDK just disappear. So, the net effect, no matter what Broadcom’s motivation might be is pretty hard for us to ignore at this point. A VMware technology that is used to move and protect VMware workloads has now become harder for customers and migration vendors to get their hands on. For many customers who may be looking at their exit path from VMware, this feels like just another obstacle placed in the exit path from the platform. Evidence of changes to VDDK access The company ShapeBlue has documented the change as of August 25, 2026. They discovered that the VMware VDDK pages referenced in the VMware to KVM migration documentation were returning error. They then went on to test numerous VDDK URL paths that included version specific paths for VDDK 8 and 9. However, both versions are showing to be unavailable. ShapeBlue documented the change on August 25, 2026, after discovering that the VMware VDDK pages referenced by its VMware-to-KVM migration workflow were returning errors. ShapeBlue tested numerous VDDK paths, including version-specific locations for VDDK 8 and 9, and reported that all of them were unavailable. You can read ShapeBlue’s detailed announcement on the VDDK removal here: Broadcom Removes VDDK Pages Without Explanation: What You Need to Know. They made the observation that Broadcom has not published a public announcement where they explain the reasoning behind this being removed, withdrawn, or deprecated. Very interesting. Broadcom support has seemingly confirmed this was intentional One of the strongest pieces of evidence we have so far that this is an intentional withdrawal of the bits for the VDDK comes from Broadcom customers who have opened up support cases. You will find the discussion on the Reddit thread interesting. A customer posted the response they received directly from Broadcom Customer Care. The customer on the Reddit thread reported that Broadcom told them the VDDK was “no longer available for use or download“. They also pointed the customer back to backup and recovery products from authorized Broadcom Technology Alliance Partners. Again, read this for yourself on the Reddit thread here. There is another recent Reddit discussion on the official VMware Reddit thread’s subreddit on the topic. Users there are reporting the same thing. One admin said they opened a ticket with Broadcom and were told by support the VDDK had been intentionally removed and was no longer available through the previous method. Another discussion in the VMware subreddit contains users reporting essentially the same thing. One administrator said they opened a ticket with Broadcom and support confirmed VDDK had been intentionally removed and was no longer available through the previous method. Read the VMware community discussion in this sub Reddit here. The post was recently removed by VMware moderators but you can still see the comments on the thread here: [ Removed by moderator ] : r/vmware. So, I think the writing is on the wall here that it is difficult for us to just chock this up to some sort of website glitch where the VDDK has disappeared. Microsoft has already changed its documentation on VMware migration However, we may have even stronger evidence from an equally large company as Broadcom, Microsoft. Microsoft has now updated its guidance on the Azure Migrate process and its agentless migration of VMware workloads over to Azure. Historically, Microsoft documentation has instructed admins to install VMware VDDK on the Azure Migrate appliance. Now though, Microsoft has added a disclaimer or warning to their official guidance that Broadcom may restrict access to the VDDK. So, basically, they are saying if you can’t get your hands on the VDDK, then you need to use the agent-based migration instead of the agentless migration method. So, this helps to put the nail in the coffin on the question of whether or not this is a real development or not. You can read the full Microsoft guidance here: Set up an Azure Migrate appliance for server assessment in a VMware environment. Red Hat customers have the same roadblock Red Hat has also published a support article on August 27, 2026, which you can find here: Unable to download VMware VDDK images for Migration Toolkit for Virtualization (MTV). So, this is also an issue for organizations migrating VMware workloads into OpenShift Virtualization. The KB says that customers may receive a “not found” or “access denied” error. Since the software is proprietary to Broadcom, Red Hat is saying they can’t host or redistribute the package itself. So, they are simply asking customers to contact Broadcom support to request access. Because VDDK is proprietary Broadcom software, Red Hat says it cannot host or redistribute the package itself. Red Hat looks to also be investigating long term alternatives to remove or work around the dependency on the VDDK. Red Hat Engineering is also investigating longer-term alternatives to remove or work around the dependency. They make mention of using something like a storage copy offload, but this will depend on the underlying storage vendor and its capabilities. Nutanix Move impacted So, yet another environment that is affected by this is Nutanix. Nutanix customers have now hit this snag as well. A Nutanix community user has noted that they were preparing a migration from ESXi to AHV with the Nutanix Move utility but they found that the VDDK link gave them a 404, even after they logged into their Broadcom account. Read my blog on the Nutanix Move utility here: Nutanix Move: Migrate from VMware ESXi Free Download. The customer in the Nutanix Community post was specifically needing the VDDK 7.0.3.1 and the VDDK 8.0.3.2. You can read the community post here: vSphere VDDK Download for Nutanix Move. There is another discussion that is similar with a customer deploying Nutanix Move to start moving VMs off their existing VMware 8 environment. Broadcom support supposedly told them that the VDDK had moved into VMware’s Technology Alliance Program and you had to be a part of that with the right relationship and support access. You can read that particular post here: VDDK 8.x required for Nutanix Move missing possible issues later. Platform9 is calling this out directly Platform9 is one of the vendors that has called this out very vocally and directly. This is because the vJailbreak project is designed to help organizations migrate off the VMware platform. They published an article just a few days ago (September 1st) that explained that Broadcom had restricted public VDDK access and that its traditional VDDK plus NBD migration is now affected when customers don’t already have the files they need for the VDDK. Check out my blog post on Platform9 here: Platform9 Community Edition Free Download and Install: Migrate from VMware. Platform9 has other alternatives that uses storage assisted migration to move the data onto compatible storage and an “accelerated” option they call it that can use a proxy VM inside VMware to connect more directly to VM storage that doesn’t need the VDDK. Read the Platform9 post here: Broadcom Cut Public Access of Virtual Disk Development Kit (VDDK) Overnight. This “smells” a lot like lock in for VMware customers This is one of those details where the conversation I think is going to get even more uncomfortable for VMware customers. I think there are some very interesting “developments” in the last few days that may point the needle in a certain direction of thought. But I will let you be the judge of this. At VMware World just the past few days, supposedly they have brought back VMware vSphere Standard edition? And, ironically, the VDDK that is used to migrate off the platform has suddenly disappeared. I think so many customers are already having a hard time trying to plan