v1.3.6 - Mutex Permission Handling

Fix: Handle Mutex Permission Issues

Problem: On some systems, the mutex existed but the current process couldn't access it (UnauthorizedAccessException). The app would say 'Monitor already running' even though no actual process was running.

Root Cause: Previously, any UnauthorizedAccessException was treated as 'someone else holds the mutex, so monitor is running'. But this could also indicate:

• Permission issues
• Different user session
• Corrupted mutex from system restart

Solution: When UnauthorizedAccessException occurs:

1. Fall back to checking actual RobloxGuard processes
2. If processes exist Monitor is running (legitimate permission issue)
3. If NO processes exist Allow new monitor (false positive from broken mutex)

Changes:

• Gracefully handles UnauthorizedAccessException
• Validates with Process.GetProcessesByName as fallback
• Allows app to start when permission issues block mutex access
• Prevents getting stuck on 'Monitor already running'

Files:

• \RobloxGuard.exe\ - Single-file executable
• \RobloxGuard.exe.sha256\ - SHA256 checksum

Installation

Download and run. Auto-installs on first launch.