HN Showcase
Back to browse
Crowdsourced tracker for what each Windows/M365 update breaks

Crowdsourced tracker for what each Windows/M365 update breaks

by dantelofisial·May 19, 2026·1 point·0 comments
Visit ProjectView on HN

AI Analysis

●●SolidSolve My ProblemNiche Gem

Finally a centralized feed for broken updates that beats waiting for r/sysadmin megathreads.

Strengths
  • •Groups scattered reports from Reddit and blogs into single rows keyed by KB number for clarity.
  • •Open JSON API allows easy integration with existing monitoring stacks like Grafana or Zabbix.
  • •Automated scanning of specific subreddits and tech blogs fills the gap before official MS advisories.
Weaknesses
  • •Dependent on the quality and speed of community reporting; sparse data during quiet update cycles.
  • •Lacks deep technical filtering or automated remediation scripts beyond linking to source posts.
Category
Productivity
Target Audience

System administrators, IT managers, MSPs

Similar To

AskWoody · BleepingComputer · Microsoft Release Health

Post Description

Sysadmins find out about a broken Windows update three ways: a user ticket the morning after Patch Tuesday, an r/sysadmin thread 48 hours later, or Microsoft's own Known Issues page 1–3 weeks deep. There's no central feed of "this KB broke this thing on this config." Bleeping Computer and AskWoody are the closest, but slow and unstructured.

So I built one.

What it does: - Pulls posts every 4–6h from r/sysadmin, r/msp, r/Intune, r/ActiveDirectory, r/exchangeserver, r/AZURE via the Reddit JSON API - Pulls RSS from MS Health Dashboard, Bleeping Computer, AskWoody, BornCity, MS Security Blog, and the Windows IT Pro / Intune / Exchange TechCommunity boards - Groups by (primary KB, component) so 12 threads about the same 802.1X bug become one row with 12 source links - Ranks by score + post_count + recency - Optional Thursday digest email via Resend

Every regression row links back to the underlying Reddit/RSS posts — the classifier is not authoritative, the source threads are. If the LLM misreads something the evidence is one click away.

What I'd love feedback on: - Sources I'm missing. Specifically non-English ones (BornCity is the only DE source right now; nothing for JP/KR where MS ships region-specific KBs). - Classifier failure modes. Edge cases where it's calling things regressions that aren't, or missing real ones.

Free to read. Digest signup is optional. I'm the only person on it.

Similar Projects