(2026) How to Active Windows and Office Using Powershell - Still Works!

Table of Contents

PowerShell used to be that scary blue window only "IT guys" touched, but honestly, it’s become a lifesaver for regular users lately. One of the biggest use cases I’ve seen popping up is using it to bypass the headache of Windows or Office activation.

If you’ve spent any time on tech forums recently, you’ve probably seen this specific string of code:

irm https://get.activated.win | iex

It looks like gibberish, but it’s actually a pretty clever automation tool. I wanted to break down what it actually does, how to use it, and—more importantly—the "gotchas" I’ve noticed after trying it out myself.

How it works (The Simple Version)

Essentially, this command tells your computer to go to a website, grab a script, and run it instantly. It uses Microsoft’s own activation tools (specifically KMS, which big companies use for thousands of laptops) and adapts them for home use. It’s not "generating" a fake key; it’s more like "tricking" the system into thinking it’s part of a volume license.

It’s perfect for those fresh Windows installs where that annoying "Activate Windows" watermark is staring you in the face, or when Office starts hounding you with pop-ups.

The Step-by-Step

If you’re sitting there with a trial version and want to get it sorted, here’s the workflow. It’s surprisingly fast:

1. Open PowerShell as Admin: This is the most important part. Hit the Start menu, type "PowerShell," right-click it, and choose Run as Administrator. If the window title doesn't say "Administrator," the script will fail.

2. Paste the Code: Copy and paste the command:

   irm https://get.activated.win | iex

   Hit Enter.

3. Pick Your Option: A little menu will pop up in the window. It’s usually as simple as pressing 1 for Windows or 2 for Office.

4. Wait a Minute: You’ll see some text scrolling by. As long as you don't see a wall of red text, it’s working.

5. Check Your Status: Once it says "Permanent Activation" (or similar), head over to your System Settings to confirm the watermark is gone.

The “Real Talk” on Limitations

I’ve used this on a few machines, mostly test boxes and spare laptops. On a fairly new Windows 11 system with a stable connection, it worked almost instantly. I remember glancing at the clock and thinking, “That’s it?”—about half a minute and the system behaved like it was activated.

But it’s not always that clean. I tried the same thing on an older laptop I keep around for experiments. Weak Wi-Fi, old drivers, generally tired hardware. The script just sat there doing nothing. No dramatic failure, no error message—just stalled. That alone tells you something: this kind of method depends heavily on a solid internet connection and a system that isn’t already limping along.

There are a few realities you really shouldn’t ignore before relying on this.

First, this is firmly in gray-area territory. This is not the same as owning a retail key or an OEM license. In practice, Microsoft seems to treat it more like an extended grace period than true ownership. For a personal PC at home or a budget build you’re putting together for basic use, that might be fine. In a work environment, it’s a terrible idea. If a company ever gets audited, nobody wants to explain that activation came from a PowerShell script pulled off the internet. That conversation won’t end well.

Second, Windows updates can undo everything. I’ve seen systems stay fine for months, then a big feature update rolls through and suddenly the watermark is back like nothing ever happened. At that point, you’re reminded this was never meant to be permanent. Sometimes rerunning the method works again. Sometimes it doesn’t, at least not right away. You’re depending on something unofficial to keep up with official changes, and that’s always a gamble.

Security is the other elephant in the room. Running a script directly from the web means you’re trusting code you didn’t write and don’t fully control. Even if a source is widely accepted in online communities, trust is still trust. The safer habit—especially if you’re even a little technical—is to slow down, look at what’s being executed, and understand it at a basic level. Blind execution is how people end up with systems doing things they never agreed to.

Bottom Line

PowerShell itself isn’t the problem. It’s one of the most powerful tools Windows offers, and honestly, it’s a lot cleaner than downloading sketchy “activator” .exe files that are often stuffed with malware. From that angle, this approach can feel like the least bad option.

Still, it’s important to be honest about what this is. It’s a workaround, not a replacement for a real license. Think of it as a temporary bridge—something that makes a low-budget PC usable for everyday tasks while you decide what to do long-term.

If anything, experiences like this are a reminder that convenience, legality, security, and permanence rarely line up perfectly in software. Knowing where a method falls on that spectrum matters just as much as knowing that it exists.