This is a myth. UI has nothing to do with backwards compatibility. If they could do it in W7, they can definitely do it now. Also remember that the issues showcased with the images came with W8 and W10. Backwards compatibility would break if they somehow changed registry format, not if they change the explorer shell, upon which many different changes have already been made that renders many program unusable. For example a explorer patcher, gave proper dark theme in W7. When I tried to use that file on W8, it did not work, explorer crashed at boot and I had to run SysRestore. So, its a myth that MS changes Windows UI, keeping backwards compatibility in mind. In the current scenario, MS can't fix it because its a mess and the team that fixes the UI prefers a redo than improving what already exists.
If I left my system on for a long time in hibernate the cursor behaved erratic. I believe it's a bug in this Build.
Thank god we can do that, easily using XMouseButton and emulating shift + F10. I Shift + F10 that thanks to an info buried in their explanation of the new UI
With the latest build I have this Microsoft Teams Preview running on startup. When I try to log in using my private Microsoft Account, my own Microsoft 365 account or my company Microsoft 365 account (this is the one I use for Microsoft Teams) all of them are showing: Is this to be expected? Does this new preview feature that integrates directly with Windows 11 require some special flag enabled on Microsoft 365 to work?
its needs to be configured and i think theres on demand download from there server. Mine worked after a few mins. 365 isnt needed
Hmm, updated to the .100 build (using WU) and got an error message about not being able to find Edge. Anyone else seen this? Edge is working btw. Edit: it appears to be associated with an Event Viewer message saying Faulting application name: msteams.exe Edit2: it seems this happens after every reboot. Msteams.exe loads in the background and closes with a fault when the error dialog is closed.
defrag and optimize wont open. oh wait it does but its extremely slow at openening and clciking advanced takes forever. it could possibly be my fault as i have to take a disk offline to create a system image as windows decides to back up the game drive too. Maybe work properly after a reboot
.100 cu files are still called Windows 10: windows10.0-kb5004300-x64.cab windows10.0-kb5004300-x64.psf windows10.0-kb5004568-x64.cab Only one that doesn't have a win10 branding is the servicing stack and it doesn't have any os branding: ssu-22000.100-x64.cab edit: Just noticed it lists the image version as 10.0.22000.1 instead of 11.0.22000.1
I think there is no way they will get something refined enough to be called RTM for September/October. The will release an half baked ISO, and the real thing will be more or less ready for October 2022. The anniversary edition.
Any idea how to manually enable Teams in the new .100 build? Any setting or group policy? Don't see the Teams icon on the taskbar yet.
They are holding back the CBS packages related to core functionality of the OS and working on them in private. The build that gets called the final end user or RTM version will have these included by default. They won't be patched in later. We'll also possibly have a new KMS version to content with. I'm not saying it's definite. Just possible. A lot of the "Under the hood" stuff is missing from this build that will be in the final version. I still haven't seen any of the DirectX stuff that was promised in 11 in this build. Perhaps I'm mistaken but I think that is also coming in a future build.