Simple scenario: Set a static IP address on one TB adapter on one Win 11 (doesn't matter) computer. Set static IP address on another TB adapter on another computer. Connect the TB ports between the 2 computers. The adapter on either computer will lose ability for simple ping to other computer as a result of 'bad, corrupt, whatever' Thunderbolt variable state in the EFI NVRAM. Proof: Clear the NVRAM on the affected computer and the TB Networking (just ping) capability returns
little fooch
Posted on • Updated on
Thunderbolt Adapter loses simple network ability due to EFI Variables
For further actions, you may consider blocking this person and/or reporting abuse
Latest comments (0)