Main Forum > Tweaking.com Support & Help

Windows Repair task 04 (Register System Files) clobbering Vista VSS??

(1/4) > >>

GLykos:
Ran the first four tasks in the repairs library (WR 3.8.0).  Believe as a result of that the Vista backup and restore function is broken.

Attempting to create backup in System Properties, System Protection says "The restore point could not be created for the following reason:  Catastrophic failure (0x8000FFFF)  Please try again."

App Event Log shows "Volume Shadow Copy Service error: The VSS event class is not registered.  This will prevent any VSS writers from receiving events. This may be caused due to a setup failure or as a result of an application's installer or uninstaller."

Searching for fix to register the VSS event class, find "Beginning with Windows Vista and Windows Server 2008, Windows component installation is manifest-based, and most of the registry is locked down even to Administrator. ***However, the VSS binaries in Windows Vista and Windows Server 2008 still contain the code to perform self-registration. The code is removed in Windows 7 and 2008 R2.***  It is not recommended to re-register VSS binaries in Windows Vista and Windows Server 2008 or later operating systems."

Continuing, "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 Windows be reinstalled to resolve."

That said - does task 04 re-register the Vista DLL's associated with the VSS event class, or does it exclude them from processing?

As a side note - now what??

Thanks,
George


P.S.  Realized that the same problem was posted on 1/9.  The additional information above may help to figure out what's going on.

In response to a query in a reply to that post -

   vssadmin list writers returns:  vassadmin 1.1 - VSCS administration cmd-line tool and copyright notice.  No values

   vssadmin list providers returns:  Name: 'MS Sfwr Shadow Copy provider 1.0'  Provider type: System.  Provider Id: <b5946137-7b9f-4925-af80-51abd60b20d5>.  Version: 1.0.0.7

Boggin:
I've contacted Shane for him to investigate this error for you.

Shane:
So i looked up this error and checked on my vista system in vmware and was getting the same error.

Also when I ran vssadmin list writers in a cmd.exe window it came back blank.

So I opened my windows repair, unselected all the repairs and told it to only repair the volume shadow copy service. After that it started working just fine. Which is odd, as I dont know why it wasnt working in the first place. This is with Windows repair v3.8.0

So I have it running all the repairs and will see if the error comes back or not.

So try that as well, run the repairs but only run the 1 repair, repair volume shadow copy and let me know if that fixes it. So i know the repair fixes it I need to see if there is something else in a different repair that might be breaking it.

Shane

Shane:
Ok so ran all repairs reboot and vss is working fine.

So now I am just running repair 4, the register system files, and after a reboot vssadmin list writers comes back blank.

So I am looking to why that is happening. Whats odd is why it is only happening on vista. I will see what i can find and get a fix out for it in the next update :-)

Shane

Shane:
Well that was the strangest bug I  have seen lately lol

Ok I found the fix and will put out version 3.8.1 tomorrow.

So in the register system files is the same files as the vss repair, yet the vss repair would fix what the other repair broke. So i compared them and I noticed one small thing and decided to try something.

As an example, in the register system files.txt file I had these commands

eventcls.dll /i /s
eventcls.dll /s

The /s is for silent when registering a file and the /i is the DLLinstall command.

So you will see it does the /i first and then calls again to do a normal register.

So in the vss repair I noticed I had the /i 2nd instead.

So as a test I switched every file in the register system files that had a /i command to be 2nd instead (They where all first) I then ran that repair and guess what, VSS starting working properly again. I was a little shocked.

So for some reason calling a normal regsvr32 after doing the /i seems to break something in vista. I dont have this problem in 7 8 and 10.

But at least I found the fix for it, so I will have the update out tomorrow :-)

Shane

Navigation

[0] Message Index

[#] Next page