It will do this when trying to stop windows services, as shown in this setup screen fragment:
When examining the logfile you will encounter this entry:
[2:18:33 PM Info] Action 14:18:33: StopServices. Stopping services
[2:18:37 PM Info] Detailed Log information for product E:\Msi\Microsoft BizTalk Server 2010_64.msi is available at DetailedLog
[2:18:37 PM Info] MSI installation returned 1601 - The Windows Installer Service could not be accessed. This can occur if the Windows Installer is not correctly installed. Contact your support personnel for assistance.
When analyzing the detaild log, you find this entry:
MSI (s) (5C:E8) [14:18:33:961]: Executing op: ServiceControl(,Name=WinMgmt,Action=2,Wait=1,)
MSI (s) (5C:E8) [14:18:37:493]: Internal Exception during install operation: 0xc00000fd at 0x000000007723A725.
Reason for this is that BizTalk Setup tries to stop and start the WMI Service. As Officescan is dependent on this, it would als need to be stopped and started and that might be disabled as a policy. As a result setup fails.
To check if this is indeed the cause, try to stop the WMI Service by hand using the services manager in Administrative Tools. If it gives a list containing the service OfficeScan NT Listener.
In order to succeed, you need have Trend services disabled by a domain administrator. I suggest installing a scanning tool that does not rely on heavily used services.
