You define a Windows PowerShell script execution policy by applying a Group Policy Object, or you apply a local Group Policy.
You try to install a Microsoft Exchange Server 2010 or Microsoft Exchange Server 2013 update rollup or service pack.
The setup process fails after the Remove Exchange Files step is completed.
In this scenario, Exchange Server does not work on the affected server. Additionally, you cannot restart the setup process.
This issue occurs because the required Windows Management Instrumentation (WMI) service stops during the installation process. The WMI service is needed to query Active Directory Domain Services (AD DS) to verify the Windows PowerShell script execution policy that must run as a part of the setup.
To avoid this issue, follow these steps:
Disable the execution Group Policy by using the Group Policy Management Console (Gpmc.msc) or Local Group Policy Editor (Gpedit.msc). Group Policy objects for the execution Group Policy must be set to Undefined.
Install the Exchange Server 2010 or Exchange Server 2013 update rollup or service pack.
Re-enable the previously defined Windows PowerShell script execution policy in the Group Policy Management Console or Local Group Policy Editor.
Note The issue that is described in the "Symptoms" section is resolved in Exchange Server 2010 SP3. In Exchange Server 2010 SP3 and later versions, the Windows PowerShell script execution policies are verified correctly. Therefore, you do not have to disable the script execution policies when you install an update rollup or service pack.
For more information about Exchange Server 2010 SP3, click the following article number to view the article in the Microsoft Knowledge Base:
2808208 Description of Exchange Server 2010 Service Pack 3
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
To verify the execution policies before you begin the installation process, run the following Windows PowerShell cmdlet: