Editor

Muhd Radhi Wahab

Editor of Windows Now. Radhi has spent 26 years with Windows — from repairing PCs in the Windows 98 era to running Windows Server and networks — and brings that hands-on background to every guide the site publishes.

Editor, Windows Now · 26 years in Windows, Server & networking · LinkedIn

Twenty-six years with Windows

Muhd Radhi Wahab — Radhi to most people who work with him — has been fixing, configuring and running Windows systems for 26 years. He started where many of the best systems people start: at the workbench, repairing PCs in the Windows 98 era, back when a fix meant chasing IRQ conflicts, hunting down driver disks, and coaxing temperamental hardware into cooperating. That grounding in how a computer actually behaves — not just how the settings screen describes it — still shapes how he approaches every problem today.

Over the two and a half decades since, his work moved steadily up the stack: from single machines to the servers and networks that tie them together. His day-to-day now centres on Windows Server and networking — Active Directory, DNS and DHCP, file and print services, remote access, and the quiet, unglamorous discipline of keeping infrastructure available and secure. The through-line is the same skill he learned at the repair bench: work the problem methodically, from the most likely cause to the least, and never guess when you can check.

From the repair bench to the server room

The path from PC repair to server administration is a well-trodden one, and it teaches something no documentation can: what really breaks, how often, and why. A technician who has replaced failing drives understands in his bones why a backup strategy has to assume hardware will fail. Someone who has untangled a driver conflict late at night knows that “just reinstall Windows” is the last resort, not the first. Someone who has stood up a domain controller for a small office knows the difference between a setting that genuinely matters and one that merely looks important.

That accumulated, hands-on judgement is exactly what a good how-to guide is meant to distil. It is the difference between a page that dutifully lists every option Microsoft offers and a page that tells you which one to reach for first — and warns you where the tidy official answer won’t survive contact with a real machine. Radhi has spent his career on the wrong end of both kinds of advice, and Windows Now is his attempt to publish only the first kind.

What Radhi works with

His expertise spans the full Windows stack that Windows Now covers:

  • Windows client — from Windows 98 through to Windows 11: installation, drivers, performance tuning, updates, and the everyday troubleshooting that keeps a PC usable.
  • Windows Server — setup and roles, Active Directory Domain Services, DNS and DHCP, file shares and Remote Desktop, plus the edition and licensing choices that so often trip people up.
  • Networking — the wiring underneath it all: IP addressing, name resolution, remote access, and the diagnostic habits that turn “the internet is down” into a specific, fixable fault.
  • PC hardware — the physical layer that software people often forget, and the reason he reads a problem from the metal up rather than assuming it is always software.

That range is why Windows Now can cover everything from why there is no sound in Windows 11 to setting up Active Directory on Windows Server without the guides feeling as though they were written by different people with different depths of knowledge.

How he edits Windows Now

As editor, Radhi is responsible for the site’s modern how-to content. Every guide is checked against primary sources — Microsoft Learn and Microsoft Support for Windows, and the official documentation for the server and networking topics — and, just as importantly, against experience: does this actually work on a real machine, in the order we have written it?

He works to a simple standard, set out in full on the Windows Now editorial standards page: primary sources first, no invented figures or credentials, and clearly dated updates as the software changes. Where an exact detail cannot be confirmed, the guide says so plainly rather than guessing. The goal is never to publish the longest article on a topic; it is to publish the one that actually solves the reader’s problem and is true on the day it goes live.

He also stewards the restored windows-now.com archive. The historical posts on the site were written by their original authors between roughly 2003 and 2010; Radhi’s role there is editorial and custodial — restoring them faithfully, keeping the original bylines and dates intact, and making sure the old links keep working — never rewriting someone else’s history under his own name.

What you can expect from his guides

Land on a Windows Now guide and you should hear the voice of someone who has done the thing, not merely read about it. In practice that means:

  • The fix that works most often, first — with the deeper, more involved repairs kept in reserve for the cases that genuinely need them.
  • Plain language over jargon, without dumbing down the parts that actually matter.
  • Honesty about limits — when a problem may not be fixable, when hardware is the real culprit, and when the safe first move is to back up.
  • Steps that are dated and revisited, because Windows, Windows Server and the tools around them never stop moving.

Connect

You can find Muhd Radhi Wahab on LinkedIn at linkedin.com/in/radhiwahab. If you have spotted an error in one of our guides, or want to suggest a topic, the contact details are on our about page — corrections to factual or safety issues are always prioritised.