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: Most helpful
  1. lmacri 2,505 Reputation points
    2023-08-30T03:10:53+00:00

    Just an FYI that Version 2308 / Build 16731.20170 was released on 28-Aug-2023 for Microsoft Office C2R users on the Current Channel. However the release notes at https://learn.microsoft.com/en-us/officeupdates/current-channel#version-2308-august-28 do not mention anything about a fix for the "Outlook closed while you had items open. Reopen those items from your last session?” prompt or the missing setting at File | Options | General | Start Up Options.

    Microsoft's background article Outlook Unexpectedly Prompts to Reopen Items From Your Last Session also hasn't been updated since 03-Aug-2023 and still states "The Outlook Team is investigating this issue. We will update this topic when the fix status is available" so it looks like the bug fix isn't ready yet.


    Dell Inspiron 5584 * 64-bit Win 10 Pro v22H2 build 19045.3324 * Firefox v117.0.0 * Microsoft Defender v4.18.23070.1004-1.1.23070.1005 * Malwarebytes Premium v4.6.1.280-1.0.2117 * Macrium Reflect Free v8.0.7279 * Microsoft Office 2019 Home and Business 2019 Version 2307 / Build 16626.20170 Click-to-Run

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2023-08-30T00:40:40+00:00

    Thanks Paul for your previous reply that fixed this issue for you.

    I had this issue too, and just the simple process of running outlook as administrator has fixed it for me for now..

    Fingers crossed it doesn't come back (version 2307 atm)

    Edit: nope still happening

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2023-08-27T23:11:58+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.

    If people are still on 2306 they need to update, its currently at 2308 I am not saying 2308 has fixed it due to I stopped having this issue when I did what I posted a while ago and I was still using 2306 and have still yet to have this issue happen.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2023-08-27T23:09:11+00:00

    The only way to properly fix this 2019 Outlook issue is for Microsoft to replace the "Start up Options" code in the Option section under the general tab.

    That option does the exact same thing as doing the Registry change and nothing more.

    Also while you have the save outlook settings to the cloud enabled that registry change or that Start up Options will do absolutely nothing which is why they don't fix anything long term.

    But I also think that Start up Options should be populated like it is within Outlook in Microsoft 365 due to that option is populated there.

    But the fix I posted a while ago fixes the issue due to I have not had that issue since I first posted that fix.

    Was this answer helpful?

    0 comments No comments