Audio issue after upgrading to Windows 10, Version 1809

Well that's something, if that's true than I'd assume it has to be a driver issue... I'll have to see if I can dig up a computer without the Realtek chip around here and see what results I get.

Just to verify the test. You are running Windows 10 - update 1809 - (I haven't mentioned it before but I'm using Windows Pro.) and to test, you put the computer to sleep which also locked your computer, and before logging back in you clicked the Ease of Access Icon on the lock screen, which played the audio as expected.

If this is all correct, do you happen to know what audio chip/board your computers are using and what drivers windows is using for them?

Thanks for all your help!

Okay, that still is good information.

Thanks

Same problem here after win10 1809 realtek hd audio mute with fast startup enabled.
disabled fast startup as workaround ... running driver 6.0.1.8258 17/09/19
lenovo T460

For anyone out there that is seeing this issue, we ended up sending Microsoft a computer having this issue and they say that they have created a fix for it, that is at least going to be in the next major release of Windows 10, but they might put it out a a fix sooner, supposedly it's in the testing stage, but my contact says they still don't have any kind of an ETA.
Early on they said "So far we've determined that the events our code is dependent on to determine if system has resumed and console is unlocked are not getting fired when the Assigned Access user auto-logons." They had to get a few different departments involved to get a fix, so evidently it's not a simple fix.
At this point I'm starting to wonder if the 1903 version just might get out before the fix, but we'll see. If anyone has a workaround short of never letting the computer sleep I'd be interested in hearing it.

It seems on my Lenovo thinkpad T460 the problem is solved after some quality updates from windows update, In my case I am using Azure and fingerprint to login, and to have audio i discovered it was enough to lock/unlock the screen after the boot. But now problem seems gone , don’t know if they pushed the fix you mentioned... but something changed for sure with latest updates