When you try to install Office you may get an error message that says, We’re sorry, but we could not start your Office installation. Another installation is in progress, please try again later. Or the error message might contain one of these error codes 0-1018, 17003-2031, or 2035-0. Show This error usually occurs if another installation, update, or uninstall was running before you tried to install Office. Check for an Office icon in the Windows system tray and click it to check the install progress. If an install is already running, wait until it's done before you start your Office install. If you can't find an Office icon in the system tray, follow the steps below to restart Office and then try the installation again. If that doesn't work run the uninstall too to clean up any full or partial Office installations and then reinstall Office. Restart your computer and reinstall Office
Uninstall and reinstall OfficeUse the Office uninstall support tool to completely uninstall Microsoft 365 from your computer and try reinstalling Microsoft 365 again.
See AlsoUninstall Office from a PC Need more help?Want more options?Explore subscription benefits, browse training courses, learn how to secure your device, and more. Communities help you ask and answer questions, give feedback, and hear from experts with rich knowledge. 1 - the software had run well on my main computer for years, and until a few days ago. That machine is running Windows 10 Pro, build 19045.2364. It is running Word version 15928.20198. 2 - the other computer is a Microsoft Cloud Computer, running Windows 10 Enterprise, build 19045.2364, with Windows Feature Experience Pack 120.2212.4190.0. 3 - the file shown in the code as a "template" is not a word template file - it is a .docx file that i use as a prototype. (I don't think it matters for this thread, but what the application does is to take the prototype and then append another file to it - and then I loop through the whole document to clean up formatting, styles, replacing certain characters or strings, etc.) The issue turns out to be that I open the prototype file with the ReadOnly property set to true - see above. The fix was to copy the prototype (so that the original does not get altered), open it as ReadOnly: false, and then go through my process. My guess is that the latest update of the Word kernel is more "strict" about the ReadOnly property and does not allow editing at all. The old version allowed editing but required that the resulting file get saved to a new name (which is what I used to do). I ended up solving this through guesswork - so what i find frustrating is that I'd have been in a better position to understand what changed if I had been able to look up the exception message and get a clear understanding of what it meant ("This method or property is not available because the current selection is in a limited editing zone."), and I sure wish there had been documentation of this being a change from the earlier version of Word that had worked up until a few days earlier - and continues to work on the un-upgraded machine. I hope this helps. Like every other MSFT developer, my days always ping pong between admiration and frustration with MSFT. |
