-
-
Notifications
You must be signed in to change notification settings - Fork 86
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
Comments
Message that will be displayed on users' first issue |
Great documentation of the issue! This is an intended configuration. Thunderbolt comes with vulnerabilities. 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
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 |
Thanks, I was able to change the values for those two policies with random strings using the same format: 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. |
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:
Expected behavior
USB-C Port should function as normal
Screenshots
Desktop (please complete the following information):
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.
The text was updated successfully, but these errors were encountered: