Understanding and Resolving Windows Installation Issues: A Case Study of Error 0x80070570 on a Custom PC Build
Introduction
Building a custom PC offers unmatched control over hardware and performance, but it also comes with unique challenges, especially when installing or reinstalling Windows. One common obstacle encountered by enthusiasts and professionals alike is the Windows error code 0x80070570, which often manifests during installation or update processes. This article presents a detailed case study of a home-built PC experiencing this error post-initial Windows 11 Pro installation, explores potential causes, and outlines practical troubleshooting steps.
System Specifications
The custom build in question features:
- CPU: AMD Ryzen 9 9600X
- GPU: PowerColor Red Devil RX 9070XT
- Motherboard: MSI B850 Tomahawk Max
- RAM: 32GB Corsair Vengeance (compatible with AM5)
- SSD: Samsung 990 Pro NVMe SSD
- Operating Systems attempted: Windows 11 Pro, Windows 10 Pro
Initial Installation Success
The installer successfully deployed Windows 11 Pro on the first attempt, utilizing a bootable USB created via Microsoft’s Media Creation Tool. Post-installation, the user installed AMD’s Adrenalin graphics software, which led to subsequent issues—specifically, the software failed to open, indicating potential conflicts or corruption, possibly exacerbated by attempts to force a restart during Windows Update.
Encountered Issue: Error 0x80070570
After cleaning the SSD with DiskPart and attempting to reinstall Windows (both 11 and 10), the user encountered the error:
“Windows cannot open the required license file. The file may be corrupt or missing. Error code: 0x80070570.”
Troubleshooting Efforts and Observations
-
Repeated Media Creation: Multiple attempts to recreate the installation USB using the Media Creation Tool were made, testing different USB ports, including USB 2.0 and USB 3.2, without success.
-
UEFI and Legacy Modes: Both boot modes are enabled, suggesting the system is configured to support secure and flexible boot options.
-
System Stability: The user reports excellent stability with Linux, indicating hardware integrity may not be the root cause.
-
Additional Diagnostics Planned:
- Running MemoryTest86 to check RAM stability.
- Using MSI motherboard BIOS diagnostic tools to verify SSD health.
Potential Causes and Recommendations
Given the information,
Share this content:
