Robert Moca

I write the guides on Zepe. All 37 of them, and I rewrite them when Windows changes underneath.

Why I started this

Because I kept losing afternoons to the same thing you probably did, and that is genuinely the whole origin story. A Windows setting would not do what I expected, I would search for it, and I would land on a page with six hundred words of preamble, a numbered list that matched no version of Windows I had in front of me, and a method Microsoft had quietly removed two years earlier, presented as if it were current.

What I noticed after enough of those afternoons is that the pages were never wrong in an interesting way. They were wrong because nobody writing them had asked why the setting behaved as it did. Take hidden files. Almost every guide tells you to tick Hidden items in File Explorer and stops there. But Windows uses two separate attributes, Hidden and System, and that checkbox only touches the first. So you tick it, the file you are actually looking for still is not there, and the guide has no explanation to offer because it never had one.

That gap is the entire reason this site exists. Once someone tells you there are two attributes, the problem stops being mysterious and you can solve the next one yourself. That is what I am trying to do on every page.

How I actually write a guide

I am not going to pretend this is a sophisticated process. It is mostly stubbornness, applied in the same order every time.

Find the real question. The search someone types is rarely the thing they want. People searching for how to open a .aae file want to know whether it is safe to delete, because their photo folder is full of them. So that is the question the guide answers.
Work out the mechanism first. Before writing a step, I want to know why the thing behaves as it does. Laptop brightness is a command to the panel backlight; a desktop monitor’s brightness lives in the monitor’s own firmware. Once you know that, it is obvious why Windows has a slider for one and never will for the other, and no list of clicks teaches you that.
Go to the primary source. Microsoft Learn, Microsoft Support, the published command references. Not other people’s articles, because that is how an error gets copied twenty times until it looks like consensus.
Run the commands. Every command in a guide is written out in full, with the output you should expect, so you can tell a success from something that silently did nothing. That distinction matters more than people realise; a command that fails quietly is worse than one that errors.
Say what breaks. If a step is destructive, irreversible, or needs Pro rather than Home, it says so in the guide, not in a disclaimer at the bottom.

What I will not publish

Some of this is worth stating plainly, because leaving things out is most of what makes a guide usable.

Methods that no longer work. If Microsoft closed a route off, I say it is closed. Listing it anyway to pad the article out just costs you time.
Five methods where one works. If four of them are worse, I will tell you which to use and why the others exist.
Registry edits reached for casually. Sometimes the registry genuinely is the answer, and then I give it with the risk stated. It is not a way to look advanced.
Confident answers to questions that do not have one. Occasionally the honest response is that a thing cannot be done, or needs hardware you do not have. I would rather say so than invent a workaround that wastes your evening.

There is a fuller version of this in the editorial standards, including how corrections are handled.

What I write about

Currently 37 guides across 8 areas of Windows — files and folders, display and desktop, accounts and security, network and devices, performance and storage, updates and recovery, the command line, and versions and licensing. Mostly Windows 10 and 11, with Windows 7 where people are still running it and deserve a straight answer about that.

I am not affiliated with Microsoft in any way. Windows is their trademark; I just write about it.

Tell me when I get it wrong

This is not a formality. Windows changes, I miss things, and readers catch them. If a menu path has moved, a command behaves differently on your build, or a guide simply does not cover the situation you are in, email me and I will fix it and say what changed.

contact@zepe.online
Include the guide, your Windows version (press Win + R, type winver), and what you saw instead.