Updating windows update agent
For more information, see the following examples: AWS has removed all Windows AMIs dated 20 due to an issue with an unquoted path in the configuration for the Amazon EC2 Hibernate Agent.For more information, see Issue with the Hibernate Agent (20 AMIs).Amazon Web Services did not release updated Windows Server AMIs in February. The following features, which were previously available in Enterprise edition only, are now enabled in Standard, Web, and Express editions with SQL Server 2016 SP1: All Windows Server 2008 R2 AMIs for July were removed and rolled back to AMIs dated 20, because of an issue discovered in the AWS PV driver. The August AMI release will include Windows Server 2008 R2 AMIs with the fixed AWS PV driver and July/August Windows updates. If you run the Docker service on Windows Server 2016 AMIs, the service is configured to use a different CIDR value than the default internal IP address prefix value. Windows Server 2016 AMIs use 172.17.0.0/16 to avoid a conflict with the default Amazon EC2 VPC/subnet.If you don't change VPC/subnet settings for your EC2 instances, then you don't need to do anything.To ensure that customers have the latest security updates by default, AWS keeps Windows AMIs available only for three months.After releasing new Windows AMIs, AWS makes the Windows AMIs that are older than three months private within 10 days.
To subscribe to Windows AMI notifications AWS provides updated, fully-patched Windows AMIs within five business days of Microsoft's patch Tuesday (the second Tuesday of each month).
It shows 0 updates needed, all updates show "installed or not applicable".
These are fresh server installs, they have just been installed straight from a disk image created November of last year.
I have a hard time believing that there are 0 applicable updates for a fresh Windows Server 2016 install.
I have ensured that BITS and the Windows Update services are running.