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

Anonymous
2023-07-05T13:34:20+00:00

This just started happening. Whenever I open Outlook, I get the message "Outlook closed while you had items open. Reopen items from last session?" even though this is not true -- I did not have items open when I closed Outlook. Using Windows 11. Screenshot of what version of Outlook I have:

Outlook | Windows | Classic Outlook for Windows | For business

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
Answer accepted by question author
Anonymous
2023-07-07T17:46:51+00:00

I'm on build 2306. Is this the reg key in question?

HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Outlook\Preferences
DWORD: ReopenWindowsOption
Value: 1

Yes.

Some users that updated to 2306 have reported that the key was not already in the Registry and had to add it and the value.

Was this answer helpful?

40+ people found this answer helpful.
0 comments No comments

178 additional answers

Sort by: Oldest
  1. Anonymous
    2023-07-18T19:01:37+00:00

    Why is everyone downgrading Office, there is absolutely no reason to do so and you run the risk of any security holes that might of been fixed in the current latest update.

    I just did the following:

    #1 Run Outlook as an Elevated Process (i.e. as Administrator) this is so that if Outlook needed to set stuff outside the Users location (i.e. SYSTEM LOCATIONS)#2 Once opened if popup saying closed with open files, then click on NO.

    #3 Disable storing the Outlook settings under Cloud storage options shown in the image below:

    #4 Set (add DWORD 32-bit item with name ReopenWindowsOption if not already there) ReopenWindowsOption and set its value to 1 in the following location: Computer\HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Outlook\Preferences

    #5 Close Outlook and Reboot-System just to make sure new settings are loaded up.

    To be honest I think it might just be the disabling of Outlook saving its settings on the cloud that was causing this issue, but I thought I would say what I changed just in case it was a combination of what I did as a whole.

    Image of Outlook settings in the cloud:

    I did this back on the 13th July and have not gotten any more of those popups since.

    Was this answer helpful?

    4 people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2023-07-18T19:29:39+00:00

    Hi Drcard:)),

    I printed and followed exactly your excellent step by step instructions to achieve the rollback to the previous version, so I should have opened the Admin command prompt.

    It's time to rush off to work, I will try to reply more in depth tonight, but be aware I'm at nowhere near the level you are at.

    Pete

    Was this answer helpful?

    0 comments No comments
  3. lmacri 2,505 Reputation points
    2023-07-18T21:19:10+00:00

    Why is everyone downgrading Office, there is absolutely no reason to do so and you run the risk of any security holes that might of been fixed in the current latest update.

    I just did the following ... and have not gotten any more of those popups since.

    Hi Paul From London:

    Do your instructions also restore the missing settings at File | Options | General | Start Up Options or do they just prevent the “Outlook closed while you had items open. Reopen those items from your last session?” prompt from appearing at Outlook startup? As far as I know you must roll back to Version 2305 or earlier to restore those missing settings.

    Unfortunately, I am unable to follow Step # 3 of your instructions and disable the Store My Outlook Settings in the Cloud checkbox because I do not have a section titled Cloud Storage Options at File | Options | General in my Outlook 2019 C2R settings. See the image in my 13-Jul-2023 post <here> on page 3 of this thread.

    I only see the occasional “Outlook closed while you had items open. Reopen those items from your last session?” prompt at Outlook startup, and while this is somewhat annoying I agree with you that I don't want to roll back to Version 2305 since this will remove the security patches for the 10 exploits patched by Version 2306 / Build 16529.20182 on 11-Jul-2023 (see the Release Notes for Microsoft Office Security Updates). I've decided it's safer to just to wait and see if the next Office C2R update fixes the bug being discussed in this thread.


    Dell Inspiron 5584 * 64-bit Win 10 Pro v22H2 build 19045.3208 * Firefox v115.0.2 * Microsoft Defender v4.18.23050.5-1.1.23060.1005 * Malwarebytes Premium v4.5.33.272-1.0.2069 * Macrium Reflect Free v8.0.7279 * Microsoft Office 2019 Home and Business 2019 Version 2306 / Build 16529.20182 C2R

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2023-07-19T08:31:55+00:00

    Hi Gregory Assistance Needed,

    I thought I saw a post from you in **** asking if someone can advise how to roll back to 2035. If I'm wrong apologies in advance, if correct I have put Drcards:)) procedure below.

    Just so everyone knows:

    The procedure to revert to a prior version (any prior version) applies to Microsoft 365, and the C2R versions of 2013, 2016, and 2019 of Outlook. The Outlook versions must be Click-To-Run and will not work for other versions.

    That command tells the Client to Run app file on these system to upgrade to the version listed in the command.

    To help understand this process here are my instructions oh how to revert to a prior version written in more detail.

    Undo an Outlook Update

    Note: This applies to only C2R versions of Outlook. This includes Microsoft 365 and the C2R versions of 2013, 2016, and 2019. To see if you have the C2R version: open Outlook, select File > Office Account. Look for C2R or Click-to-Run after the version and build number under About Outlook.

    What

    A command in an Administrator’s Command window and an Internet connection can cause Outlook to “update” to the build number indicated in the command. Using the prior version’s build number reverts Outlook to the prior version and “undoes” the update.

    Why

    When an update to Outlook (which installs silently) causes problems, you can undo the update and revert to the version you had before the update occurred as a way to get rid of the problem. Reverting to a prior version and stopping updates avoids the problems and gives Microsoft time to fix the update bug. After you find out the update has been fixed, then you can resume updates problem free (hopefully).

    How

    Step 1 - Disable Outlook Updates

    • Open Outlook

    • Select File > Office Account

    • Click dropdown arrow by Update Options

    • Select Disable Updates. This will cause an UAC box to open to authorize this change. Click Yes to allow the change in settings.

    Step 2 - Find Build Number to Revert To

    • The command directs Outlook to change its files to match those found in the build number indicated in the command. In order to revert to the prior version you need the build number for that prior version. Here’s how to find that build number for the prior version:

    • Open Outlook

    • Select File > Office Account

    • Under About Outlook note your current version and build number

    • Click the dropdown arrow for Update Options and select View Updates. This opens your default browser to a Microsoft Release Notes page with a list of versions for your Outlook.

    • Click the version list just below the version you currently have. The version number is a link to specific details of that version including the build number for that version.

    • Make sure you have the right version and if the same version number is listed twice, select the last one released. To make sure I get the build number correct, I highlight and copy just the number as well as write it down.

    Step 3 - Revert to Prior Version

    • You must have your PC connected to the Internet. Close Outlook.

    • Open an Administrator Command window by opening a Run box (WinKey + R), enter cmd, press the Ctrl + Shift + Enter keys at the same time, and click Yes to the UAC query box that opens.

    • At the prompt enter the following command and press the Enter key:

    CD %programfiles%\Common Files\Microsoft Shared\ClickToRun\

    • The above command is suitable for copy and paste. Note the space between CD and %. This command will change the prompt location to the folder where the OfficeC2RClient.exe application file is kept. The above command changes the prompt location to the default location on all the versions stated above except 2013 C2R, whose default location is in a different folder. Search for the folder that contains the OfficeC2RClient.exe file and adjust the command above to change the prompt location to that folder.

    • With the prompt location at the folder that the OfficeC2RClient.exe file is located in, enter the following command:

    OfficeC2RClient.exe /update user updatetoversion=16.0.build number

    • The above command is Not suitable for copy and paste. The build number must be replaced by the actual build number for the version you want. Notice the 16.0. before the build number. This is the Office group number which is 16.0 for 365, 2016, and 2019. For 2013 the group number is 15.0. Note the period between the group number and the build number. Example of the command for Outlook 2019 C2R to revert from version 2306 to version 2305 (Build 16501.20210):

    OfficeC2RClient.exe /update user updatetoversion=16.0.16501.20210

    • After pressing the Enter for your command various windows will open as the OfficeC2RClient app gets the files from Microsoft and performs the version placement requested.

    • When finished the prompt will return to the same prompt location awaiting your next command.

    • Close the Command window.

    • Open Outlook and check the version/build in Office Account and you will see the version build you requested.

    • You will also see that whatever the last update did, reverting to a prior version has undone what it did.

    Was this answer helpful?

    0 comments No comments