Windows 10 1709 Download
Raingarda Krzynowek
I noticed the Windows Update Assistant had somehow got on to my Enterprise version of Windows and was asking my users to update to the 1709 version of Windows 10. I use Wsus for updates and had turned the 1709 update off. As the disruption of 1-2h install time was too long. The plan was to get all the laptops in test it and then update it for them.
After the Win 10 1709 update was installed (only on a few machines so far) through the windows update assistant I saw that they were not auto signing onto the wifi using my 802.11x policy through GPO, I thought the cert had expired but its fine. After doing a bit of research on the issue I have found the 1709 update was causing wifi issues. for some people.
These were the old WIfi settings. they still work fine for the older version of Windows 10 but not the new version. it may be something to do with my self-signed cert. Why disabling active probing fixed this issues. i still have no idea.
Sooo ... is an upgrade from 1709 to 1803 even possible? It is a little crappy if we have to reinstall the half year releases from scratch every time ... I understand this would be less of an issue if we use the non-lts windows versions solely as container images, but I would like to run this on my server as well ...
So you are saying that Windows Server 1709 Core that has been running my server since it was released in september 2017 is not an RTM version of Server 2016, but 1803 is? That does not make any sense.
It's like 1709 was just swept under the carpet? Or should we expect to reinstall version 1809, 1903 and 1909 as well, when they will be released? That reduces the usability of the semi-annual core versions to be something that we use as the basis of our container images, where we can just bump the version number in docker files ... seems like a bit of a problem to me.
However, it looks like they dropped that feature when they announced, in late March, that the SAC versions would be focused entirely on "modern applications and innovation scenarios such as containers", and would drop most of the infrastructure roles.
Accordingly, 1803 has even fewer infrastructure services than 1709 (which dropped Storage Space Direct just as it was released). So an in-place upgrade would have likely stripped out features from a 1709 installation, causing issues for administrator who (rightfully) expect an in-place upgrade to maintain roughly the same feature set.
@Dave Patrick, I just want to make sure that this is clear for everyone. There is no such thing as Windows Server 2016 1803. There is only one RTM release of Server 2016, and that was 1607. There is Windows Server 2016 and then there is Windows Server 1803. You must view them as two different product offerings.
The Windows Server releases with YYMM build numbers, like 1607, 1709, 1803, etc... are part of the windows semi-annual channel (SAC) and will be released every six months. These releases will be bleeding edge releases and will not support the GUI interface at all, only a core install. They will only have a support life span of 18 month. Even though there is cases of engineers upgrading a SAC deployment to the next release, this is not supported and MS is expecting you to deploy brand new installs when the new version is released.
The Windows server release with the actual year referenced are the Long Term Servicing Channel. They are what we are used to seeing released every so many years, 2012, 2016, 2019, etc... They will include some of the technologies that have been released in the SAC channel that have been deemed production stable and supportable. These releases will have the normal mainstream support of 5 years. These releases on the other hand can be upgraded from old to new releases.
After installing the Servicing Stack updates up to 2019-07, I thought I'd try installing the 2019-07 Cumulative Update for Windows 10 KB4507465, since that should work with the Servicing Stack from the same month. That also claims to be "not applicable".
The problem you are running into is that the Windows Update catalog does not contain the required updates necessary to update your installation if you are indeed running 16299.15. Even if you are running 16299.1268, any update released after April 9th, 2019, does not apply to your installation.
Any update released after April 9th, 2019, for Windows 10 version 1709 can only be installed on (Windows 10 Enterprise, Windows 10 Education, and IoT Enterprise) version 1709. The reason you are being told KB4520006 not applicable to your installation is due to the fact you are not running a supported edition of Windows.
The last delta update that can be installed on your system would be KB4507455. Any update after April 9th, 2019, on the Windows Update Catalog, is an express update which can only be installed on supported editions of Windows 10 version 1709.
After installing the Servicing Stack updates up to 2019-07, I thought I'd try installing the 2019-07 Cumulative Update for Windows 10 KB4507465, since that should work with the Servicing Stack from the same month. That also claims to be "not applicable."
The Servicing Stack updates only allows your installation to receive updates through Windows Update, WSUS, or System Center Configuration Manger. You were able to install KB4509093 due to the fact it was released before April 9th, 2019.
You can upgrade your installation to Windows 10 Enterprise, of course even Windows 10 Enterprise version 1709, will stop receiving updates on April 9th, 2020. On April 10th, 2020, Microsoft will no longer release security and quality updates for Windows 10 version 1709.
You can try and install KB4507455 and then attempt to install a cumulative update released after April 9th, 2019. However, I ran into the same problem with a VM that was running Windows 10 version 1507. I was unable to even download updates for that version from the catalog, since the updates, did not even exist. Even direct links to the update themselves did not work.
Reminder:- March 12th and April 9th will be the last two Delta updates for Windows 10, version 1709. Security and quality updates will continue to be available via the express and full cumulative update packages. For more information on this change please visit our blog.
Reminder: Windows 10, version 1709, will reach end of service on April 9, 2019 for devices running Windows 10 Home, Pro, Pro for Workstation, and IoT Core editions. These devices will no longer receive monthly security and quality updates that contain protection from the latest security threats. To continue receiving security and quality updates, Microsoft recommends updating to the latest version of Windows 1
I've been using a OneDrive folder as my Arduino Sketch folder to always work on the latest ino files from my PC or my laptop. This worked fine until the latest WIndows 1709 upgrade that brought new OneDrive functionality.
danghoanganh:
I had the same problem with onedrive after the fall creator update. Just un-check "Files On-Demand" in onedrive setting, arduino IDE can normally read and compile sketch. In my case, it works.
I receive the same error. Adding --isolation=hyperv to the command line, does allow the container to start. Likewise when I tried to a docker build using a dockerfile, failure to provide --isolation=hyperv on the command line, resulted in the mismatch error.
I feel like I am missing something basic. When I read -peek-1-windows-server-version-1709/ and wanted to try it, it pointed me to the windows experience blog announcing windows server insider preview build 16237.
Similarly, the helpful youtube video from Microsoft Mechanics describing version 1709, indicates that the nanoserver image has been reduced in size from >1 GB to 195 MB. Yet, when I look at the size of the nanoserver I downloaded after the install of the server, the image size is still 1.07GB. I would very much like the smaller version. Where do I find the documentation that instructs me to it? I must be missing something very basic. Any assistance is greatly appreciated.
I have a laptop with A8 5550M processor with Radeon HD 8550G. The graphics drivers from windows update works in windows version 1607, while in 1709 it suddenly doesn't work anymore. Thus the laptop felt like using a computer without graphics power; like using a PC without a GPU, but disabling integrated graphics, everything felt sluggish, stutters and screen tearing every where, even though cpu usage is nowhere near high. What should I do, after rolling back fro 1709 back to 1607, the last few days apparently windows kept forcing me to update without any cancel button, and defering update in settings seems not working either it kept installing Windows update assistant on the background. Can i do anything to make the drivers work again?
your not the only one with problems after the update to 1709 in combination with AMD hardware. My systems hangs completely after updating to 1709. Reinstalled everything but still fails. Here are my hardware details:
To ensure devices in enterprise environments are running the most current and secure version of Windows with the latest security updates, any device on Windows 10 Enterprise edition or Windows 10 Pro edition that is configured to receive updates automatically from Windows Update will be automatically offered Windows 10, version 1709 after January 18, 2018. This does not apply to long-term servicing editions.
d3342ee215