Windows 10: Windows 10 takes 15 minutes to start

You will see this problem posted all over the web on various support forums MS or not. As with most windows problems, these are the solutions you will see

run sfc/dism

disable unnecessary background processes

update drivers


It is true that you do need to use sfc/dism every few months, especially if you have had a system crash bsd.

And, yes, keep your drivers up to date, background processes trimmed.


Those things won't solve this problem and usually not most others, as important as they are.


Another solution to this problem you will see, is disable fast startup. This is on by default. Doing that also makes no difference.

I found where a user suggested that this works if you turn it back on. Not for me. This function has no affect on start up time. For me.


It seems that MS in their wisdom has decreed that MS 10 should have a 15 minute start up. Not that they or their apologists will admit that. The rest of it is, I find that even after the desktop appears after 15 minutes, Windows is still loading stuff 10 minutes or so later, slowing down any use you might want to make of your computer. Exactly how much intrusion into my affairs do you need MS? I have disable all of that stuff too that I can find. Didn't help.

:)

 

Network drivers take a long time (15+ minutes) to install

I'm running Windows 10 Pro 20H1 and I have a problem.

Any network driver that is listed under Network adaptors in Device Manager takes a very long time to get installed. This includes the Cisco AnyConnect Secure Mobility driver, TAP-Windows Adaptor V9, and ... most importantly ... various Hyper-V network drivers,
i.e. Virtual Switch, Virtual Extension, Virtual Adaptor, etc.

Examples:

1. If I grab a copy of tap-windows-9.21.2.exe and run it, the installation takes 15+ minutes, and all this time is spent waiting for Windows to configure the driver class. During this time, tap-windows-9.21.2.exe appears stuck.
   
2. If ask Device Manager's Add Hardware Wizard to install an arbitrary Network Adaptor, even Microsoft Loopback Adaptor, again, the installation takes 15+ minutes, during which the Add Hardware Wizard appears stuck.
3. If Hyper-V Manager attempts to configure a virtual adaptor, switch, extension, etc., again, the installation of the virtual device's driver takes 15+ minutes.

During this 15+ minutes, the driver appears in Device Manager with a yellow icon. The Properties window reads:

Windows is still setting up the class configuration for this device. (Code 56)

Perhaps the most obvious workaround is to suck it up and with the 15+ minutes. Sadly, no. While I might have had the patience to wait 15+ minutes, some apps, like Hyper-V Manager don't. They bail with an error message.

Steps that I have followed to troubleshoot this issue:

• Running various Windows and Microsoft Support troubleshooters
• Resetting the network configuration, both via Setting and via netcfg -d
• Uninstalling all apps that install a network adaptor and starting over from zero
• Updating Windows

 

Windows 10 Tweaks

Pressing “Windows+Pause Break” (it’s up there next to scroll lock) opens the “System” Window.

Windows 10: In the new version of Windows, Explorer has a section called Quick Access. This includes your frequent folders and recent files. Explorer defaults to opening this page when you open a new window. If you’d rather open the usual This PC, with links to your drives and library folders, follow these steps:

• Open a new Explorer window.
• Click View in the ribbon.
• Click Options.
• Under General, next to “Open File Explorer to:” choose “This PC.”
• Click OK

credit to Lifehacker.

 

N97 15 minute call limit?!?

The thing is that before I went to version 20, I have had conversations longer than 15 minutes without a problem. 20 is when this started happening. I just upgraded to 21, but not yet have the opportunity to have 15+ minute discussion. Maybe version
21's listed enhancement of "Improved call reliability" addresses this bug? Grrrr!