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: Most helpful
  1. Anonymous
    2022-10-18T17:06:40+00:00

    Ok I followed the instructions exactly as provided in the link above and the problem persists. So there's something difference between the Clean Boot with everything disabled and the Diagnostic boot with only basic services and startup apps. With the first the problem persists, the second it goes away. This indicates that the process that is responsible is a Microsoft service or app that's part of the core of Windows. I verified that all third party processes were disabled.

    I'm wondering if the Process Explorer avenue would help.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2022-10-18T16:11:37+00:00

    Ok I will do this. I have a question about that before I start . If I’ve done the msconfig Diagnostic boot with only basic MS services and startup apps and that eliminated the problem, I would think I would have eliminated my installed third party startup apps as the culprit and that it must be an MS process.. But maybe there’s a difference with the Clean Boot technique I’m not seeing. I will do it anyway but just wanting to know what the difference is aside from hiding the MS services.

    Also did you see anything interesting in the Process Explorer information I provided? I’m only asking because Auggie was headed down that path of identifying what process gets kicked every 73 seconds.

    Thanks again for sticking with this. It’s driving me crazy!!

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2022-10-18T15:52:45+00:00

    Brian, Establish a Clean Boot to get rid of Startup freeloaders that can hog resources and cause issues by conflicting:

    https://www.makeuseof.com/clean-boot-windows-11/

    In msconfig itself, on Services tab, check the box to Hide all MS Services (VERY IMPORTANT!) and then post back a screenshot of what's still checked.

    Do the same in Settings > Apps > Startups and Task Manager > Startups.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2022-10-18T08:33:31+00:00

    I tried a different troubleshooting technique. I used msconfig to boot in Diagnostic mode with only basic services and startup apps started. The system ran fine - no hiccups. I reset the Ethernet adaptor and rebooted sand everything was still good. Then I rebooted normally and the problem reappeared. So it's some service/process that isn't part of the basic stuff.

    There are probably several hundred processes on this machine. How do I troubleshoot? The startup programs apparently are not the issue.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2022-10-18T06:26:41+00:00

    Ok - remember that this problem started in Windows 10 and persisted through the Windows 11 upgrade, so a repair immediately after I did an upgrade a few days ago doesn't seem warranted.

    I completed all the steps above, which were primarily aimed at viruses or other malware or other system integrity issues. I have Acronis Cyber Security installed, Windows Defender and now Malwarebytes and none of those have detected anything including the Malwarebytes scan I just ran. I also verified that the dllhost.exe executable was in the proper place, and none of the many many websites about COM Surrogate have mentioned symptoms like I have. Auggie was on track of something with the Process Explorer data for the process which initiates during the graphics freeze, dllhost.exe. I provided the data but after he had left the thread. Over the last couple of days I've taken a lot of time to capture Process Explorer data during the time of the graphics freeze. So I would appreciate it if you could take a look closely at my last few entries in the other thread and also take a look at the PE data I posted on the Google Drive.

    You said we must continue in this thread, but all my information is in the other thread. Do I have to copy and paste or how does this work?

    Thanks!

    Was this answer helpful?

    0 comments No comments