Global GUID BoxName

[7qCyZyMs]

As shown in the picture, this is what I have tried in the past half year.

Why do I adopt GUID BoxName? Because I have a large need to name boxes in languages other than English, the work of translating them into filter acceptable inputs has exhausted me.

I mean, you can fill the BoxName with GUID, UUID, or even anything randomly tapped on the keyboard without consuming any brainpower. Then focus on the name you really want to use on BoxAlias.

This kind of BoxName does not cause any obstacles in search. You can use Sandman File Panel to jump to the desired position.

[7qCyZyMs]

I wonder if there are enough multilingual users to require an automatic generator GUID code mechanism for BoxName.

Push Sandboxie-Plus to abandon the ancient BoxName and turn it into a meaningless and conflict-free ID string.

In this way, when you create a new Box in the UI, the name you immediately fill in is actually BoxAlias. There is no need to enter the section to edit, and there are not many input filters.

[offhub]

While using auto-generated GUIDs for box names might reduce naming conflicts, it would create a much bigger usability problem. Imagine spending 5 minutes digging through folders trying to figure out which GUID corresponds to which sandbox—that’s not efficient.

Meaningful box names (like ‘TestBrowser’ or ‘UntrustedDownloads’) act as instant identifiers, making it easy to manage sandboxes at a glance. If aliases were the only human-readable part, users would lose quick visual recognition in file explorers, logs, or backup paths.

[7qCyZyMs]

It doesn't take a few seconds. Double-clicking \drive in the File Panel is a good entry point. Just click once in the title bar to jump to the root path \Sandbox , and explorer will select the corresponding folder and highlight it automatically. In the worst case without a file structure in Panel, the Cell of the Path/Command Line column can also be copied, or click BoxContent-ExploreContent.