How To Fix Health Report Is Not Available In Windows Defender

You open Windows Security, click Device performance & health, and Windows hits you with: “Health report is not available.” Cool. Thanks, Windows. Very informative.

The good news: this is usually fixable without sacrificing your laptop to the tech gods. The “health report” feature depends on a few Windows components (diagnostics logs, services, and system health data). If any one of them is missing, corrupted, blocked by policy, or simply having a Monday, Windows Security shrugs and shows that message.

Below is a practical, step-by-step guide to get the health report backwritten for real humans, not robots that say “kindly do the needful.” Let’s get your dashboard green again.

What “Health Report Is Not Available” Actually Means

The Device performance & health tile in Windows Security doesn’t magically “scan your soul.” It reads diagnostic information that Windows generates through built-in monitoring and reporting (think Performance Monitor reports, system diagnostics logs, and supporting services).

If those reports can’t be created, can’t be read, or were deleted/blocked, Windows Security can’t display the summaryso you get the dreaded health report not available message.

Quick Checks (Do These FirstThey’re Surprisingly Effective)

1) Reboot like you mean it

Yes, I know. But a full restart can kick stuck services back into gear and rebuild some temporary caches. Save your work, restart, then check the tile again.

2) Install pending Windows updates

If your system is behind on updates, Windows Security components can get out of sync. Go to Settings > Windows Update and apply pending updates, then restart once more.

3) Check for third-party antivirus conflicts

If you’re running another antivirus suite, it may disable or partially replace Microsoft Defender components. Temporarily disable it (or uninstall to test), reboot, and see if the health report returns.

Fix #1: Repair or Reset the Windows Security App

If the Windows Security interface is glitching, repairing the app is often the fastest win. This targets the Windows Security app without nuking your whole system.

Option A: Repair/Reset from Settings (easy mode)

1. Open Settings > Apps > Installed apps.
2. Find Windows Security.
3. Click Advanced options.
4. Try Repair first. If that doesn’t work, try Reset.
5. Restart your PC.

Option B: Reset Windows Security via PowerShell (still safe, just nerdier)

Open PowerShell as Administrator, then run:

Let it finish, reboot, then check Device performance & health again. If the tile loads, congratulationsyou just performed a small exorcism.

Fix #2: Rebuild the Health Report Data (PerfLogs / System Diagnostics)

A very common cause is corrupted or missing diagnostic reports. The health report pulls from Windows diagnostics, which often live under C:PerfLogs. If those reports got deleted by “cleanup” tools, a failed update, or a well-meaning human with a broom, Windows Security loses the plot.

Step 1: Try generating a fresh system diagnostics report

1. Press Win + R, type perfmon, and press Enter.
2. In the left pane, go to Reports > System > System Diagnostics.
3. If a report exists but looks broken or outdated, don’t panic. We can regenerate it.

Step 2: Run the built-in report command

Open Run (Win + R) and enter:

Wait about a minute while Windows collects data. Then reopen Windows Security and check whether the health report is back.

Step 3: If PerfLogs is corrupted, rename it (the classic “turn it off and on again,” but for folders)

This sounds dramatic, but it’s reversible and often effective.

1. Open File Explorer and go to C:.
2. Find PerfLogs.
3. Rename it to PerfLogs.old (you may need admin permission).
4. Restart the PC.
5. Run perfmon /report again to regenerate data.

If you don’t see PerfLogs at all, that can also trigger the issue. In many cases, Windows recreates needed folders automatically after a reboot and report generation.

Fix #3: Repair System Files (DISM + SFC)

If Windows Security components or diagnostics modules are damaged, the health report can fail. The clean way to repair core Windows files is: DISM (repairs the Windows image) followed by SFC (repairs system files).

Run DISM

1. Right-click Start > open Windows Terminal (Admin) or Command Prompt (Admin).
2. Run:

Then run SFC

When both finish, restart and re-check Windows Defender health report status. This pair fixes a surprising number of “Windows is being weird” problemswithout reinstalling anything.

Fix #4: Make Sure the Right Services Are Running

Windows Security relies on background services to collect and report health signals. If a service is disabled, Windows Security can’t get the info it needs.

Check Windows Security-related services

1. Press Win + R, type services.msc, press Enter.
2. Look for (names may vary slightly by Windows version):

• SecurityHealthService (Windows Security Service)
• Security Center (often shown as wscsvc)
• Microsoft Defender Antivirus Service (often WinDefend)

For each service: set Startup type to Automatic (or Automatic (Delayed Start)), then click Start if it’s stopped. Restart and test again.

Fix #5: Verify (and Repair) WMI Repository Health

Windows Management Instrumentation (WMI) is one of those invisible Windows plumbing systems that everything uses and nobody wants to think about. When it breaks, things fail in confusing wayslike your health report going missing.

Step 1: Verify the repository

Open an elevated Terminal/Command Prompt and run:

If it says the repository is consistent, greatmove on. If it reports inconsistency, try salvaging it.

Step 2: Attempt a salvage repair

Restart afterward and check Windows Security again.

Step 3: Rebuild WMI (last resort, handle with care)

Full WMI rebuilds can have side effects in enterprise tools and management software. If you’re on a work PC, consider checking with IT first. If it’s your personal machine and you’re comfortable, follow Microsoft’s guidance carefully for WMI rebuild procedures.

Fix #6: Run Microsoft Defender Offline Scan (Because Some Malware Plays Hide-and-Seek)

Sometimes the health report breaks because Defender components are being interfered withby malware, corrupted drivers, or security hooks. An offline scan runs outside the normal Windows session, making it harder for stubborn threats to dodge detection.

1. Open Windows Security.
2. Go to Virus & threat protection.
3. Select Scan options.
4. Choose Microsoft Defender Offline scan > Scan now.

Your PC will restart, scan, then boot back into Windows. After that, revisit Device performance & health.

Fix #7: Try a Clean Boot to Eliminate Conflicts

If some startup service or “helpful” optimization suite is blocking diagnostics, a clean boot helps isolate it.

1. Press Win + R, type msconfig, press Enter.
2. On the Services tab, check Hide all Microsoft services, then click Disable all.
3. Open Task Manager > Startup tab, disable non-essential startup apps.
4. Restart and test Windows Security again.

If the health report works in a clean boot, re-enable items gradually until you find the troublemaker.

Fix #8: If It Says “Managed by Your Organization,” That’s Not a VibeIt’s Policy

On work/school PCs, Windows Security can be controlled by Group Policy, MDM, or organizational security baselines. That can disable certain reporting features or lock the interface.

• Check Settings > Accounts > Access work or school for connected organization accounts.
• If this is your personal PC and an old work account is still connected, removing it can restore normal behavior.
• If it’s truly a managed device, your best fix is contacting ITbecause fighting policy is like arguing with a vending machine: loud and rarely successful.

Fix #9: The “Everything Else Failed” Options

If you’ve tried the resets, diagnostics rebuild, DISM/SFC repairs, and service checksand Windows still refuses to show the health reportyour installation may be deeply out of alignment. These options are heavier, but reliable.

Option A: In-place reinstall using Windows Update

Newer Windows builds offer a repair reinstall that keeps your apps and files while refreshing system components. Look for options like Reinstall now in recovery/update repair areas (wording varies by version).

Option B: Reset this PC (keep files)

This reinstalls Windows while preserving personal files, but you’ll likely need to reinstall apps and reconfigure settings. Back up anything important anywaybecause Murphy’s Law has excellent uptime.

How to Keep the Health Report Working (So You Don’t See This Again Next Week)

• Avoid “registry cleaner” tools that delete logs or services indiscriminately.
• Don’t delete PerfLogs unless you’re intentionally rebuilding it (like we did above).
• Keep Windows updated so Defender platform components stay consistent.
• Limit overlapping security tools that fight Defender for control of scanning and reporting.

Conclusion

When Windows Defender says Health report is not available, it’s rarely a single “mystery bug.” It’s usually a missing diagnostics report, a broken Windows Security app registration, corrupted system files, disabled services, or (occasionally) WMI acting like it forgot how to WMI. Start with the simple fixes, then move up the ladder: reset Windows Security, rebuild PerfLogs diagnostics, run DISM/SFC, verify services, and only then dip into WMI repair or a repair reinstall.

Once the report returns, keep it healthy by avoiding aggressive cleanup tools and staying current on updates. Your future self will thank youquietly, from a life with fewer surprise triangles and warning icons.

Extra: Real-World Experiences (What People Actually Run Into)

Let’s talk about what typically happens in the wildbecause the “Health report is not available” message rarely appears in a vacuum. It usually shows up after a change. Sometimes it’s a big change (feature update), sometimes it’s a tiny one (“I deleted a folder because the internet said so”), and sometimes it’s the classic: “I installed three antivirus tools so now I have triple security.” (That’s not how that works.)

One common pattern: someone runs a disk cleanup or a third-party optimizer that proudly announces it removed “unnecessary logs.” Windows diagnostics logs are indeed logsbut Windows Security uses them to build its health report. When those files disappear, Windows Security can’t summarize anything, so it returns the digital equivalent of a shrug. Renaming PerfLogs and regenerating reports fixes this more often than you’d think, especially on machines where multiple users have been “tidying up.”

Another pattern is the half-broken Windows Security app after a Windows update or a store component mismatch. You’ll see symptoms like: the app opens blank, buttons don’t respond, or the health page is the only one that fails. In those cases, the PowerShell reset command is the hero of the story. It’s quick, it’s reversible, and it doesn’t require you to spend your weekend reinstalling Windows while whispering “why” into a mug of coffee.

Then there’s the “managed device” surprise. People buy a used laptop, or they connected a work account months ago and forgot about it, and suddenly Windows Security says settings are managed by an organization. Translation: some features are locked down by policy. If that’s the situation, you can repair and reset all day long and still get nowhere, because policy can override your local settings. Removing old work/school accounts (when appropriate) often restores normal behavior.

A trickier experience shows up with system corruption. Maybe the PC was force-shut down during updates, had a failing SSD, or survived a blue-screen spree. Windows might still boot fine, but behind the scenes core components are damaged. That’s when DISM + SFC saves the day. It’s not flashyno progress bars that feel like a sci-fi moviebut it can quietly repair the underlying pieces Windows Security relies on. In practice, people run these tools and suddenly multiple weird problems vanish at once: the health report returns, Windows Update behaves, and the Start menu stops sulking.

Finally, there’s the “WMI gremlin” scenarioless common, but memorable. WMI issues can cause odd reporting failures across Windows. Most home users never touch WMI, but it’s there, and it’s important. If verification fails, salvaging the repository can bring reporting back. The key lesson from the real world: do the safe steps first. WMI rebuilds and repair installs are powerful, but they’re not the first move. Treat them like the fire extinguisher behind glass: useful when needed, but you don’t want to smash it open just because the toaster looked at you funny.