Windows 10 KB4598291 broke Discord screen share with audio
3 min. read
Updated on
Share this article
Improve this guide
Read our disclosure page to find out how can you help Windows Report sustain the editorial team Read more
Key notes
- After installing optional update KB4598291, Discord screen share with audio stopped working for many users.
- No matter the troubleshooting steps they tried, gamers still experienced Discord audio not working.
- So it seems that while KB4598291 brought many important fixes, it also caused other issues.
- And there is only one way to fix the Discord screen share broken audio option.
Last week, Microsoft rolled out KB4598291, an optional cumulative system update that contained lots of fixes for browser-use and games.
However, it seems that while the update did correct frequent crashes, it also brought along other issues, which users have rapidly shared on dedicated forums.
Discord users, for instance, encountered problems with their audio while sharing their screen or while using the platform.
I updated Windows. I would consistently get Sorry we couldn’t access… – UAC also would not always pop up. Even when it did though, it didn’t matter.
It took just one user to voice out the issue on the forum, that others followed.
How to keep Discord running without problems?
Discord is now the only free messaging tool that keeps you connected to all your gaming communication channels. To be safe from getting connection, server or simply login errors, you could use Opera GX, the only gaming browser with Discord integration and optimization.
Opera GX keeps you logged in, so you won’t have any authentication issues. Moreover, if you do, you may always change access servers by using Opera’s free built-in VPN feature. Last, but not least, you can choose how many resources shall each tab consume so you could have all PC’s power focused on your main activities like gaming, trading, editing, etc.
Opera GX
Get the best Discord experience on Opera GX starting now!How do I fix Discord audio after update crash?
One user also posted a full list of what he tried to troubleshoot audio in Discord. All his solutions are commonsensical and are general fixes that anyone would try (and that we’d also recommend) when faced with such a problem.
I’ve tried almost all the fix available on the internet but none seems to work. From adding Google Chrome to the games list under Game Activity, resetting the Voice Settings, uninstall and update the audio drivers of the system. I’ve also reinstalled Discord twice or thrice but that didn’t work too.
What others have also tried was to access the chat platform in another browser, but that didn’t work either.
So the only thing left to do to make sure that Discord works smoothly again is to actually uninstall the faulty update.
How do I uninstall an optional update?
- Type update in the home screen search field.
- In the Settings’ Update & Security section go to View update history.
- Click on Uninstall updates.
- Choose the update corresponding to KB4598291, right-click on it and Uninstall.
The procedure is the same if you want to uninstall any other cumulative update that is causing issues with one or more apps or processes.
What issues did KB4598291 fix?
KB4598291 was launched as an optional update, meaning that it wasn’t immediately pushed onto Windows 10 systems and that users could actually choose whether they want to install it or not.
And yet, many users supposedly were interested in the many fixes it contained:
- Ctrl+Caps Lock and Alt+Caps Lock key combination for some regions
- Freeze when playing games in tablet mode or in full-screen.
- Faulty process when extracting online-only ZIP files
- Blank lock screen after a device wakes up from Hibernate
- Duplicate cloud provider folders in the File Explorer
- Incorrect deactivation of some Windows 10 Education devices after upgrading to Windows 10, version 2004
- Issue with Start menu, Cortana, and tiles pinned to the Taskbar
So reverting KB4598291 to fix Discord will most likely also cause some of these bugs to reappear (in case you also experienced them). But at this point, this is the only fix, until the next Patch Tuesday updates.
