This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(268.8, 64%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERP%3C/text%3E%3C/svg%3E)
Hi,
I am creating a multi-window application in C++ using WinUI3. To make the application even running if no windows are visible, I am creating an invisible window.
During exiting the application, we need to close all the Windows to come out of the event loop. So, while closing the visible windows, I don't face an issue. But while closing the Invisible Window, I am facing an error which is caught by my Vectored Exception Handler.
This is the error that I am facing:
Exception thrown at 0x00007FFE661953AC (KernelBase.dll) in Application.exe: WinRT originate error - 0x80000013 : 'The given object has already been closed / disposed and may no longer be used.'.
This is the exception code if I print inside VectoredExceptionHandler--> Exception Code: 1074266625 The thread 'DManip Delegate Thread' (10600) has exited with code 0 (0x0).
There is also a post which is being posted few years back and it is still open -- https://github.com/microsoft/WindowsAppSDK/issues/1836
Is it possible to reproduce the issue in a simple C++ project?
Yes, it is possible to reproduce the issue, create a blank WinUI3 app. Build it and run it and close the application, you would get the same error.
Where is the invisible window that causes the issue?
Just for replicating the issue, I said to create this sample project. Once upon closing the application you would get the same error message. Aren't you facing that issue?
The exception message can be observed, but the sample does not seem to have a hidden window.
Someone else already spent time with default applications:
I could reproduce the issue. I suggest you could follow the thread in the Github or post the new issue to the Github for better help.