My case: msi installer created with WiX. SQL Server Express 2008 R2 SP1 installer was started from within my installer via C# custom action. Custom action was starting the sql server installer via the command line.
And it was working fine in Windows Server 2008, Windows 7, even in Windows XP. However, in Windows 8 it gave out about compatibility.
I updated the installer to SQL Server 2008 R2 SP2. That's when it started to get stuck at ExecuteStahdardTimingsWorkflow with no progress.
Looking at %ProgramFiles%\Microsoft SQL Server\100\Setup Bootstrap\Log revealed the piece below which gave me a clue that it cannot top msiexec.exe (Windows Installer) service.
What helped (a little bit brutal): added piece of code to the custom action that searched for Windows Installer service process id and explicitly killed it with taskkill /F /PID xxxxx (stopping didn't help!)
2013-10-07 13:17:44 Slp: Completed Action: InitializeMsiAction, returned True
2013-10-07 13:17:44 Slp: ----------------------------------------------------------------------
2013-10-07 13:17:44 Slp: Running Action: MsiTimingAction
2013-10-07 13:17:44 Slp: ----------------------------------------------------------------------
2013-10-07 13:17:44 Slp: Running Action: Install_SqlSupport_Cpu64_Action
2013-10-07 13:17:44 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
2013-10-07 13:17:44 Slp: Sco: Attempting to open registry subkey
2013-10-07 13:17:44 Slp: Sco: Attempting to open registry subkey SOFTWARE\Microsoft\VisualStudio\9.0
2013-10-07 13:17:44 Slp: Sco: Waiting for service 'msiserver' to accept the stop request.
2013-10-07 13:17:44 Slp: Sco: Returning service status Running
2013-10-07 13:17:49 Slp: Sco: Returning service status Running
2013-10-07 13:17:54 Slp: Sco: Returning service status Running
....
2013-10-07 13:20:39 Slp: Sco: Returning service status Running
2013-10-07 13:20:44 Slp: Sco: Returning service status Running
---------------- Peter Dementiev