The snapshot creation failed because the VSS writer {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f} on source machine MACHINENAME did not respond within the expeted time interval.
Fix 1:
- Open regedit and go to HKLM\Software\Microsoft\Windows NT\CurrentVersion\ProfileList
- Under the ProfileList key, delete any subkey that has ".bak" on the end.
If that was not the case, then try this:
Fix 2:
When
we run the "vssadmin list writers" command from the command prompt,
we don't see the system writer in the list. This is because of the access
permission not defined properly. In order to assign the correct permission,
please run the following commands from the command prompt:
Takeown
/f %windir%\winsxs\temp\PendingRenames /a
icacls
%windir%\winsxs\temp\PendingRenames /grant "NT AUTHORITY\SYSTEM:(RX)"
icacls
%windir%\winsxs\temp\PendingRenames /grant "NT
Service\trustedinstaller:(F)"
icacls
%windir%\winsxs\temp\PendingRenames /grant BUILTIN\Users:(RX)
Takeown
/f %windir%\winsxs\filemaps\* /a
icacls
%windir%\winsxs\filemaps\*.* /grant "NT AUTHORITY\SYSTEM:(RX)"
icacls
%windir%\winsxs\filemaps\*.* /grant "NT Service\trustedinstaller:(F)"
icacls
%windir%\winsxs\filemaps\*.* /grant BUILTIN\Users:(RX)
--------------------------------------------------------------
-
After that we ran
net
stop cryptsvc
net
start cryptsvc
-------------------------------------------------
Once
this has been done, again ran the "vssadmin list writers" command and
this time we should see the system writer listed there.
