Outlook 2016/2021 remains running after CreateObject() from VBA in Version 2412 and later

Hi everyone, I’d like to report a behavior change that affects Outlook (Classic) in Office 2016 and 2021, starting from Version 2412 (Build 16.0.18324.20168). We use VBA to check whether Outlook is...

bugcheck

outlook

VBA

MysterCamel

Iron Contributor

Jul 29, 2025

Add Application.Quitat the end of your VBA code to force-close Outlook. Then update Office to the latest version. If the process still lingers, check if COM objects are properly released, or replace CreateObjectwith GetObjectin your code.

Hans-DieterGehlen

Copper Contributor

Jul 31, 2025

Add Application.Quitat the end of your VBA code to force-close Outlook

Tried that already. That didn't help.

Then update Office to the latest version.

Version 2506 Build 16.0.18925.20076. Should be the latest non-beta version.

check if COM objects are properly released

Which other COM objects should be released if I never instantiated any other? We're talking about a fresh instance of Outlook.

replace CreateObjectwith GetObjectin your code.

How can I create an Outlook instance with GetObject if it is not running at all? My issue is just for this case. If Outlook was started before: no issue.

Any idea on why before update 2412, there was no issue at all?

Forum Discussion

Outlook 2016/2021 remains running after CreateObject() from VBA in Version 2412 and later

Resources