How to change Windows Update settings using SCONFIG.


In this post, we are going to walk through how to manage the Windows Update settings on Windows Server 2016.

Applies to:

  • Server with Desktop Experience
  • Server Core

 

Validate your current WU settings using SCONFIG

To determine what updates your machine has already installed, follow these steps:

  • Open a command prompt with Admin permissions.
  • Type sconfig and press Enter.
    • NOTE: There may be a short pause as the tool inspects your system.

       

  • Option #5 shows the current configuration of your Windows Update settings.

     

Change your Windows Update Settings

To change your Windows Update Settings with SCONFIG, follow these steps:

  • Open a command prompt with Admin permissions.
  • Type sconfig and press Enter.
    • NOTE: There may be a short pause as the tool inspects your system.

       

  • Press 5 and then Enter. This will bring up the following options for you to choose from:

     

     

    • (A)utomatic – This will configure your machine to automatically scan, download, install and reboot after applying any updates.
    • (D)ownloadOnly – This will automatically scan, download and notify the admin if updates need to be installed. This is the default setting on Windows Server 2016.
    • (M)anual — This turns Automatic Updates off. Your system will never check for updates.

       

  • Press the letter specified in the “( )” and press Enter to apply.
  • When the tool applies the configuration you have selected, you will see a message pop-up similar to the one below. Click the OK button to dismiss the message. The tool will refresh the menu and option 5 will now show the new configuration.

     

     

That’s it, you are all set.

Your thoughts, questions and feedback are very valuable to us and we encourage you to share them in the comments section below.


Comments (22)

  1. anon says:

    i would like a setting “notify only”

    1. Can you elaborate a bit more on the scenario in which you see this option being used? We have the ability today to configure the machine to scan for updates and notify the admin if any need to be downloaded. Learn more at: https://technet.microsoft.com/en-us/library/cc708449(v=ws.10).aspx

  2. Harry Johnston says:

    Note that sconfig can’t change the WU settings if the WindowsUpdate\AU registry key doesn’t exist. (This can happen, for example, if you have a group policy applied to the system and then remove it.)

    Also that the Windows Update Settings panel seems to have a nasty habit of installing updates without permission no matter what the settings are.

  3. In Desktop Version I’m able to adjust the time when the server is allowed to reboot automatically. Is there an option in Core Version too?
    So that the server can automatically Download and Install all Updates and then (on a given time) it will reboot itself?!

    1. This feature does not exist on Windows Server 2016 (Server Core), but we are really keen on understanding when and how you would use it if it were implemented. Could you elaborate a bit more about your scenario? Such as would it be used on Hyper-V hosts, Domain Controllers, etc.? Thanks for helping improve the product.

      1. In Domain Controllers it would be absolutely great! in Hyper-V and other clusters the CAU is doing fine at the moment

  4. Mahadev says:

    Though I have done it on day 1 after the install of 2016, its still not downloading the hot-fixes automatically. Internet/proxy all are working. I have scheduled it for midnight 3AM, but no fixes are being downloaded nor getting installed automatically, on my 6 servers.

    1. Did you use SCONFIG to change the default? If you check the registry value for the AUOption, what is it set to? You can find the exact key by using the following: https://technet.microsoft.com/en-us/library/cc708449(v=ws.10).aspx.

  5. gchq says:

    I ran SConfig and 5 is set to ‘DownloadOnly’ – however update status says ‘Your device is scheduled to restart outside of active hours’ – active hours for us are 24/7 apart from scheduled maintenance on the Saturday after patch Tuesday. Is this warning just there to make us head for the brandy bottle in sheer panic, or will it carry out the threat and throw us under the proverbial bus with an unmonitored restart when it feels like it?

    With preview 5 we set this in group policy and it patiently waited after installing x-days until we were ready to reboot

    Server 2016 – Desktop Experience.

    Thanks

    1. gchq says:

      Seems like the only answer is to disable ‘Reboot’ in Task Scheduler UpdateOrchestrator and rename the Reboot file to prevent Windows re-enabling the schedule again… It would be bad enough having a desktop rebooting of it’s own accord – but a server??

    2. This is a known bug in the Windows Update Settings UI in which the text does not correctly reflect the configuration of your Windows Update settings. The feature team is actively working on a fix. At this time, we recommend that you leverage SCONFIG to verify your servers update configuration.

  6. Kevin Dahl says:

    Why would you build a command line interface that then has the confirmation dialog outside of the command line?

    Also, the install updates feature has such minimal feedback that it’s rather useless – it currently says ‘Downloading updates…’, though I know they were already downloaded and I can see that it’s installing them when I look at the resource monitor.

    This sconfig solution looks to be pretty half baked at this point. The whole windows update path on Server 2016 is feeling disturbingly incomplete.

    1. SCONFIG was meant to provide a very basic and quick way to configure and manage several common aspects of Server Core installations. It is called out above to provide a way to verify your server’s Update configuration until the fix for the Windows Update Settings page can be implemented.

  7. Onder Cura says:

    I thought sconfig was deprecated as part of Windows Server 2016? Shouldn’t we be using PowerShell to do this instead?

    1. We recommend using PowerShell whenever possible. SCONFIG is not yet on a deprecation path and is available to use on Windows Server 2016 (Server Core) and Windows Server 2016 (Desktop Experience) install options.

  8. Sean says:

    Active hours should be more than 12 hours, and we should also be able to select which weekdays are active/inactive, our business is almost 24/7 and we would like the ability to select inactive hours of Sunday between 1am and 5am which is a more likely time we will not have active users on the system.

    It would also be really, really good if the updates downloaded through a proxy server. With our proxy the updates are detected, but the downloads never go past 0%. Open the firewall, remove the proxy and all os a sudden it works. This is very frustrating when wanting to do manual updates instead of relying on SCCM/WSUS

    1. Thank you for the feedback. I will pass this along to the development team.

  9. mdw says:

    There’s an issue with the settings and the UI being out of sync.

    I used SCONFIG to set updates to Manual. But the Settings UI (even after restarting the machine) states “Available updates will be downloaded and installed automatically, except over metered connections…”

    Any ideas from the Microsoft folks on this discrepancy?

    1. This is a known bug in the Windows Update Settings UI in which the text does not correctly reflect the configuration of your Windows Update settings. The feature team is actively working on a fix. At this time, we recommend that you leverage SCONFIG to verify your servers update configuration.

  10. mdw says:

    We’re migrating to Server 2016 w/desktop experience and want to set a specific date and time every week (or month) to automatically check for and apply Windows Updates. Outside of the time window we specify we don’t want any downloading or checking for updates.

    Is this possible? We’re fine with using powershell if that helps.

    1. In order to configure a weekly install schedule please use the “Configure Automatic Updates Group” policy Option 4 and pick the day and time of install. If you also use the “Always Automatically Restart at Scheduled Time” then we will only restart the device for Updates then.

      Irene Giannoumis
      Senior Program Manager

  11. anon says:

    Apologies for the off-topic remark but the Microsoft Update Catalog, although recently updated to remove the ActiveX requirement and the cart, is still in dire need of a major overhaul. Its navigation should not include pop-ups for downloading files and the files themselves need to be labelled and presented more clearly. Furthermore, most of the contact links on the Update Catalog appear to be no longer valid so users don’t know how to contact you.