• Thread Author
Something strange is happening on the C: drive of millions of PCs worldwide, and it’s not a ghost in the machine. If you’ve recently updated your Windows 11 system and discovered an unfamiliar, empty folder named ‘inetpub’ sitting quietly in the corner like a wallflower at a prom, you’re not alone. The sudden presence of this directory has sparked confusion, debate, and—because it’s the internet—wild conspiracy theories across social forums and tech blogs. But before you pull up your sleeves and get busy with the delete key, here’s exactly why Microsoft wants you to leave that mysterious folder right where it is.

A Folder Appears: The Curious Case of ‘inetpub’​

Let’s set the scene: It’s the morning after you install the April 2025 cumulative update for Windows 11, version 24H2. You’re just poking around File Explorer, maybe looking for some old family photos or trying to remember where you stashed that overdue spreadsheet. Then you spot something new—an ‘inetpub’ folder, empty as your soul after a full day of Zoom calls. Even more intriguing, you don’t remember ever setting up a web server, or having any intention to become the next Jeff Bezos of your local network.
The impulse to delete anything that wasn’t there yesterday is understandable. After all, good cyber hygiene means keeping your system free of clutter and random files. However, unlike that suspicious .exe you found lurking in your Downloads folder back in 2017, the ‘inetpub’ folder is not an invader; it’s the exact opposite.

Not a Bug, but a Feature (Really)​

Microsoft, in a rare moment of clarity, has confirmed that the creation of this folder is no accident. This isn’t the programming equivalent of dropping your keys in the hallway and hoping nobody notices. The presence of ‘inetpub’ on your system drive is 100% intentional and, surprisingly, not even related to whether you have IIS—Internet Information Services, Microsoft’s own web server suite—installed.
The company spells it out in classic corporate speak: “After installing the updates listed in the Security Updates table for your operating system, a new %systemdrive%\inetpub folder will be created on your device. This folder cannot be deleted regardless of whether Internet Information Services (IIS) is active on the target device. This behavior is part of a change that improves protection and does not require any action from IT administrators and end users.”
Translated from Microsoft-ese: this folder is your PC’s new bouncer, and even the owner can’t kick it out.

Why Does an Empty Folder Matter?​

Why would you need an empty directory, especially one with a name synonymous with web hosting? Here’s where things get interesting. Security researchers are no strangers to the weird and wonderful ways attackers exploit seemingly innocent system quirks. One such trick is a “folder squatting” attack, where a bad actor creates a directory in a coveted system location, like the proverbial dog on your freshly cleaned carpet.
This might allow them to sneak in malicious files, redirect important data writes, or escalate their privileges, especially if the folder is missing and the system—mistakenly or otherwise—creates it with weak security settings. Microsoft’s preventative approach? Make sure the folder always exists, to eliminate that potential attack scenario. Leaving the folder there, even empty, ensures that updates and other system operations don’t inadvertently leave a security hole big enough for a hacker to drive a proverbial bus through.

IIS? No IIS? It’s Irrelevant​

Previously, the mere sight of an 'inetpub' directory signaled that a machine was running IIS. The rise of remote work and the proliferation of web-enabled apps ensured that only administrators and advanced users ever even noticed its presence.
But now, Microsoft's move firmly decouples the folder from the service. Regardless of whether you spin up web apps on your lunch break or wouldn’t know a .NET Core runtime if it danced across your desktop, you get the folder. The reason is simple: bad actors don’t care whether you intend to run a web server. They’ll exploit any system that provides an opportunity.

"It’s My Drive, and I’ll Clean If I Want To!"​

We get it—digital minimalism is a real thing. There’s something cathartic about pruning away old folders, deleting redundant files, and banishing everything extraneous to a well-organized digital bin. The presence of untouchable, unexplained files can be maddening. But in the case of ‘inetpub,’ your best move is to leave it untouched.
Not only is manually deleting the folder unlikely to be successful (Microsoft has set the permissions to make deletion nearly impossible without serious effort), but removing it could create a system state that’s less secure—undoing the hard work of Microsoft’s army of security engineers.
Consider it an extra lock on the door: maybe a little unsightly, perhaps even unnecessary most of the time, but the one time you desperately need it, you’ll be glad it’s there.

A Brief History of System Folders Gone Rogue​

If this sounds like déjà vu, you’re not wrong. Microsoft has a long history of dropping mysterious folders on users for deeply technical, if not immediately obvious, reasons. The 'Windows.old' directory is infamous for swelling with gigabytes of data after major updates. The ‘$WINDOWS.~BT’ and ‘$WINDOWS.~WS’ directories appear, do their inscrutable dance during upgrades, and vanish (if you’re lucky) as silently as they arrived.
Each time, users flood forums, launch tech support requests, and sometimes even create elaborate rituals (or scripts) to get rid of what they see as digital detritus. This time, though, Microsoft is being proactive—sort of. They’re telling you upfront: “Don’t delete that folder.”

The Anatomy of ‘inetpub’: More Than Just an Empty Shell​

While at first glance the folder appears devoid of content, the absence of files is, in fact, a feature, not a bug. The magic lies in its metadata and Windows’ internal bookkeeping.
By preemptively creating ‘inetpub’ with the correct permissions during the update, Microsoft ensures that any future installations—say, if you do decide to live out your dreams as an amateur web admin—inherit the expected security posture. No more accidental world-readable web roots, no more misconfigured permissions that let attackers stroll in uninvited.
This is one example of “defense in depth.” By removing even seemingly innocuous opportunities for attack, Microsoft hopes to close off as many avenues as possible, even ones most users might never appreciate.

Conspiracy Theories and Other Tall Tales​

As with any unexplained change in software (especially from a company with Microsoft’s “colorful” history), the internet has responded with the gusto you’d expect. Some, tongue firmly in cheek, suggest the folder is a sign of a secret government backdoor. Others posit it’s the first step in some Microsoft plot to turn every desktop into a locked-down, SaaS-only paradise.
Rest assured: the ‘inetpub’ folder is as bland as they come. If it harbored any secret data, Microsoft wouldn’t put it in plain sight with a name that’s a literal signpost for system administrators everywhere.

What’s Next? Living Peacefully With ‘inetpub’​

So, what do you do now that this little digital squatter has moved in? Absolutely nothing. Microsoft isn’t requiring any action from users or IT administrators. The folder sits quietly. It doesn’t use up any appreciable resources. It doesn’t run any processes, phone home, or muck about with your registry.
The official advice is simple: let it be. After all, fighting with your OS over an empty directory is like arguing with a cat. It doesn’t care, it won’t change, and the odds are you’ll just end up exhausted.

For the Technically Curious: A Closer Look at Security Strategy​

To truly appreciate why this matters, you need to slip into the mindset of an attacker. Many privilege escalation exploits hinge on exploiting missing directories or files with privileged names. If a system-level folder is missing, and a low-privilege process creates it before the OS or an admin does, the resulting folder might have dangerously lax permissions.
By making sure key folders like ‘inetpub’ are always in place, Microsoft eliminates an entire class of privilege escalation attacks in one fell swoop. It’s a textbook example of what security pros mean by “least privilege”—giving each user, process, and directory only what’s required, and nothing more.
It’s also a gentle nod to IT departments everywhere: yes, even home users are getting enterprise-class defense tactics. Whether you like it or not.

IT Admins: What Should You Do?​

For once, there’s little for IT admins to actually administer. No registry keys to tweak, no group policies to set, no scripts to run at startup. Microsoft isn’t asking you to audit, maintain, or tweak the folder in any way. In fact, any attempt to “fix” this change will likely result in a call from your favorite Redmond support desk.
If you’re building images or deploying updates at scale, double-check your custom cleanup routines. Automated scripts that attempt to purge empty directories might now log an endless stream of errors (and those red lines on your dashboard are rarely cause for celebration).

What If You Really, Really Want It Gone?​

Let’s face it, there’s always someone who can’t sleep at night knowing there’s an empty folder out there with their name (well, Microsoft’s name) on it. Sure, with enough registry hacking, permission-busting, and general digital mayhem, it’s possible to delete ‘inetpub’. But the next time your system updates, odds are it’ll come back—like that clown statue in the horror movie that you swear you never bought.
Worse, removing it could inadvertently lower your system’s defenses. Unless you really want a front-row seat to “What Not to Do With Windows Security,” let this folder coexist with your healthy system paranoia.

Looking to the Future: Microsoft’s New Approach​

In a world where every software update has the potential to trigger panic, Microsoft’s decision to openly discuss this change is welcome, if a little overdue. The company is learning, albeit slowly, the value of transparency with its user base.
We can reasonably expect this pattern to continue. The days of opaque patch notes (“Various bug fixes and improvements”) are, hopefully, numbered. The next time Microsoft decides to drop a new folder, system file, or service in your lap, perhaps they’ll actually tell us why—with minimal gibberish.

The End of the Empty Folder Panic?​

Will the internet learn to stop worrying and love the ‘inetpub’ folder? Maybe. More likely, it’ll fade into the background hum of Windows oddities—like Cortana, Edge, and that one weird driver update that never seems to go away.
But perhaps that’s the real victory here. If the price of a more secure PC is a single empty folder quietly lurking on your C: drive, most of us can live with the trade-off. After all, compared to ransomware, rootkits, and relentless phishing attacks, an empty folder is the least of our worries.
So the next time you’re poking around in File Explorer, give ‘inetpub’ a nod of respect. It’s a silent sentinel, warding off threats you’ll hopefully never see. And while it may not have the glamour of a brand-new feature, or the sparkle of a cutting-edge app, it might just be the most important folder you’ll never use.

Final Thoughts: Folders, Fear, and the Future of Security​

Software engineering is a game of cat and mouse, and the best moves are the ones users don’t have to think about. Security improvements that don’t break workflows, don’t annoy users, and—ideally—don’t even get noticed are a rare and beautiful thing.
The ‘inetpub’ story isn’t really about a folder, or even about IIS. It’s about the evolving nature of cybersecurity: preempting the next clever attack before it ever sees the light of day, no matter how strange the solution might look. Sometimes, the best defense is the one you never have to think about. And if that means embracing an empty folder with open arms, well, stranger things have happened in Windows.
Go ahead—leave it there. Your system just got a bit safer, whether you noticed or not.

Source: TechNave Microsoft warns you not to delete this file in the latest Windows 11 update | TechNave
 
Last edited:
The recent Windows 11 update released in April 2025 has introduced a curious yet significant change: the automatic creation of an empty folder named "inetpub" in the system drive's root directory, typically C:\inetpub. Although it may look like a harmless leftover or unnecessary clutter, this folder is deeply tied to a critical security patch addressing a serious vulnerability in the Windows operating system. At first glance, the inetpub folder might confuse both casual users and IT professionals who neither run web servers nor expect such a directory on a non-server Windows PC. However, understanding the rationale behind this folder's presence and the security implications is crucial for maintaining system integrity and protecting against potential exploits.

The Origin and Purpose of the 'inetpub' Folder​

Traditionally, the "inetpub" folder is a designated directory for Microsoft's Internet Information Services (IIS), which is a Windows web server platform. On systems with IIS enabled, this folder hosts website content, web application files, log files, and scripts necessary for web server operation. Usually, this directory exists only if IIS is installed and activated by the user or system administrator.
However, with the April 2025 cumulative update (notably KB5055523), Microsoft has mandated the creation of this folder on all Windows 11 installations — even those without IIS enabled. This design decision stemmed from an important security requirement rather than feature deployment. The folder acts as a protected container integral to the mitigation of vulnerability CVE-2025-21204, a privilege escalation risk connected to Windows Update's handling of symbolic links.

Understanding CVE-2025-21204 — The Vulnerability​

CVE-2025-21204 concerns the improper processing of symbolic links (symlinks) within the Windows Update servicing stack. Symbolic links are file-system objects that reference other files or directories. When mishandled, they provide an attacker an opportunity to manipulate system operations by redirecting file access or modification to unauthorized locations. Without adequate checks, malicious actors could exploit symlink handling to gain elevated privileges or sabotage security-critical files.
Specifically, this vulnerability allowed local attackers — requiring only standard user access — to interfere with the Windows Update process by replacing directories with symlinks or directory junctions. Such manipulation could cause Windows Update to fail, roll back, or worse, open doors for privilege escalation. Microsoft’s response was to create a hardened, system-owned directory, the inetpub folder, which could safely anchor critical files during the update process and prevent symlink spoofing attacks.

How the Vulnerability Manifests: The 'inetpub' Folder Exploit​

Security researcher Kevin Beaumont revealed a notable attack vector exploiting the inetpub folder. Despite inetpub's system-trusted status, Windows servicing stack doesn't verify if this directory is a symbolic link or junction. This oversight allows a non-admin user on the PC to run a simple command that replaces the inetpub folder with a directory junction pointing to any arbitrary file, such as Notepad.exe.
For example, the attacker could run:
mklink /J C:\inetpub C:\Windows\System32\notepad.exe
This command tricks Windows Update into interacting with a file, not a directory, causing the update process to misbehave, ultimately resulting in a failure or rollback of updates. Since the servicing stack runs with SYSTEM privileges, this discrepancy can be exploited without administrative rights, representing a serious denial-of-service risk and potentially facilitating further exploits.

Security Implications and Risks​

The key security risk is that any user account, even without admin privileges, can subvert the Windows Update process by modifying the inetpub folder's target location through junction points. Given that Windows Update is fundamental for delivering security patches and system improvements, interfering with its operation can leave computers exposed to other vulnerabilities, malware, and attacks.
This vulnerability highlights an underlying challenge in Windows’ handling of symbolic links and trusted system folders — the exploitation of implicit trust and insufficient verification in system-critical paths.

Temporary Mitigations Until a Microsoft Fix​

Microsoft has yet to release an official fix or patch addressing this residual vulnerability stemming from the inetpub folder's treatment. However, users and administrators can implement a powerful temporary mitigation by locking down permissions on the inetpub folder. The objective is to ensure only SYSTEM and TrustedInstaller accounts have write or delete permissions on the folder, effectively blocking any non-system process, including those run by admin or standard users, from modifying the folder structure or creating directory junctions.
The following summarizes the steps to secure the inetpub folder’s permissions:
  • Navigate to C:\inetpub in File Explorer.
  • Right-click on the folder and select Properties.
  • Go to the Security tab and click Advanced.
  • Click Disable inheritance at the bottom and choose Remove all inherited permissions when prompted.
  • Click Add, then Select a principal, enter SYSTEM, and confirm.
  • Assign Full Control permissions to SYSTEM.
  • Repeat the above step for NT SERVICE\TrustedInstaller to ensure TrustedInstaller can manage the folder.
  • Confirm all changes and exit.
With these restrictive permissions, standard users and even administrators cannot tamper with the inetpub directory, effectively preventing the junction point exploitation. Windows Update and system processes can still read and write as needed since SYSTEM and TrustedInstaller retain full control.
Should users wish to revert these permission changes, especially if update failures occur, they can re-enable inheritance and remove the manually added permission entries to restore default behavior.

Challenges and User Experience Considerations​

The inetpub folder saga exemplifies the difficulties in patching operating systems against evolving and sometimes subtle vulnerabilities. While created as a safeguard, the inetpub folder itself introduced a novel attack vector due to the way Windows Update trusts this directory without sufficient verification.
This scenario reflects a broader pattern where patching one security vulnerability inadvertently exposes another, necessitating layered protections and careful design to avoid whack-a-mole cybersecurity battles.
Additionally, the folder's unexpected presence on systems without IIS caused confusion among users and IT professionals alike. Microsoft's explicit advisories warn users not to delete the folder since doing so would disable the security patch and expose the system to the original symbolic link vulnerability.
For those who have deleted the inetpub folder accidentally or intentionally, Microsoft recommends restoring it by enabling IIS temporarily:
  • Open Control Panel and navigate to Programs and Features.
  • Click on Turn Windows features on or off.
  • Check Internet Information Services (IIS) and apply changes to recreate the inetpub folder.
  • After the folder is restored, IIS can be disabled without deleting the inetpub folder again.
Alternatively, reinstalling the relevant security update will also restore the folder with appropriate permissions.

Broader Reflections on Windows Security​

This situation underscores the increasing complexity of Windows security architecture, where protection mechanisms often involve intricate file system permissions, symbolic link management, and legacy components repurposed for defense. The inetpub folder now serves as an invisible sentinel guarding against a specific exploit pattern, even on systems where it seemingly does nothing.
It also reveals challenges in balancing system cleanliness and user expectations with layered security. Empty system folders that appear redundant or extraneous may be crucial defensive elements hidden from typical user interactions.
Critically, the inetpub case highlights the importance of user education and communication from vendors. Lack of clear documentation initially spurred confusion and misguided deletion of the folder, potentially exposing users to risk. Moving forward, transparency around such "behind-the-scenes" components in Windows updates will be vital to help users and administrators maintain security without unnecessary alarm.

Conclusion​

The appearance of the "inetpub" folder on Windows 11 systems following the April 2025 update is not arbitrary but a vital component of Microsoft's ongoing security efforts. Intended to solidify protection against a symbolic link privilege escalation vulnerability (CVE-2025-21204), the folder functions as a trusted platform directory crucial for Windows update processes. Yet, this design introduced a vulnerability whereby non-admin users can exploit junction points to disrupt updates.
Until an official fix arrives from Microsoft, users and IT administrators can safeguard their systems by restricting write and delete permissions on the inetpub folder to SYSTEM and TrustedInstaller. Avoid deleting the inetpub folder and follow Microsoft’s restoration procedure if necessary.
This episode is a compelling illustration of modern Windows security’s evolving nature—a blend of legacy components repurposed, layered defenses implemented, and the perpetual cat-and-mouse game between vulnerabilities and patches. For users, it stresses the value of staying informed and cautious regarding seemingly minor system changes that carry substantial security weight behind the scenes.

Sources:
  • MakeTechEasier: Windows inetpub Folder Vulnerability and Temporary Solutions
  • WindowsForum.com community insights and official Microsoft update advisories

Source: Windows 11's New Inetpub Folder is Hackable. Try This Temporary Fix - Make Tech Easier