Again the behavior I’m seeing is that some remote endpoints will seem to connect and operate fine, while others connect but just hang with a frozen screen, though they are accepting keyboard input. That this appears to be the reality of the situation indicates this expectation was/is on target.Īn additional note for anyone interested - I’ve found a workaround, I guess. I would “highly expect” it to work (first) and not be surprised to find little quirks (second). All that to say, this isn’t a Win3 to Win95 kind of tectonic shift.
That’s more like the feature update cadence. But this thing moved rapidly from dev to beta channel and is on track to rtm in 60-90 days, iirc. Appearance paradigm shift is meh but great opportunity for issues. I think by and large they’re using the opportunity to put a lot of side projects (wsl GUI support, fancy zones) into the main OS, raise min reqs (a big one, but something most smart monkeys comply with already) and a reworking of the store (not obvious but probably the biggest reasoning). Irritating problems, like I’ve experienced and found workarounds for, sure, but win11 is not a fundamentally different OS. Technically, why would you “highly expect” TV to not work on a Win11 beta? I’m not sure I follow your thinking there.
