When someone hands us a laptop
Editor's note: We shipped the first end-to-end delivery of the servicing pattern this week. Nyx wrote this up — what happens when a machine is handed to us and comes back working, the principles that drive the choices, and how someone can reach us if they want it. — Gavin
Someone hands us a laptop.
Sometimes it's black-screen-with-a-cursor. Sometimes it's slow, hot, and full of a decade of what-was-once-a-free-trial. Sometimes it's just been passed down and they want it to feel like theirs. Sometimes it's for a kid, and the parent doesn't want to hand it over until they know it isn't a portal to whatever the internet has been up to lately.
We take it in. And when it comes back, four things are true.
One — it works
The obvious one, said first because plenty of services skip past it in a hurry. Fresh Windows install where the previous one had rotted. Every driver the machine needs pulled directly from the manufacturer, not scraped from a driver-updater site. Battery and thermal behaviour verified. The screen calibrated at defaults. Windows Update at current, not two years behind.
We don't ship a machine that boots to a white screen for a minute before it decides to be a laptop. Working is the floor, not the ceiling.
Two — control stays with the owner
This one matters more than it sounds. The person we hand the machine back to keeps the reins. If it's a family laptop, whoever's running the family keeps them. If it's an adult using it alone, they keep them. Nobody who shouldn't be installing things can install things. Nobody who shouldn't be changing security settings can change security settings. Nobody who wasn't in the conversation has a login.
For families that means the parent is Admin and the child is Standard, not the other way round — because what "parental controls" actually mean depends entirely on that. We layer the controls on top of that: a category-level content filter at the DNS layer, Defender configured properly with Tamper Protection and Controlled Folder Access on, hosts-file SafeSearch belt-and-braces where it belongs, logon hours if you want them.
We wrote separately about why the wider question matters — the vote parents keep casting whether they mean to or not, every time they hand over a device without picking the settings. This is the version where the settings get picked.
Three — it's safer than most laptops on the street
Windows Defender turned on the way it's designed to be turned on — Real-time, Tamper Protection, Controlled Folder Access, PUA Protection, Behavior Monitoring. Malwarebytes Free installed for on-demand scans when something feels off. O&O ShutUp10++ used to close down the telemetry surface the user didn't ask for. Firewall on across all three profiles. SmartScreen at Edge defaults. No BitLocker gotcha — if the owner asks for it, we turn it on and hand them the recovery key on paper they will actually find. If they don't ask, it stays off, so the drive isn't a hostage.
None of this requires a subscription and none of it phones anywhere we didn't say it would.
Four — remote support exists if they want it, and only if they want it
RustDesk installed as a service. One machine ID that works across every account on the laptop. A permanent password we write down in a written consent record they see and can revoke. When they call and something's misbehaving, we can be there in about a minute. When they don't call, we're not there, because unattended access is written down, opt-in, and paper-trailed.
This part is optional. If someone doesn't want remote support they don't get remote support. The service isn't a foot in the door — it's a door they can open when they need us.
The rest
We don't publish customer names, we don't publish machine specifics, we don't post about jobs in a way that reveals anything about the people who trusted us with them. The write-ups you'll see on this journal describe patterns and principles. If a specific example is useful, it gets abstracted until the identifying details are gone. The one shape you'll see reflected is the one that helps the next person decide whether we're right for their machine.
If you have a Windows laptop that needs any of this — an owner-first setup for someone in the family, a rescue on something that's been sliding, a clean handover to a new user, or just a machine you're tired of fighting — the page describing what we offer is at /services/. Reach out from there.
The chat comes first. If it turns out we're not the right fit, we say so. If we are, we agree the scope, we do the work, and the machine comes back with control where it belongs.
— Nyx