Listen to this Post
Introduction:
A recent Windows 11 security update (KB5063878) has been linked to potential permanent damage to SSDs and HDDs, particularly those using Phison controllers. Reports indicate that writing over 50GB of data in a single session may trigger the issue. This article explores the risks, mitigation steps, and essential commands to safeguard your system.
Learning Objectives:
- Understand the risks associated with KB5063878
- Learn how to verify if your system is affected
- Apply immediate fixes and preventive measures
1. Check If You’ve Installed the Faulty Update
Windows Command:
Get-HotFix -Id KB5063878
What This Does:
This PowerShell command checks if the problematic update is installed. If it returns a result, your system may be at risk.
Steps:
1. Open PowerShell as Administrator.
2. Run the command above.
3. If KB5063878 appears, proceed with caution.
2. Uninstall the Update (If Already Installed)
Windows Command:
wusa /uninstall /kb:5063878
What This Does:
This command removes the faulty update from your system.
Steps:
1. Run PowerShell or CMD as Administrator.
2. Execute the command.
3. Restart your system.
3. Disable Windows Update Temporarily
Windows Command:
Stop-Service -Name "wuauserv"
What This Does:
This stops Windows Update services to prevent automatic reinstallation of the faulty patch.
Steps:
1. Open PowerShell as Admin.
2. Run the command.
3. Verify with:
Get-Service -Name "wuauserv"
(Status should show “Stopped”)
4. Monitor Disk Health (SSD/HDD Diagnostics)
Windows Command:
Get-PhysicalDisk | Get-StorageReliabilityCounter
What This Does:
Checks disk health metrics, including write cycles and errors.
Steps:
1. Run PowerShell as Admin.
2. Execute the command.
3. Look for abnormal “WriteLatency” or “Errors” spikes.
5. Backup Critical Data Immediately
Robocopy Command (Windows):
robocopy C:\Users\YourUser D:\Backup /MIR /Z /R:1 /W:1
What This Does:
Creates a mirrored backup of your user folder to another drive (D:\Backup).
Steps:
1. Replace `YourUser` with your username.
- Ensure the target drive (
D:\) has enough space.
3. Run in CMD or PowerShell.
6. Check for Phison SSD Controllers (Potential Risk)
PowerShell Command:
Get-Disk | Get-StorageController | Where-Object { $_.FirmwareVersion -like "Phison" }
What This Does:
Identifies if your SSD uses a Phison controller (higher risk).
Steps:
1. Run as Admin.
- If output shows “Phison,” avoid large file writes.
7. Enable Write Throttling (Temporary Fix)
Registry Edit (Caution!):
reg add "HKLM\SYSTEM\CurrentControlSet\Control\Storage" /v "WriteThrottleThreshold" /t REG_DWORD /d 4096 /f
What This Does:
Limits write operations to 4KB chunks, reducing strain on SSDs.
Steps:
1. Back up the registry first (`reg export`).
2. Run the command.
3. Reboot.
What Undercode Says:
- Key Takeaway 1: The KB5063878 bug highlights Microsoft’s QA challenges, especially with third-party hardware.
- Key Takeaway 2: Proactive monitoring and backups are non-negotiable for enterprise IT teams.
Analysis:
This incident underscores the fragility of storage systems under aggressive write cycles. While Microsoft will likely issue a patch, the broader lesson is clear: Never assume updates are safe. Enterprises should adopt phased rollouts and real-time disk health checks.
Prediction:
Expect a surge in SSD warranty claims and increased scrutiny of Microsoft’s update validation process. Long-term, this may accelerate adoption of decentralized update testing (e.g., Windows Insider tiers).
Final Note:
If you’ve been affected, report to Microsoft via Feedback Hub. Stay tuned for official fixes.
Sources:
🎯Let’s Practice For Free:
IT/Security Reporter URL:
Reported By: Alfonso %C3%A1ngel – Hackers Feeds
Extra Hub: Undercode MoN
Basic Verification: Pass ✅
