How to fix Microsoft Office error code 0-2048 in Windows?

Error Code: 0-2048 (0) comes from the Office Deployment Tool, the setup.exe that installs Office LTSC 2024, 2021, 2019 and Microsoft 365 Apps from a command. In most cases the tool did not receive its configuration file, so nothing was installed. Open Command Prompt as administrator, go to the folder that holds setup.exe and the XML file, and run the command again.

Facts checked on 14 October 2026. Steps written for the Office Deployment Tool 16.0.20326.20112 on Windows 11 (25H2 and 26H2) and Windows 10 22H2, read against Microsoft's documentation.

What error code 0-2048 (0) means when Office says Couldn't install

The window is small and white, with the Microsoft logo and the heading Couldn't install. Under the text there is a link, Go online for additional help., and the line Error Code: 0-2048 (0). It opens a second or two after you start setup.exe with a command, and the only button is Close.

That setup.exe is the Office Deployment Tool (ODT), Microsoft's command-line installer for Click-to-Run versions of Office. It consists of two files: the tool and an XML file that says what to install. The code 0-2048 is shown when the tool stops before the installation begins. Nothing was changed on the PC, so there is nothing to clean up or roll back.

Microsoft's support page Troubleshoot installing Office lists dozens of installation codes, from 0-3 to 30183-4. The code 0-2048 is not among them, and we found no Microsoft Learn article that defines it. What exists is the answer of Microsoft's own forum staff: the error appears when the tool cannot find or read the XML configuration file referenced in the command.

Which Office you are installing decides whether you need this tool at all

Many readers meet this error because a video or a seller told them to install Office with a command and a configuration.xml. That is the right way for some products and the wrong way for others. Check your product first, because the fastest fix may be to stop using the tool.

• There is no lifetime Microsoft 365. A Microsoft Q&A moderator answered a reader with this error who had followed a video for an "Office 365 lifetime" key: Microsoft 365 is always a subscription. A one-time purchase is called Office 2024 or Office 2021.
• Office LTSC 2024 is not for every Windows 10 PC. Microsoft lists Windows 11, Windows 11 LTSC 2024, Windows 10 LTSC 2021, Windows 10 LTSC 2019, Windows Server 2025 and Windows Server 2022. Ordinary Windows 10 Home and Pro are not on the list.
• The tool itself runs on Windows 11 and Windows 10, and on Windows Server 2022, 2019 and 2016. Windows 10 left support on 14 October 2025, so new Office releases are not tested on it.
• The product ID must fit the licence. Microsoft's note is short: if you use the wrong product ID, you cannot activate Office.

What causes error code 0-2048, from the most common to the rare

Microsoft publishes no list of causes for this code. The ranking below is our reading of the reports on Microsoft Q&A, where Microsoft's forum staff and the people who solved the error describe what they changed, checked against the rules in Microsoft's deployment guides. It is an order of likelihood, not a statistic.

How the tool looks for configuration.xml: the command, word by word

The whole installation is one line with three parts. Microsoft's deployment guide for Office LTSC 2024 gives it as setup /configure configuration.xml, typed in an elevated command prompt in the folder where you saved the tool and the file. Each part can cause 0-2048 if it does not match what is on the disk.

• A file name without a folder is searched for where the command window currently is. The prompt shows that place before the > sign.
• For a network share, Microsoft asks for the full network path of both setup.exe and the configuration file.
• After a successful installation the command prompt shows Products configured successfully. That sentence is Microsoft's own sign that the tool read the file.

How to fix error code 0-2048 (0) when installing Office

Fix 1 to Fix 4 repair the command and the file, and they solve the form of the error that names the configuration file. Fix 5 to Fix 7 are for the general failure text. Fix 8 is for home products, which do not need this tool. Use the table to pick your start.

Fix 1. Run the command in an elevated Command Prompt, from the folder with both files

5 minutesNo riskEveryone who sees the configuration file text, first.

Microsoft's guides for Office LTSC 2024, LTSC 2021 and Office 2019 all say to open an elevated command prompt and go to the folder of the tool before typing the command. In the accepted answers on Microsoft Q&A, elevating the window alone ended the error for people whose file was correct.

1. Select Start and type cmd.
2. Right-click Command Prompt and select Run as administrator. Select Yes when Windows asks for permission.
3. Check the title bar. It must begin with Administrator:.
4. Go to the folder that holds setup.exe and your XML file. Replace C:\ODT with your folder:

   cd /d C:\ODT

5. List the folder and check that both files are shown:

   dir

6. Start the installation. Use the exact name of your XML file:

   setup.exe /configure configuration.xml

• Windows Terminal or PowerShell: right-click Start and select Terminal (Admin). In PowerShell the tool is started as .\setup.exe /configure configuration.xml, with the dot and the backslash in front.
• The Run box (Win + R): Microsoft's offline installer page uses it with the full path of the tool, for example c:\odt\setup.exe /configure installOfficeProPlus32.xml. If that gives 0-2048, use the elevated window above.
• Double-clicking setup.exe gives the tool no file name at all. It always needs a command.

Fix 2. Check the real name and extension of the configuration file

5 minutesNo riskThe XML was written or edited in Notepad, renamed, or downloaded under another name than the one in the command.

Microsoft staff name this trap in their answer to the error: the file must be in XML format, not Configuration.xml.txt. Windows hides known extensions by default, so a text file can look exactly like the XML file the command asks for.

1. Open the folder with the tool in File Explorer.
2. Select View > Show > File name extensions. On Windows 10 the same File name extensions check box is on the View tab.
3. Read the full name of the file. If it ends in .xml.txt, right-click it, select Rename, delete .txt and confirm the change of extension.
4. Compare the name with the command, letter for letter. config.xml, Configuration.xml and configuration (1).xml are three different names for the tool.
5. If the name contains spaces, either rename the file or put the name in quotation marks in the command.
6. Run the command from Fix 1 again with the corrected name.

A file name with spaces needs quotation marks

setup.exe /configure "Office 2024 config.xml"

To avoid the hidden ending when you save from Notepad, select File > Save as and set Save as type to All files. Type the name with .xml at the end and keep the encoding UTF-8, which is what Microsoft's forum staff advise for this file.

Fix 3. Move the tool and the file to a short local folder, or use full paths

5 minutesNo riskThe files are in Downloads, on the desktop, on a USB stick, in a OneDrive folder, or on a mapped network drive.

Microsoft's own example for a single PC is a folder named c:\ODT. A short local path removes spaces, long names and cloud folders from the question, and the highest-voted user answer on Microsoft Q&A is to place both files in a directory of the system disk.

1. Create the folder C:\ODT in File Explorer.
2. Move setup.exe and your XML file into it. Do not put them inside the Office folder that /download created.
3. Open an elevated Command Prompt as in Fix 1.
4. Run the command with full paths, so that the current folder no longer matters:

   C:\ODT\setup.exe /configure C:\ODT\configuration.xml

On a network share the rules change in an elevated window. Windows keeps drive letters per logon session, and Microsoft documents that mapped drives can be unavailable in an elevated command prompt. The drive Z: that you see in File Explorer may not exist there.

From a network share: pushd gives the elevated window its own temporary drive letter

pushd \\server\share\ODT
setup.exe /configure configuration.xml
popd

• One administrator wrote on Microsoft Q&A that pushd was what ended her 0-2048 error with Office LTSC 2024 on a server share.
• The other way is Microsoft's rule for shares: pass the full network path for both files, \\server\share\ODT\setup.exe /configure \\server\share\ODT\configuration.xml.
• SourcePath inside the XML is a different thing. It says where the installation files are, and Microsoft notes that it should not include the /Office part of the path.

Fix 4. Build a new configuration file with the Office Customization Tool

10 minutesNo riskThe file is found but not accepted: it was copied from a web page, edited by hand many times, or made for another product.

Microsoft staff describe the error as a file the tool cannot find or read, and their second advice after the elevated window is to create the file with the Office Customization Tool. The web tool writes valid XML with product IDs and channels that exist, which hand editing often gets wrong.

1. Open config.office.com/deploymentsettings in a browser. No sign-in is needed to create a file.
2. Under Products and releases choose the architecture, then your product, for example Office LTSC Professional Plus 2024.
3. Choose the language, and leave the installation options on the Office Content Delivery Network unless you install from a share.
4. Under Licensing and activation accept the terms automatically if you want, and enter the KMS or MAK key settings for a volume product.
5. Select Finish, check the summary on the right and select Export.
6. Accept the licence terms, name the file configuration.xml and save it to C:\ODT.
7. Run the command from Fix 1.

If you prefer to check a hand-written file, compare it with Microsoft's sample from the deployment guide for Office LTSC 2024, reduced here to one product.

Office LTSC Professional Plus 2024, 64-bit, from the Office servers (replace the key with your own)

<Configuration>
  <Add OfficeClientEdition="64" Channel="PerpetualVL2024">
    <Product ID="ProPlus2024Volume" PIDKEY="#####-#####-#####-#####-#####">
      <Language ID="en-us" />
    </Product>
  </Add>
  <RemoveMSI />
</Configuration>

Fix 5. Download the newest Office Deployment Tool and extract it again

5 minutesNo riskThe setup.exe came from a seller, an old archive or a video link, or the window shows the general failure text.

Microsoft's deployment guides repeat one sentence at every troubleshooting step: make sure you have the newest version of the tool. It is released about once a month, and an old copy may not know the product IDs or channels of Office LTSC 2024.

1. Right-click your current setup.exe, select Properties and open the Details tab. Note the File version.
2. Open Microsoft's download page: Office Deployment Tool.
3. Download the file. Its name begins with officedeploymenttool.
4. Double-click it, accept the Microsoft Software License Terms and select C:\ODT as the folder.
5. Let it replace the old setup.exe. Keep your own XML file. The extracted sample configuration.xml can overwrite a file of the same name, so rename yours first.
6. Run the command from Fix 1.

In October 2024 a user on Microsoft Q&A suspected that one build of the tool, 16.0.18129.20030, caused the error with Office LTSC 2021. Microsoft never confirmed a faulty build, and the release notes of that period only say "Resiliency and Reliability Improvements". Going back to an older build is not a fix we can recommend.

Fix 6. Remove the Office version that conflicts with the new one

15 to 30 minutesRead the warningAnother Office, a trial, Visio or Project is already on the PC, or the window shows the general failure text.

Microsoft's first answer to this code in 2021 was to uninstall other Office versions with its uninstall tool. Its compatibility rules explain why: two products of version 16.0 with different installation technologies cannot share a PC, and all Office products on one device must be either 32-bit or 64-bit.

1. Open an Office app if one starts and go to File > Account. If Update Options is shown, it is Click-to-Run. If only About is there, it is an MSI installation.
2. Windows 11: open Settings > Apps > Installed apps. Windows 10: open Settings > Apps > Apps & features.
3. Find every Microsoft 365, Office, Visio and Project entry. Select Uninstall for the ones that conflict. Every screen: Uninstall a program or app in Windows.
4. Restart the PC.
5. If an entry refuses to go, open Microsoft's page Uninstall Microsoft 365 or Office from a PC and start the uninstall troubleshooter. It opens in the Get Help app.
6. Restart again and run the command from Fix 1.

• Microsoft notes that the uninstall troubleshooter covers Microsoft 365, Office 2021, 2019 and 2016, needs Windows 10 or later and currently cannot uninstall Office 2024.
• RemoveMSI removes the 2007, 2010, 2013 and 2016 versions that were installed with Windows Installer. It does not remove Click-to-Run versions.
• The old advice to run Get-AppxPackage with Remove-AppxPackage only removes the Microsoft Store edition of Office. It does nothing for a normal installation.

Fix 7. Rule out the internet connection, disk space and security software

10 to 20 minutesLow riskThe window asks whether your internet connection works and whether you have enough space, or the error appears only on one network.

Unless the XML names a local source, the tool fetches the installation files from the Office Content Delivery Network, and Microsoft requires network connectivity even in download mode. Office LTSC 2024 needs 4 GB of available disk space, and Microsoft staff suggest one test without antivirus or firewall interference.

1. Open a browser and load https://config.office.com. If it does not open, fix the connection first: How to check your internet connection in Windows.
2. Disconnect a VPN, or try another network such as a phone hotspot, and run the command again.
3. Open Settings > System > Storage and read the free space on drive C:. Office is always installed on the system drive, and Microsoft says the location cannot be changed.
4. If less than 4 GB is free, make room: Free up disk space and delete temporary files.
5. Pause the real-time protection of your antivirus for this one test and run the command once more. Steps for Microsoft Defender: Turn off Microsoft Defender protection for a moment.
6. Turn the protection back on straight after the test, whatever the result.

If the installation works only with the protection paused, do not leave it off. Add C:\ODT\setup.exe to the exclusions of the security program, or ask its maker why it blocks a Microsoft installer. On a company network, the proxy or firewall has to allow the Office Content Delivery Network, which is the network administrator's job.

Fix 8. Install a home or small business product without the Deployment Tool

20 to 40 minutesNo riskYou have Microsoft 365 Family, Personal or a business plan, or a one-time purchase such as Office Home 2024, and used the tool only because a guide said so.

Microsoft's overview of the tool says plainly that it is for enterprise administrators, and sends everyone else to the normal download from the account. That route needs no XML file and no command, so the code 0-2048 cannot appear in it.

1. A product key that was never used is redeemed first: Microsoft's install page sends home products to microsoft365.com/setup or setup.office.com, where the key is linked to a Microsoft account.
2. Go to m365.cloud.microsoft/apps and select Sign in. Use the account that owns the product.
3. Select Install apps, then Install, and run the small installer that downloads.
4. If that installer fails as well, open Microsoft's page Use the Office offline installer and select the Office for home tab.
5. In the Install window choose Offline installer in the Choose a version list, pick the language and select Install.
6. Double-click the downloaded image file, for example O365HomePremRetail.img. Windows opens it as a virtual drive.
7. Open the Office folder on that drive and run Setup64.exe for 64-bit Office or Setup32.exe for 32-bit.

Microsoft describes the offline installer as a way around proxy, firewall, antivirus and connection problems during installation. For a business plan the same page uses the Deployment Tool with a short XML file, which brings you back to Fix 1 to Fix 4.

If 0-2048 is still there: find the setup log and read it

The error window gives one sentence. The tool writes more than that to a log file, and Microsoft's deployment guides end every troubleshooting paragraph with the same advice: review the log files in the %temp% folder. A second set is written by the part of setup that runs under the system account.

1. Run the failing command once more and note the time.
2. Open %temp%, switch to the Details view and sort by Date modified, newest first.
3. Open the newest file whose name begins with the name of your PC and ends in .log. It opens in Notepad.
4. Press Ctrl + F and search for the name of your XML file. The lines around it show the path the tool worked with.
5. Search for error and fail, and read the lines just before the end of the file.
6. Repeat it in %windir%\Temp. If no new file exists there, setup stopped before the installation part began, which points back to the command and the file.

If the log is too short to explain anything, Microsoft's article on enterprise logging turns on verbose logging for installation with two registry values. Run them in an elevated Command Prompt.

Turn verbose setup logging on

reg add HKLM\SOFTWARE\Microsoft\ClickToRun\OverRide /v LogLevel /t REG_DWORD /d 3
reg add HKLM\SOFTWARE\Microsoft\ClickToRun\OverRide /v PipelineLogging /t REG_DWORD /d 1

Turn verbose setup logging off again

reg delete HKLM\SOFTWARE\Microsoft\ClickToRun\OverRide /v PipelineLogging
reg delete HKLM\SOFTWARE\Microsoft\ClickToRun\OverRide /v LogLevel

• What to send to support or to your administrator: the exact command and the content of the XML file with the product key removed. Add the File version of setup.exe, the newest log from both folders and the Windows version from Settings > System > About.
• Test with a second administrator account. If the same folder and command work there, your profile or its temporary folder is at fault. Steps: Create a new user account to test a problem.
• A managed work PC may block command-line installers by policy. Then only the administrator can install Office, and no fix on this page will change that.

How to avoid error code 0-2048 the next time you install Office

The error is a mismatch between a command and a file, so prevention is a small routine. Administrators who install Office often keep one clean folder and never type the command from memory.

Frequently asked questions

What does error code 0-2048 (0) mean?

It means that the Office Deployment Tool stopped before it installed anything. In nearly all recent reports the text above the code is "We couldn't find the specified configuration file. Check the file path and file name." Microsoft's forum staff put it this way: the tool cannot find or read the XML file referenced in the command. Microsoft has no support article for the code and does not list it among its Office installation errors. The usual causes are a command window that is not elevated and a file name that does not match.

Why do I get error code 0-2048 (0) with Office 2024 or Office LTSC 2024?

Because Office LTSC 2024 can only be installed with the Office Deployment Tool, so every buyer of a volume licence has to type the command, and many do it for the first time. The product needs the ID ProPlus2024Volume or Standard2024Volume and the channel PerpetualVL2024. Retail Office 2024, such as Office Home 2024, does not need the tool at all: it installs from your Microsoft account. If a seller sent you a configuration.xml for a retail product, try the normal download first, as in Fix 8.

The configuration file is in the same folder as setup.exe. Why can the tool not find it?

Most often because the command window is not elevated or is not in that folder. Several people on Microsoft Q&A had both files side by side and a correct name, and the error ended when they opened Command Prompt with Run as administrator. Microsoft has not explained this behaviour. Check three things: the title bar says Administrator, the prompt shows the folder with both files, and dir lists the XML file under exactly the name you type. A hidden .txt ending is the other classic reason.

Does error code 0-2048 mean my internet connection or disk is the problem?

Usually not. An older form of the window asks "Is your internet connection working?" and whether you have enough space on your main hard drive, and a user who posted it on Microsoft Q&A in 2021 was sure both were fine. That text is the general failure message of Office setup. Check the connection and the free space once, because the tool does need both: Office LTSC 2024 requires 4 GB of available disk space. Then go on with the newest tool and the conflict check in Fix 5 and Fix 6.

Is error code 0-2054 (0) the same as 0-2048 (0)?

No, but it is a neighbour from the same tool. Users report 0-2054 (0) with the text "The configuration file wasn't specified", which is what you get when setup.exe is started with a mode but with no file name, or by a shortcut that drops the name. We found no Microsoft page that defines either code. In practice both are repaired the same way: an elevated Command Prompt in the folder of the tool, and the full command setup.exe /configure configuration.xml with the real name of your file.

Will SFC, DISM or a clean boot fix error code 0-2048?

Very unlikely. The error is raised by the Office Deployment Tool before it touches Windows, and its text is about a file path. System File Checker repairs Windows system files and a clean boot removes startup programs. Neither changes what you typed or how the XML file is named. No solved report on Microsoft Q&A that we read credits them. They do no harm, but they cost half an hour that Fix 1 and Fix 2 do not need. Reinstalling Windows for this code is never justified.

Where is the Office setup log file?

In two temporary folders. %temp% is the folder of the signed-in user, and Microsoft's deployment guides name it for problems with the Deployment Tool. %windir%\Temp holds the logs of the installation itself, which runs under the system account. The files are named after the PC, the date and the time and end in .log. Sort by date, open the newest one in Notepad and search for the name of your XML file and for the word error. Verbose logging is switched on with two registry values described above.

Is there an official Microsoft fix or patch for error 0-2048?

No, and none is needed, because Microsoft does not treat it as a bug. There is no entry for the code on Microsoft's list of Office installation errors and no fix note in the release history of the Deployment Tool, whose entries only say "Resiliency and Reliability Improvements". Microsoft's standing advice is general: use the newest version of the tool, check that the configuration file and the command reference the correct locations, and review the log files in the %temp% folder.

This page is in English. Is the error the same in other languages, for example "0-2048 (0) office ошибка"?

Yes. The setup window is translated, but the code 0-2048 (0) and the cause stay the same in every language of Office and Windows. The commands on this page are identical everywhere: cd /d, setup.exe /configure configuration.xml, the folder %temp%. Only the labels of Windows menus differ, such as Run as administrator. The Language ID inside the XML file, for example en-us or fr-fr, decides in which language Office is installed, and a wrong value there is one more reason to create the file with the Customization Tool.