Keep Getting "Outlook closed while you had items open. Reopen items from last session?" Even Though It's Not True

Hello and good morning/afternoon/evening (whichever applies)

I apologize for any misunderstanding (it's a byproduct of continuous threads).

Below is a copy/paste of my post from July 15. It worked for me flawlessly without any issues. I reverted back to the prior build in minutes.

Soon after I posted, Pete read my post and said he would try what I wrote, Later that day he replied saying that it did not work for him. I am using Outlook 2019 C2R and he's using Outlook 2021 C2R and he thought that might be the reason it didn't work for him.

On July 16 you posted a more thorough explanation of the procedure. There were also a few additional posts by others. Pete said he would try it again.

On July 17 (today) Pete said that your instructions worked. I reviewed what you wrote and what I wrote and couldn't find any difference in the command line so I was asking Pete if he made an error entering the command or if I've been overlooking an error in what I wrote.

I want to correct my post if there is an error because I don't want bad information posted since others will likely try it.

😊😊😊😊😊

----------------------------------------------------------------

POST FROM JULY 15 2023

This is how to revert back to Build 2305:

First, you need to disable Office updates. If you don’t disable updates, the problem update will reinstall itself. You can disable updates from the File menu in any Office application.

In Outlook go to File, Office Account, Update Options and click onDisable Updates.

Open the command prompt as administrator. If you are using Outlook 2016, 2019, or 365, copy the following line, then right click in the command prompt window to paste it. "C:\Program Files\Common Files\microsoft shared\ClickToRun\officec2rclient.exe" /update user updatetoversion=16.0.16501.20210

INCLUDE THE "QUOTES" AS SHOWN ABOVE. If you look at the screenshot below you'll see the first time I entered the command I forgot the beginning quote and it was not recognized. I then put in the quote, pressed Enter and the "update", or in this case "reversion", downloaded and installed.

To revert back to any other build, you can find the build numbers here:

Version numbers of update branches for Office 365 clients.

The format to revert back to a prior build is:

"C:\Program Files\Common Files\microsoft shared\ClickToRun\officec2rclient.exe" /update user updatetoversion=16.0.xxxxx.yyyyy (where you change xxxxx.yyyyy to the build you want)

I just did it and it works without any issues. I hope this helps others.

Hi G,

If the command did not revert to a prior version for you, what did the Command Prompt display? When a command doesn't run it generates an error message. What did the error message say?.

The command tells the OfficeC2RClient application to install the version indicated by the build number that was entered. In order for this to work:

The Command must be executed in an Administrator's Command window

The prompt must be moved to the folder that the OfficeC2RClient.exe file is located in. The example Path to the OfficeC2RClient.exe file is a default location and the Path to the location of the OfficeC2RClient.exe file on your system may need to be adjusted, but if the wrong Path is entered, the Command prompt will respond with an error message.

The build number must be entered exact for the version you want and the group number (16.0) must be part of that build number that is requested.

The PC must be connected to the Internet to allow the app to install the version.

Dear Pete

I see that you were able to revert back to the previous build. I'm glad you can put this to rest for a while. I wanted to ask if the steps you performed were different than the ones I posted. If so, would you please let me know what was different and if I had made any any errors or omissions so I can correct and update the information/instructions?

Thanks in advance and have a great day.

G

FYI (as the original poster of the question) I made the registry change several days ago, and the problem has not recurred.