Privacy settings in registry do not match GUI settings

Found this with WIn10 v1709 and recently with v1803. The privacy settings in the registry stay "allow" when all have been turned off in Settings.

HKCU\Software\MIcrosoft\Windows\CurrentVersion\:
DeviceAccess\Global\D89823BA-7180..., Key = Value, ValueData = Allow (let apps access my calendar)
DeviceAccess\Global\8BC668CF-7728..., Key = Value, ValueData = Allow (let apps access my call history)
DeviceAccess\Global\9231CB4C-BF57..., Key = Value, ValueData = Allow (let apps access and send email)
DeviceAccess\Global\21157C1F-2651..., Key = Value, ValueData = Allow (let apps read or send messages)
DeviceAccess\Global\A8804298-2D5F..., (let apps control radios) Allow
DeviceAccess\Global\BFA794E4-F964..., (enable/disable location) Allow
DeviceAccess\Global\E5323777-33FA..., (let apps access\control\my mic) Allow

...on through the rest. I'll be the first to admit I'm a little paranoid, but shouldn't these be deny when turned off in Settings? The 1803 is still an Insider ISO made from the upgrade directories/files, but that doesn't explain them still set to allow in 1709. Am I missing something?

This is extremely useful but I'd like to point out that there seems to be different behavior when using the registry settings and using the GUI.
Let's assume I'm using Skype and have the Audio Devices dialog up.
I use the Privacy Settings GUI to DISABLE access to the microphone. SKYPE's access to the mic is immediately disabled.
Now let's assume I use the registry keys to disable access. In this case, while the registry keys are accurately reflected in the Privacy GUI ( the radio buttons are off), the running SKYPE can still access the mic. I have to end task Skype, restart the Audio Settings dialog and only then is access to the microphone disabled.

Thoughts?

Additional info: I'm using the following keys:
1. [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\CapabilityAccessManager\ConsentStore\mi crophone]
"Value"="Deny"

2.
[HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\CapabilityAccessManager\ConsentStore\mic rophone]
"Value"="Deny"

3. [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\AppPrivacy]
"LetAppsAccessMicrophone"=dword:00000002
"LetAppsAccessMicrophone_UserInControlOfTheseApps"=hex(7):00,00
"LetAppsAccessMicrophone_ForceAllowTheseApps"=hex(7):00,00
"LetAppsAccessMicrophone_ForceDenyTheseApps"=hex(7):00,00

Hi Brink,
Thanks for the quick reply. I did use that tutorial. Those are the keys that you mention.
To be clear, the registry settings that you mention work. The difference is that using the keys requires a reboot (or ending all the tasks that might be using the mic and restarting them) while the GUI is immediate.

I have a bit better results when turning off the specific driver, using the method you laid out in another tutorial:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\MMDevices\Audio\Capture

When changing the values in regedit in the above key, changes are more immediate.

The weird thing is that Windows MUST be doing something "else" than just setting the keys because the change is immediate when using the GUI. I'm going to do more research :)

Again the interesting thing is that :
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\MMDevices\Audio\Capture

is more immediate. I'll post back results when I have them. Thanks!

Mitchell, results?