Skip to content

Commit e9d5bdf

Browse files
committed
Acrolinx fixes
1 parent 474a956 commit e9d5bdf

1 file changed

Lines changed: 5 additions & 5 deletions

File tree

support/windows-client/setup-upgrade-and-drivers/usb-audio-video-devices-malfunction.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
title: USB-connected Audio or Video Devices Experience Glitches when Connected to Specific Intel-based Devices
3-
description: Apply a registry fix to resolve USB audio/video issues on Intel 500/600/700 PCH systems with discrete TPM.
3+
description: Describes how to apply an update and a registry fix to resolve USB audio/video issues on Intel 500/600/700 PCH systems that use discrete TPM chips.
44
ms.service: windows-client
55
ms.topic: troubleshooting-general
66
ms.date: 10/02/2025
@@ -24,11 +24,11 @@ You might observer one or more of the following symptoms:
2424

2525
## Affected devices
2626

27-
This issue affects Intel-based system using a 500, 600, or 700 series Platform Controller Hubs that have discrete TPM chips (dTPMs). Computers that use firmware TPM technology aren't affected.
27+
This issue affects Intel-based system using a 500, 600, or 700 series Platform Controller Hubs that have discrete Trusted Platform Module (dTPMs) chips. Computers that use firmware TPM (fTPM) technology aren't affected.
2828

2929
## Workarounds
3030

31-
The following steps might resolve the issue. This relief might be temporary.
31+
You might temporarily resolve the issue by following these steps.
3232

3333
1. Unplug the device, and then reattach it to the computer.
3434
2. If the previous step doesn't work, restart the computer.
@@ -47,7 +47,7 @@ The October 2025 update for Windows 24H2 introduces a fix for this hardware issu
4747

4848
1. Confirm that the device uses a dTPM instead of an fTPM. To find this information, you might have to check the device's BIOS settings or contact the device manufacturer.
4949

50-
1. Run the diagnostic script that's provided in the [More information](#more-information) section of this article.
50+
1. Run the diagnostic script in the [More information](#more-information) section of this article.
5151

5252
This script checks whether the fix applies to your device.
5353

@@ -66,7 +66,7 @@ The October 2025 update for Windows 24H2 introduces a fix for this hardware issu
6666

6767
## More information
6868

69-
You can use the following Windows PowerShell script to determine whether your PC has one of the controllers that might be affected. To run this script, create a file that uses a name such as **Check-USBSplitTransactionVulnerability.ps1**. Then paste the following text into the file, From a PowerShell command prompt, run the script.
69+
You can use the following Windows PowerShell script to determine whether your PC has one of the controllers that might be affected. To run this script, create a file that uses a name such as **Check-USBSplitTransactionVulnerability.ps1**. Then paste the following text into the file. From a PowerShell command prompt, run the script.
7070

7171
> [!NOTE]
7272
> In Device Manager, the device in question appears under **System Devices**. It has a name that resembles "Intel(R) LPC Controller/eSPI Controller."

0 commit comments

Comments
 (0)