The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.

Im unable to get Acronis Backup Advanced 11.5_43994 installed on a Windows server 2008, it has had agents installed on it before and always worked with no issues, but it seems after uninstalling an earlier agent and installing a newer version that it now wont allow to install.

It fails at the 2nd stage of the install when installing the "Acronis Backup 11.5 Agent for Windows" with an error

"The service cannot be started, either because it is disabled or because it has no enabled devices associated with it."

Iv looked on Acronis KB and seen some similar errors and i have run the 'abr_cleanup.exe' tool which has successfully completed and removed all Acronis components, but the install still fails.

I have also ran the WMI Diags tool from Microsoft which has run its various scans, which is coming back with some warnings, please see the below extract from the txt file that was generated as part of this vbs script being run.

WARNING: WMI provider DCOM registrations missing for the following provider(s): ..................................... 8 WARNING(S)!
32534 11:22:19 (0) ** - ROOT/CIMV2, Win32_WIN32_WINDOWSPRODUCTACTIVATION_Prov ({EA231B91-099E-4D02-9EE7-73976D6A085F})
32535 11:22:19 (0) **   Provider DLL: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
32536 11:22:19 (0) ** - ROOT/CIMV2, Win32_WIN32_COMPUTERSYSTEMWINDOWSPRODUCTACTIVATIONSETTING_Prov ({A2B6D807-EE1E-40F6-BDF4-B4D6F552783E})
32537 11:22:19 (0) **   Provider DLL: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
32538 11:22:19 (0) ** - ROOT/CIMV2, Win32_WIN32_PROXY_Prov ({AF134D0A-6706-4ACD-BA76-D0A852474C99})
32539 11:22:19 (0) **   Provider DLL: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
32540 11:22:19 (0) ** - ROOT/CIMV2, CmdTriggerConsumer ({797EF3B3-127B-4283-8096-1E8084BF67A6})
32541 11:22:19 (0) **   Provider DLL: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
32542 11:22:19 (0) ** - ROOT/PERFMON, SmonlogProv ({F95E1664-7979-44F2-A040-496E7F500043})
32543 11:22:19 (0) **   Provider DLL: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
32544 11:22:19 (0) ** - ROOT/MICROSOFTIISV2, IIS__PROVIDER ({D78F1796-E03B-4A81-AFE0-B3B6B0EEE091}) (i.e. WMI Class 'IIsMimeMapSetting')
32545 11:22:19 (0) **   Provider DLL: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
32546 11:22:19 (0) ** - ROOT/MICROSOFTACTIVEDIRECTORY, TrustPrv ({8065652F-4C29-4908-AAE5-201C891904C5}) (i.e. WMI Class 'Microsoft_DomainTrustStatus')
32547 11:22:19 (0) **   Provider DLL: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
32548 11:22:19 (0) ** - ROOT/MICROSOFTACTIVEDIRECTORY, ReplProv1 ({29288F43-39B1-40DB-B41F-CE899450E911}) (i.e. WMI Class 'MSAD_ReplPendingOp')
32549 11:22:19 (0) **   Provider DLL: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
32550 11:22:19 (0) ** => This is an issue because there are still some WMI classes referencing this list of providers
32551 11:22:19 (0) **    while the DCOM registration is wrong or missing. This can be due to:
32552 11:22:19 (0) **    - a de-installation of the software.
32553 11:22:19 (0) **    - a deletion of some registry key data.
32554 11:22:19 (0) **    - a registry corruption.
32555 11:22:19 (0) ** => You can correct the DCOM configuration by:
32556 11:22:19 (0) **    - Executing the 'REGSVR32.EXE <Provider.DLL>' command.
32557 11:22:19 (0) **    Note: You can build a list of classes in relation with their WMI provider and MOF file with WMIDiag.
32558 11:22:19 (0) **          (This list can be built on a similar and working WMI Windows installation)
32559 11:22:19 (0) **          The following command line must be used:
32560 11:22:19 (0) **          i.e. 'WMIDiag CorrelateClassAndProvider'
32561 11:22:19 (2) !! WARNING: Re-registering with REGSVR32.EXE all DLL from 'C:\WINDOWS\SYSTEM32\WBEM\'
32562 11:22:19 (0) **          may not solve the problem as the DLL supporting the WMI class(es)
32563 11:22:19 (0) **          can be located in a different folder.
32564 11:22:19 (0) **          You must refer to the class name to determine the software delivering the related DLL.
32565 11:22:19 (0) ** => If the software has been de-installed intentionally, then this information must be
32566 11:22:19 (0) **    removed from the WMI repository. You can use the 'WMIC.EXE' command to remove
32567 11:22:19 (0) **    the provider registration data.
32568 11:22:19 (0) **    i.e. 'WMIC.EXE /NAMESPACE:\\ROOT\MICROSOFTACTIVEDIRECTORY path __Win32Provider Where Name='ReplProv1' DELETE'
32569 11:22:19 (0) ** => If the namespace was ENTIRELY dedicated to the intentionally de-installed software,
32570 11:22:19 (0) **    the namespace and ALL its content can be ENTIRELY deleted.
32571 11:22:19 (0) **    i.e. 'WMIC.EXE /NAMESPACE:\\ROOT path __NAMESPACE Where Name='MICROSOFTACTIVEDIRECTORY' DELETE'
32572 11:22:19 (0) **    - Re-installing the software.

To be honest im a little uncomfortable playing around with registry settings as i dont have a recent backup of this box, do you have any further advice regarding this issue?