I've noticed that when a Toad Beta update is available and I agree to update it fron within the app, it removes my substituted drive letters (e.g. ones mapped with SUBST.exe). This can have unexpected negative impacts on people's systems and simply shouldn't happen.
Also, if this is corrected in the OS, you do not see the SUBST drives when you open / save files, until you restart Toad.
I haven't checked if the same issue happens on Toad updates.
I cannot reproduce this. I used subst to map 2 virtual drives to paths. I opened Toad and I see them in the Editor's Open File dialog. While Toad was open, I mapped a 3rd drive and it is shown when opening the Open File dialog. I realized I left Windows Explorer open doing this so I closed it and mapped a 4th drive. It also shows in the Open File dialog without needing to restart Toad. All 4 of those drives remain after applying the beta update from the notification within Toad Beta. I tested by running the second to last 2024 R2 beta (24.2.266.4641) and clicking the new beta available notification to upgrade to 24.2.276.4667.
Very strange, it happens every time I upgrade the Toad beta and the new drive issue not appearing too. I only get this with Toad, no other app. BTW I'm using the 32 bit version.
Perhaps it's Windows version specific or some side effect of my company's background apps (anti-virus, monitoring, etc.), I'll keep my eye on it.
I have observed that this depends on how you install the update.
If you select the option that Toad is installed and then restarted automatically, then at least for me it was the case that Toad appears to be restarted in the admin context.
Network drives that I had connected as a normal user were then not available.
Since I noticed this, I always select the option that the update starts after Toad has been closed.
Then I select “Fast Exit” to save the current workspace und exit toad.
After the update, I start Toad manually and have not had the problem since then.