Latitude

2 Bronze

Latitude 5400, no sound after May 2021 Windows update

Hey,

Issue:
I'm an IT Tech and the company I work for and we've some 5400 models. After May 2021 Windows update, there is no sound. The Sound Icon stays RED Cross (No Sound Device Installed).

Issue could have been caused by the May 2021 Windows update. My best guess is "2021-05 Cumulative Update for Windows 10 Version 1909 for x64-based Systems (KB5003169)".

Device details:
Windows Version: 1909 build: 18363, Windows 10 Enterprise
Processor: i5-8365U, RAM: 16 GB, x64 Bit 

What happens:
Device will ask for reboot and will says failed to update the windows and rolling back the update. and when user logins in to laptop Sound is missing.

Tried:
BIOS update to 10.1.1, Audio update . Re-installed Audio and created another windows login account and same issue with that too. Uninstalled the May-21 Windows update and still same issue.

Temporary workaround =

  1. Remove the USB headset from the Laptop and wait for 30 seconds and connect back to laptop.
  2. Right click on the Sound/speaker icon (bottom right corner)
  3. Click Open Sound settings
  4. Right side under, "Related Settings", click Ease of Access audio settings
  5. Right side under, "Related Settings", click Sound settings
  6. Now you should be able to see the USB headset audio device is now detected
  7. Slide the volume to test the sound and it should work.

Please not this is only a temporary workaround. A reboot will bring back the problem and same step will fix it.

What I m looking for: Is there any fix?

Replies (40)

Adding localservice to local admins fixes the problem but is obviously insecure. I think it’s because the Windows audio service relies on the localservice account which cannot do something required to start the service. Check your group policies for user rights assignment oddities. I’m still trying to figure out myself but will post any updates here. Have had a ticket open with Dell for a week but no reply. 

Please try these steps:

1. Roll back with system restore, and validate audio is working fine

2. Reboot, then run Dell Command Update or Dell Support Assist

        a. Install all drivers/bios/firmware updates suggested

3. Reboot

3. Install the windows update again, updating drivers prior resolved on one machine, but still have not found the       root cause

 

 

WIndows audio service was a red herring, I noticed on a machine that the audio service is started but the speakers/mic are still in an error state until we visit the ease of access screen, or until we add localservice to local admins. I have 600 machines blocked from picking up update 2004 until I have a fix for this

We've found a few machines which haven't picked up 2004 (still on 1909) which have the issue. The only update they've picked up is the one mentioned in the original post, "2021-05 Cumulative Update for Windows 10 Version 1909 for x64-based Systems (KB5003169)".

We've had the same problem with a number of 5400's.


What we've found that seems to work is to apply the latest BIOS to the machine, then run a system restore and jump back to before the updates were applied. Sound should be back.

 

So far (knock on wood) that's solved the issue and the update can be applied again without breaking audio.

 

But boy a fix sure would be nice wouldn't it?

2 Bronze

It appears that monthly patch that failed was causing the following registry key to break.


consolesecurity located in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations
The ConsoleSecurity shows as Zero-Length Binary Value

Import the registry key from a working machine (which is the same for all machines I believe) and this has fixed the issue for me.

2 Bronze

Todd, congratulations sir I believe you've found the final, and more appropriate solution than the net local group modification.  After seeing your post, I checked one of our affected computers, and sure enough the registry value was empty.  My assumption is the May cumulative updates corrupted this somehow and there's nothing putting it back yet.

I'm curious if you'd be willing to share how you identified this as I spent more time trying to figure it out than I care to share, and it's a bit odd for a terminal service configuration to have an impact when not using remote desktop.  However, conceptually it does lend itself towards some behavior we noticed with a few other workarounds that would break as soon as the user logged off and logged back in.

For anyone worried about copying some scary looking binary values from one computer to another, I converted the binary data to a more human readable SDDL security descriptor format.  The output from a default Windows 10 machine is below, and it looks pretty straightforward without any additional unique SIDs that you might find from domain or locally unique groups on the PC.  Importing the reg value from any other Windows 10 computer should be safe on most computers.

"O:SYG:SYD:(A;;CC;;;IU)(A;;0xf03bf;;;SY)(A;;CCSWLOSDRCWDWO;;;LS)(A;;CCLO;;;NS)(A;;0xf03bf;;;BA)(A;;CCWPCR;;;RD)S:NO_ACCESS_CONTROL"

2 Bronze

Going to give this a try and report back. If it works I will owe you 600 beers Todd - one for each affected machine!

2 Bronze

                I was waiting to see if Junes patching would also fail in some cases and break users machines here is what I know.

  • The issue only occurs with patch KB5003169
  • Not everyone is affected only users who experience the following: Patch installs but fails, and retries 2-3 times. After it is installed users have the following issues.
    • Issue #1: Have No Audio (Red X)
    • Issue #2: Users now have use Ctrl Alt Del at log on 
  • This affected multiple companies as seen here for Microsoft or here for Dell.

 

Solutions Shown Below. 

ISSUE #1. It appears that monthly patch that failed was causing the follow registry key to break.

consolesecurity located in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations

 

ToddLaRiviere_0-1627516973737.jpeg

 

 

The ConsoleSecurity shows as Zero-Length Binary Value

 

However, it should appear as

ToddLaRiviere_1-1627516973739.jpeg

 

 

Import the registry key (from known working machine, I have regkey if needed) to affected user to resolve this issue. 

 

ISSUE #2 - All users that have this issue also have another issue where they are required to use CTRL ALT DEL to log in

 

ToddLaRiviere_2-1627516973742.jpeg

 

This is related to Local Security Policy being changed

Users were changed to

ToddLaRiviere_4-1627516973749.jpeg

 

Changing this to enabled fixes it

Thank you @Todd LaRiviere
This worked for me and is more secure that the other CMD fix.

Solutions Shown Below. 

ISSUE #1. It appears that monthly patch that failed was causing the follow registry key to break.

consolesecurity located in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations

The ConsoleSecurity shows as Zero-Length Binary Value
Exported the registry key from known working machine, saved as a reg file the ran on the affected laptop to resolve this issue. 

Top Contributor
Latest Solutions