Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > alt.comp.os.windows-10 > #184308

Re: After years of reboots - I finally today solved a 99-port lockup after Microsoft Updates

From Marion <marion@facts.com>
Newsgroups alt.comp.os.windows-10, alt.comp.os.windows-10, 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 15:45 +0000
Organization BWH Usenet Archive (https://usenet.blueworldhosting.com)
Message-ID <vvdar2$ro3$1@nnrp.usenet.blueworldhosting.com> (permalink)
References <vv4b6h$3052$1@nnrp.usenet.blueworldhosting.com> <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>

Cross-posted to 3 groups.

Show all headers | View raw


On Tue, 6 May 2025 22:06:40 +0800, Mr. Man-wai Chang wrote :


>> I wonder... Do we event need the Winnat functionality?
>> To find out what happens if I don't restart it, I won't.
>> How else can I find out what uses Winnat on Windows 10?
> 
> You sure that it had nothing to do with the firewall and/or the free 
> anti-virus scanner??
> 
> NAT should be automatic and working by default, I dunno....

Thanks for trying to help as this issue had frustrated me for years. 

I'm not sure of anything, but like most people here, I stopped using
antivirus scanners (e.g., Avast) years ago when Windows Defender got
better. Now I just use the Windows default.

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.

But "something" is telling Winnat to reserve 1400 ports randomly on boot.

The main reason I never tracked it down was that nothing was using the
ports so I couldn't figure out what the problem was aiming in that manner.

The other reason I never tracked it down before was that a reboot fixed it.
But now I realize a reboot simply moved the 1400 reserved ports to a
different random set. That randomness also explains why sometimes I had to
reboot twice.

One reason for posting this information, other than you help anyone with
the same problem, is to see if anyone else has random ports excluded.

When people run this command, do they get two lines or more of output?
C:\> netsh int ipv4 add excludedportrange protocol=tcp startport=55500 numberofports=101

Back to alt.comp.os.windows-10 | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


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