Error 30088-1021 (0) is a generic Microsoft Office Click-to-Run installation failure. It does not prove that your hard drive is full or that a DVD is missing. The installer may instead be unable to read its source, may be conflicting with an existing Office installation, or may be using an invalid or outdated Office Deployment Tool (ODT) configuration.
Start by identifying whether this is a normal Office install or update, an ODT deployment, a network-share installation, or an RDS/virtual-machine deployment. Then follow the matching fix below.
As an Amazon Associate I earn from qualifying purchases.
What the message actually means
The dialog mentions internet access, free space on the main drive and an Office installation disk. These are generic checks, not a definitive diagnosis. The “disk” can mean a local folder, removable media or a network installation source; modern Click-to-Run installations do not normally require a physical DVD.
Free tools Windows power users keep installed
One-click scans. No signup required.
The code has been reported with Office 2016, Microsoft 365 Apps/Office 365 ProPlus, ODT deployments, network sources, virtual machines and Remote Desktop Services (RDS). Microsoft has not published a dedicated root-cause definition for 30088-1021 (0). Microsoft’s guidance for related installation failures consistently points to repair, complete removal, eliminating unsupported MSI/Click-to-Run combinations and using a current ODT. Community examples include RDS and network deployments, Office 2016 virtual-machine deployments and UNC-source deployments.
#1 Best Overall
Identify your installation scenario first
- Are you installing Office for the first time, updating an existing suite or modifying it?
- Are you running
setup.exewith an ODT XML file? - Is the source local, removable or on a server share?
- Is the target a normal Windows PC, virtual machine, RDS server or managed device?
- Are Office, Visio or Project remnants installed through MSI, Click-to-Run or the Microsoft Store?
- Which product, language, channel and 32-bit/64-bit architecture are required?
These answers determine whether repair instructions or deployment validation is appropriate. Consumer repair steps will not correct an invalid ODT XML file, and a server deployment may require shared computer activation and a different licensing model.
Before changing Office
- Check the system drive. Verify free space on
C:(or the Windows system drive), not only on the drive containing your XML or downloaded Office files. - Record the installation state. Note the Office product, version, architecture, language, license type and whether it is MSI, Click-to-Run or Store-based.
- Protect user data. Confirm access to documents, templates, Outlook data files, macros and custom dictionaries. Uninstalling Office removes applications, not documents, but add-ins may need to be reinstalled.
- Check the source. Ensure the local folder or media exists and remains available for the entire installation.
Fix 1: Repair an existing Office installation
Use repair when Office is already installed and the failure occurs during an update or modification. Microsoft recommends Online Repair for many damaged installations, while Quick Repair is faster and less comprehensive. The labels vary slightly by Windows release.
- Open Settings > Apps > Installed apps.
- Find Microsoft 365 or Microsoft Office, open its menu and choose Modify.
- Run Quick Repair first.
- If the code returns, run Online Repair, restart Windows and retry.
On older Windows versions, use Control Panel > Programs and Features > Microsoft Office > Change > Repair. Repair will not fix an inaccessible ODT source or malformed XML. See Microsoft’s related repair sequence at this Office installation-error guide.
Fix 2: Remove conflicting Office products
Microsoft generally does not support common combinations of Click-to-Run and Windows Installer (MSI) Office on one computer. Older Office, Visio or Project components can block a Microsoft 365 Apps deployment. Check for Office 2010, 2013 or 2016 MSI editions, Professional Plus remnants, language packs, standalone Outlook/Access/OneNote, trial editions and Microsoft Store Office.
Rank #2
- Designed for Your Windows and Apple Devices | Install premium Office apps on your Windows laptop, desktop, MacBook or iMac. Works seamlessly across your devices for home, school, or personal productivity.
- Includes Word, Excel, PowerPoint & Outlook | Get premium versions of the essential Office apps that help you work, study, create, and stay organized.
- 1 TB Secure Cloud Storage | Store and access your documents, photos, and files from your Windows, Mac or mobile devices.
- Premium Tools Across Your Devices | Your subscription lets you work across all of your Windows, Mac, iPhone, iPad, and Android devices with apps that sync instantly through the cloud.
- Easy Digital Download with Microsoft Account | Product delivered electronically for quick setup. Sign in with your Microsoft account, redeem your code, and download your apps instantly to your Windows, Mac, iPhone, iPad, and Android devices.
- Record the user’s license, architecture, language, add-ins and any Visio or Project components that must remain.
- Uninstall conflicting products through Settings > Apps > Installed apps or Control Panel > Programs and Features.
- Restart Windows.
- Retry with a clean, validated configuration.
For supported legacy MSI products, ODT can remove them during deployment with RemoveMSI. Microsoft documents the limitations at Upgrade from MSI to Microsoft 365 Apps.
<Configuration>
<Add OfficeClientEdition="64" Channel="Current">
<Product ID="O365ProPlusRetail">
<Language ID="en-us" />
</Product>
</Add>
<RemoveMSI />
</Configuration>This example must match your entitlement, channel, architecture and deployment policy. RemoveMSI targets supported MSI-based Office, Visio and Project versions; it does not remove previous Click-to-Run products, which require separate removal.
Fix 3: Validate an Office Deployment Tool installation
For ODT deployments, the XML, product source and command line are primary suspects. Download the current ODT package and ensure setup.exe is from that package. Microsoft’s configuration reference covers SourcePath, product IDs, languages, channels, architecture and removal options: Office Deployment Tool configuration options.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsStart with a minimal configuration
<Configuration>
<Add OfficeClientEdition="64" Channel="Current">
<Product ID="O365ProPlusRetail">
<Language ID="en-us" />
</Product>
</Add>
</Configuration>Use the correct product ID and language for your license. Run the commands from the folder containing the intended ODT executable, or use fully qualified paths:
setup.exe /download configuration.xml
setup.exe /configure configuration.xml"C:OfficeDeploymentsetup.exe" /configure "C:OfficeDeploymentconfiguration.xml"Confirm that the XML is well formed, the source exists, the account can read it, the download completed before /configure, and the selected channel is compatible with the product. Add multiple products, languages, excluded apps, shared computer activation, update policies and network SourcePath only after this basic test works.
Fix 4: Test network paths and permissions
Mapped drives frequently disappear when setup runs elevated or under a deployment account. Prefer a UNC path such as \servershareOffice. Open that path in File Explorer on the target computer, then test it from the same elevated identity that will run setup. Verify both share and NTFS permissions and keep the source available throughout installation.
To isolate networking, copy setup.exe, the XML and (for an offline deployment) the downloaded Office folder to a local test directory:
mkdir C:ODT-Test
cd /d C:ODT-Test
setup.exe /configure configuration.xmlIf the local test succeeds while the share fails, investigate authentication, SMB policy, proxy behavior, antivirus inspection or source availability. A local success isolates the fault; it does not by itself prove which network component is responsible.
Fix 5: Replace an outdated ODT package
An old deployment binary can fail during configuration. Microsoft documents updating ODT for related installation failures at this Office installation guide. Replace the old setup.exe with the latest ODT release and retest before changing a working XML. Do not assume Microsoft has mapped a particular ODT version directly to error 30088-1021 (0).
Fix 6: Completely uninstall and reinstall
If repair and ordinary uninstall do not resolve a damaged installation, use Microsoft’s current uninstall troubleshooter/Get Help workflow on the same Windows PC. It requires Windows 10 or later and Microsoft currently states that it does not uninstall Office 2024. Follow Microsoft’s instructions at Uninstall Office from a PC.
- Run the supported removal workflow.
- Restart Windows.
- Reinstall from your Microsoft account or the organization’s approved source.
- Verify that only the intended Office installation technology remains.
Do not immediately restore an old deployment cache or XML without validating it. Uninstalling Office removes the applications, not your saved documents and workbooks, although add-ins and some custom settings may need to be restored.
Special cases: RDS, virtual machines and legacy products
RDS and shared computers
RDS deployments require the product and licensing model intended for shared computers, including shared computer activation where applicable. Also verify per-machine versus per-user installation, profile handling and architecture. Microsoft Q&A reports show this error in RDS and virtual-machine deployments, but those reports do not establish one universal fix: RDS deployment example.
Best Value
Virtual machines
Check whether a snapshot contains remnants of another Office build, whether the source is reachable from the VM and whether activation and user-profile requirements match the deployment design. Test a clean local source before modifying the image.
Office 2016, Visio and Project
Do not assume an Office 2016, Visio or Project component can coexist with the requested Microsoft 365 Apps architecture or installation technology. Record what must remain, remove only supported conflicts and validate product IDs before deployment.
32-bit and 64-bit architecture
64-bit Office is generally preferred for modern systems and large workbooks, but 32-bit add-ins and legacy integrations may require 32-bit Office. An incompatible existing component can block the requested architecture; choose one supported architecture for the installation.
Recommended Free Tools
If the error continues
Escalate with evidence instead of repeatedly retrying. Preserve:
- The exact dialog text and code.
- Windows edition and build.
- Office product, version, architecture, language and installation technology.
- The ODT version, complete XML with secrets and tenant-specific details removed, and exact command.
- Whether the source is local, removable or a UNC path.
- Free space on the system drive.
- Office setup logs and relevant Event Viewer entries.
- Whether a clean local installation succeeds.
A security scan is reasonable only when there are independent signs of malware; malware is not established as the standard cause of this Office code. Avoid deleting arbitrary registry keys or folders without a Microsoft-supported procedure and a backup.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
