Troubleshooting Guide
Solutions to every common issue you may encounter when downloading, installing, activating, or running RescuePC Repairs.
This page is for: Anyone who has hit a problem getting RescuePC to run. Each issue includes the symptom, cause, and exact steps to resolve it.
Jump to Issue
"Windows protected your PC" (SmartScreen)
Symptom
A blue screen appears saying "Windows protected your PC" with the publisher listed as unknown or the app flagged as unrecognized.
Cause
Windows SmartScreen blocks executables that do not yet have widespread usage data in Microsoft's reputation database. This happens to all new or niche software, even when code-signed.
Solution
- Click "More info" — this reveals the publisher name and the "Run anyway" button
- Verify the publisher shows "RescuePC Software"
- Click "Run anyway"
Why this is safe: RescuePC is code-signed with an Authenticode certificate (CN=RescuePC Software, valid through 2031). You can verify the signature by right-clicking the EXE → Properties → Digital Signatures tab. SmartScreen reputation improves automatically as more users download and run the software. This prompt typically stops appearing after a few months.
"This app can't run on your PC" (Windows S Mode)
Symptom
Windows displays "This app can't run on your PC" or "For your protection, Windows only allows apps from the Microsoft Store."
Cause
The PC is running Windows in S Mode, which restricts application installation to Microsoft Store apps only. RescuePC is a desktop application and is not available in the Store.
Solution — Switch Out of S Mode (Free)
- Open Settings → System → Activation (Win 11) or Settings → Update & Security → Activation (Win 10)
- Under "Switch to Windows Home/Pro," click "Go to the Store"
- Click "Get" in the Microsoft Store page that opens — this is free
- Wait for the switch to complete (may take 1–2 minutes)
- Restart your computer
- Run RescuePC again
Important: This is permanent
Switching out of S Mode cannot be reversed. This is a Microsoft limitation, not a RescuePC requirement. If you are on a managed device (school or work), check with your IT administrator before switching.
"Access Denied" or App Won't Open (Corporate/University PC)
Symptom
The EXE fails to launch, shows "Access Denied," or displays "This app has been blocked by your system administrator."
Cause
Enterprise security policies — AppLocker, Windows Defender Application Control (WDAC), or Software Restriction Policies (SRP) — block applications not on the organization's allowlist.
Solutions (try in order)
- Copy to Desktop: Some policies only block execution from Downloads or temp folders. Copy the entire RescuePC folder to your Desktop and try again.
- Contact IT: Ask your IT administrator to whitelist RescuePC. Provide: Publisher
O=RESCUEPC SOFTWARE, C=US, and link them to the Deployment Guide. - Use a personal device: Enterprise policies on managed PCs cannot be bypassed by end users. If IT will not whitelist the app, use an unmanaged PC.
For IT Administrators
RescuePC uses a two-process architecture: a standard-user UI and an elevated repair runner. Both binaries are Authenticode-signed. Allowlisting should cover the publisher certificate, not individual file hashes, to avoid breakage on updates.
- • Publisher:
O=RESCUEPC SOFTWARE, C=US - • Certificate expiry: 2031
- • SHA-256 hashes: Available on the Download page and via support request
- • Full deployment guide: Enterprise Deployment Guide
PowerShell Disabled or Scripts Do Not Run
Symptom
RescuePC opens but repairs fail immediately, show "PowerShell is disabled," or display execution policy errors in the log.
Cause
Group Policy or enterprise configuration restricts PowerShell execution, or PowerShell is running in Constrained Language Mode (CLM), which prevents full script execution.
Solution
RescuePC automatically bypasses the standard PowerShell execution policy (Restricted, AllSigned, RemoteSigned) by invoking scripts with the -ExecutionPolicy Bypass flag. This works in most environments.
If scripts still fail:
- Verify you are running RescuePC as Administrator (right-click → Run as administrator)
- Check if PowerShell is in Constrained Language Mode — open PowerShell and run
$ExecutionContext.SessionState.LanguageMode. If it returns "ConstrainedLanguage," your IT department has locked down PowerShell. - Ask IT to exempt the RescuePC directory from CLM, or use an unmanaged device
Note: Constrained Language Mode is an enterprise security feature that cannot be bypassed without administrator or Group Policy changes. This is by design.
BitLocker Recovery Key Prompt After Repair
Symptom
After running a repair (usually a boot or disk repair), your PC restarts and shows a blue screen asking for a 48-digit BitLocker recovery key.
Cause
Boot configuration changes can modify the PCR measurements that BitLocker uses to verify system integrity. When BitLocker detects a change, it requires the recovery key to unlock the drive.
Solution — Retrieve Your Recovery Key
- On another device (phone, tablet, or another PC), go to aka.ms/myrecoverykey
- Sign in with the Microsoft account linked to this PC
- Find the recovery key that matches the Key ID shown on the BitLocker screen
- Enter the 48-digit recovery key on the locked PC
- Your PC will boot normally
Prevention
RescuePC automatically detects BitLocker-encrypted drives and excludes dangerous boot repairs from Fix All. If you manually run a boot repair on a BitLocker system, the recovery key prompt is expected behavior.
No Microsoft account?
If your recovery key is not stored in a Microsoft account, check for a printed key, a USB drive backup, or contact your IT department (for managed PCs). If no recovery key exists, a Windows reinstall is required.
Repairs Complete But the Problem Persists
Symptom
All repairs show "Pass" in the report, but the original problem (slowness, errors, crashes) is still present after restarting.
Likely Causes
The problem is not caused by software misconfiguration. RescuePC fixes software — if the root cause is hardware, malware, or severe OS corruption, repairs will succeed but the underlying issue remains.
Diagnostic Steps
- Check the repair report — open the HTML file in
logs\repair_logs\and look for any repairs that failed or flagged warnings - Restart the PC — some repairs (Windows Update resets, service repairs) require a reboot to take effect
- Run the specific repair again individually — Fix All runs safe repairs only; the fix you need may be in the Advanced tab
- Run a full antivirus scan — active malware can re-break what RescuePC repairs
- Test hardware — run Windows Memory Diagnostic (
mdsched.exe) and check SMART data on your drives
If the problem is confirmed to be hardware (bad RAM, failing drive, overheating CPU), RescuePC cannot fix it. See What RescuePC Cannot Fix for the full list of limitations.
Fix All Completes Instantly (No Repairs Actually Run)
Symptom
Clicking Fix All shows completion in seconds with no progress or output, and the repair report shows nothing ran.
Cause
The extracted files still have Windows Zone.Identifier security flags (NTFS Alternate Data Streams) that block PowerShell script execution.
Solution
RescuePC v2.1.5+ automatically removes Zone.Identifier flags on launch. If you are seeing this issue:
- Close RescuePC completely
- Re-launch it (right-click → Run as administrator)
- Check
logs\unblock.log— it should show files were unblocked - If the issue persists, re-extract the ZIP to a new folder and try again
License Activation Fails
Symptom
The activation dialog shows "Invalid key," "Activation failed," or does not respond after clicking Activate.
Common Causes
Typo in the license key (keys are case-sensitive), no internet connection, or a corporate firewall blocking HTTPS traffic to rescuepcrepairs.com on port 443.
Solution
- Copy/paste the key from your email — do not type it manually
- Verify internet access — open a browser and confirm you can reach any website
- Check your firewall — ensure port 443 (HTTPS) to
rescuepcrepairs.comis not blocked - Try a different network — corporate proxies sometimes block unknown domains
- Check for VPN interference — some VPNs route traffic through regions with different DNS, which can cause TLS failures
If activation still fails after these steps, email [email protected] with your license key and a screenshot of the error. We respond within 1 business day.
Antivirus Quarantines or Blocks RescuePC
Symptom
Your antivirus (Norton, McAfee, Kaspersky, Bitdefender, etc.) flags RescuePC as a threat, quarantines the EXE, or prevents it from running.
Cause
RescuePC modifies system settings, resets services, and runs PowerShell scripts — behaviors that some antivirus heuristics flag as suspicious, even when the actions are legitimate repairs.
Solution
- Add an exclusion for the entire RescuePC folder in your antivirus settings
- Restore from quarantine if the EXE was already moved — check your antivirus quarantine and restore the file
- Verify the signature — right-click the EXE → Properties → Digital Signatures → verify "RescuePC Software" is the signer
- Re-extract if the antivirus deleted files from the ZIP — some AV tools silently remove files during extraction
Why this happens: Antivirus heuristics look for programs that modify services, reset network stacks, and run scripts — all things RescuePC does intentionally. This is a false positive. RescuePC is code-signed, does not access personal files, and uses only built-in Windows tools.
Troubleshooting FAQ
Can I undo a repair if something goes wrong?
Yes. Every repair creates a Windows System Restore point before making changes. Go to Control Panel → Recovery → Open System Restore, and select the restore point created by RescuePC. This reverts all system changes made during that repair session.
Where are the repair logs stored?
HTML repair reports are saved in logs\repair_logs\ inside the RescuePC folder. Each file is timestamped with the repair date and time. Raw PowerShell output logs are in the logs\ directory.
Why does RescuePC need Administrator access?
System repairs modify protected Windows components — registry keys, services, system files, and boot configuration. These operations require elevated (Administrator) privileges. Without elevation, Windows blocks the changes and repairs fail silently.
I ran Fix All but one specific problem was not fixed. What now?
Fix All only runs safe, non-destructive repairs. Some issues require specific repairs from the Advanced tab or targeted repairs that are excluded from Fix All (boot repairs, partition fixes, display driver resets). Check the Repair Categories guide to find the right repair for your specific issue.
Still Need Help?
If none of the solutions above resolved your issue, contact support. To help us diagnose the problem quickly, include:
- • Your Windows version — Settings → System → About (e.g., Windows 11 23H2)
- • The exact error message — screenshot preferred
- • The repair report — attach the HTML file from
logs\repair_logs\ - • Whether the PC is managed — school, work, or personal device
Average response time: under 1 business day. Enterprise customers with P1/P2 SLA: see your license agreement for response commitments.
Related Documentation
Disclaimer:The troubleshooting steps provided are general guidance. RescuePC Repairs is provided "as is" without warranty. See our EULA for complete terms.
© 2026 RescuePC Software. All rights reserved.