We help IT Professionals succeed at work.

Vssadmin commands not working under Vista 64

1,408 Views
Last Modified: 2013-11-29
I was trying to manage the volume shadow copy service through the command prompt, using the Vssadmin commands such as "Vssadmin list volumes" and so on. Trouble is, I get errors with any Vssadmin command I use.

I'm obviously typing them in administrator mode, but here's what I get (translated from italian):

"vssadmin list shadowstorage

Error: Unexpected failure: Catastrophic failure"

In the event viewer, here's what I get:

"(Event ID 33)
Volume Shadow Copy Service error: The VSS management class is not registered. This may be due to a setup failure or as a result of an application's installer or uninstaller.

(Event ID 8193)
Volume Shadow Copy Service error: Unexpected error calling routine CoCreateInstance. hr = 0x80040154."

Is there any way to fix this? Restoration points are set to happen on C: and do work. But I can't make this command lines work.
Comment
Watch Question

noxchoIT Product Manager
CERTIFIED EXPERT
Top Expert 2009

Commented:
Go to services and stop your VSS service. Restart PC and start it. Then try to apply the commands again.
Daniele BrunengoIT Consultant, Web Designer

Author

Commented:
I tried that but nothing has changed.
Daniele BrunengoIT Consultant, Web Designer

Author

Commented:
Is there no one can help me?
IT Product Manager
CERTIFIED EXPERT
Top Expert 2009
Commented:
This one is on us!
(Get your first solution completely free - no credit card required)
UNLOCK SOLUTION
Daniele BrunengoIT Consultant, Web Designer

Author

Commented:
These articles are very interesting, thanks. Anyway, I've found out there was no "real" error. Trouble was, I was using the "Open a command prompt" shell extension, and I was starting it from the Total Commander shell. This is a 32bit shell, my OS is 64bit. Looks like the "Open a command prompt" extension works in 32bit when opened from a 32bit shell. So I couldn't access fully my system32 folder, since it is fully accessible only from true 64bit apps.

This is why the command didn't work. But I wouldn't have found this out if I hadn't run the list of commands from the last article you linked to: one of the commands, containing vssvc.exe, said the file wasn't recognized as an executable, internal or external or batch file.

So it occurred to me that if the files can't be accessed then the command prompt must be 32bit.
So I opened a command prompt the usual way, and bang!, the errors were gone. I'm so used to Total Commander, I would never have thought about this if not for the article you linked, so I'll give you the points.
noxchoIT Product Manager
CERTIFIED EXPERT
Top Expert 2009

Commented:
thanks for points. Glad to be helpful even this small way.
Unlock the solution to this question.
Join our community and discover your potential

Experts Exchange is the only place where you can interact directly with leading experts in the technology field. Become a member today and access the collective knowledge of thousands of technology experts.

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.