Skip to main content
re register vss writers

Re Register VSS Writers In Windows

Re Register VSS Writers

“Re Register VSS” writers is the process that brings the unstable writers back to stable state. VSS writers are very important because they are used by backup applications to take the backup. For example, Microsoft Exchange has its own VSS Writer called “Microsoft Exchange Writer”. These writers should be in the “Stable ” state for the backups to be completed successfully.

We can check the status of the writers by running the following command on CMD:

VSSAdmin List Writers

The result looks like this:

vssadmin list writers

Some times the writers become unstable or hang, as a result the backup fails. A simple server restart usually brings them back to the stable state as a result the backup starts working again. But some times the writers do not come back to the stable state. In those situations, we have to re register the volume shadow copy service Dll’s.


The method is same in Server 2008, 2008 R2, 2012, 2012 R2 and Server 2016. The steps are as follows:

First of all, open CMD and go to the “%WinDir%system32” directory

Secondly, run Net Stop VSS and Net Stop SWPRV to stop the volume shadow and MS Software shadow copy provider services.

Stop Services

Next run the following commands one by one to re register the dlls and services.

regsvr32 /s ole32.dll
regsvr32 /s oleaut32.dll
regsvr32 /s vss_ps.dll
vssvc /register
regsvr32 /s /i swprv.dll
regsvr32 /s /i eventcls.dll
regsvr32 /s es.dll
regsvr32 /s stdprov.dll
regsvr32 /s vssui.dll
regsvr32 /s msxml.dll
regsvr32 /s msxml3.dll
regsvr32 /s msxml4.dll
vssvc /register
re register vss writers

Finally, run “Net Start SWPRV” and “Net Start VSS” to start the MS software shadow copy provider and volume shadow services.

Check the writers again by running “VSSAdmin List Writers”, and hopefully this time the writers will be in stable state and most importantly the backups will also complete.


For further reading, “Volume Shadow Copy Service”.


Automatically detect settings

Downloading Proxy Script in Google Chrome

Downloading Proxy Script in Google Chrome

At time you may see “Downloading Proxy Script” in the lower left corner of chrome window in google chrome and the websites taking forever to load. This problem is faced when you are using a proxy server to access the internet. Companies use proxy server to control the internet access for their employees. While users put the proxy in their Internet Explorer Proxy options. Google chrome uses these proxy settings from internet explorer to reach the internet.


The solution to “Downloading Proxy Script” problem is pretty simple. You just need to uncheck the “Automatically Detect Settings” in the proxy settings.

First of all, In Google Chrome go to settings and look for “Proxy settings”. Alternatively you can open the Internet Options in Internet Explorer. Because both open the same window.

Automatically detect settings

On the connections Tab, click “Land Settings” and UNCHECK “Automatically Detect Settings”, click OK.

Finally, close the chrome and open it again, now Google chrome will load the sites faster without showing the “Downloading Proxy Script”.


If you want to know more about Proxy settings in internet explorer you can read Technet article about “How to configure Internet explorer to use proxy server”

0x800706BA RPC server unavailable

0x800706BA RPC Server Unavailable

0x800706BA RPC Server Unavailable

0x800706BA RPC server unavailable is an error that you may face in multiple applications. When the “Remote Procedure Call” connectivity between two devices fails, this error may appear.

To confirm if we have the RPC between two devices, we can run the following command:

Get-WmiObject Win32_ComputerSystem –ComputerName DestinationServer

The successful RPC connectivity result look like this:

RPC Successful

If the RPC connectivity fails, the result will be as follows:

0x800706BA RPC server unavailable


To troubleshoot the “0x800706BA RPC server unavailable” error, check the following:

  • First of all, make sure the remote/destination device is up and running.
  • Make sure the RPC service is running on remote/destination device.
  • Check if you have any firewall in between both devices and required ports are open.
  • Check If Windows Firewall is enable on either side, disable it and then try again.
  • Make sure the antivirus is not blocking any traffic.
  • Finally, Try to have connectivity by using the IP instead of the name to confirm it is not DNS issue.