HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
TemporalAgent7
awesome-windows-privacy
Security & Privacy2021–2023
TemporalAgent7 / awesome-windows-privacy · Archived

awesome-windows-privacy

A list of awesome tools, documentation and scripts for better privacy on Microsoft Windows

4Distinct people
6Mentions
1Explicit recommenders
574GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A list of awesome tools, documentation and scripts for better privacy on Microsoft Windows

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

You don't even indicate which download link you used, it was "earlier this week" so nobody can try and reproduce it, and you don't even say what it was detected as? Plus you…

Someone1234 used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by month6 dated mentions

Observed mentions: 2021-10-09 17:51:18 UTC to 2023-05-03 11:42:28 UTC.

0122021-10-01 00:00:00 UTC to 2021-11-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsOct 20212021-11-01 00:00:00 UTC to 2021-12-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-12-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-01-01 00:00:00 UTC to 2022-02-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-02-01 00:00:00 UTC to 2022-03-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-03-01 00:00:00 UTC to 2022-04-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-04-01 00:00:00 UTC to 2022-05-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2022-05-01 00:00:00 UTC to 2022-06-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-06-01 00:00:00 UTC to 2022-07-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-07-01 00:00:00 UTC to 2022-08-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsJul 20222022-08-01 00:00:00 UTC to 2022-09-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-09-01 00:00:00 UTC to 2022-10-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-10-01 00:00:00 UTC to 2022-11-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-11-01 00:00:00 UTC to 2022-12-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-12-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-01-01 00:00:00 UTC to 2023-02-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2023-02-01 00:00:00 UTC to 2023-03-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2023-03-01 00:00:00 UTC to 2023-04-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-04-01 00:00:00 UTC to 2023-05-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-05-01 00:00:00 UTC to 2023-06-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsMay 2023

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Oct 20212021-10-01 00:00:00 UTC2021-11-01 00:00:00 UTC101
Nov 20212021-11-01 00:00:00 UTC2021-12-01 00:00:00 UTC000
Dec 20212021-12-01 00:00:00 UTC2022-01-01 00:00:00 UTC000
Jan 20222022-01-01 00:00:00 UTC2022-02-01 00:00:00 UTC000
Feb 20222022-02-01 00:00:00 UTC2022-03-01 00:00:00 UTC000
Mar 20222022-03-01 00:00:00 UTC2022-04-01 00:00:00 UTC000
Apr 20222022-04-01 00:00:00 UTC2022-05-01 00:00:00 UTC101
May 20222022-05-01 00:00:00 UTC2022-06-01 00:00:00 UTC000
Jun 20222022-06-01 00:00:00 UTC2022-07-01 00:00:00 UTC000
Jul 20222022-07-01 00:00:00 UTC2022-08-01 00:00:00 UTC000
Aug 20222022-08-01 00:00:00 UTC2022-09-01 00:00:00 UTC000
Sep 20222022-09-01 00:00:00 UTC2022-10-01 00:00:00 UTC000
Oct 20222022-10-01 00:00:00 UTC2022-11-01 00:00:00 UTC000
Nov 20222022-11-01 00:00:00 UTC2022-12-01 00:00:00 UTC000
Dec 20222022-12-01 00:00:00 UTC2023-01-01 00:00:00 UTC000
Jan 20232023-01-01 00:00:00 UTC2023-02-01 00:00:00 UTC202
Feb 20232023-02-01 00:00:00 UTC2023-03-01 00:00:00 UTC110
Mar 20232023-03-01 00:00:00 UTC2023-04-01 00:00:00 UTC000
Apr 20232023-04-01 00:00:00 UTC2023-05-01 00:00:00 UTC000
May 20232023-05-01 00:00:00 UTC2023-06-01 00:00:00 UTC101

What Hacker News says

6 sources
The issue is that it's the way Microsoft conduct business at all. The default should be opt-in not hard to find opt-outs for every patch. I would say no, there is no way to make it more tolerable unless you run something like shutup10 or https://github.com/TemporalAgent7/awesome-windows-privacy but then again if you care that much you should simply just run Linux because in reality there is no real good solution since spyware is baked right into the product.
In MSFT is forcing Outlook and Teams to open links in Edge and IT admins are angry
Someone1234·Jan 20, 2023Recommendation phrase
You don't even indicate which download link you used, it was "earlier this week" so nobody can try and reproduce it, and you don't even say what it was detected as? Plus you linked to a site that has a whole article talking about them getting regularly flagged for false-positives due to the sensitive settings they're changing within Windows (see "Virus?" link). Like what is it you expect to happen here? Plus why are you using this sketchy looking tool instead of one of the many scripts available[0] or Open Source tools[1] that do the same thing while making the source code readily readable? I don't personally endorse any of this stuff, in fact I recommend against it. A lot of these scripts disable or remove security features and break functionality that has nothing to do with privacy. Plus users that use this stuff are self-selecting as t
Read the rest
he exact kind of users without the technical knowledge to know what they're doing, why, or how to undo it (or else they'd just make the changes "by hand"). Breaking Windows Update is a common symptom of this stuff (e.g. install -> rollback -> install -> rollback, loop), and they won't know how to fix it then just blame Microsoft. I guess my point is: You try to get sketchy things, from sketchy sites, and it gets flagged thusly, it is working as intended. If you're here to complain that Microsoft pointed your gun away from your own foot, well too bad? Better luck next time, guess? [0] https://github.com/TemporalAgent7/awesome-windows-privacy#po... [1] https://github.com/TemporalAgent7/awesome-windows-privacy#os...
In Tell HN: Windows Defender considers W10Privacy to be malware
Appx packages are not where the bloat is. These are "store" / UWP apps which are generally sandboxed / very restricted in API access - so they take up disk space but not much else after you close them. Sure, if your goal is to save a bit of disk space, this will help; but I suspect when most people think about "bloat" they think of things that slow down their computer (things that actively consume memory / cpu / network). In my experience, that bloat is mostly services and scheduled tasks. I started collecting scripts / documentation on debloating with a primary focus on restoring privacy here: https://github.com/TemporalAgent7/awesome-windows-privacy (it's not very maintained but maybe someone finds something useful there)
In Debloating Windows 10 with one command and no internet scripts
There are a lot of open source scripts and tools on GitHub for accomplishing the same goal (in various state of being out-of-date, abandoned, etc.); I started collecting the ones that appear somewhat active here: https://github.com/TemporalAgent7/awesome-windows-privacy I plan on going through them to weed out duplicates and duds. You shouldn't trust any of those blindly, but definitely read through the code; I'm particularly interested in coming up with a list of services and scheduled tasks that can be safely disabled without impacting any of the applications and services I'm using (I want Windows Update, OneDrive, Office, Defender, Store and store apps, MS Account login and Xbox Gaming for example, which most tools want to disable).
In O&O ShutUp10++ – Free anti-spy tool for Windows 10, 11

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.