Revision history [back]

click to hide/show revision 1
initial version

Yes, This a known system issue as per the Microsoft KB article. where the registry path to Eventcls.dll is incorrect or because the registry data type for the TypeLib setting is incorrect.

To fix this issue please follow the steps given below.

  • Click Start, type regedit in the Start Search box, and then press ENTER.

  • Locate and then click the following registry key:

HKEYLOCALMACHINE\SOFTWARE\Microsoft\EventSystem{26c409cc-ae86-11d1-b616-00805fc79216}\EventClasses{FAF53CC4-BD73-4E36-83F1-2B23F46E513E}-{00000000-0000-0000-0000-000000000000}-{00000000-0000-0000-0000-000000000000}

  • Locate the TypeLib registry value.

NOTE The registry type of TypeLib should be shown as REGEXPANDSZ. If that is not the case, you have to delete the key, and then you have to recreate the key. To do this, follow these two steps:

      a. Select the TypeLib registry value, and then delete it.

      b. Create a new Expandable String Value, and then name it TypeLib.

- Double-click the TypeLib registry value. In the Value Data box, type

%systemroot%\system32\EVENTCLS.DLL,

and then click OK.

  • Close Regedit.
  • Click Start, type services.msc in the Start Search box, and hit Enter.

  • Right-click the following services one at a time and click Restart:

       • COM+ Event System 
       • Volume Shadow Copy
    
  • Close the Services snap-in.
  • Open an elevated command prompt, type

vssadmin list writers

and then hit ENTER.

  • Verify that the VSS writers are now listed.

Copyright © Vembu Technologies 2021. All Rights Reserved.