Groups > alt.comp.os.windows-10 > #182548

Re: Dealing with Windows Security's "Ransomware protection"

From	...w¡ñ§±¤ñ <winstonmvp@gmail.com>
Newsgroups	alt.comp.os.windows-10
Subject	Re: Dealing with Windows Security's "Ransomware protection"
Date	2025-02-25 11:57 -0700
Organization	windowsunplugged.com
Message-ID	<vpl3r1$24smp$1@dont-email.me> (permalink)
References	<vpkfnq$1vpet$2@dont-email.me>

Show all headers | View raw

John C. wrote on 2/25/2025 6:14 AM:
> Windows Security's "Ransomware protection" is about as much of a PITA as
> User Account Control.
> 
> I have this protection on, but man, I really don't like the way it
> blocks so many of the programs I have on my system from doing things.
> 
> To allow an "app" (God I hate that corruption of the word APPLICATION),
> here's what you do (in case you don't know):
> 
> 1. Open Windows Security
> 2. Click on "Virus & threat protection"
> 3. Scroll down all the way so that you can see "Ransomware protection"
> 4. Click on "Manage ransomware protection"
> 5. Under "Controlled folder access" (which at this point should be in
> the "On" position), click on "Allow an app through Controlled folder access"
> 6. Click on the "Add an allowed app" button
> 7. Take it from there to add an application to the list.
> 
> Does this PITA actually outweigh having Ransomware protection? That's a
> question I'm asking myself. As long as Windows Security doesn't actually
> remove a program before I have a chance to do this for a program, I can
> probably live with it. However, if a program actually DOES get removed,
> I will disable this protection.
> 
> I've already turned UAC down to the lowest possible setting because it
> was distracting me way too often.
> 
> What do YOU think about Ransomware protection?
> 
> TIA.
> 

Just another layer of o/s hardening - Ransomware/Controlled Folder Access 
(aka CFA)
  - CFA checks apps against a list of trusted apps
  - Blocks apps that are suspicious or malicious from changing files in 
protected folders
  - Notifies you when an app is blocked from making changes

The default in Windows 10/11 for CFA is 'Off' - i.e. disabled, requires 
user intervention to enable.
  => Based on the information provided(or lack of), it might make sense 
to turn off CFA.

-- 
...w¡ñ§±¤ñ

Thread

Dealing with Windows Security's "Ransomware protection" "John C." <r9jmg0@yahoo.com> - 2025-02-25 05:14 -0800
  Re: Dealing with Windows Security's "Ransomware protection" Frank Slootweg <this@ddress.is.invalid> - 2025-02-25 13:52 +0000
    Re: Dealing with Windows Security's "Ransomware protection" Ed Cryer <ed@somewhere.in.the.uk> - 2025-02-25 15:23 +0000
      Re: Dealing with Windows Security's "Ransomware protection" Paul <nospam@needed.invalid> - 2025-02-25 13:35 -0500
        Re: Dealing with Windows Security's "Ransomware protection" Ed Cryer <ed@somewhere.in.the.uk> - 2025-02-25 19:02 +0000
          Re: Dealing with Windows Security's "Ransomware protection" Paul <nospam@needed.invalid> - 2025-02-25 16:09 -0500
      Re: Dealing with Windows Security's "Ransomware protection" ant@zimage.comANT (Ant) - 2025-02-25 21:27 +0000
  Re: Dealing with Windows Security's "Ransomware protection" VanguardLH <V@nguard.LH> - 2025-02-25 10:08 -0600
    Re: Dealing with Windows Security's "Ransomware protection" "John C." <r9jmg0@yahoo.com> - 2025-02-27 06:32 -0800
      Re: Dealing with Windows Security's "Ransomware protection" wasbit <wasbit@nowhere.com> - 2025-02-28 09:37 +0000
  Re: Dealing with Windows Security's "Ransomware protection" Newyana2 <newyana@invalid.nospam> - 2025-02-25 11:37 -0500
    Re: Dealing with Windows Security's "Ransomware protection" "John C." <r9jmg0@yahoo.com> - 2025-02-27 06:35 -0800
      Re: Dealing with Windows Security's "Ransomware protection" Newyana2 <newyana@invalid.nospam> - 2025-02-27 10:20 -0500
        Re: Dealing with Windows Security's "Ransomware protection" "John C." <r9jmg0@yahoo.com> - 2025-02-27 07:31 -0800
          Re: Dealing with Windows Security's "Ransomware protection" Newyana2 <newyana@invalid.nospam> - 2025-02-27 12:11 -0500
            Re: Dealing with Windows Security's "Ransomware protection" "John C." <r9jmg0@yahoo.com> - 2025-02-28 05:17 -0800
              Re: Dealing with Windows Security's "Ransomware protection" Newyana2 <newyana@invalid.nospam> - 2025-02-28 11:21 -0500
                Re: Dealing with Windows Security's "Ransomware protection" "Allan Higdon" <allanh@vivaldi.net> - 2025-02-28 15:39 -0600
                Re: Dealing with Windows Security's "Ransomware protection" Newyana2 <newyana@invalid.nospam> - 2025-02-28 22:29 -0500
                Re: Dealing with Windows Security's "Ransomware protection" "John C." <r9jmg0@yahoo.com> - 2025-03-02 05:59 -0800
                Re: Dealing with Windows Security's "Ransomware protection" "John C." <r9jmg0@yahoo.com> - 2025-03-02 05:55 -0800
              Re: Dealing with Windows Security's "Ransomware protection" VanguardLH <V@nguard.LH> - 2025-02-28 11:55 -0600
                Re: Dealing with Windows Security's "Ransomware protection" "John C." <r9jmg0@yahoo.com> - 2025-03-02 06:03 -0800
                Re: Dealing with Windows Security's "Ransomware protection" ant@zimage.comANT (Ant) - 2025-03-03 00:46 +0000
                Re: Dealing with Windows Security's "Ransomware protection" Hank Rogers <Hank@nospam.invalid> - 2025-03-02 19:19 -0600
        Re: Dealing with Windows Security's "Ransomware protection" Frank Slootweg <this@ddress.is.invalid> - 2025-02-27 16:12 +0000
      Re: Dealing with Windows Security's "Ransomware protection" VanguardLH <V@nguard.LH> - 2025-02-27 14:03 -0600
  Re: Dealing with Windows Security's "Ransomware protection" ...w¡ñ§±¤ñ  <winstonmvp@gmail.com> - 2025-02-25 11:57 -0700
    Re: Dealing with Windows Security's "Ransomware protection" "John C." <r9jmg0@yahoo.com> - 2025-02-27 06:38 -0800
      Re: Dealing with Windows Security's "Ransomware protection" ...w¡ñ§±¤ñ  <winstonmvp@gmail.com> - 2025-02-28 10:56 -0700
        Re: Dealing with Windows Security's "Ransomware protection" "John C." <r9jmg0@yahoo.com> - 2025-03-02 06:05 -0800

csiph-web