Windows-Specific Issues

Solutions to problems unique to Windows users.

.NET Runtime Issues

[Content to be written - .NET 8.0 installation, runtime errors]

Network Drive Problems

[Content to be written - UNC paths, mapped drives, NAS disconnections]

Microsoft Store Issues

[Content to be written - installation problems, update failures]

Windows System Integration

[Content to be written - file associations, Windows permissions, external drives]

Rando Closed Unexpectedly

If Rando runs into a problem it can't recover from, it closes and shows a message telling you that details were saved to a file. Sending us that file is the fastest way to get the problem fixed, because it records exactly what went wrong.

Where the file is:

%LocalAppData%\Rando\Logs\crash.log

Paste that path into the File Explorer address bar (or into the Start menu) to open the folder. Once the log passes 5 MB the older half is kept alongside it as crash.old.log.

What's in it: the date and time, which part of Rando failed, your Rando version, your Windows version, and the technical details of the error. It does not contain your photos, your folder contents, or your file names.

Sending it: the file stays on your PC. Nothing is sent anywhere unless you choose to attach it to an email or support message yourself.

If Rando closes without any message at all, the crash log may still have caught it — check the file anyway. If there's no file and no message, that usually points to something outside Rando (a missing .NET runtime, or Windows shutting the app down); see the .NET Runtime Issues section above.

This page is under development. Content will be sourced from /docs/windows-app.md and support history.