Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

USB-C Thunderbolt Port no longer reading devices #60

Closed
mostdcoa opened this issue Jun 7, 2023 · 4 comments
Closed

USB-C Thunderbolt Port no longer reading devices #60

mostdcoa opened this issue Jun 7, 2023 · 4 comments
Assignees
Labels
bug Something isn't working documentation Improvements or additions to documentation

Comments

@mostdcoa
Copy link

mostdcoa commented Jun 7, 2023

Describe the bug
Thunderbolt USB-C Port no longer recognizes devices on Dell Latitude 7490. Port still has power, but will not recognize connected devices such as USB-C removeable media, yubikeys, or cellular devices.

To Reproduce
Steps to reproduce the behavior:

  1. run the sos-optimize-windows.ps1 script
  2. usb-c devices are no longer recognized. Devices can still be charged with the port such as a cell phone
  3. Device Manager shows Detection Verification and PCI to PCI Bridge driver erros and that the driver cannot be installed due to forbidden by system policy.

Expected behavior
USB-C Port should function as normal

Screenshots
image

image

Desktop (please complete the following information):

  • OS: Windows 11 Enterprise
  • Browser: N/A
  • Version: 22

Additional context
Not sure if this is a DMA Protection or Autrun Issue. This policy was changed for the NSA policies but reverting these options didn't change anything.
image

@github-actions
Copy link

github-actions bot commented Jun 7, 2023

Message that will be displayed on users' first issue

@simeononsecurity
Copy link
Owner

simeononsecurity commented Jun 8, 2023

Great documentation of the issue!

This is an intended configuration. Thunderbolt comes with vulnerabilities.
https://www.tenable.com/audits/items/CIS_MS_Windows_8.1_v2.4.0_Level_2_Bitlocker.audit:e4e937538159f22fa3a4e5bfe4a84e51

Usually undoing the GPOs applied won't undo the setting. You'll have to reenable it manually. By specifically setting the enabled value to true and removing or changing the device id's in there.

For instance on the target machine you want to fix you can open the local group policy editor

navigate to the following path

Computer Configuration\Policies\Administrative Templates\System\Device Installation\Device Installation Restrictions

there should be two policies enabled there, leave them both enabled but open them up and remove the values stored in them. If they error out complaining there must be a value, replace the line with a bunch of random numbers. Be sure to keep any special chars in there. Reboot and hopefully that fixes it for you..

You can try this to remove the specific device id's however

# Remove the device ID from the list of restricted device IDs
$deviceID = "PCI\CC_0C0A"
$existingDeviceIDs = (Get-ItemProperty -Path "HKLM:\SOFTWARE\Policies\Microsoft\Windows\DeviceInstall\Restrictions").DeviceIDRestrictions
$updatedDeviceIDs = $existingDeviceIDs -notlike "*$deviceID*"
Set-ItemProperty -Path "HKLM:\SOFTWARE\Policies\Microsoft\Windows\DeviceInstall\Restrictions" -Name DeviceIDRestrictions -Value $updatedDeviceIDs

# Set the DenyDeviceIDsExist value to 1 to enable device installation restrictions
Set-ItemProperty -Path "HKLM:\SOFTWARE\Policies\Microsoft\Windows\DeviceInstall\Restrictions" -Name DenyDeviceIDsExist -Value 1

# Display the updated device ID restrictions
$updatedDeviceIDs

@simeononsecurity simeononsecurity pinned this issue Jun 8, 2023
@simeononsecurity simeononsecurity self-assigned this Jun 8, 2023
@simeononsecurity simeononsecurity added bug Something isn't working documentation Improvements or additions to documentation labels Jun 8, 2023
@mostdcoa
Copy link
Author

mostdcoa commented Jun 8, 2023

Thanks, I was able to change the values for those two policies with random strings using the same format:
{0000e-123-1234-1234-000000}
and
PCI\00

Upon restart I was able to use the thunderbolt port.

I appreciate the quick response and your work on this project.

@mostdcoa mostdcoa closed this as completed Jun 8, 2023
@simeononsecurity
Copy link
Owner

simeononsecurity commented Jun 8, 2023

Thanks, I was able to change the values for those two policies with random strings using the same format: {0000e-123-1234-1234-000000} and PCI\00

Upon restart I was able to use the thunderbolt port.

I appreciate the quick response and your work on this project.

Glad it was resolved for you. I'll add this to the list of possible concerns in the readme.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

2 participants