Now that the Creators Update (Redstone 2) is the 'production' branch of Windows 10 Mobile, we can see 'Patch Tuesday' fix round-ups for it, with the official list for the 'October 2017' update' mainly composed of security patches, at least in terms of mobile relevance. Again, it's still significant to see this arriving simultaneously for 'mobile' in lock step with 'desktop', in terms of the under the hood modules, though this month may also see the desktop jumping ahead to a different branch with the formal release of the so-called 'Fall Creators Update' to production users.*

* You see, although the Fast ring Insiders on mobile have got the '1709' branch of Windows 10, we just don't know yet how much (if at all) Microsoft will push this out to production users. In theory it should happen, given all the business users still - in practice, who knows?

Here's the quoted changelog, with mobile-relevant items emboldened (most of the specific fixes are for the Desktop):

This update includes quality improvements. No new operating system features are being introduced in this update. Key changes include:

• Addressed issue where some UWP and Centennial apps show a gray icon and display the error message "This app can't open" on launch.
• Addressed reliability issue that causes the AppReadiness service to stop working.
• Addressed issue where applications that use the Silverlight map stack stop working.
• Addressed issue where VSync prevents devices from entering Panel Self Refresh mode, which can lead to reduced battery life.
• Addressed issue where user customizations (like pinned tiles) made to an enforced partial Start layout are lost when upgrading to Windows 10 1703.
• Addressed issue where the Universal CRT caused the linker (link.exe) to stop working for large projects.
• Addressed issue that prevents Windows Error Reporting from saving error reports in a temporary folder that is recreated with incorrect permissions. Instead, the temporary folder is inadvertently deleted.
• Addressed issue where the MSMQ performance counter (MSMQ Queue) may not populate queue instances when the server hosts a clustered MSMQ role.
• Addressed issue with the token broker where it was leaking a token that caused sessions to remain allocated after logoff.
• Addressed issue where Personal Identity Verification (PIV) smart card PINs are not cached on a per-application basis. This caused users to see the PIN prompt multiple times in a short time period; normally, the PIN prompt only displays once.
• Addressed issue where using the Cipher.exe /u tool to update Data Recovery Agent (DRA) encryption keys fails unless user certification encryption already exists on the machine.
• Addressed issue where using AppLocker to block a Modern app fails. This issue occurs only with Modern apps that come pre-installed with Windows.
• Addressed issue with form submissions in Internet Explorer.
• Addressed issue with the rendering of a graphics element in Internet Explorer.
• Addressed issue that prevents an element from receiving focus in Internet Explorer.
• Addressed issue with the docking and undocking of Internet Explorer windows.
• Addressed issue caused by a pop-up window in Internet Explorer.
• Addressed issue where a Vendor API deleted data unexpectedly.
• Addressed issue where using the Robocopy utility to copy a SharePoint document library, which is mounted as a drive letter, fails to copy files. However, in this scenario, Robocopy will copy folders successfully.
• Addressed issue where MDM USB restrictions did not disable the USB port as expected.
• Addressed issue where creating an iSCSI session on a new OS installation may result in the "Initiator instance does not exist" error when attempting to connect to a target.
• Addressed issue where connecting to RDS applications published using Azure App Proxy fails. The error message is, “Your computer can’t connect to the Remote Desktop Gateway server. Contact your network administrator for assistance”. The error can occur when the RDP cookie size limit is exceeded. This update increased the size of the RDP cookie limit.
• Addressed issue where USBHUB.SYS randomly causes memory corruption that results in random system crashes that are extremely difficult to diagnose.
• Addressed issue that affects the download of some games from the Microsoft Store during the pre-order phase. Download fails with the error code 0x80070005, and the device attempts to restart the download from the beginning.
• Addressed issue where the ServerSecurityDescriptor registry value does not migrate when you upgrade to Windows 10 1703. As a result, users might not be able to add a printer using the Citrix Print Manager service. Additionally, they might not be able to print to a client redirected printer, a Citrix universal print driver, or a network printer driver using the Citrix universal print driver.
• Security updates to Microsoft Windows Search Component, Windows kernel-mode drivers, Microsoft Graphics Component, Internet Explorer, Windows kernel, Microsoft Edge, Windows Authentication, Windows TPM, Device Guard, Windows Wireless Networking, Windows Storage and Filesystems, Microsoft Windows DNS, Microsoft Scripting Engine, Windows Server, Windows Subsystem for Linux, Microsoft JET Database Engine, and the Windows SMB Server.

As usual, in today's malware-strewn and fraudulent times, we should never disregard security fixes (e.g. to the Edge browser) though, so update today in all affected mobiles, just in case!

Curiously, the Release Preview ring hasn't gotten this update, probably because this ring is now handling the Fall Creators Update on the PC. I'll do a separate post on this, on what all this means for people with Lumia 830, 930, etc. tomorrow. I've got good news though....(!)

As ever, with all phones, head into Settings/Update & Security/Phone update in order to get the update immediately.