Highlighted

Need to know why we can't re-register the VSS dll's on windows 2008.

Hello Team,

I want to know why we can't re-register the VSS dll's on windows 2008.

Is there any article available where I will find the perfect reason in details.  Also if I re-register the VSS dll's on windows 2008, then what all those difficulties and issues I will faced after that.

 

Regerds,

Santosh Pawar.

1 Solution

Accepted Solutions
Accepted Solution!

Read the MS TN

Read the MS TN below

http://support.microsoft.com/kb/940184

in particular, note this

This article is not for use with Windows Vista, with Windows Server 2008, or with later Windows operating systems. Starting with Windows Vista and with Windows Server 2008, Windows component installation is manifest-based. Trying to manually register specific components, as described in the following steps, can have unexpected results that may require you to reinstall Windows to resolve.

View solution in original post

4 Replies

Hi Santosh,   The TN below

Hi Santosh,

 

The TN below will explain why. Check for the section above Related Articles:

http://www.symantec.com/business/support/index?page=content&id=TECH173983

Thanks!

Accepted Solution!

Read the MS TN

Read the MS TN below

http://support.microsoft.com/kb/940184

in particular, note this

This article is not for use with Windows Vista, with Windows Server 2008, or with later Windows operating systems. Starting with Windows Vista and with Windows Server 2008, Windows component installation is manifest-based. Trying to manually register specific components, as described in the following steps, can have unexpected results that may require you to reinstall Windows to resolve.

View solution in original post

Thanks for your reply

Thanks for your reply Guys......

I will go through your articles.

 

Regards,

Santosh Pawar

Santoshpawar,         

Santoshpawar, 

        Awesome techdocs provided above by Craig and PKH. Not really much more to be said. Note that VSS issues outside of restarting the box to bring the writer back to a state 1 stable state would be best troubleshot by M.S. The pararagh following  PKH's qoute above ends with "For more information please contact Microsoft, or refer to their documentation." This may be the best/safest course of action.