Group Policy not affect Settings app?

I have a new Windows 10 Pro laptop that I am configuring. I am a Windows 10 newbie, and am especially new to using Group Policy to configure it.

I decided to disable both AutoRun and AutoPlay, since they seem like major security breaches, so I implemented the 2 Group Policy changes described here.

However, if I open Settings app > Devices > AutoPlay, I see that AutoPlay still has its default insecure value, which is On.

How come changing the Group Policy did not lead to a change in Settings app?

Is this normal behavior, or am I doing something wrong?

Earlier today I did another port titled "scheduling Windows Defender full scan: problems and questions".

Some of the issues that I discuss there have to do with Group Policy, so I wonder if I am doing something wrong or just not understanding how it works.

There is generally no need to fiddle with Group Policy. Dd you do a full PC reboot ?

Steve C said:

There is generally no need to fiddle with Group Policy.

Why do you think that?

Do you have a fundamental reason?

Or, is it simply a practical reason, such as maybe editing Group Policy is a bit harder than configuring stuff thru the Settings app?

Steve C said:

Dd you do a full PC reboot ?

Great point. I thought that I did yesterday, and should have mentioned that in my original post.

But to make sure, I first verified that my Group Policy values disabling AutoRun and AutoPlay are still there, but the Settings app shows AutoPlay enabled (it has no option for AutoRun). Then I restarted my laptop. Lo and behold, nothing changed: Group Policy values disabling AutoRun and AutoPlay are still there, but the Settings app shows AutoPlay enabled.

So, I am still mystified.

One more thing to note: I am using the "Local Group Policy Editor", and changing the "Computer Configuration" tree. I did not touch the "User Configuration" tree, since my understanding is that the former tree takes precedence if any values disagree.