Chat icon remained... But Teams integration got disabled for me in this build. Note: stopping the app from systray and relaunching fixed the problem..
Yes, and it's possible they could rework the renew pc option so that it won't remove certain updates. It's just very unlikely. This build is extremely janky and unfinished. They're tinkering with surface level stuff, not adding any of the actual operating system functionality.
I have a hypothesis that Windows Insider builds function a bit like the secondary effect of crowdfunding in that their main function isn't really to improve the operating system, or in this case to make people feel like they are ironing out issues that they really don't like about a build. I have a theory that MS knows that this is an effective way to generate user interest in the core fanbase and thus power the hype. They get to look like they're fixing issues people care about and everyone gets interested in a build. It's a win/win for MS. They could easily do all of the things they're doing without the Insider program. The access media constantly write articles about the builds and upcoming features. It's a smart business decision even though it doesn't really serve any functional purpose.
If they did include Direct Storage in this build, which I'm not sure they haven't, I could see it getting chopped and put in win10 builds much like we did with the server data dedup stuff. It would really be wise for them to hold it out for the final build and force it to be required for Win11 alone.
Possible, even likely. But keeping something internally until the last minute would expose them to undetected problems, that they have to fix with post RTM CUs, which in turn will lead to my initial point of having a decent build only during the AD2022,...
It might not seem like it with these buggy insider builds, but they actually have an extensive testing and debugging process at MS. The things they are tinkering with, while they are causing bugs and issues, are only surface level linked to UI and newer features. I haven't read the articles thoroughly, but I've skimmed a bit on the win11 dx features and they've been working on them for quite a while. It is my understanding that you need to call the functions with the files installed. The articles also date back quite a ways, so when they were demo'ing the features, they had been working on them for quite a long time. But what does that mean for us? Well for me? Nothing. I don't have the hardware. There's also no games that I'm aware of that openly support it afaik. So they had to test it on beta software as it is. How useful it is depends on how much it helps performance I suppose. It's kinda hard to predict the desire for a thing we know little about. It could help a lot or very little. I really don't know yet. It could help sell hardware upgrades, or people could just shrug at the very slight increase in performance and not bother.
This is also another known bug they're already investigating, but if you've already registered it, it should work again without entering in the settings again.
Sure that makes sense. But still I had a bit of experience as internal quality control for a fairly mainstream project. We were like 60 testers, each one provided with diferent HW, each one with multiple boot machines and various VMs. One of the internal builds proved stable everywhere (and wasn't even a major build, just a small update), so we gave the green light for the public beta. Happened that in like 2/3% of the installations that app became completely unusable, slow, crashy, and leaded even to BSOD on some machines. The coders spent like a week of h24 work to figure what's going on given no one, either coders or internal betatester, was able to reproduce the bug. To be clear it was a plain app, not something that requires kernel drivers or alike. Finally one of the coders was lucky enough to have at home an affected machine and understood the problem. it was that a small share of Intel and AMD CPU lacked a rarely used instruction,i don't even remember what feature it was, but that was the problem. Now I can only imagine that such a strange case is a corner case on a plain app, but in a whole OS stuffed with zillion of features and kernel things, cases like this would be "the norm".
I have good news. I got in touch with Microsoft and from now on, they are only catering to you specifically for all future Windows products. Every future Windows 11 build will be directly based upon your - and only your - feedback and bug reports. I personally thought they might continue taking into account the millions of other businesses and users, but apparently your personal problems and wishes are all that matters to them now. Congrats!
That's the entire point of Win11 so far. Dramatically improve/polish UI/UX experience compared to 10, without disrupting stability, performance or compatibilty. The underline OS at launch will be a lot similar to 10 in October while a proper kernel and Core OS refresh may happen in late 2022 well...with co_refresh branch.
The point so far seem more moving another notch up the lock of the OS, with the mandatory uefi/lack of x86 buids and TPM stuff. The GUI overhaul (calling it improvement is rally too much) is more like a beet of sweetener to make the above pill easier to swallow.