Windows 11 Lengthy Boot

I’ve contacted Xfinity and this is a known issue for gaming equipment that requires a consistent network connection. The solution is to configure the modem for Port Triggering, a secure form of Port Forwarding. Reading the instructions it’s complicated, and mostly talks about WiFi connectivity to game consoles. But hopefully this will pertain to a hard wired PC. Right now I’ve reset the modem to factory and attempting to login as admin, which is not working. Of course. I’ll get it eventually.

So I’m in the process of doing that and will post the results,

Brian -

I'm still here and engaged.

All router manuals and setup guides are online. I'd google yours to reset and optimize it, check for any known issues.

There are good general guides here for reset and optimizing router:

https://www.lifewire.com/resetting-a-home-netwo...

https://www.pcmag.com/article/258865/how-to-set...

http://www.maximumpc.com/article/features/ultim...

https://www.techrepublic.com/article/how-to-opt...

Your router model will also have specific reset steps and optimizations. I'd be all over that. If it's less than a year old ask for router Support to help you optimize it.

I'd also plug ethernet directly into modem to test. For this you can ask for support from the IP which must get it working properly as part of the monthly bill. If they tell you it's a Windows problem, tell them you've already eliminated all possibilities working with a Moderator and 10 year MVP in Microsoft's Community forums.

Keep me posted on your progress as I will be here to help until the case is resolved.

Ok - now that I've isolated it to being network related and happening with both WiFi and Ethernet, this morning I had the idea of connecting my computer to the Internet with my cell phone hot spot. The problem disappeared. OMG finally! So it's got to be something either in the router, or in the Comcast network. Now we see if Comcast can help solve this.

Thanks for sticking with me Greg. That was pretty hairy, but it turned out to be something relatively simple after all that. If you have any interest in the final solution let me know and I will post.

These articles do not appear to pertain to my issue. Mostly they about network lag, which I do not have on any of the many devices in our home. Also network lag does not occur like clockwork - every 73 seconds. I find nothing in the other articles that either I haven't tried or that's pertinent.

That said it is related to network activity and I did some more testing.

To see if it was related to the Ethernet adaptor and connection to the router I disconnected the Ethernet cable and enabled WiFi. The same glitch occurs on WiFi. I know that the modem/router can't be the culprit because none of the other many streaming and other network dependent devices are having any issues. And I've rebooted that modem/router several times between the time this started and now.

When this glitch occurs, using TM, I can see that there is network traffic that starts and ends with the freeze. My guess is whatever process is generating the traffic is somehow getting exclusive use of the Windows process that sends and receives network traffic and blocking any other process from using it. This process sits above the driver level since it affects both the Wifi and Ethernet traffic. Most apps aren't really affected by this as a continuous stream is not required, there is application buffering etc that shields them from being interrupted by temporarily not having access to the network. But these flight sim apps,, when they are configured to use the network, do depend on continuous access.

Also remember that this happens even when all startup apps are disabled, and all non-MS services are disabled. So it has to be an MS process of some sort that is getting kicked off every 73 seconds. Why this has started recently I cannot hazard a guess. I don't remember if or when I made any changes to the system around the time this started happening.

Something else interesting. I had a third party service, RTSS Rivatuner, that started up with Windows. When I was using Process Explorer to try to see what was going on, I was looking at the comings and goings of dllhost.exe instances. When the freeze happened, a dllshost.exe instance was initiated with a RTSS server footprint. It's in one of the reports on the Google Drive. My guess is that ordinarily that process would come and go so quickly that it wouldn't be noticed. But when the network was blocked, it was hung, waiting for network access to resume. It also looks like under some conditions that process is doing some sort of exclusive send, as the receive traffic drops off when this happens.

Is there a way of getting more help on this from Microsoft? In all the searching both you and I have done we haven't seen anything that explains this behavior so it must be very rare. It might require doing a network or system trace. Anyway - looking for ideas. Thanks.

Keep me posted.