Windows on Vibhu Bhatnagar — PowerShell & Infrastructure Engineer

Delete Stubborn Files and Folders on Windows

Tue, 28 Apr 2026 04:52:05 +0530

What This Covers

You have a file or folder that won’t delete — Access Denied, locked by the system, or held open by a running process. This covers three methods to force-delete it: Command Prompt, PowerShell, and scheduling deletion at next boot using Task Scheduler with SYSTEM rights.

Before You Start

Run everything as Administrator — right-click CMD or PowerShell → Run as administrator
Set the path variable at the top of each method — everything else uses it
This is irreversible. Double-check the path before you run anything
These methods bypass permission locks — use only on files you own or manage

Steps

Method 1: Command Prompt

set TARGET=C:\path\to\locked-folder

takeown /F %TARGET% /R /A
icacls %TARGET% /grant Administrators:F /T
rd /S /Q %TARGET%

For a single file, replace the last line with:

Cut MCP Token Costs 88% with jmunch-mcp

Fri, 24 Apr 2026 23:36:10 +0530

Introduction

If you run Claude Desktop, Claude Code, or any MCP-enabled client through the day, you are burning tokens you never asked for. Every MCP server call that returns a large payload — GitHub issues, Firecrawl scrapes, search results — dumps the entire response into context whether your agent needed three lines or three hundred thousand tokens worth of data.

jmunch-mcp is a transparent MCP proxy that sits in front of your existing MCP servers and fixes this without changing anything about how you work.

Running PowerShell as the Logged-On User from SYSTEM Context

Thu, 23 Apr 2026 12:00:00 +0530

If you have ever deployed a PowerShell script through Intune, a RMM agent, or Task Scheduler running as SYSTEM, you have hit this wall at least once: the script works perfectly when you run it interactively, but returns nothing — or the wrong thing — when deployed at scale.

The reason is almost always the same. The script is collecting user-specific data. And SYSTEM is not the user.

The Problem: SYSTEM and the User Are Not the Same Session

When Intune or your RMM agent executes a PowerShell script, it runs in the SYSTEM context. SYSTEM is a highly privileged account, but it is completely isolated from the interactive user session happening on the same machine at the same time.

Managing Printer Mappings Across User Profiles with PowerShell

Thu, 23 Apr 2026 10:00:00 +0530

Printer management at scale is one of those problems that looks trivial until you are staring at 200 workstations, each with multiple user profiles, each with their own mapped printers, and a print server migration starting in two days.

Doing it manually is not an option. Doing it via Group Policy works for connected machines but breaks for laptops on VPN, offline profiles, and anyone who mapped printers manually outside GPO. What you actually need is something that understands how Windows stores printer mappings per user, can work on both online and offline profiles, and can be deployed from your RMM in a single script run.