diTii.com Digital News Hub

Sign up with your email address to be the first to know about latest news and more.

I agree to have my personal information transfered to MailChimp (more information)


New Additional Cumulative Updates for Windows 10, version 1703, More in Creators Update

Windows 10 Mobile Insider Preview Build 15207, released to Insiders in the Fast ring, comes with just one additional fix and mostly remain the same as Build 15205 released last week.

The new build adds “a privacy page to Windows 10 Mobile OOBE” and “upgrade experiences that allows you to quickly and effectively make common privacy changes while setting up the device,” writes Dona Sarkar. However, “Insiders have reported that their device would crash or reboot shortly after unlocking their device for the first time after the upgrade if their device did not have a password configured to unlock the device.”

After updating to Build 15207, you will see this privacy page one more time – but should no longer experience a crash or reboot.

Windows 10 Mobile Creators Update is now available to all 13 supported devices in the Release Preview ring as on April 25.

However, the Feedback Hub still says: “If you are a Windows Insider on an unsupported device, you can stay on the Windows 10 Creators Update and receive Cumulative Updates via the Release Preview ring. However, you do so at your own risk as it’s unsupported. If you are on one of these unsupported devices and in the Fast or Slow ring, you will need to switch to the Release Preview ring via Settings > Update & security > Windows Insider Program.”

Also, the Windows 10 Mobile build 15063.251 should soon be available in the Release Preview and Slow rings.

Microsof also made available Windows 10 build 15063.250 for PCs to everyone, rather than just Insiders.

Here’s the full changelog:

  • Addressed issue where VMs might experience loss in network connectivity while provisioning IP addresses.
  • Addressed issue that does not initiate a remote ring on the device when RemoteRing Configuration Service Provider (CSP) is used.
  • Addressed issue where a memory leak occurs in Internet Explorer when hosting pages containing nested framesets that load cross-domain content.
  • Addressed issue where Internet Explorer 11 does not save JavaScript files when exporting to an MHT file.
  • Addressed issue that causes users to get logged out from Web applications intermittently.
  • Addressed issue with a very dim internal monitor that may occur when booting with the external monitor only and then switching to the built-in panel only.
  • Addressed issue where running Win32 Direct3D applications or games in full-screen exclusive mode causes the system to become unresponsive when resuming from Connected Standby.
  • Addressed issue where when upgrading to Windows 10, version 1703, with the system language set to Chinese, the progress page displays geometric shapes instead of the correct localized strings.
  • Addressed issue that prevents the lock screen from being disabled using Group Policy on Professional SKUs.
  • Addressed issue in Windows Forms configuration options, which causes antivirus applications to stop working at startup.
  • Addressed additional issues with compatibility, Internet Explorer, and Microsoft Edge.
  • According to the Windows 10 Update History site, there are no known issues for this cumulative update.

Microsoft is providing new update options for Windows 10, version 1703 (also known as the “Creators Update”).

With these changes, Microsoft will now routinely offer one (or sometimes more than one) additional cumulative updates each month, that will contain only “new non-security updates,” so they will be considered “Updates” in WSUS and Configuration Manager, said Michael Niehaus.

These new “Updates” and “Critical Updates”, Microsoft willn’t be installed on any devices running Windows Update for Business, that have been configured to defer quality updates.

The following options are available to organizations with these new non-security cumulative updates:

  • Deploy each of them just like the updates on “Update Tuesday.” This enables the organization’s PCs to get the latest fixes more quickly.
  • Deploy each of them to a subset of devices. This enables the organization to ensure that these new non-security fixes work well, prior to those same fixes being included in the next “Update Tuesday” cumulative update which will be deployed throughout the organization.
  • Selectively deploy them, based on whether they address specific issues affecting the organization, ahead of the next “Update Tuesday” cumulative update.
  • Don’t deploy them at all. There is no harm in doing this since the same fixes will be included in the “Update Tuesday” cumulative update (along with all the new security fixes).
Windows 10 version 1703 Servicing Plan
Windows 10 version 1703 Servicing Plan

The company has also published Windows 10 technical documentation on docs.microsoft.com, that help IT pros who need to deploy, update, manage, and secure Windows 10 and related technologies.

The documents includes:

Two weeks is passed since the Windows 10 Creators Update rolled out to general public, millions of customers are now running the Creators Update and have provided feedback using the Feedback Hub app as well.

Microsoft notes, the first phase, which targets newer devices, their update experience will help them in deciding “the next phase of the rollout.” Based on the issues reported, Mirosoft saysm they do any of the following:

  • Document the issue and provide users more information on the issue, potential user impact, and (in some cases) specific guidance including troubleshooting or workaround/remediation guidance. You can find more information via our support channels, including the Windows community forum.
  • Update Windows itself, or work with a PC, accessory, or ISV app partner to post a driver or compatibility update.

Furthermore, the company is advising users to wait until the Creators Update is automatically offered to them, as thoese who use Software Download Site to manually install, bypass many of the blocks. “Deploy a ‘block’ prevent further rollout of the Creators Update to impacted devices until an issue is resolved.”

“Blocking availability of the update to devices we know will experience issues is a key aspect of our controlled rollout approach. We decide what to block based on user impact, and blocking issues are a high priority for us to address as quickly as possible. During the time it takes to address an issue, we want to limit the number of customers exposed to that issue,” writes Mirosoft.

Get Latest News

Subscribe to Digital News Hub

Get our daily newsletter about the latest news in the industry.
First Name
Last Name
Email address
Secure and Spam free...