Quick answer
Test an application’s Open and Save dialogs independently of File Explorer. A dialog may use a different interface path or be implemented by the application itself. Use a temporary folder and a disposable file to verify actual opening and saving.
What matters for this task
A screenshot of a working Explorer window does not establish that every application dialog behaves correctly. Record the application name and version alongside the Windows and StartAllBack versions when reporting a problem.
Steps to follow
- Open a harmless test document from an application’s File > Open command and note the dialog appearance.
- Use Save As to write a new copy into a temporary folder. Confirm the extension and destination before saving.
- Repeat in a second application to distinguish a single-program problem from a broader shell issue.
- Compare a simple Explorer style or disabled customization while keeping the applications and test files unchanged.
Verify the result
Confirm that the resulting file exists at the chosen path and can be reopened. Correct appearance is not enough if navigation or saving fails.
Limits and rollback
Restore the previous Explorer style if it isolates the issue. Do not overwrite an important document while experimenting with a problematic Save dialog.
Questions about this task
Will every program use the same file dialog?
No. Test the programs you rely on instead of assuming that one working dialog covers all of them.
What information belongs in a report?
Include the application version, Windows build, StartAllBack version, dialog type, and smallest reproducible action.
Primary sources
Publisher claims and Windows procedures are linked below. The comparison and diagnostic steps are editorial guidance, not a claim of hands-on Windows testing.
Windows 11 download · Review compatibility and the publisher’s license terms before installing.
Download for Windows 11 File source and installation notes