Windows 10: Welcome Screen > 15 minutes

Hi, I'm a Windows 10 Pro User. Here's my specsrocessor IntelR CoreTM i5-4200U CPU @ 1.60GHz 2.30 GHz Installed RAM 12.0 GB 11.9 GB usable System type 64-bit operating system, x64-based processor Edition Windows 10 Pro Version 21H2 Installed on ‎17-‎Sep-‎21 OS build 19044.1466 Experience Windows Feature Experience Pack 120.2212.3920.0 For the last 2 weeks I noticed that Windows welcome screen has become slower and slower. First it took around 2 minutes, but now, it's > 15 minutes!! I don't use any login authentication, so it's probably not bcs of that. First I wondered if it was be

:)

 

windows 7 64 freezes after 15 minutes of inactivity

Can you suggest a fix for my Toshiba laptop with Windows 7 64? It freezes the screen after 15 minutes of inactivity/

 

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

 

Overclocking / Undervolting guide for Vega 56 or 64?

Here's a quick laundry list:

List of software to use for overclocking and testing
Examples:
Wattman (and how to find and use it, like an overview, including profiles)
Unigine Valley or Heaven (use this for quick testing while changing settings in Wattman and checking for stability / artifacts) ...just suggesting this
How to monitor cores / mem speeds and temps during testing (I've seen screen overlays, and others using GPUz)

Step-by step overclocking in Wattman
Fan speeds
Power limit
Temp limit
Voltages
Core speeds
Memory speeds