{"id":353757,"date":"2024-09-18T11:02:46","date_gmt":"2024-09-18T11:02:46","guid":{"rendered":"https:\/\/www.ninjaone.com\/script-hub\/diagnosi-dei-problemi-di-windows-update\/"},"modified":"2024-10-13T19:04:04","modified_gmt":"2024-10-13T19:04:04","slug":"diagnosi-dei-problemi-di-windows-update","status":"publish","type":"script_hub","link":"https:\/\/www.ninjaone.com\/it\/script-hub\/diagnosi-dei-problemi-di-windows-update\/","title":{"rendered":"Guida alla diagnosi dei problemi di Windows Update tramite PowerShell"},"content":{"rendered":"

La diagnosi dei problemi di Windows Update pu\u00f2 essere un compito noioso per i professionisti IT, soprattutto quando si gestiscono pi\u00f9 macchine. Ritardi o errori nel processo di aggiornamento possono portare a vulnerabilit\u00e0 di sicurezza, problemi di conformit\u00e0 e instabilit\u00e0 generale del sistema.<\/p>\n

Lo script PowerShell<\/a> fornito offre un approccio semplificato\u00a0per diagnosticare e risolvere i problemi comuni di Windows Update<\/strong>, garantendo che i sistemi rimangano aggiornati e sicuri. In questo articolo si approfondiscono le funzionalit\u00e0 dello script\u00a0per la diagnosi dei problemi di Windows Update opera eseguendo una serie di controlli sui principali componenti e servizi di Windows Update, e si discute di come lo script possa essere uno strumento prezioso per i professionisti IT e i Managed Service Provider (MSP)<\/a>.<\/p>\n

Background<\/strong><\/h2>\n

Windows Update \u00e8 un componente fondamentale per mantenere l\u2019integrit\u00e0 e la sicurezza di un sistema basato su Windows. Tuttavia, diversi fattori possono ostacolarne il buon funzionamento, dalle configurazioni errate dei servizi ai problemi di rete. I professionisti IT devono spesso affrontare l’arduo compito di risolvere questi problemi manualmente, processo che pu\u00f2 richiedere molto tempo ed essere soggetto a errori umani<\/a>.<\/p>\n

Lo script PowerShell per la diagnosi dei problemi di Windows Update opera eseguendo una serie di controlli sui principali componenti e servizi di Windows Update fornito affronta questa sfida automatizzando il processo di diagnostica, e assicurando che i problemi pi\u00f9 comuni vengano identificati e risolti rapidamente. Utilizzando questo script, i team IT possono mantenere l’integrit\u00e0 del sistema, ridurre i tempi di inattivit\u00e0<\/a> e migliorare l’efficienza complessiva<\/a>.<\/p>\n

Lo script per la diagnosi dei problemi di Windows Update:<\/h2>\n
#Requires -Version 5.1\r\n\r\n<#\r\n.SYNOPSIS\r\n    Diagnose Windows Update issues.\r\n.DESCRIPTION\r\n    Checks that CryptSvc, and bits or running or not\r\n    Checks that wuauserv is running and the startup type is set correctly.\r\n    Checks WaaSMedic plugins doesn't have issues. (Only applies to OS Build Version is greater than 17600).\r\n    Checks if NTP is setup.\r\n    Checks Windows Update logs for any errors in the last week.\r\n\r\n.EXAMPLE\r\n    (No Parameters)\r\n    ## EXAMPLE OUTPUT WITHOUT PARAMS ##\r\n    [Info] Last checked for updates on 4\/29\/2023\r\n    [Issue] Windows Update has not checked for updates in over 30 days.\r\n\r\nPARAMETER: -ResultsCustomField WindowsUpdate\r\n    Saves results to a multi-line custom field.\r\n.EXAMPLE\r\n    -ResultsCustomField WindowsUpdate\r\n    ## EXAMPLE OUTPUT WITH ResultsCustomField ##\r\n    [Info] Last checked for updates on 4\/29\/2023\r\n    [Issue] Windows Update has not checked for updates in over 90 days.\r\n.OUTPUTS\r\n    None\r\n.NOTES\r\n    Minimum OS Architecture Supported: Windows 10, Windows Server 2016\r\n    Release Notes: Initial Release\r\nBy using this script, you indicate your acceptance of the following legal terms as well as our Terms of Use at https:\/\/www.ninjaone.com\/terms-of-use.\r\n    Ownership Rights: NinjaOne owns and will continue to own all right, title, and interest in and to the script (including the copyright). NinjaOne is giving you a limited license to use the script in accordance with these legal terms. \r\n    Use Limitation: You may only use the script for your legitimate personal or internal business purposes, and you may not share the script with another party. \r\n    Republication Prohibition: Under no circumstances are you permitted to re-publish the script in any script library or website belonging to or under the control of any other software provider. \r\n    Warranty Disclaimer: The script is provided \u201cas is\u201d and \u201cas available\u201d, without warranty of any kind. NinjaOne makes no promise or guarantee that the script will be free from defects or that it will meet your specific needs or expectations. \r\n    Assumption of Risk: Your use of the script is at your own risk. You acknowledge that there are certain inherent risks in using the script, and you understand and assume each of those risks. \r\n    Waiver and Release: You will not hold NinjaOne responsible for any adverse or unintended consequences resulting from your use of the script, and you waive any legal or equitable rights or remedies you may have against NinjaOne relating to your use of the script. \r\n    EULA: If you are a NinjaOne customer, your use of the script is subject to the End User License Agreement applicable to you (EULA).\r\n#>\r\n\r\n[CmdletBinding()]\r\nparam (\r\n    [int]$Days = 30,\r\n    [string]$ResultsCustomField\r\n)\r\n\r\nbegin {\r\n    if ($env:Days) {\r\n        $Days = $env:Days\r\n    }\r\n    if ($env:resultscustomfield -notlike \"null\") {\r\n        $ResultsCustomField = $env:resultscustomfield\r\n    }\r\n    function Test-IsElevated {\r\n        $id = [System.Security.Principal.WindowsIdentity]::GetCurrent()\r\n        $p = New-Object System.Security.Principal.WindowsPrincipal($id)\r\n        $p.IsInRole([System.Security.Principal.WindowsBuiltInRole]::Administrator)\r\n    }\r\n    function Test-WaaSMedic {\r\n        [CmdletBinding()]\r\n        param()\r\n        $WaaS = 0\r\n        Try {\r\n            $WaaS = New-Object -ComObject \"Microsoft.WaaSMedic.1\"\r\n        }\r\n        Catch {\r\n            Write-Host \"WaaS Medic Support: No\"\r\n        }\r\n    \r\n        Try {\r\n            if ($WaaS -ne 0) {\r\n                Write-Host \"WaaS Medic Support: Yes\"\r\n                $Plugins = $WaaS.LaunchDetectionOnly(\"Troubleshooter\")\r\n    \r\n                if ($Plugins -eq \"\") {\r\n                    [PSCustomObject]@{\r\n                        Id        = \"WaaSMedic\"\r\n                        Detected  = $false\r\n                        Parameter = @{\"error\" = $Plugins }\r\n                    }\r\n                }\r\n                else {\r\n                    [PSCustomObject]@{\r\n                        Id        = \"WaaSMedic\"\r\n                        Detected  = $true\r\n                        Parameter = @{\"error\" = $Plugins }\r\n                    }\r\n                    \"Plugins that might have errors: \" + $Plugins | Out-String | Write-Host\r\n                }\r\n            }\r\n        }\r\n        Catch {\r\n            Write-Host \"WaaS Medic Detection: Failed\"\r\n        }\r\n        Finally {\r\n            # Release COM Object if we aren't running test cases\r\n            if (-not $env:NinjaPesterTesting) {\r\n                [System.Runtime.Interopservices.Marshal]::ReleaseComObject($WaaS) | Out-Null\r\n            }\r\n        }\r\n    }\r\n    function Get-TimeSyncType {\r\n        [string]$result = \"\"\r\n        [string]$registryKey = \"HKLM:\\SYSTEM\\CurrentControlSet\\Services\\W32Time\\Parameters\"\r\n        [string]$registryKeyName = \"Type\"\r\n    \r\n        if ((Test-Path $registryKey -ErrorAction SilentlyContinue)) {\r\n            $registryEntry = Get-Item -Path $registryKey -ErrorAction SilentlyContinue\r\n            if ($null -ne $registryEntry) {\r\n                return Get-ItemPropertyValue -Path $registryKey -Name $registryKeyName\r\n            }\r\n        }\r\n        return $result\r\n    }\r\n    function Test-ConnectedToInternet {\r\n        $NLMType = [Type]::GetTypeFromCLSID('DCB00C01-570F-4A9B-8D69-199FDBA5723B')\r\n        $INetworkListManager = [Activator]::CreateInstance($NLMType)  \r\n        return ($INetworkListManager.IsConnectedToInternet -eq $true)\r\n    }\r\n    function Get-ComponentAndErrorCode([string]$msg) {\t\r\n        $Codes = [regex]::matches($msg, \"0x[a-f0-9a-f0-9A-F0-9A-F0-9]{6,8}\")\r\n        if ($Codes.count -gt 1) {\r\n            $CodeList = \"\"\r\n            # there can be more than one error code can be returned for the same component at once\r\n            foreach ($Code in $Codes) {\r\n                $CodeList += \"_\" + $Code\r\n            }\r\n            return $CodeList\r\n        }\r\n        else {\r\n            return $Codes[0].Value\r\n        }\r\n    }\r\n    function Get-DatedEvents($EventLog) {\r\n        $DatedEvents = @()\r\n        if ($null -eq $EventLog) {\r\n            return $null \r\n        }\r\n        foreach ($Event in $EventLog) {\r\n            #$eventMsg = $event.Message\r\n            $DatedEvents += $Event.Message\r\n        }\r\n        return $DatedEvents\r\n    }\r\n    function Get-SystemEvents($EventSrc, $Time) {\r\n        $Events = Get-WinEvent -ProviderName $EventsSrc -ErrorAction 0 | Where-Object { ($_.LevelDisplayName -ne \"Information\") -and (($_.Id -eq 20) -or ($_.Id -eq 25)) -and ($_.TimeCreated -gt $Time) }\r\n        return $Events\r\n    }\r\n    function Get-HasWinUpdateErrorInLastWeek([switch]$AllLastWeekError) {\r\n        $Events = @()\r\n        $EventsSrc = \"Microsoft-Windows-WindowsUpdateClient\"\r\n        $startTime = (Get-Date) - (New-TimeSpan -Day 8)\r\n        $wuEvents = Get-SystemEvents $EventsSrc $startTime\r\n        if ($null -eq $wuEvents) {\r\n            return $null\r\n        }\r\n        $Events += Get-DatedEvents $wuEvents\r\n        $LatestError = Get-ComponentAndErrorCode $Events[0]\r\n        $ErrorList = @{}\r\n        $ErrorList.add(\"latest\", $LatestError)\r\n        if ($AllLastWeekError) {\r\n            foreach ($str in $Events) {\r\n                $ECode = Get-ComponentAndErrorCode $str\r\n                if ($null -ne $ECode -and !$ErrorList.ContainsValue($ECode)) {\r\n                    $ErrorList.add($ECode, $ECode)\r\n                }\r\n            }\r\n        }\r\n        return $ErrorList\r\n    }\r\n    Function Get-LocalTime($UTCTime) {\r\n        $strCurrentTimeZone = (Get-CimInstance -ClassName Win32_TimeZone).StandardName\r\n        # If running test cases return current date\r\n        if ($env:NinjaPesterTesting) {\r\n            return Get-Date\r\n        }\r\n        $TZ = [System.TimeZoneInfo]::FindSystemTimeZoneById($strCurrentTimeZone)\r\n        Return [System.TimeZoneInfo]::ConvertTimeFromUtc($UTCTime, $TZ)\r\n    }\r\n    $IssuesFound = $false\r\n    $Log = [System.Collections.Generic.List[String]]::new()\r\n}\r\nprocess {\r\n    if (-not (Test-IsElevated)) {\r\n        Write-Error -Message \"Access Denied. Please run with Administrator privileges.\"\r\n        exit 1\r\n    }\r\n\r\n    if (-not $(Test-ConnectedToInternet)) {\r\n        Write-Host \"[Issue] Windows doesn't think it is connected to Internet.\"\r\n        $IssuesFound = $true\r\n    }\r\n\r\n    # Check CryptSvc amd bits services\r\n    $Service = Get-Service -Name CryptSvc\r\n    if ($Service.StartType -notlike 'Automatic') {\r\n        Write-Host \"[Issue] (CryptSvc) CryptSvc service is set to $($Service.StartType) but needs to be set to Automatic\"\r\n        $Log.Add(\"[Issue] (CryptSvc) CryptSvc service is set to $($Service.StartType) but needs to be set to Automatic\")\r\n        $IssuesFound = $true\r\n    }\r\n    else {\r\n        Write-Host \"[Info] (CryptSvc) CryptSvc service is set to $($Service.StartType)\"\r\n        $Log.Add(\"[Info] (CryptSvc) CryptSvc service is set to $($Service.StartType)\")\r\n    }\r\n\r\n    $Service = Get-Service -Name bits\r\n    if ($Service.StartType -eq 'Disabled') {\r\n        Write-Host \"[Issue] (bits) BITS service is set to $($Service.StartType) but needs to be set to Manual\"\r\n        $Log.Add(\"[Issue] (bits) BITS service is set to $($Service.StartType) but needs to be set to Manual\")\r\n        $IssuesFound = $true\r\n    }\r\n    else {\r\n        Write-Host \"[Info] (bits) BITS service is set to $($Service.StartType)\"\r\n        $Log.Add(\"[Info] (bits) BITS service is set to $($Service.StartType)\")\r\n    }\r\n\r\n    # Check that Windows Update service is running and isn't disabled\r\n    $wuService = Get-Service -Name wuauserv -ErrorAction SilentlyContinue\r\n    if ($wuService.Status -ne \"Running\") {\r\n        $Service = Get-Service -Name wuauserv\r\n        if ($Service.StartType -eq 'Disabled') {\r\n            Write-Host \"[Issue] (wuauserv) Windows Update service is set to $($Service.StartType) but needs to be set to Automatic (Trigger Start) or Manual\"\r\n            $Log.Add(\"[Issue] (wuauserv) Windows Update service is set to $($Service.StartType) but needs to be set to Automatic (Trigger Start) or Manual\")\r\n            $IssuesFound = $true\r\n        }\r\n        else {\r\n            Write-Host \"[Info] (wuauserv) Windows Update service is set to $($Service.StartType)\"\r\n            $Log.Add(\"[Info] (wuauserv) Windows Update service is set to $($Service.StartType)\")\r\n        }\r\n    }\r\n\r\n    # Check WaaSMedic\r\n    $SupportWaaSMedic = [System.Environment]::OSVersion.Version.Build -gt 17600\r\n    if ($SupportWaaSMedic) {\r\n        $Plugins = Test-WaaSMedic\r\n        $PluginIssues = $Plugins | Where-Object { $_.Parameter[\"error\"] } | ForEach-Object {\r\n            $PluginErrors = $_.Parameter[\"error\"]\r\n            \"[Potential Issue] WaaSMedic plugin errors found with: $($PluginErrors)\"\r\n        }\r\n        if ($PluginIssues.Count -gt 1) {\r\n            Write-Host \"[Issue] Found more than 1 plugin errors.\"\r\n            $Log.Add(\"[Issue] Found more than 1 plugin errors.\")\r\n            $PluginIssues | Write-Host\r\n            $IssuesFound = $true\r\n        }\r\n    }\r\n\r\n    # Check if NTP is setup\r\n    if (\"NoSync\" -eq (Get-TimeSyncType)) {\r\n        Write-Host \"[Issue] NTP not setup!\"\r\n        $Log.Add(\"[Issue] NTP not setup!\")\r\n        $IssuesFound = $true\r\n    }\r\n\r\n    # Check Windows Update logs\r\n    $EventErrors = Get-HasWinUpdateErrorInLastWeek -AllLastWeekError\r\n    if ($EventErrors.Count -gt 0) {\r\n        if (![string]::IsNullOrEmpty($allError.Values)) {\r\n            Write-Host \"[Issue] Event Log has Windows Update errors.\"\r\n            $Log.Add(\"[Issue] Event Log has Windows Update errors.\")\r\n            $errorCodes = $allError.Values -join ';'\r\n            Write-Host \"[Issue] Error codes found: $errorCodes\"\r\n            $Log.Add(\"[Issue] Error codes found: $errorCodes\")\r\n            $IssuesFound = $true\r\n        }\r\n    }\r\n\r\n    # If no issues found, get number of days since the last check for updates happened\r\n    if (-not $IssuesFound) {\r\n        $LastCheck = Get-LocalTime $(New-Object -ComObject Microsoft.Update.AutoUpdate).Results.LastSearchSuccessDate\r\n\r\n        Write-Host \"[Info] Last checked for updates on $($LastCheck.ToShortDateString())\"\r\n        $Log.Add(\"[Info] Last checked for updates on $($LastCheck.ToShortDateString())\")\r\n\r\n        $LastCheckTimeSpan = New-TimeSpan -Start $LastCheck -End $(Get-Date)\r\n        if ($LastCheckTimeSpan.TotalDays -gt $Days) {\r\n            $Days = [System.Math]::Round($LastCheckTimeSpan.TotalDays, 0)\r\n            Write-Host \"[Issue] Windows Update has not checked for updates in over $Days days.\"\r\n            $Log.Add(\"[Issue] Windows Update has not checked for updates in over $Days days.\")\r\n            $IssuesFound = $true\r\n        }\r\n    }\r\n\r\n    if ($ResultsCustomField) {\r\n        Ninja-Property-Set -Name $ResultsCustomField -Value $($Log | Out-String)\r\n    }\r\n\r\n    if ($IssuesFound) {\r\n        exit 1\r\n    }\r\n    exit 0\r\n}\r\nend {\r\n    \r\n    \r\n    \r\n}<\/pre>\n
 <\/p>\n\n
<\/h2>
<\/p><\/div>
<\/a><\/div><\/div>\n
Analisi dettagliata<\/h2>\n
Lo script per la diagnosi dei problemi di Windows Update opera eseguendo una serie di controlli sui principali componenti e servizi di Windows Update, ognuno dei quali \u00e8 essenziale per il corretto funzionamento del processo di aggiornamento. Ecco una descrizione passo per passo di come funziona lo script:<\/p>\n
1. Controllo dell’elevazione dei permessi<\/strong>: Lo script per la diagnosi dei problemi di Windows Update inizia verificando che venga eseguito con i privilegi di amministratore, necessari per modificare i servizi di sistema e accedere a registri specifici.<\/p>\n
2. Test di connettivit\u00e0 Internet<\/strong>: Controlla se il sistema \u00e8 connesso a Internet, un requisito fondamentale per scaricare gli aggiornamenti.<\/p>\n
3. Controlli dello stato dei servizi<\/strong>:<\/p>\n