Windows 10 May 2019 update or Windows 10, Version 1903 was released for all the PC users except few user's PC, where Microsoft suspects there might be a issue if they upgrade to the latest version.
However, many users who want to try this new build has already started downloading the update manually in the form of ISO (you can download windows 10 1903 iso) and are experiencing issues like brightness not working, not being able to connect to Bluetooth,etc.
Other users has reported that after upgrading to the latest version of Windows 10 May 2019 update, audio is not working with dolby atmos headphones and speakers.
While, there is no permanent solution, available at the moment all i can say, is this is a known issue to Microsoft, and they are actively working on a fix.
Here, is What Microsoft Says,
However, many users who want to try this new build has already started downloading the update manually in the form of ISO (you can download windows 10 1903 iso) and are experiencing issues like brightness not working, not being able to connect to Bluetooth,etc.
Other users has reported that after upgrading to the latest version of Windows 10 May 2019 update, audio is not working with dolby atmos headphones and speakers.
While, there is no permanent solution, available at the moment all i can say, is this is a known issue to Microsoft, and they are actively working on a fix.
Here, is What Microsoft Says,
After updating to Windows 10, version 1903, you may experience loss of audio with Dolby Atmos for home theater (free extension) or Dolby Atmos for headphones (paid extension) acquired through the Microsoft Store due to a licensing configuration error.
This occurs due to an issue with a Microsoft Store licensing component, where license holders are not able to connect to the Dolby Access app and enable Dolby Atmos extensions.
To safeguard your update experience, we have applied protective hold on devices from being offered Windows 10, version 1903 until this issue is resolved. This configuration error will not result in loss of access for the acquired license once the problem is resolved.
We are working on a resolution for Microsoft Store and estimate a solution will be available in mid-June.So, if you are facing this issue, we request you to not update to this new build, if you had already did, then we request you to wait until a fix is available.
