fwiw for my loale (German) these labels were broken/looked wrong in 26100.560 but were fixed in 26100.712, so chances are they'll get around to it for other locals as well
Albacore was able to enable a limited version of Recall on a Snapdragon 7cx computer which lacks an NPU. He was also able to enable it on x64. Looks like Recall does not actually require an NPU. At least not for the Core features of the App.
you are not following this thread, check this thing first https://forums.mydigitallife.net/posts/1837777 I think it stutters on high refresh rate displays, and everyone on 60 Hz can't see anything because animations are slow as hell anyway
Which is why I am asking about the hardware being used because animations are fine on my end and exactly the same as 22635.xxxx. For you I would say the issue is definitely using hardware that is not even allowed to install Windows 11. To think that old of a CPU would run this OS without issues is ignorant. I almost held off upgrading to this build because of disingenuous information like this.
a ton of evidence are against your claim, you can't explain why a lot of people with modern high end gaming rigs are facing the same issue and also people with even older mobile CPU are fine logically, this is just about high refresh rate displays and nothing else you should also be aware that some people cannot tell the difference between 30 and 60 fps, so it's not possible to diagnose this issue remotely I trust my own experience and even Zac Bowden, this 26100 build is a disaster
It is still early to say so. A significant patch which could even amount to a new build without changing the number and pretending to be only a regular update can change everything just before the official release. There might be good reasons why we see this build being unusually delayed.
I think the problem could in fact be related to higher refresh rates + VRR, as installing 24H2 on another potato laptop with Intel i5 8th Gen at 60hz (obviously with no VRR) wasn't that bad animations wise (or at least was as bad as 23H2). MS definitely needs to sort this, especially considering that except for the stuttery animations (especially opening/using Task View) 24H2 is really fast/snappy at opening/moving stuff, faster than 23H2.
Hi. I have latest Release Preview, 712, but Snipping Tool and Paint are not the last version even after MStore update. Any fix? Thank you.
Today, Like I said, I tested W11 24H2 (again) complete Vanilla (unmodded) ISO, without the 'autounattend.xml' & this time, I have both -Windows.old folder in C Drive -DefaultUser0 in the User folder (which was not there earlier with 'autounattend.xml') This concludes the test, plus, and another issue is like the majority of the users are complaining/discussing, 24H2 graphical animation is not smooth /polished Better to spare this 24H2 branch another couple of months for optimization & bug fixing. Currently sticking with the main 23H2 branch.
The Windows old folder only comes if you haven't deleted/formatted everything. DefaultUser is normal.
The official ISOs of 26100.560 are rocking !! I can see that there is a noticeable difference in launching apps and UAC admin elevation prompts are faster. The whole build feels polished and snappy. No placebo. Install it yourself and see. I don't know what they cooked.... but this is well done.
MS keeps breaking symlinks. I spent 2 days trying to figure out, why apps fail to install, even via winget, like NET Runtime. 24H2 does not like Temp moved to ramdisk, neither does it like to run setup from it, I have downloads folder in ramdisk.
defaultuser0 supposed to be deleted after oobe setup or pasword reset The Defaultuser0 account is used during the initial setup process to configure system settings, install drivers, and perform other tasks. It’s not meant for regular use and should not be logged into directly. Automatic Deletion: Ideally, Defaultuser0 should disappear automatically after the first reboot following installation. However, there are cases where it might persist even after the installation is complete.
Windows.old folder appeared after install for me after deleting partitions and installing fresh, didn't have the Default User folder though