Other times, users want to turn off automatic updates because they prefer a certain version of an app. Often, users will notice that the service host network service is taking up a lot of their bandwidth and slowing things down.
Also, you could see if there was a more recent build number available, and first try performing an update (moving forwards is always preferable than going backwards, no).The Windows Store’s ability to update apps automatically can be a very useful tool, but it can also be a nuisance. If that didn’t work, then I look to go further back, and so on. Typically, if you suddenly encounter a new issue, I’d determine my current build number and then try reverting to previous build number.
To learn more about changing update channels look over How to ‘Switch Channels’ for Office 2016 ProPlus. You would first need to switch update channels to make that version/build available to your installation and then you could perform the upgrade.
Your Update Channel is CriticalĪnother thing to be aware of is that even though say 1708 is available in the current channel, but is not in the Deferred channel, if you are using the Deferred channel you cannot upgrade to 1708. Remember to to disable automatic update should you wish to be frozen at this specific build. 2094 with the build number you want installed on your machine. Officec2rclient.exe /update user updatetoversion=.2094 Run the officec2rclient.exe /update command indicating the exact build number you which implementedĪ Concrete Example cd C:\Program Files\Common Files\Microsoft Shared\ClickToRun.Change into the folder that houses the officec2rclient.exe.Open a Command Prompt (as an administrator).These are the steps to revert/update to a specific build number: It is in fact very simple to do and takes but 2 command. Whenever performing a reversion or upgrade, I’d urge you to take note of the current Version/Build No of your installation should the change not be beneficial and you wish to return back to the initial state. So in fact, the xxxx.yyyy does not represent the version number but rather the build number! Yet, when you look at the Version and build numbers of update channel releases you’ll notice that the versions is actually a 4 character long number (1705, 1706, 1707, …).
xxxx.yyyy represents the full version number In the article, they mention that you have to execute a command similar to the one below officec2rclient.exe /update user updatetoversion=16.0.xxxx.yyyyġ6.0. Version/Build, Even Microsoft Can’t Keep Things Straight!
Now let’s make a few corrections and additions to their article!įirst and foremost, I think it important to point out that while this command can be used to uninstall an update and revert back to any build of your choosing (probably it primary function), it can also be used to perform an upgrade. How to revert to an earlier version of Office 2013 or Office 2016 Click-to-Run. You can read Microsoft’s instructions on uninstalling an update by using the following link: Microsoft no longer offers a graphic interface to manage the updates and one must use the “DOS” command prompt to uninstall updates (or as Microsoft now refers to it as “Revert to an earlier version”). With Office 365, much to most people’s dismay, one can no longer simply open the Control Panel to uninstall an update. This, on the surface, sounds like a brilliant approach, but as we have recently seen (updates 1705, 1706, 1707) sometimes updates can introduce new bugs that are more problematic then the ones they are supposedly resolving. While Office 365 will, unless reconfigured, automatically updates itself based on the Update Channel (you can learn more about Update Channel by reviewing Overview of update channels for Office 365 ProPlus) you have chosen to use (and yes, I too, never made any such choice and was automatically setup on the Deferred Channel). With Microsoft’s major push of Office 365, more specifically Click-to-run (C2R or CTR), I think it important to briefly touch base on the entire update process.ĭo note that the following also applies to the C2R versions of Access 2013, 2016, 2019, 2021+ the only difference being the build numbers.