Taskbar Unresponsive when 2nd User signs in Windows 10

S

Santa8aby

Hello,


After building a new PC and installing Windows 10 via USB, the taskbar and start button just spins and is unresponsive when the 2nd user signs in. When switching back to the first user, the taskbar & start button is normal. Switching back to the 2nd signed in user, it still spins. However, if I force sign-out the 1st user via the task manager, then the start menu and all icons load immediately.


I've tried reinstalling Windows twice, but the issue reoccurs once I add the 2nd user and sign in with that account. Using the steps from


Resolves the issue, but once I reboot or sign out and in again with the 2nd user, the issue reoccurs.


Very odd, can anyone assist please?



Below is my msinfo32.


OS Name Microsoft Windows 10 Home

Version 10.0.19042 Build 19042

Other OS Description Not Available

OS Manufacturer Microsoft Corporation

System Name DESKTOP-433241K

System Manufacturer ASUS

System Model System Product Name

System Type x64-based PC

System SKU SKU

Processor AMD Ryzen 7 5800X 8-Core Processor, 3801 Mhz, 8 Core(s), 16 Logical Processor(s)

BIOS Version/Date American Megatrends Inc. 1216, 11/24/2020

SMBIOS Version 3.3

Embedded Controller Version 255.255

BIOS Mode UEFI

BaseBoard Manufacturer ASUSTeK COMPUTER INC.

BaseBoard Product ROG STRIX B550-F GAMING (WI-FI)

BaseBoard Version Rev X.0x

Platform Role Desktop

Secure Boot State Off

PCR7 Configuration Binding Not Possible

Windows Directory C:\Windows

System Directory C:\Windows\system32

Boot Device \Device\HarddiskVolume1

Locale United States

Hardware Abstraction Layer Version = "10.0.19041.488"

User Name DESKTOP-433241K\scuze

Time Zone Eastern Standard Time

Installed Physical Memory (RAM) 32.0 GB

Total Physical Memory 31.9 GB

Available Physical Memory 27.6 GB

Total Virtual Memory 36.9 GB

Available Virtual Memory 30.6 GB

Page File Space 5.00 GB

Page File C:\pagefile.sys

Kernel DMA Protection Off

Virtualization-based security Not enabled

Device Encryption Support Reasons for failed automatic device encryption: TPM is not usable, PCR7 binding is not supported, Hardware Security Test Interface failed and device is not Modern Standby, Un-allowed DMA capable bus/device(s) detected, TPM is not usable

Hyper-V - VM Monitor Mode Extensions Yes

Hyper-V - Second Level Address Translation Extensions Yes

Hyper-V - Virtualization Enabled in Firmware No

Hyper-V - Data Execution Protection Yes

Continue reading...
 
Back
Top Bottom