Protostarship/SystemGuardian
SystemGuardian is a powerful Windows service designed for real-time system monitoring, failure prevention, and automated recovery. It safeguards critical system components, detects driver failures, registry modifications, and service disruptions, and takes automatic corrective actions to prevent crashes and instability.
SystemGuardian - Comprehensive Documentation
π Overview
SystemGuardian is a high-performance Windows service designed for real-time system monitoring, failure prevention, and automated recovery. It ensures system stability by tracking drivers, services, registry changes, and system integrity, preventing potential failures, crashes, and unauthorized modifications.
π₯ Installation & Setup
1οΈβ£ Prerequisites
- Windows 10/11, Windows Insider Preview or Windows Server 2016+
- Administrator privileges
2οΈβ£ Install SystemGuardian
To install the SystemGuardian service, open a command prompt with Administrator privileges and run:
sc create SystemGuardian binPath= "C:\\Path\\To\\SystemGuardian.exe" start= autoThis registers the service in Windows and configures it to start automatically on system boot.
3οΈβ£ Start the Service
To manually start the service, run:
sc start SystemGuardian4οΈβ£ Stop or Restart the Service
If you need to stop or restart the service, use:
sc stop SystemGuardian
sc start SystemGuardian5οΈβ£ Uninstall SystemGuardian
To remove the service completely from the system, execute:
sc delete SystemGuardianβοΈ How It Works
π‘οΈ Core Features
β Real-time System Monitoring - Watches drivers, registry keys, and services for changes.
β Automated Recovery - Restores services, drivers, and registry keys from backups.
β Integrity Protection - Uses SHA-256 file hashing to detect modifications.
β Driver Verification - Blocks unsigned/unverified drivers.
β Crash Prevention - Detects system crashes and creates restore points automatically.
β Event Logging & Alerts - Logs system failures and can notify administrators.
π Recovery Process
- Detect an issue (e.g., service failure, driver corruption).
- Backup registry and critical components.
- Attempt Auto-Recovery:
- Restart failed services.
- Restore corrupted drivers from backups.
- Rollback registry keys if altered.
- Notify the user if intervention is required.
π§ Configuration Management
πΉ Configuration File Location
SystemGuardian uses a configuration file to define which system components should be monitored. The default configuration file is located at:
C:\ProgramData\SystemGuardian\config.json
πΉ What if the Configuration File is Missing?
- If the configuration file does not exist, the service will automatically generate a default configuration with standard monitoring settings.
- Users can manually create a configuration file in the same directory to customize monitoring.
πΉ Example Configuration File
{
"MonitorDrivers": true,
"MonitorServices": true,
"MonitorRegistry": true,
"CriticalPaths": [
"C:\\Windows\\System32\\drivers",
"C:\\Windows\\System32"
]
}πΉ Modifying Configuration Settings
To modify the configuration:
- Open
C:\ProgramData\SystemGuardian\config.jsonwith a text editor. - Adjust monitoring preferences as needed.
- Restart the service for changes to take effect:
sc stop SystemGuardian sc start SystemGuardian
πΉ Enable Debug Logging
To enable verbose logging for troubleshooting:
New-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Services\SystemGuardian" -Name "DebugLogging" -Value 1 -PropertyType DWord -Forceπ Service Management
πΉ Checking Service Status
To check if the service is running:
sc query SystemGuardianπΉ Viewing Logs
- Logs are saved in:
C:\ProgramData\SystemGuardian\Logs\ - Use Notepad or PowerShell to view logs:
Get-Content C:\ProgramData\SystemGuardian\Logs\latest.log -Tail 50 -Wait
πΉ Manually Recovering a Component
If a monitored component fails and SystemGuardian does not auto-recover it, you can manually recover it by running:
SystemGuardian.exe /recover "ComponentName"πΉ Restoring Registry from Backup
reg import C:\ProgramData\SystemGuardian\registry_backup.regπ Considerations & Best Practices
1οΈβ£ Always Run as Administrator - SystemGuardian requires administrative privileges to monitor and recover system components.
2οΈβ£ Regularly Check Logs - Monitor logs in C:\ProgramData\SystemGuardian\Logs\ to detect unusual activity.
3οΈβ£ Backups are Critical - Ensure that registry and system file backups are created regularly.
4οΈβ£ Avoid Modifying System Files Manually - If you need to restore a system file, use the SystemGuardian recovery process.
5οΈβ£ Verify Driver & Service Integrity - Before installing third-party drivers, use SystemGuardian's integrity verification features to ensure they are safe.
β FAQ & Troubleshooting
β How do I check service status?
sc query SystemGuardianβ Where are logs stored?
- Logs are saved in:
C:\ProgramData\SystemGuardian\Logs\
β How do I manually recover a component?
- Open a command prompt as Administrator.
- Run:
SystemGuardian.exe /recover "ComponentName"β What happens if a driver is blocked?
- SystemGuardian will isolate the driver, preventing it from running.
- The user will be notified and can choose to restore or permanently block it.
π Support
For assistance, open an issue on our GitHub repository or contact support at: relay.arbiter303@gmail.com.
Β© 2025 SystemGuardian | All Rights Reserved