Build 21277 is out as an Optional Update

Hi Johnny, 

From the beginning when they tried to change this Blurred screen on logon with Insider Builds 20211 and 20215 there were inconsistencies on the behavior, see below what I wrote you back then about what I was seeing with those builds in different situations of updates.

Now with 20277 or 21277 the behavior is back to normal and exactly the same as 19042.685.

Note that in my case I don't use VM or Hyper-V just real machines. 😉

It is ironic that this Blurred screen nonsense was implemented in response to some users FBH reports for v 1903, they wanted the blurred screen without ever specifying what the purpose behind it was. 

@Johnny_55, 

Now that you mention it, the policy "Show clear logon background" seems to work in one case but not after a sign out and back in.

If I leave the policy disabled or not configured on 20215, I see the login screen blurred when I login the first time, but if I sign out and then login again then the picture stays clear regardless of the policy setting.

More inconsistency !

The same policy setting "Show clear logon background" with 19041 works for both cases (1st login or sign off / login) .  Why did they change it in 20215 ?

With 20215:

Same behavior on the policy "Show clear logon background" on 3 different situations of update.

1. Clean install of 20215.
2. W.U. from previous 20211.1000 to 20215.1000
3. W.U. from 19041.508 to 20215.1000.

A) With policy not configured or disabled Login is blurry on 1st login and login after screen lock,

    but Login after sign off shows clear picture. 

B) With policy enabled the login picture is clear in all cases.

Case A) doesn't make any sense to me.  What are they trying to accomplish ?

fg:

Disabled, Not configured, Enabled... the IB is NOT blurry with all three.

As for the IB being "broken", if that is the only thing amiss... will continue to leave it be.  Don't want it blurred, anyway, so it's ok.

Johnny:

Yes, 1 vm, but have a hard time to think it's inheriting the behaviour when the behaviour does not exist with the Host machine.

"After rereading, it appears you may have already done this. Did you fire the vm up after setting blur on Host, then rebooting and then run vm."

Probably I have 😂 Doubt, at this point, with this discussion about it with you lot 😉 likely have done nearly any imaginable scenario 🤣 Maybe not, though, since I don't want blur anywhere probably never did that.  I was focusing (no pun intended) on the IB.  But just for you, I'll do it; standby...

Ok, blur the Host with both (computers) set to Not configured & the IB stays NOT blurred.  It is not following the Host.  It is not blurred & does not care how it is set, it is not going to blur.

That's enough... as long as there is no blur I'm happy.  Somehow the IB isn't changing with the settings.

Cheers,

Drew

My host public build has the blur but my H-V doesn't and I have not altered anything other than installing 21277

Eddie might have more info on this

@johnny_55

Regardless of the "I'm done", you had asked for a scenario to be explored and I just went through it so, you are stuck reading the results.

Drew, 

On your IB could you try Enabling the policy and then check the registry after a reboot.

After that set it back to "Not configured" and see if anything changes.

I went through it on both the IB & 20H2:

They are identical, except for 1 difference.

Yes, both, when Enabled have System in Reg & Disable, etc... value there

Yes, both, when Not configured, System, etc is gone from there

BUT❗...

20H2 is blurred if Not configured, as should be and sharp or focused if Enabled, as should be.

While the IB is sharp or focused whether Enabled OR Not configured❗ It doesn't matter which, it stays unblurred.

Johnny, YOU may find this interesting.

Cheers,

Drew

Yes, I do find this interesting.

Do you only have the one vm in Hyper-V. Suspect that possibly the vm is inheriting this behavior from the Host system.

BryceSor mentioned the same behavior as he uses Hyper-V as well (Page7 of this thread). Since I use VMware, not seeing this, still have to set it manually with gpedit.

As we all know, the Guest does inherit some things from the Host system, could this be what is at play here with H-V. What would happen within the vm if you change the Host setting, reboot, etc.

Just a suspicion. Bryce does not mention if his Host is setup with no blur, suspect it would be :-)

Regards,

Edit: After rereading, it appears you may have already done this. Did you fire the vm up after setting blur on Host, then rebooting and then run vm.

20H2 is blurred if Not configured, as should be and sharp or focused if Enabled, as should be.

While the IB is sharp or focused whether Enabled OR Not configured❗ It doesn't matter which, it stays unblurred.

 

Cheers,

Drew

 

@Drew1903, 

Sounds like your IB system is broken. Clearly the behavior does not match the settings description.

What about "Show clear logon background" set to Disabled ?  

Does it show clear even in that case ?