Repetindo a mesma resposta para o Windows 10 contorna o WSUS , que eu tinha dado na falha do servidor aqui também, já que o OP está cometendo o mesmo erro.
A solução é muito simples, certifique-se de que sua cópia do Windows 10 não tenha nenhum dos seguintes nomes de valor listados em HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate
, se você estiver executando o Windows 10 OS - versão de impacto: 1511 & 1607.
DeferFeatureUpdates
DeferFeatureUpdatesPeriodInDays
DeferQualityUpdates
DeferQualityUpdatesPeriodInDays
PauseFeatureUpdatesStartTime
PauseQualityUpdatesStartTime
ExcludeWUDriversInQualityUpdate
Mais citações do mesmo artigo :
What just happened here? Aren’t these update or upgrade deferral policies?
Not in a managed environment. These policies are meant for Windows Update for Business (WUfB).
Windows Update for Business aka WUfB enables information technology administrators to keep the Windows 10 devices in their organization always up to date with the latest security defenses and Windows features by directly connecting these systems to Windows Update service.
We also recommend that you do not use these new settings with WSUS/SCCM.
If you are already using an on-prem solution to manage Windows updates/upgrades, using the new WUfB settings will enable your clients to also reach out to Microsoft Update online to fetch update bypassing your WSUS/SCCM end-point.
To manage updates, you have two solutions:
- Use WSUS (or SCCM) and manage how and when you want to deploy updates and upgrades to Windows 10 computers in your environment (in your intranet).
- Use the new WUfB settings to manage how and when you want to deploy updates and upgrades to Windows 10 computers in your environment directly connecting to Windows Update.
— "Why WSUS and SCCM managed clients are reaching out to Microsoft Online" : This post was authored by Shadab Rasheed, Technical Advisor, Windows Devices & Deployment (9 January 2017), Microsoft Windows Server Team .
OBSERVAÇÃO: Esteja ciente de que a lista de nomes de valor do Registro mencionada no artigo da Microsoft possui erros de digitação.