microsoft / microsoft/AzureStorageExplorer
Implement proper multi-window support
@craxal is already working on this.
Since Apr 14, 2026.
- Dominant language
- No language data
- Stars
- 452
- Forks
- 92
- Avg merge
- 15h 20m
- Merged PRs (30d)
- 3
Description
Storage Explorer has the "New Window" feature but it has lots of problems today.
Related issues:
-
Quick Access data is not visible to the secondary instances.
https://github.com/microsoft/AzureStorageExplorer/issues/638 -
Local storage data is not visible to the secondary instances.
https://github.com/microsoft/AzureStorageExplorer/issues/723 -
Secondary instances may overwrite local storage data of primary instance.
https://github.com/microsoft/AzureStorageExplorer/issues/8139 -
Subscription filter data is not visible to the secondary instances.
https://github.com/microsoft/AzureStorageExplorer/issues/213 -
"New Window" doesn't work for snap.
https://github.com/microsoft/AzureStorageExplorer/issues/4529 -
Due to lack of coordination, primary and secondary instances may race and corrupt data when writing to the shared resources such as files on disk or objects in local credential store. This is currently mitigated by not allowing the secondary instance from writing to shared resources at all.
We need proper multi-window support where Storage Explorer application manages all the windows of itself and coordinate them using the shared main process. This would allow us to implement our own concurrency control to prevent race conditions and maybe allow it to work for snap since the application no longer need to have the permission to spawn new processes.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.