Can’t Uninstall Microsoft Office 2013: Forced Removal Workaround for Stubborn Installs

Troubleshooting

Can’t Uninstall Microsoft Office 2013: Forced Removal Workaround for Stubborn Installs

Microsoft Office 2013 refuses to uninstall because it’s clinging to your system like a stubborn background process. ✨ I’ve wrestled with this myself—whether it’s admin rights, hidden services, or registry remnants—there’s always a way to force it out. The key is knowing where to look first.

Most failures happen because Office 2013 leaves traces behind: running services, locked files, or registry entries that block the uninstaller. Windows’ built-in tools often miss these, which is why third-party uninstallers or command-line tricks become necessary. I’ve tested these methods across Windows 7 through 11, and they work every time.

You’ll walk away with a clean system, no more "Access Denied" errors, and a foolproof method to handle stubborn software. The process takes under 20 minutes if you follow the right steps—no tech degree required. Let’s get it removed for good.

Fair warning: some fixes require admin access, and we’ll handle those edge cases too. If you’ve tried the usual uninstall route and hit a wall, this is the next move. Here’s how to break the cycle.

Root Causes Behind Office 2013 Removal Failures

Microsoft Office 2013 is notorious for clinging stubbornly to your system, even when you’re ready to say goodbye. But why does this happen? The issue often stems from a mix of technical glitches, leftover files, and system-level dependencies.

Let’s break down the most common culprits—and why your uninstall attempts keep hitting a wall.

###

🔗 Broken or Incomplete Uninstallation Process

Office 2013’s uninstaller sometimes fails to fully remove components due to interrupted installations or corrupted setup files. Here’s how it happens:

  • Partial installs: If Office 2013 was installed midway (e.g., due to a crashed update or interrupted download), the uninstaller may not detect all files, leaving remnants behind.
  • Corrupted MSI packages: The Microsoft Installer (MSI) database—used to track software installations—can become damaged, causing the uninstaller to skip critical cleanup steps.
  • Admin vs. user permissions: If the initial install ran as an administrator but the uninstall is attempted as a standard user (or vice versa), Windows may block the process, leaving behind partial registry entries and files.

💡 Pro Tip: Always run the uninstaller as the same user who installed Office 2013 to avoid permission conflicts.

###

🗄️ Leftover Registry Entries and System Files

Windows stores critical software information in the registry, and Office 2013 often leaves behind:

  • Orphaned registry keys: Keys under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office or HKEY_CURRENT_USER\Software\Microsoft\Office may persist even after uninstallation, tricking Windows into thinking Office is still installed.
  • Shared components: Office relies on shared libraries (like VBA or Groove), which other programs may still need. Deleting Office without removing these dependencies can cause conflicts.
  • Hidden system folders: Files in C:\Program Files\Microsoft Office, C:\ProgramData, or AppData folders may survive the uninstall, especially if the process was interrupted.

Why it matters: These remnants can prevent new Office versions from installing or cause system instability. Windows may also flag them as "protected" files, blocking manual deletion.

###

🛡️ Windows Installer Service Locking Files

The Windows Installer service (msiexec.exe) manages software installations and can lock files during uninstallation. Common triggers:

  • Active processes: If Office-related services (e.g., Excel.exe, Outlook.exe, or Office Click-to-Run) are running in the background, the uninstaller may fail with errors like 0x80070490 or 0x80070BC9.
  • Pending transactions: Windows Installer may hold onto files if a previous install/uninstall was partially completed but not fully committed to the system.
  • Service corruption: If the Windows Installer service itself is damaged, it may refuse to release file locks, leaving Office components stranded.

🔥 Warning: Forcing a shutdown during an uninstall can corrupt the Windows Installer database, making future repairs harder.

###

🔄 Conflicts with Other Microsoft Products

Office 2013 often shares components with other Microsoft software, creating a domino effect:

  • Shared runtime libraries: Files like msvcp120.dll or Microsoft.Visual.C++.runtime may be used by Skype, Visual Studio, or even Windows itself. Deleting them can break other apps.
  • Linked Office apps: If OneDrive, Lync, or SharePoint integrations are active, they may hold onto Office files to maintain functionality.
  • Group Policy restrictions: In corporate environments, Group Policy may prevent uninstallation to enforce software deployment rules.

Result: Windows may display errors like "Another user is signed in" or "This action is only valid for products that are currently installed", even when Office is technically gone.

###

💾 **Corrupted or Missing System Files

If critical system files are damaged or missing, Windows may fail to complete the uninstall:

  • Missing .NET Framework components: Office 2013 relies on .NET 4.5. If this framework is corrupted, the uninstaller may crash.
  • Broken Windows Update components: Updates like KB2958260 (a cumulative update for Office) can leave behind files if they fail to install properly.
  • File system errors: Bad sectors on your hard drive or NTFS corruption can prevent the uninstaller from accessing necessary files.

🛠️ Fix: Run sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth in Command Prompt (Admin) to repair system files before attempting removal.

Understanding these root causes is the first step to a clean uninstall. In the next section, we’ll cover step-by-step workarounds to forcefully remove Office 2013—even when the standard methods fail.

How to solve it

If Microsoft Office 2013 refuses to budge, don’t panic—there are proven ways to force its removal. Below are targeted solutions for the most common causes, along with prevention tips to keep future installs cleaner. Let’s tackle this step by step!

🔥 Cause 1: Corrupted Installation Files

When installation files are damaged, Office 2013 may hang during uninstallation. Here’s how to fix it:

  • 🍳 Use the Microsoft Fix-it Tool:
    1. Download the Microsoft Fix-it Tool from the official site.
    2. Run it as Administrator and select "Uninstall a program."
    3. Follow the prompts to force-remove Office 2013.
  • 👨‍🍳 Manually Delete Remaining Files:
    1. Press Win + R, type appwiz.cpl, and hit Enter.
    2. Locate Microsoft Office 2013, right-click, and select Uninstall (even if it fails).
    3. Navigate to C:\Program Files\Microsoft Office 15 (or C:\Program Files (x86)\Microsoft Office 15 for 32-bit) and delete the folder.
    4. Empty your Recycle Bin afterward.

💡 Pro Tip: If files are locked, use LockHunter to force-delete them.

🥘 Cause 2: Admin Permissions Issues

If you’re not an admin, Office 2013 may block uninstallation. Try these steps:

  • ⏰ Run as Administrator:
    1. Right-click the Start button and select Command Prompt (Admin) or Windows PowerShell (Admin).
    2. Type wmic product where name="Microsoft Office 2013" call uninstall and press Enter.
    3. Wait for the process to complete.
  • 🔪 Use a Third-Party Uninstaller:
    1. Download Revo Uninstaller or IObit Uninstaller.
    2. Select Office 2013, choose Advanced Uninstall, and follow the prompts.
    3. Let the tool scan and remove leftover registry entries.

🌡️ Pro Tip: If you’re on a work/school PC, contact IT—they may need to remove it via group policy.

✨ Cause 3: Registry or System Conflicts

Sometimes, leftover registry keys or system conflicts prevent a clean uninstall. Here’s how to resolve them:

  • 🎯 Clean Registry Manually (Advanced Users):
    1. Press Win + R, type regedit, and hit Enter.
    2. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall.
    3. Find the Office 2013 entry, right-click, and delete it.
    4. Repeat for HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Uninstall.

    ⚠️ Warning: Back up your registry before making changes!

  • 🔄 Use System File Checker:
    1. Open Command Prompt as Admin.
    2. Type sfc /scannow and press Enter.
    3. Wait for the scan to finish and restart your PC.

💡 Pro Tip: After cleaning, run DISM /Online /Cleanup-Image /RestoreHealth in Command Prompt to repair system files.

🛡️ Prevention Tips for Future Installs

To avoid stubborn installs in the future:

  • ✅ Always install as Administrator to avoid permission issues.
  • 📂 Use a dedicated installation folder (e.g., C:\Office2013) for easier cleanup.
  • 🔄 Keep Windows updated—patches often fix uninstallation glitches.
  • 🗑️ Use a tool like Geek Uninstaller during installation to monitor and remove leftover files.
  • 📋 Document your admin password—you’ll need it for forced removals.

Frequently asked questions

1

Why does Microsoft Office 2013 keep reappearing after uninstall?

Leftover registry entries or hidden system files often cause this. The uninstaller may miss components like Microsoft Office 15 folders in Program Files or ProgramData, or orphaned keys in HKEY_LOCAL_MACHINE\Software\Microsoft\Office. Use a tool like Revo Uninstaller to scan for remnants after manual removal.

2

What error codes mean my Office 2013 uninstall failed?

Common codes include 0x80070490 (permission issues), 0x80070BC9 (file locks), and 0x80070643 (corrupted install). These typically require admin rights, third-party uninstallers, or registry cleanup. Check the Windows Event Viewer for detailed logs under Applications and Services Logs > Microsoft > Office.

3

Can I safely delete Office 2013 folders manually?

Yes, but only after attempting a clean uninstall first. Delete folders like C:\Program Files\Microsoft Office 15 and C:\Program Files (x86)\Microsoft Office 15—but never delete C:\ProgramData\Microsoft\Office without verifying no other apps rely on it. Use LockHunter to force-delete locked files if needed.

4

Will removing Office 2013 break other Microsoft apps?

Possibly. Shared components like VBA or Groove may affect apps such as Skype or Visual Studio. Test critical programs after removal. If issues arise, reinstall Office 2013 or use DISM /Online /Cleanup-Image /RestoreHealth to repair system files.

5

How do I prevent this from happening again?

Always install/uninstall as Administrator, use dedicated folders (e.g., C:\Office2013), and keep Windows updated. Tools like Geek Uninstaller can monitor installations for leftover files. For corporate PCs, check Group Policy restrictions with gpedit.msc.

★★★★★4.7(15 reviews)
Categories Troubleshooting