Renaming a sandbox breaks Group hierarchy

[typpos]

Describe what you noticed and did

When you rename a sandbox that is inside a group, then the binding to the group breaks and the ini and UI are in an inconsistent state. When you restart SB+, teh renamed box is shown outside the group. When you restart SB+ again, then the (and any) empty group is removed.

Repro:

• Install & run SB+

• Create Group G

• Create Box A inside Group G

• Note, ini contains BoxGrouping=:DefaultBox,G \n BoxGrouping=G:A

• Start an application inside Box A to ensure Box A's file system is created. Exit the application.

• Rename Box A to Box B

• SB+ shows the renamed box as expected

• Error: ini contains BoxGrouping=:DefaultBox,G \n BoxGrouping=G:A, but box name in ini and SB+ is now B.

• Restart SB+ (Sandbox > Exit)

• Error: Sandbox B is now shown outside Group G; Group G is empty

• Error: ini now contains BoxGrouping=:DefaultBox,G,B

• Restart SB+ (Sandbox > Exit)

• Error: SB+ no longer shows group G and the ini has Group G removed.

• This may be an unrelated error. Empty groups seem to always be dropped on restart. Is this intentional?

Related:

• Install & run SB+
• Create a group G and inside it Group H
• Restart SB+
• Group H is gone
• Restart SB+
• Group G is gone

How often did you encounter it so far?

Always

Affected program

n/a

Download link

n/a

Where is the program located?

Not relevant to my request.

Expected behavior

Group membership of box remains unchanged.

What is your Windows edition and version?

Windows 10 Pro 22H2

In which Windows account you have this problem?

Not relevant to my request.

Please mention any installed security software

n/a

What version of Sandboxie are you running?

v1.12.0

Is it a new installation of Sandboxie?

I recently did a new clean installation.

Is it a regression?

No response

In which sandbox type you have this problem?

In a standard isolation sandbox (yellow sandbox icon).

Can you reproduce this problem on a new empty sandbox?

I can confirm it also on a new empty sandbox.

Did you previously enable some security policy settings outside Sandboxie?

No. The problem can be reproduced in a "new" Windows Sandbox.

Crash dump

No response

Trace log

No response

Sandboxie.ini configuration

No response