BUG: Explorer plugin duplicates explorer program

[cibere]

Checks

• I have checked that this issue has not already been reported.

• I am using the latest version of Flow Launcher.

Problem Description

I'm not sure how exactly to describe this since I've only done some preliminary testing and I don't know much about how it all works.

Though, based on my observations, it seems like the normal windows behavior is for there to be a single Windows Explorer instance which controls everything. Task bar, desktop, etc. With the explorer windows being subprocesses.

As for flow's behavior, it seems to create an entirely new instance of Windows Explorer with a new explorer window set as one of its children. Due to this, when the window is closed, the child is killed, but the parent instance is not.

Due to this, opening a folder using the explorer plugin will create a persistent (but seemingly dormant) instance of Windows Explorer that never seems to go away until the computer restarts or gets shutdown. Even through task manager, there seems to be no way of killing these extra instances without restarting.

To Reproduce

1. (optional) Open task manager and monitor the processes with the name Windows Explorer
2. open up a folder in flow
3. click on the Open in default file manager result
4. (optional) observe the new windows explorer instance with the window as a child instance
5. close the window
6. (optional) observe the child process being killed, but the parent instance staying alive and seemingly dormant.

Screenshots

To compare the two behaviors mentioned above, here is the result of me opening up my downloads folder in two different explorer windows manually:

And here is what happens when I open them through flow:

Flow Launcher Version

1.19.5

Windows Build Number

Microsoft Windows [Version 10.0.22631.5335]

Error Log

No response

[Jack251970]

Just found that Open containing folder in Visual Studio also had this problem😮

[onesounds]

@Jack251970 Is there anything else I need to change because of that, by any chance?

[Jack251970]

@onesounds Nothing I believe. I have already opened an issue in VS community.