Fixing Common System File Checker Errors on Windows Server 2016 VMware vSphere Infrastructure
If you're running a Windows Server 2016 datacenter on VMware vSphere infrastructure with custom applications and security agents installed, you may encounter System File Checker (SFC) errors. This article will help you understand the key concepts surrounding this issue and offer solutions to resolve the most common errors.
What is System File Checker (SFC)?
System File Checker, also known as SFC, is a built-in utility in Windows operating systems. SFC helps identify and restore corrupted or missing system files, ensuring system stability. When SFC detects issues, it repairs them using files stored in a cached folder on the local computer or a Windows installation media.
Common SFC Errors on Windows Server 2016
Some common SFC errors on Windows Server 2016 include:
"Windows Resource Protection found corrupt files but was unable to fix some (or all) of them.""Cannot repair member file [file name] or one of its dependencies.""The system file protection service is not present or could not be started."
Why do SFC Errors Occur on Windows Server 2016 VMware vSphere Infrastructure?
SFC errors on Windows Server 2016 running on VMware vSphere infrastructure can be attributed to:
- Custom applications and security agents that modify or delete critical system files.
- Incorrect system configurations or updates.
- Hardware or network issues causing file corruption during data transfer.
Resolving SFC Errors on Windows Server 2016 VMware vSphere Infrastructure
To resolve these errors, follow these steps:
Step 1: Verify Windows Update Services
Ensure that the Windows Update service is running:
sc query wuauserv
If the service is not running, start it:
sc start wuauserv
Step 2: Run SFC and DISM Scans
Run an SFC scan:
sfc /scannow
If SFC cannot fix the issues, use the Deployment Image Servicing and Management (DISM) tool:
DISM /Online /Cleanup-Image /RestoreHealth
Step 3: Repair VMware Tools
If the error persists, reinstall VMware Tools:
- Uninstall VMware Tools from the guest operating system.
- Reinstall VMware Tools using the VMware vSphere Client.
Step 4: Investigate Third-Party Software
Review the list of third-party software installed on the system. If any of these applications are causing the issue:
- Uninstall the software.
- Contact the software vendor for assistance.
Step 5: Use a Clean Installation Media
If the issue remains unresolved, use a clean Windows Server 2016 installation media to repair the system:
- Create a bootable USB drive with the installation media.
- Restart the server and boot from the USB drive.
- Select "Repair your computer" and then "Troubleshoot" > "Advanced options" > "Command Prompt".
- Run the following commands:
Dism /Online /Cleanup-Image /StartComponentCleanup
Dism /Online /Cleanup-Image /CheckHealth
Dism /Online /Cleanup-Image /ScanHealth
Dism /Online /Cleanup-Image /RestoreHealth