The project documents advanced logging for Open-Shell Menu. Enable it only when ordinary reproduction steps are insufficient, follow the current wiki instructions, and remove sensitive details before sharing a log publicly.
What to do
- Write a short reproduction sequence and record the Windows build and Open-Shell version. This gives the log an interpretable context.
- Read the project advanced-log guide. It documents a per-user LogCategories setting; back up the relevant registry branch before an authorized change.
- Reproduce only the failing action and locate the StartMenuLog.txt file in the documented local application-data folder. Keep an untouched private copy for your own records.
- Review a sharing copy for user names, private paths, network locations, and search terms. Turn off the temporary logging setting after the investigation.
Check the result
Check that the log timestamp corresponds to the reproduced failure. Attach only the minimal relevant excerpt or a reviewed file together with the steps and version information.
Limits & precautions
Logs can contain personal or organizational information. Do not post an entire profile directory or change registry values from unverified instructions. Advanced logging is not a routine performance optimization.
Questions & answers
Should everyone enable advanced logging permanently?
No. Use it for a defined diagnostic task and disable it when finished.
Where is the documented log?
The project guide names StartMenuLog.txt under the user local OpenShell application-data folder.
Sources & scope
Documentation checked October 30, 2026. These instructions are documentation-led, not a claim of hands-on testing on your Windows build.