This change is unrelated to manually assigning drive letters when you create a RAM disk — that still works exactly as before. You can choose any letter you like.
What was removed is the separate "Global drive letters for RAM volumes" option that used to be in Settings. This option controlled the
namespace in which the drive letter was created:
- Local (per-session) namespace — the drive letter was visible only inside your current logon session. Services, elevated processes, scheduled tasks and other user sessions could not see it.
- Global namespace — the drive letter is visible system-wide to every session, service, and elevated process.
In version 26.4, RAM disk letters are always created in the global namespace and managed by the Windows Mount Manager (the same component that handles letters for normal disks). This is the more useful behaviour and matches what users expect, so the option to choose between local and global was no longer needed.
In short: assigning a specific letter still works as before. Only the internal namespace toggle was removed.