Fix it now
Microsoft’s published cause for 30053-4 and 30053-39 is narrow and specific: you are installing a Microsoft 365 language pack and you do not have the correct version of Microsoft 365 installed. The order is fixed – the matching Office build first, the language pack second. On Visio deployments that usually means the Visio configuration does not match the Office already on the machine.
setup.exe /configure configuration.xml
- Open Word or Excel on the machine and read File, then Account, then About. Note the product, the version and the update channel exactly.
- Open your configuration XML and make the Visio Product entry match: same channel, same OfficeClientEdition, and languages that exist for that build.
- Put Office and Visio in the same Add element of one configuration so they share a single Click-to-Run image, then run the command above.
- Once Visio opens, check File, then Account. An unlicensed state there means the deployment worked and the entitlement is the separate problem.
Language ID=”MatchInstalled” cannot be used with the /download switch, and needs at least one Click-to-Run product already installed. It is a configure-stage setting, not a way to fix a failing download.
If Visio installs and opens licensed you can stop here. If it installs and reports no licence, the next sections cover both halves of that.
Why it happens
There are two quite different problems hiding behind this code on Visio deployments, and they need separating before anything else. The first is the code itself. Microsoft documents 30053-4 and 30053-39 on one page with one cause: a Microsoft 365 language pack is being installed without the correct version of Microsoft 365 present. The remedy Microsoft gives is a single sentence – install Microsoft 365 before you install a language pack.
On a Visio deployment that arrives in a particular way. Visio is usually added to an estate later than Office, by a different configuration XML, sometimes pointed at a source path somebody else built. If that configuration names a language, a channel or a version the installed Office does not have, setup is being asked to lay a language pack down without the matching build behind it, and this is the code you get.
The second problem is entitlement, and it is not what this code reports. The Office Deployment Tool installs whatever product you name and does not check whether anyone is entitled to it. Deploy Visio to a hundred machines with no Visio seats and all hundred install correctly and none activate. That failure appears after a successful installation, in File, then Account, not as a setup code.
One piece of documented behaviour saves a lot of time here. MatchInstalled, which sounds like exactly the right answer for a language mismatch, cannot be used with the /download switch and only works when at least one Click-to-Run product is already installed. It belongs in the configure stage on a machine that already has Office. Putting it in a download configuration does not fix the download; it makes the configuration invalid.
The language pack has no matching Office build behind it
You have this one if The failure names a language pack, or the configuration adds a language to a machine whose Office build does not carry it.
- Install or confirm the matching Microsoft 365 or Office build first, then add the language pack.
- On a volume-licensed estate, take language packs from the Volume Licensing Service Center ISO rather than the consumer download.
- Confirm the language you want exists for the channel and version you have pinned before adding it to the configuration.
Visio is being deployed on a different channel from Office
You have this one if The install fails outright, or Visio and Office fight over updates afterwards.
- Read the channel and version of the existing Office install from File, then Account, then About.
- Put Office and Visio in the same Add element of one configuration XML, sharing one Channel value and one OfficeClientEdition.
- Re-run the configure stage with that combined configuration so the tool reconciles them into a single Click-to-Run image.
The Channel value in the Add element decides what gets installed regardless of any update channel set in the Updates element or by Group Policy.
The architectures do not match
You have this one if A 64-bit Visio configuration on a machine running 32-bit Office, or the reverse.
- Read the architecture from File, then Account, then About on the installed Office.
- Set OfficeClientEdition in the configuration to match it exactly.
- If the machine genuinely needs the other architecture, remove Office and redeploy everything at once.
Microsoft states that if Microsoft 365 Apps is already installed, a specified OfficeClientEdition must match it or the installation fails. Mixed architectures are not supported.
Visio installed but nobody holds a Visio seat
You have this one if Setup completes, Visio launches unlicensed, and Word and Excel on the same machine are perfectly happy.
- In the Microsoft 365 admin center open Users, then Active users, select the person and open the Licenses and Apps panel.
- Confirm a licence covering the Visio desktop application is assigned, and that Visio is not switched off in the app list under that licence.
- Have the user sign out of Office completely under File, then Account, and sign back in with the account holding the seat.
- If no Visio seat exists anywhere in the tenant, that is the answer: the deployment is correct and the entitlement is absent.
The local source is incomplete
You have this one if Every machine installing from one share fails identically while a fresh download works.
- Rebuild the source with
setup.exe /download configuration.xmlrather than copying the old folder again. - Check free space on the source volume; a multi-language download is large and a partial write produces failures that look like client faults.
- Install one machine from the rebuilt source before redeploying it.
Full reference
Which half of the problem you have
| What you see | Where the fault is |
|---|---|
| Setup fails naming a language pack | The documented cause: no matching Office build for that language pack |
| Setup fails and the configuration pins a channel or version | Channel, version or architecture mismatch with the installed Office |
| Install completes, Visio opens unlicensed | Entitlement, not deployment |
| Some users activate and others do not | Licences assigned to a subset, or the Visio app switched off under an assigned licence |
| Every machine from one share fails | The source, not the clients |
Configuration settings that decide the outcome
| Setting | What it controls | Constraint worth knowing |
|---|---|---|
| Channel attribute on Add | Which channel is installed | Overrides any channel set in Updates or by policy |
| OfficeClientEdition on Add | 32 or 64 | Must match an existing Microsoft 365 Apps installation or setup fails |
| Language ID | Which language packs are installed | MatchOS, MatchPreviousMSI and MatchInstalled are the documented special values |
| Language ID MatchInstalled | Matches languages already present | Cannot be used with /download; needs a Click-to-Run product already installed |
| Language TargetProduct | Which product’s languages to match | Optional companion to MatchInstalled; accepts a product ID or All |
| RemoveMSI element | Removes MSI-based Office, Visio and Project | 2007, 2010, 2013 and 2016 only; no effect on Click-to-Run |
The deployment order that works
- Read the installed Office product, version, channel and architecture from File, then Account, then About.
- Write one configuration XML with Office and Visio in the same Add element, one Channel and one OfficeClientEdition.
- Build the source once with
setup.exe /download configuration.xmlon a machine with working access. - Deploy with
setup.exe /configure configuration.xmlfrom an elevated prompt on the clients. - Add language packs after the matching build is present, never before it.
- Confirm licensing separately, in the admin centre and in File, then Account on one machine.
The seat question, stated carefully
Microsoft treats Visio for the web and the Visio desktop application as separate capabilities in its own service description, and it names Visio Plan 2 as a plan that includes desktop Visio. So the useful question is not “do these users have Visio” but “does the plan they hold entitle the installed desktop application, and is that component switched on for them”. Both halves are visible in the admin centre and neither is visible from the client.
- Users, then Active users, then the Licenses and Apps panel shows the licence and the individual services under it.
- Billing, then Licenses is the second documented route and is faster when you are checking many people at once.
- Services under a licence are assigned by default but can be deselected, including by a bulk assignment script, which is where most surprises come from.
- A change in the admin centre takes a little time to reach the client. Signing out of Office and back in is usually quicker than waiting.
- A perpetual Visio licence is the alternative to a seat, and it activates by key rather than by identity.
When a licence is the actual fix
Once the files are on the machine, the only thing between your users and a working Visio is an entitlement, and there are three honest ways to get one: a spare licence already sitting in your tenant, a reassignment from someone who has left, or a new subscription. If you do need to buy, Visio Plan 2 is the plan Microsoft names as including the installed desktop application you have just deployed, and we can supply those seats. We can also quote the perpetual Visio LTSC editions where an estate is better served by a key than by an identity. Check your existing assignments first, because on estates of any size there is usually at least one seat nobody is using, and we would rather tell you that than sell you another.
Every code this article covers
| Code | What it points at | Source |
|---|---|---|
30053-4 |
A Microsoft 365 language pack is being installed without the correct version of Microsoft 365 present | Microsoft Support |
30053-39 |
Published on the same page with the same cause as 30053-4 | Microsoft Support |
30143-37 |
Microsoft documents it as appearing when upgrading from Office 2013 to Office 2016, with uninstall and reinstall as the remedy | Microsoft Support |
30182-39 |
A Click-to-Run setup failure with no published meaning; diagnose from the source, the disk and the deployment log | not published by the vendor |
30068-39 |
The base code 30068 is documented against the Microsoft Office Click-to-Run service being disabled; the -39 suffix is not published | Microsoft Support |
30045-29 |
A Click-to-Run setup failure with no published meaning; treat it functionally, as setup stopping and rolling back | not published by the vendor |
Confirm the fix worked
- The configure stage completes without an error code.
- Visio opens and File, then Account names the product, shows it as activated, and shows the account you expect.
- Word or Excel on the same machine reports the same version, channel and architecture under About.
- In the admin centre, the user’s licence still shows Visio enabled after the client has signed in once.
- A second machine deployed from the same configuration behaves identically, which is what tells you the configuration rather than the machine was the variable.
Questions people ask about this
Does 30053-4 mean my licence is wrong?
No. Microsoft documents it as a language pack being installed without the matching Microsoft 365 version present. It happens on machines with perfectly good licences. The licensing question only appears afterwards, when Visio installs cleanly and then refuses to activate.
Can I set MatchInstalled to fix a failing download?
No. Microsoft states MatchInstalled cannot be used with the /download switch and requires at least one Click-to-Run product to be installed already. It is a configure-stage setting on a machine that already has Office.
Can I deploy Visio without touching the existing Office install?
You can add it, but not independently. Visio joins the same Click-to-Run image as Office and shares its architecture and update channel, so deploy from a configuration that names both products.
Why can users open diagrams in the browser but not in the app?
Because Microsoft treats Visio for the web and the Visio desktop application as separate capabilities. A plan can include one without the other, which is exactly what these deployments tend to expose.
Where do I get volume-licensed language packs?
Microsoft’s page for this error points volume licence customers at the ISO image in the Volume Licensing Service Center, and says to ask your administrator if you do not have access to it.
