Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > alt.comp.os.windows-10 > #182596
| From | "John C." <r9jmg0@yahoo.com> |
|---|---|
| Newsgroups | alt.comp.os.windows-10 |
| Subject | Re: Dealing with Windows Security's "Ransomware protection" |
| Date | 2025-02-27 06:32 -0800 |
| Organization | A noiseless patient Spider |
| Message-ID | <vppt1a$350ck$1@dont-email.me> (permalink) |
| References | <vpkfnq$1vpet$2@dont-email.me> <fk397qsehdwd.dlg@v.nguard.lh> |
VanguardLH wrote: > John C. wrote: >> >> Windows Security's "Ransomware protection" is about as much of a PITA as >> User Account Control. > > You were warned in the "How to boot into Windows 10 Safe Mode" thread > when you mentioned you would enable Defender's ransomware protection. Yes, and it caused me grief this morning when I attempted to get some photographs off of my camera using the freeware Cam2PC. Even though I added the application to the "Allowed Apps" list, I still can't get my pictures off of the camera other than by doing it manually in File Explorer. > It is similar to 3rd-party firewalls with an option to block all > outgoing network connections unless you choose to block always, allow > temporarily, or allow always. Yes, FWs like Kerio 2.1.5, which I loved. But Kerio didn't munge program function after you okayed one like PFA does. > In both, you get an option to throttle > what can connect by the firewall, and what can access what for > Defender's ransomware protection. You get more protection, and you > choose to do the additional control. Both come with whitelists, so some > programs are exempted, but you'll keep getting nagged until you decide > on block always or allow always. Eventually the nags wane as you keep > making those decisions unless, of course, you keep installing more > software that requires more of your decisions which you opted into > getting. Too true. And eventually, a lot of people just turn off Ransomware Protection in Windows Security. Like I just had to do. -- John C. Take back Microsoft from India.
Back to alt.comp.os.windows-10 | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll 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