How to edit the hosts file in Windows without permission errors

When testing a website on a new server before public DNS propagation or routing a production domain to a local development environment, the quickest solution is updating the hosts file on your local machine.

On Windows, this file is located in a protected operating system directory. If you simply navigate to the file and double-click to edit it, saving your changes fails with an Access Denied error.

Here is the exact step-by-step procedure to edit and save the file cleanly without permission roadblocks.

1. Where is the Windows hosts file located?#

The hosts file is located at the following absolute path:

C:\Windows\System32\drivers\etc\hosts

Because it resides within the System32 directory tree, modifying it requires elevated Administrator privileges (UAC).

2. Method 1: opening notepad as administrator#

1. Open the Windows Start menu and type Notepad.
2. Right-click the Notepad shortcut and select Run as administrator.
3. Accept the User Account Control (UAC) prompt.
4. In Notepad's menu bar, click File > Open.
5. In the file picker address bar, paste C:\Windows\System32\drivers\etc\ and press Enter.
6. In the bottom right corner of the dialog, change the filter from *Text Documents (\.txt) to All Files (\.\)**.
7. Select the hosts file and click Open.
8. Scroll to the bottom of the file and add your custom mapping in the format IP domain. For example:

   192.168.1.50 mywebsite.com
   192.168.1.50 www.mywebsite.com

1. Press Ctrl + S to save.

The file saves immediately without permission warnings.

3. Method 2: quick terminal shortcut (PowerShell or CMD)#

If you prefer using the command line:

1. Open PowerShell or Command Prompt as Administrator.
2. Run the direct command:

   notepad.exe C:\Windows\System32\drivers\etc\hosts

1. Notepad will launch with elevated permissions, opening the file directly. Make your changes and save with Ctrl + S.

Conclusion: quick validation and practical tips#

After saving the hosts file, changes take effect immediately. No system reboot is required.

To ensure your web browser and network stack pick up the new mapping without cached DNS responses:

1. Flush the local DNS cache in the terminal:

   ipconfig /flushdns

1. Verify resolution by pinging the configured hostname:

   ping mywebsite.com

The output will confirm that traffic resolves directly to the target IP configured in your hosts file.

See also

Infrastructure Case Study (RCA): Investigating a Global Email Routing Outage Post-Migration in cPanel

Infrastructure Debugging DNS resolution inconsistency: split-horizon and race conditions on Linux

Infrastructure Why PowerShell fails to detect the new Outlook in Windows (and how to fix it)

This post is licensed under CC BY-NC.