sorry that's on me, my bad, i hope i don't look stupid but hey, better late than never, at least i learned something today xD
Can anyone please share download link for: f8d6b727c3b7cae82f45ad82964df3d7b474ad405d1933be730548ce49b51fff *da-dk_windows_11_consumer_editions_version_22h2_updated_jan_2023_x64_dvd_ce435bcc.iso fb3b9c671f553ebf31f4314e4e23c00315c3d0ca2afe2c9db68136e80ba2379c *da-dk_windows_11_business_editions_version_22h2_updated_jan_2023_x64_dvd_ad596b30.iso Thanks
I dont see any new visuals in accounts, what are the ids? No change in widgets either, fullscreen icon doesn't even work yet they posted a screenshot of it
Has anyone seen any performance difference between 22621.1192 and 22623.1180? I'm trying to figure out why the 22621.1192 (which uses a newer ssu) would come out before the 22623.1180 with a lower build version and the older ssu?
After having done some additional tests with my AMD X570 chipset system running a freshly installed Build 22621.1192 on a Samsung 990 Pro NVMe SSD I found out a relationship between the "missing Systray bug" and the in-use Storage Controller driver: 1. The "missing Systray bug" doesn't appear here as long as the NVMe Controller of my Samsung 990 Pro uses either Microsoft's or Phison's generic NVMe driver. 2. After having replaced the NVMe driver by another one (tested with Samsung's v3.3.0.2003, Micron's v2.1.19.0 and Intel's v17.11.3.1007) the OS is running fine or even better, but the Systray is missing from scratch after the reboot. EDIT: I have to correct myself, because I just realized, that the Systray even disappears here while using the MS in-box NVMe driver, if no "safely removable" device is attached. So I suspect, that there is a relationship between the Device Management and the shown Systray. Notes: During my test with the MS in-box NVMe driver (just after the clean OS install), the USB stick with the OS Installation Image on it was still attached and shown as "safely removable". Any NVMe SSD as system drive is shown in the systray as being "safely removable", if the NVMe Controller is using the generic Phison driver v1.5.0.0.
You should never use a 3rd party nvme driver. Unless you have some need for it that the MS driver does not provide.