Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. Port are blocked after you install February 13 cumulative update 4074588 in Windows 10 Version 1709

Port are blocked after you install February 13 cumulative update 4074588 in Windows 10 Version 1709

View products that this article applies to.

Symptoms

Some reserved ports are blocked after you install the February 13 cumulative update KB4074588 on a container host that is running Windows 10 Version 1709.

↑ Back to the top

Cause

Before February 13 cumulative update, there was an issue which caused incorrect ports to be reserved on the computer.

This issue is fixed by February 13 cumulative update. However, if the originally intended port was being used by the applications, there may be a perceived regression in which they may be unable to reserve or bind to the port any longer.

↑ Back to the top

Resolution

To resolve this problem, check whether the port that you want to publish is already reserved on the container host. To do this, use netsh.
 

For example, run the following command:

netsh interface ipv4 show excludedportrange protocol=tcp

If the port is not reserved, you can use it. Otherwise, you must select a different port.

↑ Back to the top

Keywords: kbContentAuto, CI76893

↑ Back to the top

Article Info
Article ID : 4093046
Revision : 11
Created on : 3/30/2018
Published on : 3/30/2018
Exists online : False
Views : 580