“vssadmin list writers” does not return any writers

If you get one of the following events in your Application Event Log, try the solution below:

Event Type: Error
Event Source: VSS
Event ID: 20
Description: Volume Shadow Copy Service error: A critical component required by the Volume Shadow Copy Service is not registered. This might happened if an error occurred during Windows setup or during installation of a Shadow Copy provider. The error returned from CoCreateInstance on class with CLSID {faf53cc4-bd73-4e36-83f1-2b23f46e513e} and Name VSSEvent is [0x80040154].

Event Type: Error
Event Source: VSS
Event ID: 20
Description: Volume Shadow Copy Service error: A critical component required by the Volume Shadow Copy Service is not registered. This might happened if an error occurred during Windows setup or during installation of a Shadow Copy provider. The error returned from CoCreateInstance on class with CLSID {faf53cc4-bd73-4e36-83f1-2b23f46e513e} and Name VSSEvent is [0x80004002].

Event Type: Error
Event Source: VSS
Event ID: 8193
Description: Volume Shadow Copy Service error: Unexpected error calling routine CoCreateInstance. hr = 0x80040154.

Event Type: Error
Event Source: VSS
Event Category: None
Event ID: 8193
Description: Volume Shadow Copy Service error: Unexpected error calling routine CoCreateInstance. hr = 0x80004002.

Event Type: Error
Event Source: VSS
Event ID: 12302
Description: Volume Shadow Copy Service error: An internal inconsistency was detected in trying to contact shadow copy service writers. Please check to see that the Event Service and Volume Shadow Copy Service are operating properly.

Solution:
Click Start, click Run, type cmd, and then click OK.
Type the following commands at a command prompt. Press ENTER after you type each command (Yes, do the same thing twice ;)).

 

cd /d %windir%\system32
Net stop vss
Net stop swprv
regsvr32 ole32.dll
regsvr32 oleaut32.dll
regsvr32 vss_ps.dll
vssvc /register
regsvr32 /i swprv.dll
regsvr32 /i eventcls.dll
regsvr32 es.dll
regsvr32 stdprov.dll
regsvr32 vssui.dll
regsvr32 msxml.dll
regsvr32 msxml3.dll
regsvr32 msxml4.dll

Net stop vss
Net stop swprv
regsvr32 ole32.dll
regsvr32 oleaut32.dll
regsvr32 vss_ps.dll
vssvc /register
regsvr32 /i swprv.dll
regsvr32 /i eventcls.dll
regsvr32 es.dll
regsvr32 stdprov.dll
regsvr32 vssui.dll
regsvr32 msxml.dll
regsvr32 msxml3.dll
regsvr32 msxml4.dll

Alternatively you can download this batch file:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
PUSHD %windir%\system32
FOR %%i in (1,2) DO (
 
  Net stop vss
  Net stop swprv
 
  FOR %%j in (ole32.dll,oleaut32.dll,vss_ps.dll) DO (
    regsvr32 %%j
  )
 
  vssvc /register
 
  FOR %%k in (swprv.dll,eventcls.dll) DO (
    regsvr32 /i %%k
  )
 
  FOR %%l in (es.dll,stdprov.dll,vssui.dll,msxml.dll,msxml3.dll,msxml4.dll) DO (
    regsvr32 %%l
  )
 
)

21 responses to “vssadmin list writers” does not return any writers

This fixed my problem! Thank you! I’ve been trying the other scripts but to no avail. For some reason stopping the services and registering the DLLs twice (the script you have) worked. Thanks a lot!

This fixed the issue for me as well. I re-registered the dlls and services several times and rebooted, but the key was to do them twice in a row. Any word on why you have to register twice?

I have been trying all types of stuff for the last several weeks since I was missing my WMI System Writer. I haven’t had a successful System State backup in 3 weeks and I was really close to rebuilding my server, but this did the trick! I’m running my System State backup right now. For some reason it looks like if you register the dlls twice in a row it brings the Writers back.

If anyone’s system state backups are failing due to missing writers try the commands above. Great tip!!!

I was spinning my wheels trying to fix this issue today. Great tip…i had registered the DLL’s earlier to no avail. Doing it twice in a row fixed the issue. Thanks!!!

I can’t believe this worked, but it did! At first I thought it was a typo that they were all in there twice, but after reading the other comments I justdid exactly what it said. This is obviously a BUG. Way to go MS.

Thanks for the fix!!!!

I cannot believe IT… Your script helped me out. I already tryed lot’s of changes but nothing worked. Now your simple “do it twice” does the trick.

How did you come to this conclusion?

my deepest respect…

Running the attached batch script twice then rebooting seems to have resolved this issue for me.

Registering these components manually once as instructed did not work

It worked on Win 7 (32bit) pc as well.
Got about 3 erros saying DLL found but had a problem with registering.
Still fixed the issue.

Thanks !!!!

I am having absolute no luck with vssadmin and getting remote backups to work. I have four XP PRO machines.

Two are Dell 6400 which work with the remote backup.

Two are Dell 6500 which will not work with the remote backup.

When I run ‘vssadmin list writers’ I get error 0x8000ffff on the Dell 6500.

When I run ‘vssadmin list writers’ on the Dell 6400, I get a list of writers.

I’ve tried the batch file above with no luck. I can’t even get local IT support to assist with this either.

Any help getting these Dell 6500 to show some writes when running the ‘vssadmin list writers’ command would be greatly appreciated.

Thanks. This fixed my problem with Volume Shadow Copy. Cannot figure out why running hte same command twice fixes the problem. But does the job.

Very good tip, thank you. Worked after running twice.
We did however had to apply update KB940349 first as it did not work before.

Hi, i got the problem , there’s no writers in “vssadmin list writers”
i tried the solution but got an error while executing the batch.. failure of creating “swprv” “eventds” “es” “vssui” “msxml” “msxml4” dlls..
any idea?

Leave a Reply