When running Disk Cleanup on Windows Vista, you might encounter three special WER-related items:

1. Per user archived Windows Error Reports (typically large, 402MB in your case)
2. System archived Windows Error Reports (usually small, 18KB)
3. System queued Windows Error Reporting (can be substantial, 533MB)

The WER system collects crash data in two states:

• Queued reports: Crash data waiting to be transmitted to Microsoft
• Archived reports: Processed crash data stored locally after transmission or expiration

Here's how to inspect these files programmatically using PowerShell:

# List all WER report locations
Get-ChildItem "HKLM:\SOFTWARE\Microsoft\Windows\Windows Error Reporting" -Recurse

# Check WER queue directory (Vista-specific)
$queuePath = "$env:ProgramData\Microsoft\Windows\WER\ReportQueue"
Get-ChildItem $queuePath -Recurse | Measure-Object -Property Length -Sum

While technically safe to delete, consider submitting queued reports first:

# Manual submission via command line (admin required)
"C:\Windows\System32\wercon.exe" -reportqueuelist

For automated solutions, use the WER API:

# C# example using Windows SDK
using Microsoft.Windows.ErrorReporting;

var reports = WindowsErrorReport.GetQueuedReports();
foreach (var report in reports) {
    report.Submit();
}

Create a scheduled task to clean old reports:

schtasks /create /tn "Clean WER Archives" /tr "cleanmgr /sagerun:1" /sc monthly /st 23:00

When running Disk Cleanup on Windows Vista, you might encounter these three WER (Windows Error Reporting) components:

Per user archived Windows Error Reports     - 402 MB
System archived Windows Error Reports      - 18.0 KB  
System queued Windows Error Reporting      - 533 MB

Windows Error Reporting collects crash data when applications or the system fail. These files represent different states:

• Archived Reports: Crash data that has been processed and compressed
• Queued Reports: Crash data waiting to be sent to Microsoft

Absolutely safe to delete if:

• You don't need crash diagnostics
• You're not developing software for Windows Vista
• Disk space is a priority

Here's a PowerShell script to analyze WER files:

# Get WER report statistics
$werPath = "$env:LOCALAPPDATA\\Microsoft\\Windows\\WER"
$archiveSize = (Get-ChildItem $werPath\\ReportArchive -Recurse | Measure-Object -Property Length -Sum).Sum /1MB
$queueSize = (Get-ChildItem $werPath\\ReportQueue -Recurse | Measure-Object -Property Length -Sum).Sum /1MB

Write-Host "Archived reports: $archiveSize MB"
Write-Host "Queued reports: $queueSize MB"

# Cleanup command (admin rights required)
# Clean-WindowsErrorReporting -Archive -Queue

If you want to submit queued reports (helpful for developers):

1. Open Problem Reports and Solutions in Control Panel
2. Click See problems to check
3. Select reports and click Check for solutions

Developers might want to adjust reporting behavior:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Windows\\Windows Error Reporting]
"Disabled"=dword:00000001
"ForceQueueMode"=dword:00000001
"QueuePesterInterval"=dword:0000001e