matbanik

Published September 12, 2026 on matbanik.info I have two 2019 NVIDIA Shields in my house. A Pro in the office, a Tube in the living room. Both run the same software. Both play movies from the same Plex server. The office one needed two or three tries to load the library every time it woke up. The living-room one never did. The difference was one switch in the Plex app. Not the router. Not the firewall. One switch. Most Shield problems are like that. The box isn't broken. The fix is hiding in a different layer than the one you're poking at. This post helps you fix your NVIDIA Shield by finding the right layer first, then doing one short fix. Anything longer lives in a linked gist that you, or an AI helper, can follow. The right-hand box is the one that needed three tries. Find the layer before you fix your NVIDIA Shield Read the list. Pick the line that sounds like you. Go only to that section. Four symptoms. Only one of them is yours. 1. The pictur...

Published August 26, 2026 on matbanik.info You did everything the docs said. Enabled remote logging on the pfSense box, pointed it at your Windows machine, opened UDP 514. Nothing arrived. The Netgate forum has collected threads about this exact silence for over a decade — logs generated but never sent, syslogd quietly dead after a reboot. Somewhere between the firewall and your disk, the event vanished — and nothing in the chain will tell you where. The standard fix is a SIEM, which trades one problem for a bigger one: now you own Elasticsearch. This guide takes a different path. You open Cursor, answer five questions, and approve commands while an AI agent builds the firewall log pipeline. By the end you'll have one verified firewall event on disk, searchable history in a local database, and an AI analyst that reads your logs — but can't touch your firewall. Total footprint: one Windows service, one folder, one SQLite file. The dashed line is the security model:...

Published August 06, 2026 on matbanik.info A reviewer looked at my code and found a bug. One route returned a 500 error when it should have returned a 404. It reported the finding, clearly, with the file and the line. My agent fixed that route. Exactly that one. Five other routes had the identical bug. They sat there, untouched, while the agent reported the work complete — and it wasn't lying. It had fixed the thing it was shown. It just never thought to ask how many other places the same mistake was hiding. I spent a while assuming this was a model problem, and that a better model would fix it. That turned out to be wrong, and the fix that worked was dumber than I expected. AI coding agent guardrails are not about making the model smarter. They're about giving it somewhere to put things down. Every drawer in that cabinet is something the agent would otherwise have to keep in its head. Where AI coding agents quietly go wrong The failures that cost me the m...

Published May 22, 2026 on matbanik.info Manuel Gil's Windows Update reset script crossed half a million downloads before he archived it in March 2023. The Dev-C++ successor — Reset-Windows-Update-Tool, 513 stars on GitHub — followed it into the archive on January 16, 2026. For years, these were the tools sysadmins reached for when Microsoft's troubleshooter shrugged and said "we couldn't identify the problem." They're gone now. And nothing replaced them. Search "reset Windows Update" today and you'll find plenty of consumer guides. Screenshots of Settings panels. "Click Troubleshoot, then Additional troubleshooters." The irony: that troubleshooter is itself being deprecated with the MSDT retirement. Microsoft is sunsetting its own fix-it tool. For MSP technicians managing hundreds of endpoints, the gap is worse. You need something that runs silently through your RMM. Something that won't obliterate the Intune ring configurat...

Published May 13, 2026 on matbanik.info I started building a platform with AI agents writing most of the code. Two different models. Eleven project phases. Over 1,500 tests. More than 200 features shipped. Then one morning I opened my own repository and couldn't trace the execution path through a service I'd supposedly built. The code was clean. The tests passed. The architecture followed every pattern I'd specified. But when I tried to explain why a particular order validation happened before portfolio sync instead of after, I just... stared at the screen. The logic was there. My understanding wasn't. That's not a horror story. It's just what happens when you adopt a tool without vetting it the way you'd vet any other dependency in your stack. I started asking different questions — the kind you'd ask before adding something critical to a production system. Here are four that keep surfacing. What Changed About the Work — and What Didn...

Published April 14, 2026 on matbanik.info No Docker. No Pro license. Just two binaries and NSSM. What You're Building Two binaries — hbbs (ID/Rendezvous) and hbbr (Relay) — managed by NSSM as auto-start Windows services. Clients on your LAN connect through your server instead of RustDesk's public infrastructure. Your server generates an Ed25519 keypair on first run. Every client needs the public key to trust your server. Lose the private key, regenerate everything. --- Prerequisites | Requirement | Notes | |-------------|-------| | Windows 10/11 or Server 2019+ | Tested on Windows 11 24H2 | | Static LAN IP on the server | DHCP reservation works too | | Admin access | Service installation requires elevation | | RustDesk client installed | On both server and remote machines | --- Step 1: Download Binaries Create a dedicated directory. This guide uses C:\RustDeskServer\ — pick any path, but don't move it after service installation. RustDesk Ser...