Direct answer
A saved Box should remain available after restarts unless the user deliberately closes it, hides it through the tray controls or ends the application. Minimizing changes only its display. Closing is a separate destructive organization action that requires a prominent confirmation, while underlying files must be handled safely and never disappear silently.
Who this guide is for: For users who need to understand persistent Box visibility, safe closing, tray access, restart behavior and recovery exports.
Visible, minimized, hidden and closed are different states
An expanded or minimized Box remains part of the saved desktop organization. A Box hidden through the tray controls remains recoverable from the running application. Closing a Box removes that Box organization and therefore requires a clear warning before the action continues.
Ending Glass Desktop Box is an application-level action. It must not be confused with minimizing or closing one visible Box.
- Minimize keeps the Box and its organization
- Tray hiding keeps the Box available for restoration
- Closing requires explicit confirmation
- Ending the app closes the running application, not the user's local files
Access after every Box has been closed
While the application is running, the tray icon is the persistent place for showing Boxes and creating new Organizer or Workspace Boxes. If the application was ended, the desktop shortcut or installed application starts it again and restores access to creation controls.
Creating a new Box minimizes Boxes of the same family first and opens the new Box centrally. Organizer Boxes and Workspace/ProBox windows remain independent families.
Recovery instead of silent loss
Interrupted file operations are checked using recovery records. If an item cannot be returned automatically because a source path is missing, a destination conflicts or Windows has locked the item, the preserved data and affected path must be identified clearly.
An uninstall recovery folder is a last-resort safety export. It should be created only when there is something that could not be returned automatically, not on every clean uninstall.
Important limitations
- Recovery mechanisms reduce risk but do not replace independent backups.
- Windows can prevent moving a file that another process has locked exclusively.
- Protected system folders and internal Glass Desktop Box data remain excluded.
Frequently asked questions
Should my Boxes return after restarting Windows?
Yes. Boxes that were not explicitly closed or hidden should be restored after the application starts. They remain visible in their saved expanded or minimized state unless the user deliberately closes them, hides them through the tray controls or ends the application.
What happens when I minimize a Box?
Minimizing changes only the Box display. Its organization, files and saved state remain available and the Box can be expanded again.
What happens when I close a Box with the X button?
Closing a Box is a deliberate removal of that Box organization, not a normal minimize action. The application must show a prominent confirmation and explain how the underlying files are handled before completing the close operation.
Can I create a new Box after closing all Boxes?
Yes. Glass Desktop Box continues through its tray icon unless the application was explicitly ended. Opening the desktop shortcut or application again also provides access to the Box creation controls.
Why must the tray icon remain available?
The tray icon is the persistent control point for showing Boxes, creating new Boxes and ending the application. Closing the last visible Box must not silently remove access to the running application.
What happens when I create another Box?
Boxes of the same family are minimized first so they do not overlap chaotically. The new Organizer Box or new Workspace/ProBox opens centrally, while the other Box family remains independent.
What is the uninstall recovery folder?
It is a safety export used only when files or Box content cannot be returned to their expected location during uninstall. It should not appear when there is nothing to recover, and its plain-language read-me explains any preserved items.
What does ‘Move back failed’ mean?
The application could not automatically return one or more items to their former source path, for example because the source no longer exists or a file is locked. The source data is preserved instead of being discarded, and the recovery information identifies the affected item.