Newyana2 <
Newyana2@invalid.nospam> wrote:
"VanguardLH" <V@nguard.LH> wrote
| Have you already tried:
|
Thanks. Yes, I tried it all. See my recent post. I think I solved it.
It required yet another secret decoder ring Registry setting.
Somehow I hadn't found it in my online searches before, but
trying various search terms it finally turned up. I figured there
had to be something that would work.
Ah, yes, I see the registry setting you mention. That is a policy
settings. Home editions of Windows don't come with the policy editor (gpedit.msc), so I didn't go there, because I also have the Home
edition. You need the Pro or Enterprise edition to get the policy
editor; however, all policies are registry settings, so you can effect
most policy settings by registry edits. However, there are some you
can't do using regedit, like SRPs (Software Restriction Policies) to
restrict which apps are allowed to run or get blocked, and UserChoice
entries on protected filetype associations. Those use a hash created by
the OS to protect those registry entries from malicious alteration: if
the hash isn't valid, the registry key gets deleted, and the default put
in its place. Programs, including malware, can no longer make direct
edits on protected registry entries. For programs that used to edit the registry to make themself the default, instead the user must use the GUI
wizard afforded in the OS to select filetype handlers, or use the policy
editor to protected policies in the registry.
Many policies, however, are not protected. They are just registry edits although you might have to create a key or data item (the default gets
used in their absence, so you need to create them to define different behavior). Microsoft has an Excel spreadsheet showing the policies, and
where they are in the registry. However, there are templates you can
add to the policies, and I suspect the spreadsheet just lists the inate policies in Windows, and not any template policies you add.
https://www.microsoft.com/en-us/download/details.aspx?id=101451
That's why many articles telling you how to create or edit policies will
also give you the registry settings to effect the same policies.
Note: The registry setting you mentioned is under HKEY_LOCAL_MACHINE, so
it applies to all Windows accounts, not just for yours.
In the spreadsheet, I found:
HKLM\SOFTWARE\Policies\Microsoft\Windows Defender Security Center\Notifications!DisableNotifications
at row 4099. The description there is:
Hide notifications from Windows Security.
Enabled: Local users will not see notifications from Windows Security. Disabled: Local users can see notifications from Windows Security.
Not configured: Same as Disabled.
So you have to enable the hide option, which means you have to configure
the policy since the default is to disable the hide. In the
requirements cell, it notes:
At least Windows Server 2016, Windows 10 Version 1709
So, at some point before then, it was probably more of an option than a
policy. I recall you used to bring up the notification panel, or maybe
a security systray icon, and you could configure there to disable
notifications for various security components.
There is still a "Windows Security" systray icon, and right-clicking it
to select "View notification options" brings up yet another wizard
dialog, but looks to overlap other dialogs I already mentioned. That
also has "Firewall & network protection notifications" that I found
elsewhere along with the same checkboxes about domain, private, and
public zones to enable/disable for the firewall, or enable/disable the
entire Microsoft Defender Firewall (aka Windows Firewall). I'd check
there after your registry hack, and a Windows reboot to effect it, to
see if the firewall is disable in this GUI wizard.
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)