[Fix] Windows cannot find Winword.exe or Excel.exe — Can’t open Any Program

When you open Office programs such as Word, Excel, PowerPoint, Outlook, etc, nothing may happen (except for the screen flash) if you double-click the program shortcut. If you open the Office program’s folder and double-click the executable (e.g., winword.exe, excel.exe, powerpnt.exe, outlook.exe) directly, the following error(s) occur:

Windows cannot find ‘C:\Program Files\Microsoft Office\root\Office16\WINWORD.EXE’. Make sure you typed the name correctly, and then try again.
Windows cannot find ‘C:\Program Files\Microsoft Office\root\Office16\EXCEL.EXE’. Make sure you typed the name correctly, and then try again.
Windows cannot find ‘C:\Program Files\Microsoft Office\root\Office16\POWERPNT.EXE’. Make sure you typed the name correctly, and then try again.
Windows cannot find ‘C:\Program Files\Microsoft Office\root\Office16\OUTLOOK.EXE’. Make sure you typed the name correctly, and then try again.

avast avg debugger cannot open office apps

The result would be the same if you double-click on a .doc/.docx, .xls/.xlsx file. Cleanly uninstalling and reinstalling Office also may not help. Also, the same error can happen when you attempt to open non-Office programs installed on your computer.

Cause

This issue may be caused if you have used Avast Cleanup, AVG TuneUp, or any other tweaking program on the computer. Avast Cleanup and AVG TuneUp programs have a feature called “sleep mode” wherein some of the resource-intensive programs are identified and put down to “sleep”.

avast avg debugger cannot open office apps

When a program is set to sleep mode using Avast or AVG TuneUp, a “Debugger” registry entry is added for that program. The debugger points to one of the following Avast or AVG TuneUp executables which blocks the selected program from running in the background.

C:\Program Files (x86)\AVG\TuneUp\autoreactivator.exe
C:\Program Files\AVG\TuneUp\autoreactivator.exe
C:\Program Files (x86)\AVAST Software\Avast Cleanup\autoreactivator.exe
C:\Program Files\AVAST Software\Avast Cleanup\autoreactivator.exe

Let’s say, using AVG or Avast you activate the sleep mode for certain programs. Later, one of the following situations can cause your programs from launching.

  1. After an AVG or Avast program update, if the path to autoreactivator.exe changes, the applications which were put to sleep would fail to work.
  2. You uninstall Avast Cleanup or AVG TuneUp software without first re-enabling the apps which were put into sleep mode.
  3. Your Avast or AVG TuneUp license expires, but the blocked (sleep) programs are not automatically unblocked.

In June 2020, AVG support acknowledged this issue on their support forum:

[AVG Support]
https://support.avg.com/answers?id=9060N000000gWcYQAU

We have already informed our developers regarding the issue after updating AVG TuneUp to the latest version 20.1.

We will release a fix regarding it as soon as possible.

We request your patience and understanding.

[Avast Support]
https://forum.avast.com/index.php?topic=233129.msg1549710#msg1549710

Again we really apologize for this situation, it was caused by a bug in the update we’ve released yesterday.

We already have a fix which we are verifying right now and we will release it as an update later today.
The update will fix everything so you should be again able to use the programs you previously put to sleep without any limitations.

Please bear with us, we are trying to get it fixed as soon as possible and won’t stop until this whole situation will be resolved.

Avast software and AVG have merged in 2016. An Avast staff said that they have combined their engines while keeping separate products as both Avast and AVG are strong brands with different features.

To know more about the sleep mode feature in Avast Cleanup, check out their blog post at the following link:

A much-needed wake-up call: “Sleep Mode” for slow PCs:
https://blog.avast.com/a-much-needed-wake-up-call-sleep-modefor-slow-pcs

tips bulb iconThe debugger registry value is used to redirect a program to another program. For instance, Microsoft SysInternals’ Process Monitor replaces Task Manager in the same way. We used the debugger technique to replace Notepad with Notepad++ in one of our previous articles.




RELATED: Error “Windows cannot find taskmgr.exe” Opening Task Manager

[Fix] Windows cannot find Winword.exe or Excel.exe

To fix the Windows cannot find program.exe error when opening Office or other programs, follow one of these methods:

Option 1: Re-enable programs that were put to Sleep

If you’re still using the AVG TuneUp or Avast Cleanup program, make sure you re-enable the programs that were put to sleep mode earlier. This would release the debugger for those installed programs.

Open AVG TuneUp or AVAST Cleanup program and activate all sleeping programs. However, if you want to place those programs to sleep mode again, you can set them back to sleep mode after that. This creates new entries for the reactivator in the registry.

  • Open AVG TuneUp or Avast Cleanup, click on the Speed up icon.
  • Open Background & Startup programs.
  • Scroll down and find the section with a green font that says # programs sleeping and expand it.
    avast avg debugger cannot open office apps
  • Find your program on the list and click “wake“.
  • Repeat the same for every other program you want to wake/unblock.

Option 2: Remove the Debugger registry value manually

If you’ve already uninstalled AVG or Avast Cleanup, then follow these steps to remove the orphaned Debugger registry value for each program which was put into sleep mode.

  1. Start the Registry Editor (regedit.exe)
  2. Go to the following branch:
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options
  3. Expand the Image File Execution Options key.
  4. To unblock Microsoft Word, select the subkey named winword.exe
  5. In the right-pane, right-click the value named Debugger, and choose Delete.
    avast avg debugger cannot open office apps
  6. Click Yes to confirm. That’s it. Microsoft Word is unblocked now.
  7. Similarly, delete the Debugger registry value for every executable that was put into sleep mode. Here are some more subkeys that you may need to check:
    • excel.exe [Microsoft Excel]
    • powerpnt.exe [Microsoft PowerPoint]
    • msaccess.exe [Microsoft Access]
    • mspub.exe [Microsoft Publisher]
    • onenote.exe [Microsoft OneNote]
    • outlook.exe [Microsoft Outlook]
    • AcroRd32.exe [Adobe Acrobat Reader]
    • Chrome.exe [Google Chrome]
    • Firefox.exe [Mozilla Firefox]
    • Iexplore.exe [Internet Explorer]

    Quick Tip: With the Image File Execution Options branch selected, you can do a search for autoreactivator.exe in the Registry Editor to find and manually remove every occurrence of the debugger value.

    avast avg debugger cannot open office apps

  8. Exit the Registry Editor.

You should be able to start Office programs (and any programs that were put into the sleep mode using AVG or Avast) now.


One small request: If you liked this post, please share this?

One "tiny" share from you would seriously help a lot with the growth of this blog. Some great suggestions:
  • Pin it!
  • Share it to your favorite blog + Facebook, Reddit
  • Tweet it!
So thank you so much for your support. It won't take more than 10 seconds of your time. The share buttons are right below. :)

Ramesh Srinivasan is passionate about Microsoft technologies and he has been a consecutive ten-time recipient of the Microsoft Most Valuable Professional award in the Windows Shell/Desktop Experience category, from 2003 to 2012. He loves to troubleshoot and write about Windows. Ramesh founded Winhelponline.com in 2005.

5 thoughts on “[Fix] Windows cannot find Winword.exe or Excel.exe — Can’t open Any Program”

  1. Just want to say thanks! When it said it couldn’t find the very file I was clicking on I knew it must be something like that, but you saved me a ton of digging!

    Reply
  2. I bow down to you for this most excellent advice!! I was struggling for a few hours after uninstalling AVG. I come from mainframe background and not too familiar with the registry. Your guidance is most appreciated. 😊

    Reply

Leave a Comment