none
Office 2016 Updates Roll Back

    Question

  • I tried to Roll back my Office 2016 updates using the link below and the process only checked for updates. 

    support.microsoft.com/en-us/help/2770432/how-to-revert-to-an-earlier-version-of-office-2013-or-office-2016-click-to-run

    Is there something else that's needed?  I ran with updates enable and disabled, chose different build.  do I need to change channel first?

    Friday, May 05, 2017 5:37 PM

All replies

  • Hi Donnie G,

    I'd like to know or confirm:
    (1) what is your issue (what do you want to do)?
    (2) whether your Office 2016 is Click-to-Run (you can find it [File] > [Account])?
    (3) which version and build of your Office 2016?
    (4) why do you want to revert to earlier version?
    _______________
    Ashidacchi
    • Edited by Ashidacchi Saturday, May 06, 2017 12:27 AM
    Saturday, May 06, 2017 12:26 AM
  • If you need to roll back to an older build within the same channel you can do that. The build number is an example where your instructing the C2R client to move to that specific build.

    OfficeC2RClient.exe /update USER displaylevel=True forceappshutdown=true updatetoversion=16.0.7341.2029

    You can cross reference the builds by channel using he the following link

    https://support.office.com/en-us/article/Version-and-build-numbers-of-update-channel-releases-ae942449-1fca-4484-898b-a933ea23def7?ui=en-US&rs=en-US&ad=US#bkmk_bydate

    Since this is a SaaS application, you'll need to move forward to address each month security updates.


    Dave Guenthner [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights. http://blogs.technet.com/b/davguents_blog

    Saturday, May 06, 2017 2:02 AM
  • >>do I need to change channel first?

    The key point here is - You will need to update to a previous build on the same update channel as your current installation.

    Regards,

    Ethan Hua


    Please remember to mark the replies as answers if they helped.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, May 08, 2017 7:57 AM
    Moderator
  • My issue is that I am trying to help a client rollback his office update to a previous build, and we have tried the link below and it only comes back with "You are currently running the latest update approved by your system administrator.

    https://support.microsoft.com/en-us/help/2770432/how-to-revert-to-an-earlier-version-of-office-2013-or-office-2016-click-to-run

    He is the Company Administrator and says he has not set any policies that do not allow Rollbacks.  He is not to specific as to why he needs the rollback but says that the latest update is causing errors in outlook and he wants to rollback the latest update.

    He is currently on build 7967.2139 and wants to rollback to 7766.2076.

    I am able to complete the rollback on my machine successfully, but it only seems to check  for updates on his machine.  We have uninstalled and attempted to reinstall and older build but even then it always reverts to the 2139 build.

    The subscription is click to run and we have disable automatic updates in the office client but any install seems to come back to the 2139 build.


    ALG

    Monday, May 08, 2017 2:34 PM
  • I'm having this problem as well. Client is on 1705 8201.2102 . I've tried rolling back to build 8201.2075 and 1701 Build 7766.2092 and  1609 (Build 7369.2139) but I get the same result, You're up to date!

    Used the command OfficeC2RClient.exe /update user updatetoversion=16.09.7369.2139

    Can anyone help?

    Tuesday, June 27, 2017 3:58 AM
  • Been corresponding with Microsoft support and they cannot give me an answer either, been on the ticket for a few days now.

    Surely someone has an answer to this.

    Friday, June 30, 2017 1:28 AM
  • Same problem here. I want to rollback 16.0.8229.2073 to 16.0.8201.2102 but nothing happens. OfficeC2RClient gives me a popup with the message "Office is up to date".

    I'm frustrated.

    Friday, July 07, 2017 8:08 AM
  • I found that when I rolled pack using a previous build but the same VERSION number, I received the same 'Office is up to date" message.  I was on ver. 1707 and the latest build cause a significant conflict with other software causing an important add-in not to run.  However, when I went back to version 1706 (several builds back which was about 5-6 weeks prior) the roll-back was successful on the first try.  So my suggestion is to go back an entire version number and not just to the previous build.
    Monday, August 28, 2017 2:49 PM
  • >>do I need to change channel first?

    The key point here is - You will need to update to a previous build on the same update channel as your current installation.

    Regards,

    Ethan Hua


    Please remember to mark the replies as answers if they helped.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    As Ethan mentioned, being on the same channel is important.  If you are not using version numbers from the same channel, it isn't going to work.

    I received the same issue as the OP when I tried using the wrong channel.  If you use builds from the same channel, you're likely to be successful.

    Remember however, to use local settings, registry edit, or Group Policy to disable automatic Office Updates for the systems you're rolling back though, or they'll just patch themselves again.


    Everyone gets everything he wants. Me, I wanted to be a sysadmin. And for my sins --they made me one.


    • Edited by LoneWolf15 Tuesday, August 29, 2017 2:19 PM
    Tuesday, August 29, 2017 2:16 PM
  • Hello, I am having the same issue. The user is on 1707 build 8326.2096 and I'd like to roll them back to a previous version.  What is the command I need to use to roll them back?  I'm not sure what syntax to use for the version number.  Thanks
    Wednesday, September 06, 2017 2:48 PM