Sound Video And Game Controllers Drivers Windows 10
Double-click on Sound, video, and game controllers; Locate and double-click the driver that is causing the error; Click the Driver tab; Click Uninstall; Insert the Driver disc, and then follow the screen instructions to install the driver; 2. Download Audio Drivers – Automatic Audio Driver Updates. Oct 15, 2020 Hit Windows key + R key to open the Run dialog box and type the command – “ devmgmt.msc. This will take you directly to the Device Manager window where you can double click on the “ Sound, video, game controllers ” section to expand it and see the list of pre-existing audio drivers.
- Sound Video And Game Controllers Drivers Windows 10 Update
- Sound Video And Game Controllers Drivers Windows 10 64
- Sound Video And Game Controllers Drivers Windows 10
A Multimedia Audio Controller Driver enables your Operating System (Windows 10, Windows 8, Windows 7, Windows XP, Vista) to communicate with your audio output devices (Speakers, microphones, headphones etc.). The quality of recent Realtek sound controller and audio drivers has taken a nosedive in recent years, and the automatically installed drivers on Windows 10 have introduced a significant delay in the time it takes for sound to come out of the speakers after it is initiated by the PC.
-->See a list of known issues that have been resolved for Windows 10, version 20H2 and Windows Server, version 20H2 over the last six months. Looking for a specific issue? Press CTRL + F (or Command + F if you are using a Mac) and enter your search term(s) to search the page.
Sound Video And Game Controllers Drivers Windows 10 Update
Resolved issues
| Summary | Originating update | Status | Date resolved |
|---|---|---|---|
| Apps might fail to open, close unexpectedly or become unresponsive Devices using Microsoft Exploit Protection Export Address Filtering (EAF) might have issues with some apps. | OS Build 19042.1202 KB5005101 2021-09-01 | Resolved | 2021-09-29 14:51 PT |
| Administrator credentials required every time apps attempt to print Certain printers in some environments using Point and Print might prompt for credentials every time when printing. | OS Build 19042.1165 KB5005033 2021-08-10 | Resolved External | 2021-09-16 18:23 PT |
| Automatic input of Furigana might not work as expected In certain circumstances, the automatic Furigana input/conversion feature may not work as expected in apps. | N/A | Resolved KB5005101 | 2021-09-01 14:00 PT |
| Printing and scanning might fail when these devices use smart-card authentication Non-compliant printers, scanners, and multifunction devices might fail to print when using smart-card authentication. | OS Build 19042.1110 KB5004237 2021-07-13 | Resolved | 2021-08-03 10:36 PT |
| Certain printers unable to print Most affected printers are receipt or label printers that connect via USB. | OS Build 19042.1081 KB5003690 2021-06-21 | Resolved KB5004237 | 2021-07-13 10:00 PT |
| Internet Explorer 11 and apps using the WebBrowser control might fail to open PDFs The 64-bit versions of IE11 and apps using the 64-bit version of the WebBrowser control might show PDFs as just gray. | OS Build 19042.1052 KB5003637 2021-06-08 | Resolved KB5004760 | 2021-06-29 10:00 PT |
| A high-pitched noise might be heard when using 5.1 audio with certain settings Certain combinations of apps, audio devices and Windows settings might produce a high-pitched noise when using 5.1 audio | OS Build 19042.906 KB5000842 2021-03-29 | Resolved KB5003690 | 2021-06-21 14:00 PT |
| News and interests button on the Windows taskbar might have blurry text Certain display configurations might cause blurry text on the news and interests button in the Windows taskbar. | OS Build 19042.964 KB5001391 2021-04-28 | Resolved KB5003690 | 2021-06-21 14:00 PT |
| Apps might have issues accessing event logs on remote devices Event logs might not be accessible from remote devices unless both devices have updates released June 8, 2021 or later. | OS Build 19042.10000 KB5003637 2021-06-08 | Resolved KB5003637 | 2021-06-08 10:00 PT |
| Security updates released May 11, 2021 might not offer in managed environments Windows Server Update Services (WSUS) or Microsoft Endpoint Configuration Manager and managed devices are affected. | OS Build 19042.985 KB5003173 2021-05-11 | Resolved | 2021-05-11 19:01 PT |
| Errors or issues during or after updating devices with certain Conexant audio drivers Devices with affected Conexant or Synaptics audio drivers might receive a stop error with a blue screen. | N/A | Resolved | 2021-05-07 13:29 PT |
| Errors or issues during or after updating devices with Conexant ISST audio drivers Devices with affected Conexant ISST audio drivers might receive an error or have issues with Windows 10, version 2004. | N/A | Resolved | 2021-05-07 13:29 PT |
| Lower than expected performance in games Some users have reported lower game performance in full screen or borderless windowed mode when using multiple monitors. | OS Build 19042.906 KB5000842 2021-03-29 | Resolved | 2021-04-27 15:48 PT |
Issue details
September 2021
Apps might fail to open, close unexpectedly or become unresponsive | ||
| Status | Originating update | History |
| Resolved | OS Build 19042.1202 KB5005101 2021-09-01 | Resolved: 2021-09-29, 14:51 PT Opened: 2021-09-24, 11:00 PT |
After installing KB5005101 or a later update on devices using Microsoft Exploit Protection Export Address Filtering (EAF), you might have issues with some applications. You might be experiencing this issue if apps fail to open, fail to open files, or you might receive a white window when attempting to login. Affected platforms:
Resolution: This issue is resolved using Known Issue Rollback (KIR). Please note that it might take up to 24 hours for the resolution to propagate automatically to consumer devices and non-managed business devices. Restarting your Windows device might help the resolution apply to your device faster. For enterprise-managed devices that have installed an affected update and encountered this issue, it can be resolved by installing and configuring a special Group Policy (preferred) or setting a registry key according to the version of Windows you are using. Important Verify that you are using the correct Group Policy or registry key for your version of Windows. Group Policy (preferred): For help, please see How to use Group Policy to deploy a Known Issue Rollback. For general information on using Group Policies, see Group Policy Overview. Note Devices need to be restarted after configuring the special Group Policy or adding the registry key. Registry Key: 1, Open a Command Prompt window (cmd.exe) with elevated permissions. 2, Type the following command depending on which Windows version you are using and then press Enter. 3, All version of Windows require a restart of the device for the registry key to take effect. Before restarting Windows 10, version 1909, Windows 10, version 1809 and Windows Server 2019, you will need to also run following command from elevated PowerShell prompt: | ||
Administrator credentials required every time apps attempt to print | ||
| Status | Originating update | History |
| Resolved External | OS Build 19042.1165 KB5005033 2021-08-10 | Last updated: 2021-09-16, 18:23 PT Opened: 2021-09-16, 18:11 PT |
After installing KB5005033 or a later update, certain printers in some environments using Point and Print might receive a prompt saying, 'Do you trust this printer' and requiring administrator credentials to install every time an app attempts to print to a print server or a print client connects to a print server. This is caused by a print driver on the print client and the print server using the same filename, but the server has a newer version of the file. When the print client connects to the print server, it finds a newer driver file and is prompted to update the drivers on the print client, but the file in the package it is offered for installation does not include the later file version. Workaround: Verify that you are using the latest drivers for all your printing devices and where possible, use the same version of the print driver on the print client and print server. Affected platforms:
Resolution: This issue is resolved externally by adjusting the print drivers in your environment. If updating drivers in your environment does not resolve the issue, please contact support for your printer manufacturer (OEM). For more information, see the Q1/A1 in the 'Frequently asked questions' section of KB5005652. | ||
July 2021
Printing and scanning might fail when these devices use smart-card authentication | ||
| Status | Originating update | History |
| Resolved | OS Build 19042.1110 KB5004237 2021-07-13 | Resolved: 2021-08-03, 10:36 PT Opened: 2021-07-23, 14:36 PT |
After installing updates released July 13, 2021 on domain controllers (DCs) in your environment, printers, scanners, and multifunction devices which are not compliant with section 3.2.1 of RFC 4556 spec, might fail to print when using smart-card (PIV) authentication. Affected platforms:
Next steps: A temporary mitigation is now available. For more information, please see KB5005408 - Smart-card authentication might cause print and scan failures. | ||
Sound Video And Game Controllers Drivers Windows 10 64
Certain printers unable to print | ||
| Status | Originating update | History |
| Resolved KB5004237 | OS Build 19042.1081 KB5003690 2021-06-21 | Resolved: 2021-07-13, 10:00 PT Opened: 2021-07-08, 16:40 PT |
After installing KB5003690 or later updates (including out of band updates, KB5004760 and KB5004945), you might have issues printing to certain printers. Various brands and models are affected, primarily receipt or label printers that connect via USB. Note This issue is not related to CVE-2021-34527 or CVE-2021-1675. Affected platforms:
Resolution: This issue was resolved in KB5004237, released July 13, 2021. If you are using an update released before July 13, 2021, you can resolve this issue using Known Issue Rollback (KIR). Please note that it might take up to 24 hours for the resolution to propagate automatically to consumer devices and non-managed business devices. Restarting your Windows device might help the resolution apply to your device faster. For enterprise-managed devices that have installed an affected update and encountered this issue, it can be resolved by installing and configuring a special Group Policy. Note Devices need to be restarted after configuring the special Group Policy. For help, please see How to use Group Policy to deploy a Known Issue Rollback. For general information on using Group Policies, see Group Policy Overview. Important If you install an update released July 13, 2021 ( KB5004237) or later, you do not need to use a Known Issue Rollback (KIR) or a special Group Policy to resolve this issue. | ||
June 2021
Internet Explorer 11 and apps using the WebBrowser control might fail to open PDFs | ||
| Status | Originating update | History |
| Resolved KB5004760 | OS Build 19042.1052 KB5003637 2021-06-08 | Resolved: 2021-06-29, 10:00 PT Opened: 2021-06-25, 12:53 PT |
After installing KB5003637 or later updates, Internet Explorer 11 (IE11) or apps using the 64-bit version of the WebBrowser control might fail to open PDFs or may render as just a gray background using the Adobe Acrobat plug-in. Note Internet Explorer is only affected if Enable 64-bit Processes for Enhanced Protected Mode is enabled in the Advanced tab in Internet Options. Workaround: To mitigate the issue, you can use one of the following:
Resolution: This issue was resolved in the out-of-band update KB5004760. It is a cumulative update, so you do not need to apply any previous update before installing it. KB5004760 is now available on the Microsoft Update Catalog and must be manually downloaded and installed. You can import this update into Windows Server Update Services (WSUS) manually. See the Microsoft Update Catalog for instructions. Affected platforms:
| ||
News and interests button on the Windows taskbar might have blurry text | ||
| Status | Originating update | History |
| Resolved KB5003690 | OS Build 19042.964 KB5001391 2021-04-28 | Resolved: 2021-06-21, 14:00 PT Opened: 2021-06-14, 17:43 PT |
After installing KB5001391 or later updates, the news and interests button in the Windows taskbar might have blurry text on certain display configurations. Affected platforms:
Resolution: This issue was resolved in KB5003690. | ||
Apps might have issues accessing event logs on remote devices | ||
| Status | Originating update | History |
| Resolved KB5003637 | OS Build 19042.10000 KB5003637 2021-06-08 | Resolved: 2021-06-08, 10:00 PT Opened: 2021-06-07, 16:10 PT |
After installing KB5003637 or later updates, apps accessing event logs on remote devices might be unable to connect. This issue might occur if the local or remote has not yet installed updates released June 8, 2021 or later. Affected apps are using certain legacy Event Logging APIs. You might receive an error when attempting to connect, for example:
Note Event Viewer and other apps using current non-legacy APIs to access event logs should not be affected. Affected platforms:
Resolution: This is expected due to security hardening changes relating to Event Tracing for Windows (ETW) for CVE-2021-31958. This issue is resolved if the local and remote devices both have KB5003637 installed. | ||
May 2021
A high-pitched noise might be heard when using 5.1 audio with certain settings | ||
| Status | Originating update | History |
| Resolved KB5003690 | OS Build 19042.906 KB5000842 2021-03-29 | Resolved: 2021-06-21, 14:00 PT Opened: 2021-05-13, 19:35 PT |
After installing KB5000842 or later updates, 5.1 Dolby Digital audio may play containing a high-pitched noise or squeak in certain apps when using certain audio devices and Windows settings. Note This issue does not occur when stereo is used. Workaround: To mitigate this issue, you can try one or more of the following:
Affected platforms:
Resolution: This issue was resolved in KB5003690. | ||
Security updates released May 11, 2021 might not offer in managed environments | ||
| Status | Originating update | History |
| Resolved | OS Build 19042.985 KB5003173 2021-05-11 | Resolved: 2021-05-11, 19:01 PT Opened: 2021-05-11, 14:58 PT |
When checking for updates within Windows Server Update Services (WSUS) or Microsoft Endpoint Configuration Manager and managed devices that connect to these servers, KB5003173 might not be available or offered. Note: This might also affect Security Only and Internet Explorer Cumulative Rollups, on platforms that receive these types of updates. Affected platforms:
Resolution: This issue is now resolved on the service-side and updates should be available. Note: If you initiate a synchronization cycle and are still not being offered the updates, please check again soon. There might be slight delay as it propagates to all servers in all regions. | ||
April 2021
Lower than expected performance in games | ||
| Status | Originating update | History |
| Resolved | OS Build 19042.906 KB5000842 2021-03-29 | Resolved: 2021-04-27, 15:48 PT Opened: 2021-04-23, 18:04 PT |
A small subset of users have reported lower than expected performance in games after installing KB5000842 or later updates. Most users affected by this issue are running games full screen or borderless windowed modes and using two or more monitors. Affected platforms:
Resolution: This issue is resolved using Known Issue Rollback (KIR). Please note that it might take up to 24 hours for the resolution to propagate automatically to consumer devices and non-managed business devices. Restarting your device might help the resolution apply to your device faster. For enterprise-managed devices that have installed an affected update and encountered this issue, it can be resolved by installing and configuring a special Group Policy. Note Devices need to be restarted after configuring the special Group Policy. For help, please see How to use Group Policy to deploy a Known Issue Rollback. For general information on using Group Policies, see Group Policy Overview. | ||
Sound Video And Game Controllers Drivers Windows 10
December 2020
Automatic input of Furigana might not work as expected | ||
| Status | Originating update | History |
| Resolved KB5005101 | N/A | Resolved: 2021-09-01, 14:00 PT Opened: 2020-12-03, 12:29 PT |
When using the Microsoft Japanese Input Method Editor (IME) to enter Kanji characters in an app that automatically allow the input of Furigana characters, you might not get the correct Furigana characters and might need to enter them manually. Note for developers: Affected apps are using the ImmGetCompositionString function. Workaround: To mitigate this issue, please follow the instructions in Revert to a previous version of an IME (Input Method Editor). Affected platforms:
Resolution: This issue was resolved in KB5005101. If you have used the above mitigation, you will need to change your IME back to the latest version of Microsoft Japanese IME. | ||
May 2020
Errors or issues during or after updating devices with certain Conexant audio drivers | ||
| Status | Originating update | History |
| Resolved | N/A | Resolved: 2021-05-07, 13:29 PT Opened: 2020-05-27, 00:20 PT |
Synaptics and Microsoft have found incompatibility issues with certain versions of drivers for Conexant or Synaptics audio devices and Windows 10, version 2004 (the Windows 10 May 2020 Update). Windows 10 devices with affected Conexant or Synaptics audio drivers might receive a stop error with a blue screen during or after updating to Windows 10, version 2004. The affected driver will be named Conexant HDAudio Driver under Sound, video and game controllers in Device Manager and have versions 8.65.47.53, 8.65.56.51, or 8.66.0.0 through 8.66.89.00 for chdrt64.sys or chdrt32.sys. To safeguard your update experience, we have applied a compatibility hold on Windows 10 devices with affected Conexant or Synaptics audio drivers installed from being offered Windows 10, version 2004 or Windows Server, version 2004 until the driver has been updated. If your organization is using Update Compliance, the safeguard IDs are 25702617, 25702660, 25702662, and 25702673. Affected platforms:
Resolution: The safeguard hold with safeguard IDs 25702617, 25702660, 25702662, and 25702673 has been removed for all devices as of May 7, 2021, including devices with affected drivers. If updated drivers are not available for your device and you are offered Windows 10, version 2004 or Windows 10, version 20H2, a small number of devices might roll back to the previous version of Windows 10 when attempting to update. If this occurs, you should attempt to update to Windows 10, version 2004 or Windows 10, version 20H2 again. Please note, if there are no other safeguards that affect your device, it can take up to 48 hours before the update to a later version of Windows 10 is offered. | ||
Errors or issues during or after updating devices with Conexant ISST audio drivers | ||
| Status | Originating update | History |
| Resolved | N/A | Resolved: 2021-05-07, 13:29 PT Opened: 2020-05-27, 00:22 PT |
Synaptics and Microsoft have found incompatibility issues with certain versions of drivers for Conexant ISST audio driver and Windows 10, version 2004 (the Windows 10 May 2020 Update). Windows 10 devices with affected Conexant ISST audio driver might receive an error or experience issues while installing the update or after the device has updated. The affected driver will be named Conexant ISST Audio or Conexant HDAudio Driver under Sound, video and game controllers in Device Manager and have file name uci64a96.dll through uci64a231.dll and a file version of 7.231.3.0 or lower. To safeguard your update experience, we have applied a compatibility hold on Windows 10 devices with affected Conexant or Synaptics audio drivers installed from being offered Windows 10, version 2004 or Windows Server, version 2004 until the driver has been updated. If your organization is using Update Compliance, the safeguard ID is 25178825. Affected platforms:
Resolution: The safeguard hold with safeguard ID 25178825 has been removed for all devices as of May 7, 2021, including devices with affected drivers. If updated drivers are not available for your device and you are offered Windows 10, version 2004 or Windows 10, version 20H2, a small number of devices might roll back to the previous version of Windows 10 when attempting to update. If this occurs, you should attempt to update to Windows 10, version 2004 or Windows 10, version 20H2 again. Please note, if there are no other safeguards that affect your device, it can take up to 48 hours before the update to a later version of Windows 10 is offered. | ||