Fixing the Volume Shadow Copy service

After installing DHCP on Windows Server 2008 R2, you may start to see the following error message in the event logs :

Volume Shadow Copy Service error: Unexpected error calling routine RegOpenKeyExW(-2147483646,SYSTEM\CurrentControlSet\Services\VSS\Diag,…). hr = 0×80070005, Access is denied.

Inspection of the detailed tab of the event log entry will show information about the process that generated the error. Take note of the user mentioned after the “- User: Name:” portion of the bytes. To resolve this error, simply give that user full permission to the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\VSS registry key.

8 Comments

  1. Nice tip. But does it have to be full permission or will read suffice?

  2. The volume shadow copy service reads and writes to that key. The read error is simply the first one that occurs.

  3. Brian Ladley says:

    What if the User shows N/A?

  4. [...] service creates VSS errors in system log, similar to this DHCP issue. Happens only with Windows Server 2008 [...]

  5. I’m not sure why it would show N/A, you can try NETWORK SERVICE or SYSTEM. In my case, it was NETWORK SERVICE that was the issue.

  6. [...] service creates VSS errors in system log, similar to this DHCP issue. Happens only with Windows Server 2008 [...]

  7. Jo Cox says:

    I got the same error post install of DHCP on win 2008 r2

    I added the service account with full permission to the following key and the error went

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\VSS\diag

    Funnily enough I worked this out from a thread of someone who was having a similair error with his sharepoint office search service.
    J

  8. BrentonK says:

    When the DHCP role is installed on s Sever 2008 machine the VSS writer “DHCP Jet Writer” is added. The error in question can be cause when the account running the DHCP service does not have access to the aforementioned registry key. I believe that DHCP is set to run under the NETWORK SERVICE account by default so as Jean-Sebastien said, giving the NETWORK SERVICE account permissions to the registry key should fix it.

Leave a Reply