Windows 10 Insider Preview Dev Build 21343 (RS_PRERELEASE) - March 24  

Rolling back to the previous build (21337) brought back the "Notification Area" icons!


Hoping it will stick, if it does I may stay on this until next.

Nice sign in photo on my VMware WS VM on Fedora Rawhide w/ kernel 5.12.0-0.rc4.20210325gite138138003eb.177.fc35.x86_64

Edwin said:

You guys actually like the closed folder look??? I hate it!!!

I'm really not that invested in a preference...I just like what they've done in terms of color gradients and the icon shapes/sizes--I think that all UI icons should be minimalistic in terms of size and yet be immediately recognizable. Beyond that, it really doesn't matter to me....

TairikuOkami said:

I never liked MS anything, I use my own, there are literally millions of icons out there to choose from.

No question that's true about the system icons...but I do think Windows system icons should be universal in deployment, whether the end user elects to use them or not. It's important to be able to recognize system icons at a glance--for me, that is the purpose of UI system icons--you know, three users working on the same machine can at a glance know the difference between a folder/directory and a program executable, etc. Obviously, Microsoft's intent is to allow the customer to have the last word, of course. Windows10 is nothing if not customizable in the UI department.

JGToy said:

Rolling back to the previous build (21337) brought back the "Notification Area" icons!


Hoping it will stick, if it does I may stay on this until next.

Just turn Notifications off...is the system for some reason not letting you do that?

How To Pause, Or Even Stop All Windows 10 Notifications - OnMSFT.com

I would guess most of this still functions--I get no notifications--been so long since I had a notifications area that'd I'd forgotten about it until I saw your post!

Winuser said:

I'm not happy with this build. I have a lot of mouse lag on wireless and Bluetooth. I haven't tried a wired mouse yet. Another problem is updating store apps. I have 6 apps stuck on pending.

I'm wired--I get no lag, so lucky about that so far.

hake said:

This obsession with change for change's sake hampers user recognition of changed visual features which will lead to mistakes being made by users. There is far more than enough already to know about Windows 10 without having to relearn unnecessarily because of trivial aesthetic changes forced upon us. Windows is a tool, not a lifestyle.

I have a suspicion that the new icons probably won't require reeducation, thankfully. Because, folders still look like folders, etc. It's not like they put in a giant moose-head icon for the new folder icon--tweak his antlers and his mouth opens wide and then the folder opens to expose the contents, etc.... [MooseHead™ moose-bellow sound file, optional] You know, in these Win10 beta versions lots of things are tried, lots of experiments are conducted, and many of them never make it into the final commercial releases of Win10 and die on the vine. Maybe the Insider's Win10 beta-test program isn't your cup of tea?

TairikuOkami said:

Preparing Windows taking 30 secs is starting to get annoying, it takes longer to load the desktop than it takes to start PC. I got accustomed to pressing a button and working ASAP, now I have to wait, like in the old days.

Only time I see this delay is immediately after a new build install, in that first initial boot--and I agree that it is irritating! Normal booting, however, I use a lock screen, and when I cold boot (~10 secs to lockscreen), the system boots to the lock screen--then I bring up the PSSWRD/PIN box, enter the info, and am instantly transferred to the desktop. What I've noticed is that when my lockscreen comes up, the system continues to boot the desktop behind the lockscreen, so that by the time I put in my credentials, the desktop is 100% complete and I am instantly there... No waiting for the systray/tskmgr programs to run as they have already loaded behind the lock screen--I run several programs at boot that reside in the systray and otherwise.

I'm guessing that the first run after a new build install is taking extra time on the first boot to run and autoconfigure the program settings for the new build relative to what I run when I boot that Windows build from then on.

waltc said:

Just turn Notifications off...is the system for some reason not letting you do that?

How To Pause, Or Even Stop All Windows 10 Notifications - OnMSFT.com

I would guess most of this still functions--I get no notifications--been so long since I had a notifications area that'd I'd forgotten about it until I saw your post!

If it was just notifications I would glad do that but it was completely wiped out (clock, touch keyboard, volume, network, etc...).

Riveting to 21337 has being OK so, I will just keep it until next build.

Thanks anyway