PowerShell脚本更新hosts文件时遇占用错误致文件清空及catch块失效问题咨询

Answers to Your Questions & Fixed Script #

Let's tackle each of your questions one by one, then provide a revised script that addresses all these issues:

1. How to prevent the hosts file from being emptied?

The core issue is that Set-Content truncates (empties) the file before attempting to write new content. If the write fails due to a lock, you're left with an empty file. The safest fix is to:

• First write the modified content to a temporary file
• Only replace the original hosts file once the temporary write succeeds
  This way, the original file remains intact unless the new content is fully saved.

2. Why does Set-Content empty the file even when it can't access it for writing?

Set-Content follows this execution flow:

1. Opens the target file in truncate mode (which immediately clears all existing content)
2. Attempts to write the new content to the now-empty file
   When another process locks the file, step 1 (truncation) may still succeed, but step 2 (writing) fails. This leaves you with an empty file because the truncation happened before the lock was detected.

3. Why didn't the catch block capture the exception?

By default, PowerShell treats many cmdlet errors as non-terminating errors, which don't trigger try/catch blocks. The Set-Content error you're seeing falls into this category. To fix this, you need to force the error to be a terminating one by adding -ErrorAction Stop to the Set-Content command, or setting $ErrorActionPreference = 'Stop' at the top of your script. This tells PowerShell to treat all errors as terminating, so they'll be caught by your catch block.

4. Why is this issue intermittent, and do Windows processes briefly lock the hosts file?

Yes! Several Windows system processes regularly access or lock the hosts file, leading to intermittent locks:

• DNS Client Service (dnscache): Checks the hosts file periodically to update DNS cache, which can briefly lock it.
• Windows Defender/antivirus: Real-time protection may scan the hosts file when changes are detected, temporarily locking it.
• Browser/network apps: Some applications cache DNS records and may read the hosts file occasionally, leading to short locks.
  These operations happen at unpredictable times, hence the intermittent nature of your error.

Revised PowerShell Script #

This script fixes all the above issues:

• Uses a temporary file to avoid emptying the original hosts file on failure
• Ensures errors are caught with terminating error settings
• Includes a retry mechanism to handle intermittent locks
• Improves error handling throughout

param([switch]$Elevated)

$ErrorActionPreference = 'Stop'

function Test-Admin {
    $currentUser = New-Object Security.Principal.WindowsPrincipal $([Security.Principal.WindowsIdentity]::GetCurrent())
    $currentUser.IsInRole([Security.Principal.WindowsBuiltinRole]::Administrator)
}

if (-not (Test-Admin)) {
    if ($elevated) {
        Write-Error "Failed to elevate privileges. Aborting."
    } else {
        Start-Process powershell.exe -Verb RunAs -ArgumentList ('-noprofile -noexit -file "{0}" -elevated' -f $myinvocation.MyCommand.Definition)
    }
    exit
}

function UpdateHosts {
    param ($hostName, $ipAddress)
    
    $hostsPath = "C:\WINDOWS\system32\drivers\etc\hosts"
    $tempPath = "$hostsPath.tmp"
    $maxRetries = 3
    $retryDelay = 1000 # milliseconds

    for ($i = 1; $i -le $maxRetries; $i++) {
        try {
            # Read the current hosts content
            $strHosts = Get-Content $hostsPath -Raw
            if ([string]::IsNullOrEmpty($strHosts)) {
                Write-Error "Hosts file is empty or unreadable."
                return
            }

            # Modify the content
            $updatedContent = $strHosts -replace "[\d]+\.[\d]+\.[\d]+\.[\d]+ $hostName", "$ipAddress $hostName"

            # Write to temporary file first
            $updatedContent | Set-Content -Path $tempPath -ErrorAction Stop

            # Replace original hosts file with temporary file (atomic operation)
            Move-Item -Path $tempPath -Destination $hostsPath -Force -ErrorAction Stop

            Write-Host "Successfully updated hosts file for $hostName to $ipAddress"
            return
        }
        catch {
            Write-Warning "Attempt $i failed: $_"
            if ($i -eq $maxRetries) {
                Write-Error "All $maxRetries attempts failed. Could not update hosts file."
                # Clean up temporary file if it exists
                if (Test-Path $tempPath) { Remove-Item $tempPath -Force }
                return
            }
            # Wait before retrying
            Start-Sleep -Milliseconds $retryDelay
        }
    }
}

$ipAddress = "127.0.0.1"
UpdateHosts -hostName "local.pap360.com" -ipAddress $ipAddress

内容的提问来源于stack exchange，提问作者neubert