Guys...Im really confused .....is Windows 11 Build 26100 still develplement preview? There is no official up of 22621.3527. What the f.... is going on.
O.K. but when I tried to install this OS flash my whole damn hard disk. Is it official new Windows 11 and if YES why there is no option to upgrade Windows 23H2 ?Thanks in andvance dude for answer
really like 26100.xxx fresh installed and the new way of the Gui installed Win 11pro would have kept it but games keep crashing
Where is the option to ''always show all icons in the notification area'' ? It's really annoying to manually enable every icon.
I see a bug in 26100.268 when using notepad when i copy paste and then save, it scrambles notepad and it doesnt allow you to close it unless you Ctrl Alt delete and force it to close in task mamager.
does anyone have any idea how to change the middle click behavior in File Explorer? it opens a new tab in the background and I hate it because I have to click on that new tab on build 22631 it opened new tab with focus already on it sorry can't explain it correctly
Together with middle click to close a tab It's the standard behavior since the day Opera invented the tabs 30 years ago or so, then it was copied by other browsers, and by other tabbed SW like notepad ++. And make a lot of sense in a browser, where you middle click in a brunch of links, letting multiple tabs load the page in background (especially 30 years ago with slow connections), maybe in a FM make a bit less sense, but a different behavior would break consistency and habits. So no idea if it's possible.
Is Release Preview (22631) still a Weekly release OR has it moved to 2 Builds a Month ? Is 22635 still being released ? Beta is now 26100 ? Dev is now 26130 ?
Don't know how people are so confused by all this. Currently: 22631: Public/Release Preview 22635: Beta 26120: Dev It's going to eventually transition to: 26100: Public/Release Preview 26120: Beta The beta channel has for awhile now been a higher build version that the Public/RP release, 24H2 will continue with the same approach.
Stitched in my regristry "hacks" that stop experimentation, telemetry, numerous "features," and enable enterprise stability options. Then NTLite, removed only system apps, patched to .2, removed them again and reapplied my .reg files. Applied my autounattend that sets some BCD policies, enables extra security features, and makes many changes to the defaultuser profile as well as the system user that one typically makes for themselves (so it additionally couldn't do what I didn't want), all prior to OOBE. Installed, updated to .200something using WU, and that's it. Started gaming/surfing and not a hitch since. Only issue was with OOBE itself requiring me to use the accessibility keyboard because numerous real ones didn't work. Oh yeah, I also started out by exporting only the edition I was going to install from the .wim file so two editions I was not didn't pose any chance for issue during modification.