• Announcements

    • Terry (WGS)

      WGS Forums Will Close on January 31st 2017   01/18/17

      Hi everyone, We're coming up to We Got Served's ten year anniversary and I've been taking a good look at the site to work through some plans for the future. I wanted to give you all a couple of weeks notice that I'll be closing WGS Forums at the end of this month.  As you'll be aware, the forums were opened to support Windows Home Server users and have done so brilliantly, thanks to everyone's participation. However, with each day that passes, there are fewer and fewer WHS deployments out there, meaning that forum registrations and traffic has now dwindled. I've tried a few times over the years to test some forums on related or adjacent topics, however, they simply haven't caught on. It's clear that these were always going to be predominately Windows Home Server forums and, with the passing of that platform, they've served their purpose well. So, please take some time to archive anything you need over the next two weeks. Access to the forums will end on Jan 31st 2017. Many, many thanks once again for your participation and support here. It's been a great community! Very best wishes Terry

Client Backup Problems - VSS Issues & solution

6 posts in this topic

I just built and setup my server a week ago. One of my primary reasons for getting the server was to backup two laptops and two desktop computers in my home. I had no issues with backing up the laptops (one with WinXP Pro SP2, the other with WinXP MCE SP3). However, I had back up issues with the two desktop machines. Both are running Win XP Home SP3. Both had Volume Shadow Service (VSS) issues, given as a cyptic 0x8000FFFF error. I spent about 3 evenings researching VSS issues. It seems to be a common enough problem, but no specific fixes were in any of the WHS sites/forums. I finally resolved the issue and thought I'd write up the fix to help others. Note that the solution does require registry edits on your client computer.

1. Click Start, click Run, type cmd, and then click OK.This brings up a command prompt window.

2. At the command line type vssadmin list writers, then press enter.If you get an 0x8000FFFF error or other error, proceed with the rest of this solution.

3. Next, make sure the correct services are running. Click Start, Control Panel, Administrative Tools, Component Services. In the Component Services window, click Services (local) and you'll get a list of the services on the client computer.

4.For each of the following services check that the start up type is set to manual. This can be changed in the properties if it is not. Then, right-click the following services one at a time. For each service, click Restart:

• COM+ Event System

• COM+ System Application

• Distributed Transactions Coordinator

• Microsoft Software Shadow Copy Provider

• Volume Shadow Copy

5. Next, we'll check if there are any errors with the VSS services. In the Component Services window, click Event Viewer (local), Application. Look for errors with VSS under the Source column. I had two:

Event ID 5013

Volume Shadow Copy Service error: Shadow Copy writer ContentIndexingService called routine RegQueryValueExW which failed with status 0x80070002 (converted to 0x800423f4).

Event ID 12302

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.

6. Look up the error at support.microsoft.com. The 0x80070002 error, directed me to Article ID 907574. On my client computers, the default registry subkeys were not set correctly. I edited the registry exactly as directed in this article.

7. Look up the 0x8000FFFF error. This takes you to Article ID 940184. My procedures differs a little bit from this article. First, follow steps 1 - 4 to edit the registry.

8. Reboot the computer.

9. Bring up a command prompt window again - Click Start, click Run, type cmd, and then click OK. Type the following list of commands to register the VSS dll's.

• 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 msxml.dll

• regsvr32 msxml3.dll

• regsvr32 msxml4.dll

10. At the command prompt, type vssadmin list writers, and then press ENTER. You should see of the Writer names, Id, Instance ID and state. If you get this, your VSS problems should not be solved, the VSS service should be running and you should be able to back up the client computer to your WHS.



Share this post

Link to post
Share on other sites

Upgrade to a WGS Supporter Account to remove this ad.

Very detailed, thanks Scott. Looks like a candidate for the wiki :)

Share this post

Link to post
Share on other sites

My VSS errors are different and I can't find anything in Microsoft's support site to correct them:

Event ID: 12289

Volume Shadow Copy Service error: Unexpected error CreateFileW(\\?


806d6172696f},0xc0000000,0x00000003,...). hr = 0x80070005

Event ID: 5013

Volume Shadow Copy Service error: Shadow Copy writer

RemoveableStorageManager called routing OpenNtmsSessionW which

failed with status 0x80070015 (converted to 0x800423f3).

Also, when I enter "vssadmin list writers", all writers are stable except for:

Writer name: 'WMI Writer'

Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}

Write Instance ID: {02f38fb4-1d59-4353-b2ec-9e532ecfb4ae}

State: [7] Failed

I haven't been able to get a working backup of this system in two weeks. All my other systems backup fine. I can't find anything that will correct my problem. It is a Windows XP Professional SP3 client system.

Share this post

Link to post
Share on other sites

Thanks for the detailed information.

Some of my services were set to 'Automatic' and not 'manual' so I'm not sure how critical this is.


The service "Microsoft Software Shadow Copy Provider" does not exist in my Services Window so I was not able to check if it was set to 'Manual'.

I'm running XP SP3 so should this service exist?

Many thanks,


Share this post

Link to post
Share on other sites
The service "Microsoft Software Shadow Copy Provider" does not exist in my Services Window so I was not able to check if it was set to 'Manual'.

I'm running XP SP3 so should this service exist?

Continuous updates from original XP culminating to XP3 here, and it exists.

Running services.msc I find:

MS Software Shadow Copy Provider (Manual) (C:\WINDOWS\System32\dllhost.exe /Processid:{4FDADADC-1592-45AA-909D-CA8297BB84D0})

Volume Shadow Copy (Manual) (C:\WINDOWS\System32\vssvc.exe)


Share this post

Link to post
Share on other sites

A tip of the hat to Scottr for the most complete version of how to clean up the problem that can happen with XP systems and WHS backup. I had no problem with this system until I connected it to a WHS 2011 replacing a WHS v1 server. The backup got to 1% and failed. I found a number of sources that covered various pieces of the puzzle, but only Scottr's version mentioned the event viewer in Component Services. I had the same two errors Scottr reported, and cleaned them up by deleting a single registry subkey relating to Microsoft Visio, an application I uninstalled years ago. I left intact another one relating to an application designated as "System" in the subkey, thinking I needn't be too hasty about deleting things entitled "System." Sure enough, it was this little piece of nothing left over from Visio that was causing WHS 2011 to be incapable of backing up my XP system! Finally, "vssadmin list writers" produced a neat list of vss "writers." Don't ask me what any of this means. Many hours down the tube, but all is now working. And I owe my solution to Scottr taking the time to post back in '08.

Let me put in a plug for everyone to support this website by buying a copy of one of the e-books!

Share this post

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

Upgrade to a WGS Supporter Account to remove this ad.

  • Posts

    • I am running WSE2012 R2 and I only ever see red, yellow or green. I have never seen blue even when backing up. I can't explain what could be happening here, but maybe some feedback from other users may help us pin it down. What OS are your client PC's? Mine are all Win 10. Not sure if that may have a bearing.   
    • I made the leap from WHSv1 to WSE2012R2.  I like the new system but one thing seems to be missing.  In WHS v1, the tray icon would change colors to indicate various things blue - backing up now green - everything is healthy yellow - warnings detected (e.g. haven't backed up in a while) red - critical issues (e.g. recent backup failed) In WSE 2012 R2, however, I only get the blue and green indicators, even when there are critical errors on my home network.  For example, a server hard drive had failed for several weeks, but the connector icon in my system tray remained green.  I only discovered the issue when I happened to login to the dashboard for something else. Does anyone know if this feature has been removed in the latest WSE versions?  Or have I just mis-configured something?
    • I am building a new home server: I really want to use StableBit DrivePool and Scanner - am used to them and like the relative ease of use. Hardware = PC running Windows 7 Pro has SSD for OS and 5 additional 2TB HDDs + SansDigital Towerraid (model TR5M6G) connected by eSATA controller (pCie) with 5 2TB HDDs of varying age (2 brand new WD Red and the remaining 3 a combo of Hiatachi and Seagate of varying age - all test out fine for now). Towerraid is currently configured as JBOD, so I can't really see individual drives, and neither does StableBit drive pool - so I get a pool consisting 5 1.82 TB drives (the ones on the PC) and 1 giant 9.1TB drive. I have about 10 TB of data ready to go into this new build.  Will be adding more over time.  Not sure when but certain I'll have HDDs go bad on me, of course. My question(s): 1)  Is there a RAID configuration that will let StableBit do its thing watching individual drives and letting me identify sick drives that need to be removed/replaced?                           2)  If I decide to give up the RAID and just let DrivePool handle duplication, how do I configure the SansDig?                           3)  Am I just getting it all wrong from the get-go? Would appreciate any advice - thanks   
    • I have almost 10 TB in the storage pool so I was not surprised when my first server backup took a very long time (22 hrs.).  Lately the incremental server backups have been fast (15 - 18 min.)  Two days ago the server apparently initiated a full backup that failed twice but completed successfully this morning after about 23 hours.  An hour later the regular daily backup is back to a normal incremental backup times (18 min.) So why did the previous backup take so long, as long as a full backup would take? Does the server occasionally make a fresh start with a full backup to reduce the time a full incremental recovery takes?  (fewer increments, less processing time) I don't see a setting in the server backup options for specifying a number of increments between full backups, for example.    
    • I just posted a similar question elsewhere.  By Shadow Copies are you referring to the Windows 10 File History backups that periodically use shadow copy to backup open files? I too discovered that a huge amount of backup space was consumed by File History backups, no doubt because I was moving some large Blu-Ray files around.  That I fixed by moving the temporary and final file folders to the server, where they are backed up as part of the daily server backup.  That too, of course, uses Shadow Copies but that is another story. Has anyone done the math?  What is the equivalence .. or lack thereof ... between the traditional WS2012r2 (WHS v1 et al.) daily incremental backup :: and a Win7 System Image backup + File History backups? Restore time comparison? Which do you feel is best?
  • Popular Contributors