{"id":527,"date":"2019-10-21T22:05:12","date_gmt":"2019-10-21T22:05:12","guid":{"rendered":"https:\/\/www.dedicatedmanagers.com\/?p=527"},"modified":"2019-10-25T02:32:24","modified_gmt":"2019-10-25T02:32:24","slug":"microsoft-office-deployment-tool-couldnt-install","status":"publish","type":"post","link":"https:\/\/www.dedicatedmanagers.com\/microsoft-office-deployment-tool-couldnt-install\/","title":{"rendered":"Microsoft Office Deployment Tool \"Couldn't Install\" Error"},"content":{"rendered":"\n

While helping to install Microsoft Office 2019 on a client's computers, I came across a horrific error message that kept me baffled for nearly an hour as (it turned out) the error returned by the Microsoft Office Deployment tool was not at all accurate. <\/p>\n\n\n\n

The Microsoft Office Installation Tool error returned a window that stated, \"Couldn't install\" and \"We're sorry, we had a problem installing your Office program(s).\"<\/p>\n\n\n\n

The resolution offered by the message was a couple of questions, \"Is your internet connection working? Do you have enough free space on your main hard drive?\" with the error code \"Error Code: 30029-1007 (0)\". <\/p>\n\n\n\n

I was installing Microsoft Office 2019 on a brand new computer and was doing so using a remote management tool. Thus, I knew there was plenty of hard drive space and that the internet was working.<\/p>\n\n\n\n

This issue turned out to be that, because the computer's Windows Explorer wasn't configured to display file extensions, I had made a slight error in the name of the configuration file versus the name of the file I was trying to enter into the tool on the command line. The Microsoft Office Deployment tool was therefore not finding the configuration file and was erroring out with the nonsense message above.<\/p>\n\n\n\n

In the video below, I describe the issue in further detail and show the resolution: <\/p>\n\n\n\n

(Skip to approx 9:48 of the video if it doesn't automatically do so) <\/p>\n\n\n\n