KluczeSoft.pl
Back to Help Center
Troubleshooting

Conflict C2R vs MSI

6 min czytania·Zaktualizowano dzisiaj

Click-to-Run and MSI Conflict — Unable to Install Office

The Click-to-Run and MSI conflict message indicates that there are or have been different Microsoft Office package installation technologies on your computer that are blocking each other. In practice, the system detects that you are trying to install an Office version run by Click-to-Run (C2R), while MSI version components still exist in the system, or vice versa. The installer stops working to prevent damage to Office files, activation, or integration with Outlook, Word, and Excel.

What this error means

In simple terms: there are traces of two incompatible Office installation methods on your computer. Older versions, such as Office 2010, 2013, or some volume-licensed editions, were often installed using MSI. Newer Microsoft 365 and many new Office 2019, 2021, and 2024 editions use Click-to-Run. These methods usually cannot be mixed in one system without completely removing the previous installation.

When this problem occurs

The error most often occurs in several situations:

  • when installing Microsoft 365 on a computer where Office 2010, 2013, or 2016 MSI was previously installed
  • when trying to switch from a perpetual to a subscription version
  • after incomplete uninstallation of the old Office package
  • after computer migration, disk cloning, or system restoration from an image
  • when a different Office deployment channel is used in the company than before
  • when separate components, such as Project, Visio, or Access Runtime, are installed separately from a different installation technology

Causes

Known causes include:

  • a previously installed Office package in MSI technology
  • a previously installed Office package in Click-to-Run technology, and attempting to install an MSI version
  • remaining Office services, registry entries, or folders after a failed uninstallation
  • the presence of separate Microsoft products, such as Visio, Project, Language Pack, or Proofing Tools, from a different type of installer
  • conflict between 32-bit and 64-bit versions
  • outdated or corrupted Windows system files
  • incorrect Office activation status or remnants of trial versions
  • deployment of a package from a different licensing channel than the previous installation

Step-by-Step Solution

1. Close all Office applications

Close Word, Excel, Outlook, Teams, and the Office installer.

2. Check if Office is still visible in the system

Open Command Prompt as Administrator and run:

wmic product get name

If you see old Office components, Visio, or Project on the list, you need to remove them.

3. Uninstall old Office from Control Panel

Go to:

Control Panel > Programs and Features

Remove all items related to:

  • Microsoft Office
  • Microsoft 365
  • Visio
  • Project
  • Access Runtime
  • Language Pack

After uninstalling, restart your computer.

4. Check the Office license status

If there are any remaining Office activation components in the system, check them using the ospp.vbs command.

For 64-bit systems with 64-bit Office:

cd /d "C:\Program Files\Microsoft Office\Office16"
cscript ospp.vbs /dstatus

For 32-bit Office in a 64-bit system:

cd /d "C:\Program Files (x86)\Microsoft Office\Office16"
cscript ospp.vbs /dstatus

If the tool shows old keys or an incorrect license status, it's a good idea to completely remove the old Office installation before reinstalling.

5. Check Windows activation

Windows activation issues are not the primary cause of this error, but they can make it difficult to activate Office after installation. Check the system status:

slmgr.vbs /dlv

You can also use:

slmgr.vbs /xpr

If Windows is not activated correctly, fix the system activation first.

6. Repair Windows system files

In the same CMD window, run the following commands in sequence:

DISM /Online /Cleanup-Image /RestoreHealth

After completion:

sfc /scannow

If either tool detects errors, restart your computer.

7. Remove Office remnants and install the correct version

After restarting, run the installer for only one version of Office: either Click-to-Run or MSI. Do not mix installation types, architectures (32/64-bit), or deployment channels.

Alternative Repair Methods

If the primary method does not help, perform one of the following actions.

Method 1: Remove accompanying products

Often, the conflict is not caused by Office itself, but by a separate component, such as Visio or Project. Remove all Microsoft Office products and then reinstall them using the same installation technology.

Method 2: Use full cleanup after failed uninstallation

If Office does not disappear from the system despite uninstallation, run again:

DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow

Then, check the Office status again:

cscript ospp.vbs /dstatus

If the Office16 directory does not exist, it usually means that the package has been removed, and you can proceed with reinstalling.

Method 3: Check compatibility between 32-bit and 64-bit versions

If you are installing 64-bit Office, remove all previous 32-bit components. This also applies to add-ons, language modules, and separate applications, such as Project or Visio.

Method 4: Installation after a clean system boot

If the installer still reports a conflict, perform a clean boot of Windows and then run the Office installer. This helps when the blockage is caused by security software, a management agent, or an old integration module.

If you need further assistance, please contact us at [email protected] or call 00 800 121 1654.

When to contact support

Call 00 800 121 1654 when:

  • you cannot remove the old Office despite uninstalling and restarting
  • ospp.vbs /dstatus still shows remnants of the old license
  • the conflict involves a corporate environment with Visio, Project, or volume licensing
  • the installer still reports an error despite running DISM and sfc
  • you are unsure whether to install the MSI or Click-to-Run version
  • the problem affects multiple computers and requires proper corporate deployment

Before contacting support, prepare the name of the Office version being installed, information about the 32/64-bit architecture, and the results of the following commands:

slmgr.vbs /dlv
cscript ospp.vbs /dstatus
DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow

Related errors

The conflict between Click-to-Run and MSI is often also associated with other messages:

  • Cannot install Office package because MSI Office products were found
  • Microsoft Office Click-to-Run Installer encountered a problem
  • Error 30015
  • Error 30029
  • Error 30125
  • Error 0-1018
  • Error 0-1002
  • Error 0-30088
  • 32-bit / 64-bit architecture error
  • Conflict with Visio or Project from a different installation technology

Summary

This error does not mean a damaged product key, but most often a conflict between the old and new Office installation method. The most effective solution is to completely remove the previous components, check the license status using ospp.vbs, repair the system with DISM and sfc commands, and then install one compatible version of Office. If the problem persists, especially in a corporate environment, it is best to contact support at 00 800 121 1654 or email [email protected] for assistance.

Czy ten artykuł był pomocny?

Conflict C2R vs MSI | Help Center