ISSUE: Enumeration of the files failed (Failed to generate the backup image of System State Backup)
When performing a System State backup, the following error message is received in the backup report:
Several causes can be attributed to this issue. Most often, these causes have a direct correlation to the Image Path in the registry for a service that is installed:
- Invalid directory path.
-Path that points to a location that no longer exists.
-Path that is incomplete.
-UNC path that the service does not understand how to query.
- Invalid characters in the directory path.
-Path with dots which some application vendors may use (e.g. C:\App\bin\..\..\service.exe).
- Syntax formatting of the path.
-Path that includes space and is not enclosed by double quotes (e.g. C:\Program Files (x86)\service\service.exe).
- A valid path on SAN drives of a Failover Cluster, for example
-A service in which its path is on the passive node of a Failover Cluster pointing to a physical disk resource that is owned by another nodes when error is experienced.
To resolve the issue, identify the incorrect directory path which is causing the error:
- Launch msinfo32.exe, click Start then enter msinfo32. Review each of the paths for all the services installed.
- You can also local the incorrect paths in the registry.
Enter the following command in an elevated command prompt to export the entire services key:
>reg query HKLM\SYSTEM\CurrentControlSet\Services /s /v ImagePath > regkeys.txt
- Open the output file with Notepad to inspect each ImagePath.
- When all the paths have been identified, correct the invalid directory path using the Registry Editor.
Expand HKLM\SYSTEM\CurrentControlSet\Services, edit all invalid ImagePath value with a valid path.
- For cases where the path is valid on a SAN shared drive of a Windows Server 2008 Failover Cluster, refer to the steps outlined in the following Microsoft knowledge base article:
- For additional troubleshooting
Important: If the issue persist after correcting all invalid paths, further assistance should be pursued with Microsoft.