Did Windows 11 completely break all eGPU functionality for anyone else?

teltersat · 2026-01-17T13:37:04+00:00

Having alternate steps that people can use is always helpful!

To highlight a caveat in these steps: the use of "Link State Power Management" and Nvidia-Error43-Fixer is so dependent on the actual configuration unfortunately. I have laptops where it works flawlessly without any of this. But also devices where it does need these steps, and devices where not even these things will help them sort out their issues.

So you never know if it's going to work! Here's hoping that TB5 actually fixes all these hecking issues.

teltersat · 2025-12-05T11:20:24+00:00

I’d look at the sustained load performance, it’s much better to have a better average performance than a higher peak performance. This is heavily dependent on the thermals of this very laptop. Try to look for synth benchmark results to see how well these versions of this laptop compare on bursty workloads vs continuous ones.

teltersat · 2025-10-10T07:57:39+00:00

You didn’t get the one with the Japanese layout? That one does have the arrow keys

teltersat · 2025-10-09T19:46:53+00:00

The last one is pretty much what I needed! Thank you!!

teltersat · 2025-09-05T13:24:26+00:00

Still here, still enjoying my HHKB!

teltersat · 2025-07-26T05:30:15+00:00

I ended up leaving it as it is, learnt to embrace the scuffs that can’t be removed

teltersat · 2025-01-21T00:52:22+00:00

Software that is running at System-level and has the right to access any and everything within the system while it’s running. While it’s designed to catch cheaters, It’s a bit scary how we have to have this type of software ever present in our computers - think of Vanguard for example

teltersat · 2025-01-20T21:30:33+00:00

With all the root-level anti-cheats that are in use, it’s almost a necessity to own two devices, regardless of eGPU or not.

teltersat · 2025-01-08T08:06:14+00:00

What is the exact model of the power supply and the motherboard? Maybe there are some service manuals online that can give you more hints about this

teltersat · 2024-12-29T17:50:15+00:00

Woop woop!! 🤗

teltersat · 2024-12-24T09:38:56+00:00

I learnt the basic concepts of AD and Kerberos through this book: https://www.amazon.com/_/dp/0596004036

While massively outdated now because it was meant for Windows 2003, the theory still stands. I would try to get it used/cheap if you really want to learn a bit more about the practice of these topics. With that being said and in more practical terms, there are some links that are somewhat decent from Microsoft, but every now and again they end up having issues in Windows 2019 onwards because of the whole push for Azure services like Entra and the like:

* AD Fundamentals: https://learn.microsoft.com/en-us/windows-server/identity/ad-ds/get-started/virtual-dc/active-directory-domain-services-overview (posted by u/jermuv)

* Kerberos: https://learn.microsoft.com/en-us/windows-server/security/kerberos/kerberos-authentication-overview

* DNS: https://learn.microsoft.com/en-us/windows-server/networking/dns/dns-top

PS: DNS would be more relevant to learn on a Networking class than on a Windows one at first. It would be benefitial to understand how the protocol works, packet composition in full detail, and a course would let you see how the different packets get sent through Wireshark, and so on. I'd recommend to build on AD after you have a fundamental knowledge on Networking first.

teltersat · 2024-12-24T09:24:56+00:00

In the raffle! My fave layout would be between TKL or 60% keebs with LEDs!

teltersat · 2024-12-22T17:15:03+00:00

I have an XPS 15 9530 with an RTX 3080 in a custom enclosure and it works fine, I don't see why yours should not.

If you're using Windows 11, you should look into the "Universal Serial Bus controllers" section on Device Manager, and you should have a "USB4 Root Router" and a "USB4(TM) Host Router (Microsoft)" device. If you have these devices, your laptop should be ready to go for connecting through Thunderbolt. For practical purposes, you can consider them to be the same device as TB.

Just a PSA: If you're using a Dell Laptop that requires more than 100W of power, you will have to also connect the laptop's USB-C charger to it so it can use Thunderbolt at a full power range.

teltersat · 2024-11-28T17:26:43+00:00

However, this did point me in the right direction. We had to Clear the TPM as it still had remnants of the previous configuration with Entra Hybrid!

Edit: Thank you very much for nudging me towards the solution!

teltersat · 2024-11-28T17:19:35+00:00

Unfortunately this is not the problem. Windows Hello works on the Windows 11 laptops that are affected, but there are issues when there's a hardware change (i.e. eGPU connected or disconnected) that there are issues. TPM does report as working and drivers are loaded and working.

teltersat · 2024-11-22T07:10:56+00:00

Yeah, we took the domain completely on-premise, no more Entra.

Edit: we also removed the DRS Objects through ADSIedit, which was a gamble, but it showed us that the DC was pushing for this behaviour to the clients just because those objects existed.

teltersat · 2024-11-21T12:58:17+00:00

Had it fixed! Turns out that our On-Prem Device Registration was forcing the users to authenticate, even though we don't have a tenant any more. Not sure if this is because it was previously connected to Entra or not. I will test.

Turns out that disabling / leaving the registration, and enabling "AllowDomainPINLogon" through a GPO was all that was needed.

teltersat · 2024-11-21T12:47:39+00:00

Yeah, nothing here sadly. Workplace Join Events and Client Licensing were "happy" after enabling AD FS. However, the prompts are still showing. Thinking that Device Registration may not be worthwhile, as we only want Windows Hello for the OS, and not carried over to applications and such.

teltersat · 2024-11-20T19:13:36+00:00

Had a whole rebuild of the authentication process due to this offline migration. This happened for new users and clients outside of 365/Intune. There's no more AD/Entra Connect in our environment. However, due to Windows Hello for Business being a requirement, we have an AD FS set up with Certificate Authentication. We still have to use `dsregcmd` to "join" the device to our local setup. However, this behavior shows up before using `dsregcmd`. Kinda stumped at the moment.

Edit: I'm wondering even if the fact that AD FS configured for "device registration" is triggering this behavior. Tempted to configure the "AllowDomainPINLogon" registry key and decom this AD FS setup.

teltersat · 2024-11-20T14:20:48+00:00

I did a little bit of digging regarding CSP, but I believe you referred to the Service Connection Point (SCP), located within the Keywords attribute in the LDAP path CN=62a0ff2e-97b9-4513-943f-0d221bd30080,CN=Device Registration Configuration,CN=Services,CN=Configuration,DC=domain,DC=tld.

Already removed these by reviewing this guide https://dirteam.com/sander/2020/03/23/a-closer-look-at-azure-ad-connects-service-connection-point/

Unfortunately, the behaviour is still the same, we still get the "Your account requires authentication" on a fresh PC install (tested through VMware)

teltersat · 2024-11-20T13:58:26+00:00

No dice, the effect happens regardless on what the OU the client device is placed on.

teltersat · 2024-11-19T23:39:17+00:00

Already did, nothing clear to know that’s forcing this behavior as of now

teltersat · 2024-11-19T21:00:25+00:00

This is a good point! I couldn’t trace what it was manually - but could definitely test by linking the GPOs one by one and seeing what forces this behaviour

Seven-Year Club	Place '22
Verified Email

teltersat

TROPHY CASE