4 ms·
TLDR: TV connected to the same network hides task bar, graphical settings in Windows, and cause other issues. But why and how?
by deely3 2y ago
TLDR: TV connected to the same network hides task bar, graphical settings in Windows, and cause other issues.
But why and how?
- ErneX 2y agoIt’s explained on the solution link: https://learn.microsoft.com/en-us/answers/questions/1339707/help-with-figuring-out-what-is-causing-waitchain-d https://learn.microsoft.com/en-us/answers/questions/1339707/...
- itomato 2y agoTV somehow became the main display. "Huzzah!"
- DarkmSparks 2y agolooks like its a bug in windows where lots of new network display devices eventually corrupts the registry, and the TV gets a new identity on a regular basis - probably to protect the users identity.
- AshamedCaptain 2y agoAnd the guys conclude it's the TVs fault, not Windows. Sorry, flashbacks to the debates in The Old New Thing where Raymond would claim people blame Windows when it breaks broken software...
- ugjka 2y agobecause windows is buggy too
- hermanradtke 2y agoThe screenshot of https://learn.microsoft.com/en-us/answers/questions/1339707/help-with-figuring-out-what-is-causing-waitchain-d https://learn.microsoft.com/en-us/answers/questions/1339707/... says this: > The root cause is the TV generates random UUIDs for UPNP network discovery every few minutes. That means it poses as a new device. This caused windows to add it to the device list (Device Association Framework, aka DAF) as a new device. This means now 1000s of devices (which is the same device) filled the device tree causing it to enumerate forever. Thus the "deadlock". > TaskManager uses DasHost to enumerate devices for some reason, so that hangs. > Bluetooth relies on device discovery, so that also hangs, and Settings app along with it. > Network discovery in file explorer obviously also needs Device discovery, so that also hangs.