Build 21277 is out as an Optional Update

Correct.  There often is a gap between what should be & what is 😉 

I think we've both lived through the various phases.  And for a while there wasn't consistency in IBs with this nor are IB VMs, now, following settings, which, certainly isn't right AND are not blurred, aside from whatever the default is supposed to be.

Where it gets hazy is whether to call it an OS "bug" if only manifests itself in a vm environment.

Cheers,

Drew****

VM is supposed to emulate the real machine, if it does not behave according to settings, there is a bug somewhere with Hyper-V.

I've been running a VM shop for many years before Windows even existed.

Things are not much different.

To find the bugs caused by VM we had to compare the behavior of a native OS versus the behavior as a guest. 

The same logic still applies now. 😆

Note that there is a big difference with the mainframe environment licensing scheme.

The license is based on the model and power of the host machine and I could run as many guests as I wanted without having to pay a separate license for every guest VM  that I was running on the same host system. 

The fact that I need a separate license for testing insider builds in Hyper-V VM is really ridiculous.

Why should I pay a license for doing MS testing work ?

That is just one of the reasons why I refuse to play with Hyper-V VM, I still have plenty of old real machines sitting at home doing nothing I have no reason to use VM, not even to save electricity, given that I use solar panels.. 😎

Only the last two Insider installs have had this occur on the login screen, but the settings are set the same as my public release with regedit and gpedit  so not sure where to look now that governs that effect.

All my installs are W10 Pro.

Only the last two Insider installs have had this occur on the login screen, but the settings are set the same as my public release with regedit and gpedit  so not sure where to look now that governs that effect.

All my installs are W10 Pro.

@BryceSor, 

My installs are also all Win10 Pro x64.

Hyper-V is the variable causing the different behavior with Insider Build 21277.1000 (or 20279.1) which seems to ignore the policy settings and always shows clear logon background.

Time for MS developers to explain why ? 😉

Edit:

Yet if I install a 20H2 Build 19042.685 as a VM guest with Hyper-V the behavior follows the settings and the logon background is blurred by default as it is normally on a real machine.

So the Hyper-V seems to affect only the behavior of the Insider Development builds like, in this case,  21227.1000 or 20279.1, while 19042.685 in an Hyper-V VM guest behaves correctly according to the policy settings.   See the 2 pictures below:

Blurred picture on an Hyper-V Virtual machine with Build 19042.685 with policy "Show clear logon background" Not Configured

Same Hyper-V VM guest 19042.685 with Policy "Show clear logon background" enabled:

How can I use this feature " paste it directly into a folder" ?

• Based on Insider feedback, you can now use the built-in screen snipping experience in Windows (WIN + SHIFT + S) to create a snip of your screen and paste it directly into a folder of your choice in File Explorer to save the screenshot there. Try it out!

How can I paste it directly into a folder ?  "directly"

Take screenshot and then on file explorer go to some folder, on right click menu select paste.