Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > alt.comp.os.windows-10 > #184312
| From | Marion <marion@facts.com> |
|---|---|
| Newsgroups | alt.comp.os.windows-10, alt.comp.os.windows-11, alt.comp.microsoft.windows |
| Subject | Re: After years of reboots - I finally today solved a 99-port lockup after Microsoft Updates |
| Date | 2025-05-06 17:25 +0000 |
| Organization | BWH Usenet Archive (https://usenet.blueworldhosting.com) |
| Message-ID | <vvdgle$pg9$1@nnrp.usenet.blueworldhosting.com> (permalink) |
| References | (1 earlier) <vv8rh9$299h$1@nnrp.usenet.blueworldhosting.com> <vv8uoh$v14$1@nnrp.usenet.blueworldhosting.com> <vv92fu$jpf$1@nnrp.usenet.blueworldhosting.com> <vvd51i$3302u$1@toylet.eternal-september.org> <vvdar2$ro3$1@nnrp.usenet.blueworldhosting.com> |
Cross-posted to 3 groups.
On Tue, 6 May 2025 15:45:39 -0000 (UTC), Marion wrote :
> While I know Winnat is who is reserving the ports, I'm assuming a Hyper-V
> related app (like Docker) is commanding Winnat to reserve ports on bootup.
>
> But I don't have Docker.
> And I can't even spell Hyper-V.
Woo hoo! I think I finally found the culprit all these years who
was telling winnat to reserve random 1300 ports upon every reboot!
C:\> netsh interface ipv4 show excludedportrange protocol=tcp
Protocol tcp Port Exclusion Ranges
Start Port End Port
---------- --------
5357 5357 (1 port excluded)
33476 33575 (100 ports randomly excluded)
33576 33675 (100 ports randomly excluded)
33676 33775 (100 ports randomly excluded)
33776 33875 (100 ports randomly excluded)
33876 33975 (100 ports randomly excluded)
33976 34075 (100 ports randomly excluded)
34076 34175 (100 ports randomly excluded)
34176 34275 (100 ports randomly excluded)
34276 34375 (100 ports randomly excluded)
34376 34475 (100 ports randomly excluded)
34476 34575 (100 ports randomly excluded)
34576 34675 (100 ports randomly excluded)
34694 34793 (100 ports randomly excluded)
50000 50059 * (60 ports excluded)
* - Administered port exclusions.
I looked up what Hyper-V is, and I don't think I need it.
So I got rid of it.
PS> Get-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-All
FeatureName : Microsoft-Hyper-V-All
DisplayName : Hyper-V
Description : Provides services and management tools for creating and running virtual
machines and their resources.
RestartRequired : Possible
State : Enabled
CustomProperties :
Disable Hyper-V
PS> Disable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-All
Reboot:
C:\> shutdown /r /t 0
When the machine came up, I checked that Hyper-V is disabled.
PS> Get-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-All
FeatureName : Microsoft-Hyper-V-All
DisplayName : Hyper-V
Description : Provides services and management tools for creating and running virtual
machines and their resources.
RestartRequired : Possible
State : Disabled
CustomProperties :
Now, when I check, the 1300 random reservations are finally gone!
C:\> netsh interface ipv4 show excludedportrange protocol=tcp
Protocol tcp Port Exclusion Ranges
Start Port End Port
---------- --------
5357 5357
50000 50059 *
55500 55600 * <== I had reserved these 101
* - Administered port exclusions.
If anyone else has Hyper-V enabled (whatever the heck that is),
can you check to see what ports you have reserved by Winnat?
Back to alt.comp.os.windows-10 | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
After years of reboots - I finally today solved a 99-port lockup after Microsoft Updates Marion <marion@facts.com> - 2025-05-03 05:56 +0000
Re: After years of reboots - I finally today solved a 99-port lockup after Microsoft Updates Paul <nospam@needed.invalid> - 2025-05-03 13:38 -0400
Re: After years of reboots - I finally today solved a 99-port lockup after Microsoft Updates Marion <marion@facts.com> - 2025-05-03 22:24 +0000
Re: After years of reboots - I finally today solved a 99-port lockup after Microsoft Updates Uncle Bob <uncle.bob@nospam.net> - 2025-05-03 18:58 -0400
Re: After years of reboots - I finally today solved a 99-port lockup after Microsoft Updates Victor <victorheyne@notreal.org> - 2025-05-06 11:32 -0500
Re: After years of reboots - I finally today solved a 99-port lockup after Microsoft Updates Marion <marion@facts.com> - 2025-05-09 20:36 +0000
Re: After years of reboots - I finally today solved a 99-port lockup after Microsoft Updates Marion <marion@facts.com> - 2025-05-09 20:56 +0000
Re: After years of reboots - I finally today solved a 99-port lockup after Microsoft Updates Marion <marion@facts.com> - 2025-05-04 22:59 +0000
Re: After years of reboots - I finally today solved a 99-port lockup after Microsoft Updates Marion <marion@facts.com> - 2025-05-04 23:54 +0000
Re: After years of reboots - I finally today solved a 99-port lockup after Microsoft Updates Marion <marion@facts.com> - 2025-05-05 00:58 +0000
Re: After years of reboots - I finally today solved a 99-port lockup after Microsoft Updates "Mr. Man-wai Chang" <toylet.toylet@gmail.com> - 2025-05-06 22:06 +0800
Re: After years of reboots - I finally today solved a 99-port lockup after Microsoft Updates Marion <marion@facts.com> - 2025-05-06 15:45 +0000
Re: After years of reboots - I finally today solved a 99-port lockup after Microsoft Updates Marion <marion@facts.com> - 2025-05-06 15:50 +0000
Re: After years of reboots - I finally today solved a 99-port lockup after Microsoft Updates Marion <marion@facts.com> - 2025-05-06 17:25 +0000
Re: After years of reboots - I finally today solved a 99-port lockup after Microsoft Updates "Mr. Man-wai Chang" <toylet.toylet@gmail.com> - 2025-05-21 02:16 +0800
Re: After years of reboots - I finally today solved a 99-port lockup after Microsoft Updates Marion <marion@facts.com> - 2025-05-20 19:51 +0000
Re: After years of reboots - I finally today solved a 99-port lockup after Microsoft Updates Marion <marion@facts.com> - 2025-05-06 15:58 +0000
csiph-web