Windows 11 Lengthy Boot

Anonymous
2022-10-17T15:55:34+00:00

When I upgraded to Windows 11 recently, Windows no longer booted to the proper drive so I had to into the BIOS and select the Windows Boot Manager drive/partition. Now when it boots up in can take 45 seconds for the BIOS to start up. I assume it's looking for the boot drive, or there's something wrong with the boot drive. I think it has something to do with drive mapping.

When I go into Advanced option of WinRE, select Command line and execute a dir command for the C drive it shows my data drive. The D: drive has my Windows install. I've had a number of scary problems with my Windows 11 install so I really really don't want to touch anything unless I have expert guidance.

Thanks in advance for your help.

Windows for home | Windows 11 | Install and upgrade

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

58 answers

Sort by: Newest
  1. Anonymous
    2022-10-20T17:04:43+00:00

    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.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2022-10-20T06:14:21+00:00

    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.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2022-10-20T03:33:53+00:00

    Keep me posted.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2022-10-20T02:31:00+00:00

    Definitely will check it out.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2022-10-20T02:11:37+00:00

    It's a trending issue in Windows 11, with wifi but also ethernet. So your graph sure looks like it might apply.

    Was this answer helpful?

    0 comments No comments