title: "What Windows 11 debloat tools actually remove, and what comes back" date: 2026/08/26 tags: [windows, debloat, powershell, opensource, privacy, microsoft, tooling]

🌐 last30days v3.3.2 · synced 2026-08-26

What I learned:

Both flagship tools are enormous and both got a release this month, which is why the category never gets audited - ChrisTitusTech/winutil sits at 61K stars with 31 open issues and shipped v26.08.19, and Raphire/Win11Debloat sits at 56K stars with 29 open issues and shipped a build dated 08.24.2026 that Neowin and Gizmodo both packaged as a download the same week. Between them that is 117,530 GitHub reactions on two PowerShell scripts, and the download-mirror layer (TechSpot, Softpedia, OlderGeeks, topgit) reprints the marketing description verbatim rather than testing anything.

The measurement landed this month and it says the main promise is false - @PCMag posted on 22 August that "Debloat tools claim to make Windows 11 more efficient by removing unnecessary processes and freeing up RAM. In practice, that's not the case." The underlying four-tool test is blunter: a fresh Windows 11 install uses roughly 1.9GB to 2.1GB of RAM at boot, the tools did not materially change that baseline, and the biggest gain measured was 100MB to 200MB. WinUtil paired with O&O ShutUp10++ did not move the needle; Win11Debloat removed apps and changed settings while RAM stayed in line with baseline. The debunk got 2 likes. The single loudest social post in the whole window is the opposite claim - @Nozelcode at 426 likes and 95 reposts pitching Win11Debloat as "un script ligero de PowerShell que deja Windows como debería haber sido desde el principio."

What actually breaks is Microsoft account and Xbox sign-in, and the two things you cannot get back are the Store and XboxSpeechToTextOverlay - the concrete receipt is issue #537 on Win11Debloat, titled "After running Win11Debloat, my friend can't sign into their Microsoft account or Xbox." The project's own documentation warns against removing the Microsoft Store because it is very hard to bring back, and the recovery path is not in the tool at all: Microsoft's Gaming Services Repair Tool for Xbox services, or a system restore point you had to remember to make before you ran anything. That is the shape of the real risk - not a bricked machine, a broken login on a machine that otherwise looks fine.

The restore behaviour is structural, not a bug, and an entire product category now exists to fight it - packages provisioned in the Windows image reappear for new user profiles and after major feature updates unless they are deprovisioned at image level, which is why re-running the script every few months is standard advice. The one YouTube video in the window, Tech Authority Zone at 26,328 views and 1,324 likes, is built entirely on this premise: "Windows 11 secretly reinstalls bloatware after every update - even after you uninstall it," pitching Winhance specifically as the tool that "blocks reinstalls." The durable answer is upstream of the OS - NTLite 2026.04.10936 strips Copilot and Recall from 25H2 ISOs before deployment, and Rufus now does the same at bootable-media creation.

Microsoft put things back in public twice this window, and one of them it says is deliberate - Hacker News carried Windows 11 is quietly installing OneDrive Photos on 29 July at 53 points, then Microsoft confirms it accidentally installed new OneDrive app on Windows 11 PCs on 9 August, where the headline's own tail is "and there's no easy way to remove it yet." The sharpest item is the one no script touches: the Microsoft 365 Copilot upsell banner, which "doesn't go away even if you sign out, sign back in, upgrade to an actual Copilot license, apply Windows Registry hacks, or even reinstall the Office suite," because it is an intentional feature.

Microsoft shipped the supported version of debloating this year, and consumers are not invited - Windows 11 25H2 gives IT admins a policy to remove preinstalled inbox apps on Enterprise and Education editions and explicitly to prevent removed apps such as Clipchamp, Media Player, and Teams from reappearing, driven by a dynamic app removal list keyed on Package Family Name. A dedicated "Remove Microsoft Copilot App" setting arrived with the April 2026 security update for 25H2, but it only fires when both M365 Copilot and Microsoft Copilot are installed, the user did not manually install Copilot, and the app has not launched within 28 days. Three conditions and an edition gate is the official answer; everyone on Home and Pro gets a PowerShell script from a stranger.

The bloat the community is angry about is real and measured, which is why the tools keep getting installed anyway - the biggest Hacker News thread in the entire window, 671 points and 598 comments, is Windows 11's built-in Weather app wastes more than 1 GB of RAM, resubmitted three separate times in five days, with Tom's Hardware putting it at 1.2GB and calling it a "memory-sucking web wrapper filled with ads masquerading as an actual application." The grievance is legitimate and the remedy recovers 100MB to 200MB, which is the entire tension of the category in two numbers.

The measured guidance has quietly moved from one-click to layers, and the loudest exit is not a tool at all - itechguides now recommends debloating in layers - uninstall known-unused apps, disable startup entries, restrict background activity, review privacy settings - and says to "use WinGet for precise package removal and PowerShell only when you understand the package scope." Meanwhile HN ran Desktop Linux just cracked 10% market share, and Windows 11 is mostly to blame, and @MaxFerro10 framed the whole ladder in one line: "people are just too scared of using a debloat script or using a LTSC I went to Linux is cause why not but also I'm way too used to windows."

KEY PATTERNS from the research: 1. The category's headline claim was tested this month and failed - 100MB to 200MB against a 1.9GB to 2.1GB baseline, with WinUtil and Win11Debloat both named - per @PCMag 2. The debunk is invisible next to the pitch: 2 likes for the measurement, 426 likes and 95 reposts for the promise, in the same 30 days - per @Nozelcode 3. The named breakage is Microsoft account and Xbox sign-in, and the two unrecoverable removals are the Microsoft Store and XboxSpeechToTextOverlay - per Win11Debloat issue #537 4. Reinstallation is by design at the image level, so the tools that survive a feature update work before install rather than after - per NTLite on 25H2 ISOs 5. "Blocks reinstalls" is now the marketing hook rather than "removes bloat," which is the category conceding the restore problem - per Tech Authority Zone on YouTube 6. Microsoft confirmed an unwanted install with no easy removal in the same window it defended an unremovable upsell banner as intentional - per Windows Latest 7. The supported removal path exists but is gated to Enterprise and Education, and the Copilot policy carries three separate preconditions - per Microsoft Learn 8. The grievance is better documented than the fix: the top HN thread of the window is a 1GB Weather app at 671 points, not any debloat tool - per Hacker News

title: "What arXiv's AI moderation rules catch, and what still gets through" date: 2026/08/26 tags: [arxiv, moderation, ai-generated, peer-review, academia, preprints, research-integrity]

🌐 last30days v3.3.2 · synced 2026-08-26

What I learned:

The policy is settled and the argument has moved to enforcement - the rules themselves stopped being news. arXiv no longer accepts computer-science review articles and position papers that have not been vetted by a journal or conference, per the arXiv entry on Wikipedia, and separately runs a one-year submission ban for manuscripts containing unchecked AI-generated content - hallucinated citations, leftover chatbot instructions - described in the Issues in Science and Technology forum on AI slop as "a strict one-year ban for authors of manuscripts containing unchecked AI-generated content." What researchers are actually arguing about in this window is whether any of it can be enforced. Inside Higher Ed put the academic verdict in its headline: welcome but unenforceable.

The measured leak rate is the number that undercuts the whole scheme - a large-scale citation study on arXiv itself (arXiv:2605.07723) estimates that 78.8% of non-existent citations pass moderation and appear on the platform anyway. Screened manuscripts do disproportionately contain hallucinated citations, so the filter is catching something real - but the majority of hallucinated content still enters the scholarly record. That is the gap between a policy that reads as decisive and a pipeline that is still mostly porous.

The clearest picture of who gets caught is a git commit, not a press release - the sharpest artifact in the whole 30-day corpus is a pull request titled "Update publication plan after arXiv decline; prep Zenodo deposit", which states plainly: "arXiv declined the paper on 2026-08-18 (moderation, MOD-100537), with an account-level restriction requiring a journal reference/DOI for future submissions." That is the mechanism working end to end on a named date with a ticket number - and the consequence is not just a rejected paper but an account-level gate, with the author rerouting to Zenodo. It is the only first-person record of the penalty landing that surfaced anywhere in the window, and it lives in a repo, not a forum.

Researchers are angrier about detection than about the ban - the loudest academic thread of the month is not about arXiv at all. On r/academia, "I am DONE with Pangram and every other 'AI detector' - I'm just a good writer, and that's apparently a crime now" pulled 209 upvotes and 59 comments. The complaint is false positives on human writing, which is precisely the failure mode arXiv's own design tries to avoid - the arXiv moderation appeals process routes through a moderator flagging, a section chair confirming, and an appeal being available, rather than through a classifier score. The community fear and the actual policy are pointed in different directions.

AI showing up on the reviewer's side of the desk is the complaint with no policy attached - r/academia ran "An AI 'reviewed' my paper. The editor told me to suck it up. Should I retaliate?" at 69 upvotes and 33 comments, and r/MachineLearning ran "NeurIPS 2026 Reviewer: AI-Generated Rebuttals (and Paper)" at 119 upvotes and 56 comments. arXiv can ban a submitter; nobody in this window has a lever for a reviewer or an editor. The corpus also surfaces the escalation already in flight: "Hidden Prompts in Manuscripts Exploit AI-Assisted Peer Review", authors embedding instructions aimed at the LLM reading their paper.

The hardest line came from a mathematician, not from arXiv - @rperezmarco drew the most engagement of any X post in the window with a maximalist position: "no one should sign a paper that he hasn't written himself and understood... @arxiv should ban computer generated papers. Do the work, understand the math, write your paper, disclose the AI contribution and then you earn your credit for authorship. If you don't do it, you are just a button pusher that only deserves credit for pushing a button." That is a much broader rule than arXiv's - arXiv bans unchecked output, not generated output - and the gap between the two is the actual live disagreement.

Mathematics is where the abolitionist case is being written, and it is not the case anyone is reading - Max Weinreich's "The crisis of AI-generated mathematics" reached Hacker News on 22 August arguing for total opposition to AI use in mathematics, with proposals for departments, journals and institutions to act together. It drew 10 points and 2 comments. Three days earlier Terence Tao's "Mathematics in the age of AI" drew 210 points and 269 comments - the single biggest discussion in the corpus, and twenty times the abolitionist essay's reception. Neither is an arXiv policy document; both are being hosted by arXiv while it decides how much of this it wants to carry.

arXiv is not the only preprint server tightening, and it is not the strictest - per Editage's 2026 preprint guide, the generalist preprint service hosted by OSF stopped accepting new submissions entirely in August 2025 citing quality of incoming work, and PsyArXiv switched from moderating after posting to moderating before posting. Meanwhile the QIP 2027 call for submissions now explicitly builds in a "moderation-delay case," warning authors that they are responsible for allowing enough time for a preprint to become publicly available - conference deadlines are now being written around arXiv's queue, which arXiv itself says runs one to four days and sometimes longer.

KEY PATTERNS from the research: 1. The rules are no longer contested; enforceability is - per Inside Higher Ed 2. 78.8% of non-existent citations still pass moderation, so screening is a filter and not a gate - per arXiv:2605.07723 3. The only first-person evidence of a penalty landing is a GitHub PR with a moderation ticket number and an account-level restriction - per mavaali/agentic-trust-protocol 4. Researcher anger is aimed at AI detectors and false positives, not at arXiv's human-in-the-loop process - per r/academia 5. AI on the reviewer side has no policy attached anywhere in the window, and prompt-injection into peer review is already documented - per r/MachineLearning 6. The loudest voices want a broader ban than arXiv wrote - generated versus merely unchecked - per @rperezmarco 7. The abolitionist position is being published but not read: 10 points for Weinreich against 210 for Tao's measured essay three days earlier 8. Conference organisers are now writing arXiv's moderation delay into their submission rules - per QIP 2027

title: "What mandatory Companies House identity verification has actually changed" date: 2026/08/26 tags: [companies-house, identity-verification, uk, corporate-registry, eccta, compliance, fraud]

🌐 last30days v3.3.2 · synced 2026-08-26

What I learned:

The enforcement clock is the story, and it has not struck yet - mandatory identity verification went live on 18 November 2025 with a 12-month transition that runs to 17 November 2026, so what practitioners are actually living through right now is the last quarter of a grace period rather than enforcement itself. The clearest statement of intent in the window comes from PKF Francis Clark on 11 August, quoting Companies House directly: it will "take proportionate action against those who fail to verify their identity, so that bad practice cannot hide behind false identities," and "by the end of the financial year, all companies will have met identity verification (IDV) requirements linked to their confirmation statement or be on an appropriate pathway to compliance or enforcement action." That second sentence is doing more work than the first - "or be on an appropriate pathway" is the escape hatch that means November is a filing-rejection deadline, not a purge date.

The compliance numbers are the uncomfortable part nobody in the adviser posts leads with - per GOV.UK's own management information for April to June 2026, 55% of directors and 50% of LLP members had told Companies House they were verified by the end of June. The government's own estimate is that 6 to 7 million individuals need to verify by mid-November. Roughly half the population of directors is unverified with under three months left, and the mechanism that catches them is the confirmation statement, which means the shortfall does not resolve on a single day - it resolves company by company across a rolling twelve months of filing anniversaries.

The correction practitioners keep having to make is that this was never a directors-only regime - the single highest-scoring social item in the window is a UK adviser post on X making exactly that point: "One of the biggest misconceptions about the new Companies House identity verification regime is that only directors are required to verify their identity. That is incorrect. Under the new legal requirements, People with Significant Control (PSCs) are also required to complete identity verification," per @aishanaeem89078. PSC coverage lags directors in the official statistics, which is consistent with the misconception being real rather than rhetorical - the person who owns the company but is not on the board is the one most likely to discover the requirement at filing time.

The thing that actually bites is the personal code, not the verification - Companies House's own explainer on YouTube (8,193 views, published 29 July) is entirely about the 11-character personal code you receive after verifying, and it contains the operational trap in plain text: "If you verified your identity with GOV.UK One Login before 8 July 2026, your personal code will not have been sent by email, but you will be able to find it in the 'Manage account' section when you sign in to your account." IT Contracting's 2026 confirmation statement guide puts the consequence bluntly - existing directors have to supply that code when the company files its next confirmation statement. Verifying and then losing the code is functionally identical to not verifying.

Accountants are the ones being asked to absorb the risk, and a chunk of them are declining - the Authorised Corporate Service Provider route is being actively commercialised: Icon Offices announced its ACSP registration on 20 August specifically to sell verification services to directors and PSCs, and third-party ACSP directories now exist to list registered firms. But practitioner discussion on AccountingWEB runs the other way: firms cite training and software cost as a reason not to offer it, and describe being nervous about confirming identities for a fee when the roughly 1% of problematic cases could produce reputational and financial damage. GOV.UK's fit and proper criteria for ACSPs, refreshed 11 August, spells out the downside - Companies House "may include suspending ACSP status or ceasing registration as an ACSP." The regime moved the verification burden onto a professional intermediary and attached a licence that can be pulled.

The deadline has already been weaponised by the people it was meant to stop - Krowe Accountants flagged on 24 August that Companies House has issued a scam warning: "The scams are designed to create urgency and encourage directors to hand over personal information or click malicious links." A mandatory nationwide identity-collection exercise with a hard November deadline is close to an ideal phishing pretext, and the anti-fraud measure is currently generating fraud volume as a side effect.

On whether it removed fake directors, the honest answer from this window is that nobody has published the number - every official statistic in the corpus measures verification uptake, not register cleanliness. There is no figure for fraudulent directors identified or removed as a result of IDV. The strongest counter-evidence is older but unresolved: in March 2026, Tax Policy Associates disclosed that a Companies House flaw had let any logged-in user open the private dashboard of any of roughly five million registered companies for five months, exposing director home and email addresses and allowing changes to company and director details and filings - discovered by an operations director at Ghost Mail who could not get a response from Companies House and escalated it through Dan Neidle. BleepingComputer confirmed the agency acknowledged it. A verified identity on a register that could be hijacked through the front end is a weaker guarantee than the policy framing implies.

The community layer is close to empty, and that is itself the finding - with half of six to seven million directors unverified, Reddit produced two on-topic threads in thirty days: interpreting a director's loan at 11 points, which is not about verification at all, and has everyone sorted their Companies House ID at 5 points and 14 comments, which is the only director-to-director conversation on the subject in the corpus. Read the stats footer below with that in mind: its 9,608 Reddit upvotes are almost entirely one off-topic r/LegalAdviceUK thread about a neighbour setting their house on fire at 9,592 points, which matched on the word "house." X returned seven posts carrying 38 likes between them, all adviser marketing - @PhilipNolanUK asking "Company Directors: Have You Completed Your Companies House Identity Verification?" and @GordonB58 asking "Is your deadline approaching?". The visible conversation is professionals selling compliance to clients, not directors talking to each other. The affected population is either quietly complying or has not noticed yet.

KEY PATTERNS from the research: 1. November 2026 is a filing gate, not a purge - non-compliance surfaces as a rejected confirmation statement spread across rolling anniversaries, and the official line already contains "or be on an appropriate pathway" - per PKF Francis Clark 2. Roughly half the register is still unverified with under three months to run: 55% of directors and 50% of LLP members as of end-June against 6 to 7 million individuals in scope - per GOV.UK 3. The recurring correction advisers keep issuing is that PSCs are in scope too, not just directors, which is where the coverage gap concentrates - per @aishanaeem89078 4. The operational failure mode is the 11-character personal code rather than the verification itself, and anyone who verified before 8 July 2026 never got it by email - per Companies House on YouTube 5. The ACSP route commercialises verification while transferring liability to the firm, and a visible slice of accountants are refusing on cost-and-risk grounds rather than capability - per AccountingWEB 6. The deadline is now a phishing pretext, with Companies House itself warning about urgency-driven scams aimed at directors - per Krowe Accountants 7. No published figure exists for fake directors removed; the only hard number is verification uptake, and the March 2026 dashboard vulnerability that exposed five million companies remains the strongest argument that a verified identity and a trustworthy register are different things - per Tax Policy Associates 8. Corpus caveat: only 16 of 42 dated items fall in the last 7 days, the social layer is adviser marketing rather than affected-party discussion, and the footer's Reddit engagement is an artifact of one off-topic thread matching on "house"