Troubleshooting LibreWolf on Windows
Practical, ordered steps to diagnose and fix common problems: downloads not starting, installer issues, crashes, DRM errors, profile problems and antivirus false positives. Follow the steps in order — include exact error messages when asking for help.
1. Download problems
If the download link doesn't work, first try the direct mirror on the Download page. For JavaScript-disabled environments use the noscript direct link on that page.
Steps:
- Open the Download page and use the direct official mirror link.
- Verify the SHA256 checksum (PowerShell:
Get-FileHash -Path C:\path\to\file -Algorithm SHA256). - If download is blocked by network policies, try a different network or use a download manager that supports resuming.
- If redirect/captcha flow fails, the fallback links on the Download page will lead you to the file.
2. Installer fails or is blocked by SmartScreen/Defender
Typical causes: SmartScreen flags new binaries, Defender quarantines based on heuristics, or missing permissions.
- Verify SHA256 before running. If checksum matches, proceed cautiously.
- Right-click → "Properties" → "Unblock" if Windows marks the file as downloaded from the Internet.
- Use "More info" → "Run anyway" on SmartScreen prompts if you trust the source.
- If Defender quarantined the file, restore it and add an exclusion for the installer folder during installation; report false positives to Microsoft if necessary.
- For enterprise machines, request an exception from IT or use the portable build if admin rights are restricted.
3. Installer completes but LibreWolf crashes or won't start
Collect diagnostic info and try a clean start:
- Start LibreWolf with a new profile:
librewolf.exe -P
and create a temporary profile. - Run in Troubleshoot/Safe mode to disable extensions:
librewolf.exe -safe-mode
- Check %APPDATA% and %LOCALAPPDATA% for crash reports and logs. Open about:support in the browser when possible to gather technical details.
- Temporarily disable antivirus/firewall to rule out interference.
4. Portable build issues
Common problems: profile not writable, missing files after extraction, or extensions behaving unexpectedly.
- Ensure the portable folder is on a writable drive. Some USB drives mount as read-only.
- Do not run directly from compressed archives — extract fully before running.
- If settings fail to persist, check permissions on the profile subfolder inside the portable directory.
5. DRM / Playback errors (Netflix, Prime, etc.)
See the DRM guide — but quick checklist:
- Enable EME/Widevine preferences (see DRM & Streaming).
- Confirm Widevine CDM installed (about:support → Content Decryption Modules).
- Try a clean profile and disable privacy extensions that may block CDM downloads.
- If specific error codes appear (Netflix), note them and consult the Netflix troubleshooting guide on this site.
6. Extension & site compatibility
If websites behave incorrectly, check extensions and privacy prefs:
- Open in a clean profile to confirm whether the issue is profile/extension related.
- Temporarily disable anti-fingerprinting or aggressive tracker blockers — some sites require certain features to work.
- Use the Web Console (F12) to capture errors and network failures for debugging.
7. How to collect useful logs and report a bug
When you file an issue, include clear steps to reproduce, exact version, OS, and any logs. Useful items to attach:
- LibreWolf version (Help → About) and build number.
- OS version (Settings → System → About).
- about:support page export (copy/paste output or take a screenshot).
- Console output or errors from developer tools (F12 → Console).
- Crash report files from %LOCALAPPDATA% or the CrashReports folder if present.
- Exact error messages and steps to reproduce.
Where to report: the project's GitHub is the preferred channel — create an issue with the above details and any attachments (logs, screenshots).
8. Winget & package-manager related issues
If winget install fails:
- Run
winget source update
andwinget search librewolf
to refresh manifests. - Check network/proxy restrictions; winget requires access to the source repository.
- Validate the package ID and publisher before installing.
9. Performance & memory issues
For slowness or high memory usage:
- Restart the browser and test in a clean profile.
- Disable or remove heavy extensions and tabs that use many resources.
- Check for problematic plugins or sites in Task Manager (Shift+Esc in browser) and in Windows Task Manager.
10. When to use portable vs fresh install for troubleshooting
Portable runs isolated and is useful for testing; if an installed copy misbehaves, try extracting a portable build to a temp folder and see if the issue reproduces — this helps isolate system-level interference.
11. Quick recovery steps
- Create a backup of your profile (copy profile folder).
- Create a new temporary profile and test.
- Reinstall using the installer from the Download page.
- If nothing helps, collect logs (see section 7) and open an issue on GitHub.
12. Contact & extra help
If you need help beyond these steps, include the items from section 7 and file an issue on the project's GitHub. For urgent or private disclosures (security issues), follow the security contact procedure on the project repo.