stick with 22621 since it is not public as of yet I see 22622 in future release who knows what MS is up to these days
About as useful as using a condom when a woman is in labour he is he dosent know anything cause its this week next week then september now its october for official release in his brain
I make an ISO from UUP dump of build 22622.575 it doesn't give me any errors when creating it, I have tried to remove the requirements with Win 11 Boot And Upgrade FiX KiT v2.2 and I have also used Rufus and WinToUSB 7.1 (x64 to create the USB installation, I have done clean installations and still when checking with PowerShel using the SFC /SCANNOW command, the system status tells me that it has repaired damaged installation files. What could it be due to? Thank you
run this in an elevated cmd: Code: findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfcdetails.txt" On the desktop you can find the txt file with the errors filtered.
That rotating widget is so buggy, it worked fine yesterday ..now its broke again Stocks arent being displayed even though the widget is showing updates Weather warnings work though.
Beta has two versions 22621 and 22622 as you say. MS make it clear Beta features may not make it to RTM. RP by definition is Release Preview and thus its features will make it to RTM (unless MS pull a feature because of major issues) Beta 22621 is only a little ahead of RP 22621 of course. They sort of play leap frog - RP may get close to (or even jump over) Beta, but then Beta surges ahead. Eventually as we get nearer RTM, Beta and RP will converge to same version. However, I do not see how Beta 22622 can go backwards in build number - they only ever go forward. As we get nearer RTM, I believe MS will begin to activate/install features in 22621 it wishes to keep. However Beta 22622 will have features that will not get in RTM. I believe Beta 22622 will be the start point of Beta for next version after RTM and will probably get superseded pretty quickly. Either way, one of us must be right LOL. Actually, I do use RP 22621 as my main OS now
from blog post of 290 This approach is being used for the Beta Channel only and is not indicative of any changes or plans for final feature rollouts. The enablement package artificially increments the build number for the update with new features getting rolled out and turned on to make it easier to differentiate from devices with the update with features off by default . As a reminder, features we try out with Windows Insiders will ship when they are ready and not every feature that we try out in the Beta Channel will ship to general customers. so if im reading this correctly, 22622 is only temporary i dont think the "moments" will raise the build number up imo win11 23h2/sun valley 3 is supposed to be dead