Windows 11 CO-Release Build 22000.51 is out to Dev Channel

I also agree: the removal of notification isons of OUR choice, and removal of almost all features in the taskbar is a severe error, even if itcould be preconfigured only BY DEFAULT to show less things.

The new Taskbar does not even allow to launch the Task Manager in the DUMMY menu that appears on a RIGHT CLICK (allowing only very basic and reduced settings for the Taskbar and nothing else) !

As well icons on the task bar (running or pinned) are NO LONGER targets for drag-and-drop.

Windows 11 usability has been reduced too much ! It is a TOY only meant for basic usage on a small tablet. The look and fell seems "fun" for now only because it is new, but rapidly it will be boring.

There were much better proposals to refresh Windows (you'll find many demos in Youtube).

Linux desktop environments are now much more user-friendly and provide many good examples.

User experience in Windows has never been so poor (with limtied choices: no way to select what appears in the Start menu as well, no more groups, only 6 "favorite" apps, no more links to documents by application: it's really difficult now to find things we use the most. The complete list of apps is almost unusable as well (too slow): no more integration of the mouse or even touch event: it's very unpractical. Users that have many apps to work with are lost and are constantly searching the apps or documents they just worked a few minutes before, siomply because it's impossible to organize our work.

We don't really need the new UI theme, this is just superficial when it is now SO MUCH defective and disorganized.

The "ListView" UI component (used for example in Regedit, and lot of applications, or Advanced system settings) is not working properly with a mouse or tactile screen, or pen input on a surface (possibly not on screen):

A click with the mouse (or touch) on a row actually selects a random row displayed above (the first row of a recent display refresh).

Double-clicks are also affected (so for example a double-click to open details of an event in the EventViewer will not show the details for the expected event), as well as right-click (for contextual menus)

The bug does not occur on the 1st row. Click the 1st row, or scroll to top, this works.

Click on the 4th row visible, this has no effect, the 1st row is still selected (or reselected or deselected if you click with SHIFT or CTRL keys for selection of multiple rows)

Click on the 3rd: no effect.

Scroll down some pixels with the vertical slider to hide the 1st row. Now try selecting the 4th row: this time it is the 2nd row that is selected instead (no effect on the 1st row).

Only workaround: don't use the mouse or touch, use arrows on the keyboard !

So select the 4th row using the keyboard (it works), do not scroll or refresh the display (and avoid moving other open windows around): now you can click on the 3rd row (it works), the 4th row again (no effect, or the 3rd row is reselected/deselected), the 2nd row (it works), the 3rd or 4th row again (does not work), the 1st row (it works), the 2nd or 3rd or 4th row (does not work).

Display refreshes in ListView have a bad effect on the position of the last click: rows can be display-refreshed but the effective position of the mouse click (or touch) is lost, overwritten by the display refresh.

This looks like unsafe multithreading with lack of isolation between multiple input devices (or bad code supposed to interact with onscreen virtual keyboards), or a bug in the kernel for variables in thread storages, or in the USER32/GDI32 implementation, no longer working properly with WDDM3 display drivers, or incorrect processing of events in the windows event queue, or incorrect "thunking" code used for compatiblity.

This may be in fact a new bug specific to the WDDM3 interface for display drivers (note: my display was properly installed in Win10 with DirectX 12.1/WDDM2 display drivers, now in Win11, it is implements DirectX 12.1 with the WDDM3 driver integration interface).

All drivers in Win11 are up to date and WHQL-certified and signed. So this is another bug of Win11, severely impacting its usability, and causing !

This bug does not occur in other list view components, notably the new one used by the Files Explorer (featuring rows with variable heights, higher on touch interfaces than for mouse and keyboard only).

It seems that legacy ListViews do not properly expose their row height when queried (assuming incorrectly that it will behave like views in File Explorer).

Note: I have not tested what happens when accessibility features or devices are enabled (e.g. with eye focus, or game paddles, or secondary keyboards, or virtual keyboards, for exampel in a smarthpone or an infrared/bluetooth/wifi remote control.

Unfortunately, Microsoft, which over time has been so loved precisely because it offered free windows upgrades without all sorts of confusing conditions, this time violates its principles to the advantage of certain computer vendors, imposing absolutely unfounded conditions to be able to upgrade from windows 10 to windows 11. I may be banned but I installed the developer version on the following system: AMD Ryzen 5 1600AF CPU, 16gb RAM, AMD RX570 4gb RAM, 250gb SSD and 1Tb hdd, TPM and secure boot enabled and everything works perfectly, as much as possible in an early version. And then why all the processor restrictions imposed by Microsoft ???? I am absolutely sure that all owners of windows 10 could run windows 11 without problems.

Well then, report good performance

Microsoft has already said they are testing older cpu's and also based on the feedback they'll add older generations of cpu's (including 1st gen ryzen)

I can't update my laptop