No meu caso, esse problema foi causado por uma rota de rede inválida (especificamente, um NextHop incorreto). Aqui está a minha implementação de patch, inspirada pelo comentário @ gonzales-gokhan acima:
$destinationPrefix = '169.254.169.254/32'
$defaultNetIPConfig = @(Get-NetIPConfiguration | Sort-Object -Property 'InterfaceIndex')[0]
try {
if (@(Get-NetRoute -DestinationPrefix $destinationPrefix -PolicyStore 'ActiveStore').Length) {
Remove-NetRoute -DestinationPrefix $destinationPrefix -PolicyStore 'ActiveStore' -Confirm:$false -ErrorAction SilentlyContinue
Write-Host 'network route for instance metadata removed from ActiveStore'
}
if (@(Get-NetRoute -DestinationPrefix $destinationPrefix -PolicyStore 'PersistentStore').Length) {
Remove-NetRoute -DestinationPrefix $destinationPrefix -PolicyStore 'PersistentStore' -Confirm:$false -ErrorAction SilentlyContinue
Write-Host 'network route for instance metadata removed from PersistentStore'
}
New-NetRoute -DestinationPrefix $destinationPrefix -InterfaceIndex $defaultNetIPConfig.InterfaceIndex -NextHop $defaultNetIPConfig.IPv4DefaultGateway.NextHop -RouteMetric 1 -ErrorAction Stop
Write-Host 'network route for instance metadata added.'
}
catch {
Write-Host ('failed to add network route for instance metadata. {0}' -f $_.Exception.Message)
}