Backup SystemState from cml fails Windows Server 2016?

It seems like you are facing issues with backing up your system state using the command line in Windows Server 2016. The error you are encountering could be due to the way the system path is being referenced in the registry keys or in your backup command. Here are some points to consider and steps to troubleshoot the issue: 1. Backup Syntax: - Your syntax for backing up the system state seems correct: wbadmin start systemstatebackup -backuptarget:D: - Verify that the drive D: is accessible and has enough space to store the backup. 2. Registry Path: - The modification you made to the vsock registry keys might not be directly related to the backup issue. - Ensure that all the registry paths have been correctly updated to %SystemRoot%\system32\DRIVERS\vsock.sys. - After making the changes, restart the server to ensure the modifications take effect. 3. User Permissions: - Since you can backup using the GUI and command line for the C Drive, it indicates that the user account has the necessary permissions for backup operations. - However, double-check that the same user account has the required permissions for system state backups. 4. Troubleshooting: - To further troubleshoot the issue, try running the system state backup command with elevated privileges. - Check the Event Viewer for any specific error messages related to the failed backup operation. This could provide more insights into the root cause of the issue. - Consider using PowerShell commands for system state backups to see if it provides a similar error. If these steps do not resolve the issue, try to isolate the problem further by capturing any specific error messages or logs related to the backup failure. This information can help in identifying the exact cause and solving the problem effectively.