Windows Server AppFabric Beta2 Setup: Common issues and resolutions

Note: This information applies to Windows Server AppFabric Beta2

Issue/symptoms:
1. An unhandled exception ('System.Runtime.InteropServices.COMException') occurred in setup.exe [3668]
2. Setup.exe crashes and watson dump shows the following: System.Runtime.InteropServices.COMException (0x800B0100): No signature was present in the subject. (Exception from HRESULT: 0x800B0100

Potential resolution: The registry entries under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\ may be corrupt. The System Update Readiness Tool (KB947821) would fix some of these corrupt package entries but not all. However, it would list all entries which it could not fix, in CheckSUR.log. Manually remove those entries from registry as per this article: https://www.raymond.cc/blog/archives/2009/03/06/fix-blank-or-empty-list-in-vista-turn-windows-features-on-or-off-optionalfeaturesexe/

Issue/Symptoms:

Setup is disabled or is not enabled devices associated with service failed to start
Setup Microsoft.ApplicationServer.Setup.Core.SetupException: it is disabled or is not enabled devices associated with service failed to start
Microsoft.ApplicationServer.Setup.Installer.WusaProxy.GenerateAndThrowSetupException (Int32 exitCode, LogEventSource logEventSource)
Microsoft.ApplicationServer.Setup.Installer.WusaProxy.Invoke (LogEventSource logEventSource, String packageName)
Microsoft.ApplicationServer.Setup.Installer.CbsInstaller.InvokeWusa (InstallMode installMode)
Microsoft.ApplicationServer.Setup.Installer.CbsInstaller.Install ()
Microsoft.ApplicationServer.Setup.Client.SetupWorkflow.StartActionPhase ()
Microsoft.ApplicationServer.Setup.Client.ProgressPage.StartAction ()

Potential resolution: Check if the Windows Update server is stopped/disabled. This service needs to be running to install Windows Server AppFabric.