Microsoft Office 2016 encountered an error during Setup

Anonymous
2016-09-22T08:56:37+00:00

I have tried to install the Office on Windows 10 Home but unable to complete it. almost nearly at the end the installation process rolls back and an error message "Microsoft Office 2016 Professional encounter an error during setup" appears. I have read the thread on this same issue and have tried everything suggested there but to no avail. I had a working office on this same machine previously but due to some reasons I had to recover my windows to it's factory defaults. After that I am unable to install the office at all. Any help guys, i am attaching the screenshot of the error.

here is the log file

Setup 2016 Log File.txt

Microsoft 365 and Office | Install, redeem, activate | For home | Windows

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments
Answer accepted by question author
Anonymous
2016-10-27T18:25:08+00:00

I have found a solution to the problem and it calls for you to go into the scheduled task and delete the Office folder in that and then try to install Office. Try this...

  • I know this is a necro post but I wanted to add to the solution list for anyone else who continues to have this problem, even now in 2016.

I was having this same issue and tried every solution on this post without success.  It should be noted, my issue started after I attempted to unininstall a component of my existing Office 2013 installation.  Instead of launching the "change" dialog of the MS Office Setup, the system registered that event as a flat uninstall of Office Pro 2013.  From that point forward I was unable to reinstall Office 2013 Pro.  I had other Office 2013 apps installed (Visio and Project) so I even removed those hoping that would fix it but setup continued to fail.

At any rate, I ended up finding the solution myself, however I do not fully understand why it was an issue to begin with.  At any rate...

I first properly enabled verbose logging by following instructions found here (since the instructions contained within this post seemed to miss a few steps):  https://blogs.technet.microsoft.com/odsupport/2010/12/30/troubleshooting-office-installation-failures/

While looking at the logs I found my issue stemmed from the following command trying to be run:  

MSI(INFO): 'CAQuietExec:  Entering CAQuietExec in C:\WINDOWS\Installer\MSIEA18.tmp, version 3.6.3025.0'

MSI(INFO): 'CAQuietExec:  "schtasks.exe" /create /f /tn "Microsoft\Office\OfficeTelemetryAgentLogOn" /xml "C:\Program Files\Microsoft Office\Office15\1033\officeinventoryagentlogon.xml"'

MSI(INFO): 'CAQuietExec:  ERROR: The system cannot find the path specified.'

MSI(INFO): 'CAQuietExec:  '

MSI(INFO): 'CAQuietExec:  Error 0x80070001: Command line returned an error.'

MSI(INFO): 'CAQuietExec:  Error 0x80070001: CAQuietExec Failed'

It was erroring trying to register a scheduled task but was complaining that the system could not find the path specified.  After tracking with procmon I verified the XML file used for this command was actually being created.  I then focused on the other path mentioned in that error:  "Microsoft\Office\OfficeTelemetryAgentLogOn".

This is the path the scheduled task would actually live at so I opened Task Scheduler and drilled down through the path.  I found my path ended at "Microsoft\Office" and there were 0 tasks here.  

Since this path was empty, I deleted the Office folder entirely from Task Scheduler and re-ran setup again.  This time it finished successfully!

I don't know why the simple fact that the Office folder existed within Task Scheduler prevented this from running but its removal fixed my issue.

Was this answer helpful?

1300+ people found this answer helpful.
0 comments

50 additional answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2016-12-21T19:57:45+00:00

    Thanks a ton! Deleting the parent folder in Task Scheduler solved the issue in the OP for me as of 2016-12-21.

    I have a hunch that this is partially due to the "Get Office" thing that comes on some new PCs, since I've had this computer for 2 days and have never had office on it. The only other things I'd installed prior to Office were Matlab, Google Chrome, and League of Legends, so no other Microsoft stuff or anything office related. I had removed the "Get Office" thing, though... perhaps that left the task folder in the task scheduler. Anyhow, thanks a ton for the solution!

    For posterity, things I had tried which failed: 

    (1) This Link:

    https://support.office.com/en-us/article/Uninstall-Office-2016-Office-2013-or-Office-365-from-a-PC-9dd49b83-264a-477a-8fcc-2fdf5dbf61d8

    Ran the resulting autofix file "o15-ctrremove.diagcab"; that didn't work. Ran the manual instructions; that didn't work either.

    (2) Poking around and other sites

    Checked the registry and around my HDD looking for anything "Office" or MSO (also checked out program files, program data, etc.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2016-12-14T15:10:46+00:00

    I get this very same error but in my case, Office 2013 or 2016 fail.   Office 2010 re-installed without a problem.

    My error log shows the same task scheduler error during install, the telemetry agent task scheduler.

    I don't have any office folder in task scheduler or maybe I just don't understand where people are looking

    Here is my Task Scheduler:

    There is no Office folder to delete.   I've renamed windows help, ran the latest "office remover" o15-ctrremove.diagcab .  I've reinstalled Office 2010 and uninstalled, done the reboot etc..  Same failure.   Reran the office remover, rebooted, same failure.   Created a new empty user account and booted in clean mode.  Same failure.    

    I did notice one interesting thing.  If I do a custom install and select all for install on demand and force Skype and OneDrive to not install, the install errors on a different task with this error:

    CAQuietExec:  "schtasks.exe" /create /f /tn "Microsoft\Office\Office 15 Subscription Heartbeat" /ru SYSTEM /xml "C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE16\HeartbeatConfig.xml" <br><br>CAQuietExec:  ERROR: Cannot create a file when that file already exists. <br><br>CAQuietExec:  Error 0x80070001: Command line returned an error. <br><br>CAQuietExec:  Error 0x80070001: CAQuietExec Failed

    I am also using licensed media, it should be the same as non-profit media. "SW_DVD5_Office_Professional_Plus_2016_W32_English_MLF_X20-41353.ISO"

    I installed using this exact ISO mounted locally on Windows 10 before, it's good clean software :p

    On a side note, I have had this problem since Windows 10 was first offered as an upgrade.  This particular computer was upgraded from Windows 7 Ultimate OEM.   I've been stuck on 2010 since then and every time I tackle the problem, regardless of what install options are chosen, the error is the same.  Something about installing a task.

    The SYSTEM account has full control on the tasks folder in Windows.

    Also, this computer is on a domain and I logged in locally.   I have placed this computer in an OU where inheritance is blocked.  No group policies are being applied to this PC or user account.

    Perhaps Windows 10 stores these task definitions somewhere other than c:\windows\tasks?

    Was this answer helpful?

    20+ people found this answer helpful.
    0 comments
  3. Anonymous
    2016-12-02T19:51:58+00:00

    Been trying to sort this for hours and your solution was spot on!

    Ran the installer again after deleting the folder from the Task Scheduler and it went all the way through without a hitch.

    Thanks so much!

    Was this answer helpful?

    10+ people found this answer helpful.
    0 comments
  4. Anonymous
    2016-11-01T12:44:10+00:00

    Marivel

    I have a Volume License for our non-profit making organisation. Did the installation work after obtaining the installer?

    Was this answer helpful?

    0 comments