Some Windows Server 2012 R2, Windows 2016, Windows 2019, Windows 8.1, and Windows 10 machines that are deployed as single-session desktops do not become available immediately after they are provisioned. This issue occurs when the Windows Firewall service does not restart after its timeout period expires. You can configure the Windows Firewall service on the parent (master image) or template virtual machine to ensure that all machines in a desktop pool become available.

If you encounter this issue during provisioning, the Windows event logs display the following error: The Windows Firewall service terminated with the following service-specific error: This operation returned because the timeout period expired.

This issue occurs on Windows Server 2012 R2, Windows 2016, Windows 2019, Windows 8.1, and Windows 10 machines. Other guest operating systems are not affected.

Procedure

  1. On the Windows Server 2012 R2, Windows 2016, Windows 2019, Windows 8.1, or Windows 10 parent (master image) or template virtual machine from which you will deploy a desktop pool, select Control Panel > Administrative Tools > Services.
  2. In the Services dialog box, right-click the Windows Firewall service and select Properties.
  3. In the Windows Firewall Properties dialog box, click the Recovery tab.
  4. Select the recovery settings to restart the service after a failure occurs.
    Setting Drop-down Menu Option
    First failure: Restart the Service
    Second failure: Restart the Service
    Subsequent failures: Restart the Service
  5. Select the Enable actions for stops with errors check box and click OK.
  6. Deploy or redeploy the desktop pool from the parent (master image) or template virtual machine.