Error Encountered While Attempting to Read Local Hosts File

An error occurred while trying to access the local hosts file.

• Log Name: System
• Source: DNS Clients Events
• Event ID: 1012

If you encounter Event ID 1012, follow the steps below to address the issue.

Resolve Error Accessing Local Hosts File

When seeing the message about an error while attempting to read the local hosts file, indicated by Event ID 1012 in the Event Viewer on your Windows 11/10 device, consider the following solutions.

1. Verify the filename, type, and location of the hosts file
2. Recreate the hosts file
3. Check the permission settings for the hosts file
4. Flush the DNS cache
5. Repair system files

Let’s delve into each solution in detail.

1] Verify Hosts File Name, Type, and Location

The Hosts file must be named hosts and should not have any file type extension. You should see File in the Properties under Type of file.

It should be found in the C:\Windows\System32\drivers\etc\ directory.

If the file name is altered (like hosts.txt or hosts.ics), you will need to recreate it.

2] Recreate the Hosts File

A corrupted Hosts file may lead to this error. To rectify this, reset the Hosts file to its default state.

Navigate to the Hosts file’s location at C:\Windows\System32\drivers\etc\. Start by renaming the current Hosts file to hosts.bak (you might have to take ownership first).

Next, create a new text file named “hosts“within the %WinDir%\system32\drivers\etc folder. Paste the following content into your new Notepad file:

# Copyright (c) 1993-2009 Microsoft Corp.
#
# This sample HOSTS file is utilized by Microsoft TCP/IP for Windows.
#
# It contains IP address to host name mappings. Each entry should
# be kept on a single line. The first column is for the IP address,
# followed by the host name which should be separated by at least one
# space.
#
# Comments (like these) can also be placed on individual lines
# or after the machine name using a '#' symbol.
#
# For instance:
#
# 102.54.94.97 rhino.acme.com # source server
# 38.25.63.10 x.acme.com # x client host
# Name resolution for localhost is handled within DNS.
# 127.0.0.1 localhost
# : :1 localhost

Make sure to save the file without a. txt extension. If necessary, you can remove it afterward, ensuring the encoding is set to UTF-8 or ANSI.

3] Check Hosts File Permissions

Restrictions on file permissions can prevent access to the hosts file. To troubleshoot this, ensure SYSTEM and Administrators have the right access levels. Follow these steps:

1. Open File Explorer and navigate to C:\Windows\System32\drivers\etc\.
2. Right-click the hosts file and select Properties.
3. In the Security tab, select the appropriate user (likely Administrator) and click Change.
4. Check the box beside Full Control and click Apply > Ok.

After that, restart your computer and see if the issue is resolved.

You might also find it helpful to read about how to Lock, Manage, or Edit the Hosts File.

4] Flush the DNS Cache

If the issue persists after recreating the Hosts file, consider flushing the DNS cache. This can help fix connectivity problems, refresh DNS records, and enhance network performance. It will also let your system notice the changes made. To perform this action, follow these steps:

1. Access Start, type “Command Prompt” , and select Run as administrator.
2. Accept the User Account Control (UAC) prompt by clicking Yes.
3. Enter ipconfig /flushdns and press Enter.

Check if the problem continues after this step.

5] Repair System Files

Problems with corrupted Windows images and system files can lead to multiple issues, including those associated with the local hosts file. To fix this, you can run commands from the Command Prompt as an administrator.

sfc /scannow

Wait for the SFC tool to scan and repair your system. If it runs into issues, execute DISM as a follow-up.

We trust these suggested solutions will resolve your issue.

How to Flush DNS Cache in Hosts File?

To flush the DNS cache in Windows, run Command Prompt as an administrator and execute ipconfig /flushdns. For macOS users, use sudo killall -HUP mDNSResponder in the Terminal. These commands will clear the DNS cache, allowing your system to rebuild it from the ground up.

How to Test if the Hosts File is Functioning?

A reliable method to test the functionality of the Hosts file is to ping a domain name. If you’ve added a new host entry, you can execute ping domain-name.com, and it should translate to the corresponding IP address. A successful ping confirms that the hostname has been correctly added.