Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > alt.comp.os.windows-10 > #182712
| From | "John C." <r9jmg0@yahoo.com> |
|---|---|
| Newsgroups | alt.comp.os.windows-10 |
| Subject | Re: Dealing with Windows Security's "Ransomware protection" |
| Date | 2025-03-02 05:59 -0800 |
| Organization | A noiseless patient Spider |
| Message-ID | <vq1o7k$pv5p$3@dont-email.me> (permalink) |
| References | (5 earlier) <vpq6b3$36sd2$1@dont-email.me> <vpsd1o$3m2rg$1@dont-email.me> <vpsnpc$3o6go$1@dont-email.me> <op.22o7r8hn1svx94@office-pc.attlocal.net> <vptus9$2j6q$1@dont-email.me> |
On 25/02/28 07:29 PM, Newyana2 wrote: > On 2/28/2025 4:39 PM, Allan Higdon wrote: > >> >> If you're like me, an on-demand standalone AV scanner is enough. >> One really good one is Emsisoft Emergency Kit. >> https://www.emsisoft.com/en/home/emergency-kit/ >> >> I've been using Hellzerg Optimizer to disable Windows Defender. >> https://github.com/hellzerg/optimizer/#--how-to-disable-defender-in-windows-10-1903-and-later >> >> I disable Tamper Protection with a .Reg file. >> >> [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Defender\Features] >> "TamperProtection"=dword:00000000 >> >> You can use Winaero Tweaker to verify that Tamper Protection and >> Windows Defender are disabled. >> https://winaero.com/winaero-tweaker/ > > Thanks. Good notes to check out. I have occasionally > downloaded something like Clam to do a one-time check > when I feel a bt of paranoia. I don't think I've ever tried > Emsisoft. I used to use Trendmicro's "Housecall" free online scanner a long time ago. Still would probably work for somebody who doesn't mind knowingly exposing their soft underbelly to a corporation. -- 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