Microsoft announces new cumulative updates for Windows 10 [Updated]

By Dan Thorp-Lancaster
last updated

Microsoft has announced a fresh batch of cumulative updates for the Windows Insiders on Windows 10. The updates come a couple of weeks ahead of the next Patch Tuesday when Microsoft typically releases cumulative updates, and they pack a number of bug fixes across the board.

Here's a look at what's new for Creators Update PCs, which have been pushed up to build number 15063.447 (KB4022716) (opens in new tab):

  • Addressed an issue introduced by KB4022725 where Internet Explorer and Microsoft Edge printing from a frame may result in 404 not found or blank page printed.
  • Addressed issue where network printers may fail to install when using the printer vendor's setup software on machines with less than 4 GB of RAM. These printers will install properly if you install using the Settings app or from Devices and Printers in Control Panel.
  • Addressed issue that causes high memory usage for the Camera app on mobile platforms, which reduces battery life. Any app that uses a media capture element (MCE) or media element (ME) and plays 1080p will consume a lot of power, which will significantly reduce battery life.
  • Addressed issue where, after updating to the Creators Update, devices that have Receive Segment Coalescing (RSC) enabled have significantly low wireless throughput.
  • Addressed issue (Error 0x7F) with Windows Forms (WinForms) that causes the system to crash after upgrading to the Creators Update.
  • Addressed issue that prevents users from connecting to the Terminal Services Gateway (TSG) running on Windows Server 2008 SP2 after upgrading to the Creators Update. As a result, users cannot access Remote Desktop Services or remote apps.
  • Addressed issue where, if you specify an auto-logon configuration in Unattend.xml, auto-logon only works on the first logon, but will not work again when the device is restarted.
  • Addressed issue where users cannot sign in with Face after upgrading to Windows 10 RS2.
  • Addressed issue where, after upgrading to Windows 10 RS2, modem dial-up fails with Error 633.
  • Addressed issue where the smartcard service (sccardsvr.exe) stops periodically and never restarts when the smart card application attempts to access the cards.
  • Addressed issue where, when a laptop connected to an ISCSI disk leaves the corporate network, an error may occur when it resumes if it does not connect to the VPN fast enough.
  • Addressed issue where a remote desktop connection with Windows 2016 RDS server fails authentication when using smartcards.
  • Addressed issue where Open Mobile Alliance (OMA) Device Management (DM) uses the wrong interface to index the on-demand APN.
  • Addressed issue with a memory leak in the camera platform across all devices for PC (MIPI and USB cameras).
  • Addressed issue where, if the device lid close action was set to "Do Nothing", closing and re-opening the lid causes all Universal Windows Platform apps to stop responding.
  • Addressed issue with failed login scenarios that occur because the device does not reconnect to the host PC.
  • Addressed issue where users must wait between 40 to 60 minutes after a print spooler restart before attempting to change any printer settings.
  • Addressed issue where the cursor type does not maintain the arrow shape when the user mouses over a select option in Internet Explorer.
  • Addressed issue where searching for a string on a page that has many iframes causes Internet Explorer to stop working.
  • Addressed issue where Internet Explorer stops responding when a user clicks on an empty column header and then immediately holds down the SHIFT key and double clicks.
  • Addressed issue where the onhashchange event is not called when navigating hashed URLs in Internet Explorer.
  • Addressed issue to improve pairing, connecting, synchronizing, and notifications experiences for a third-party wearable device.
  • Addressed issue to improve Bluetooth connectivity to wearable devices.
  • Addressed issue where the NewWindow3 event is not called in Internet Explorer.
  • Address issue with a memory leak that occurs when calling BluetoothGATTRegisterEvent() and BluetoothGATTUnregisterEvent() functions for an NFC card reader.
  • Addressed issue where a clear (x) button inside HTML text fields cannot be disabled using the ::ms-clear attribute when Document Modes are less than 10 in Internet Explorer 11.
  • Addressed issue where Internet Explorer 11 would fail to load HTML page after installing KB3021952.
  • Addressed issue where a Windows Phone experiences data loss (email, contact, SMS, etc.) caused by Unistore database corruption.
  • Addressed issue where guest VMs bound to a wireless NIC can lose network connectivity if the guest does not send an Address Resolution Protocol (ARP) packet in the fixed timeout window (5 minutes).
  • Addressed issue where certain elements (input or select) cannot be active targets of any action in Internet Explorer 11. This occurs after removing an iframe that contained a cursor inside certain elements (input or select) and then adding a new iframe.
  • Addressed issue with NVIDIA drivers that stop working (Error 0x9f) when the system goes to sleep. This also causes a shutdown of Microsoft Surface Hubs.
  • Addressed issue to improve Remote Desktop Protocol connections to an RD Gateway configured for RPC over HTTP.
  • Addressed issue with non-UWP applications calling into Windows.Devices.Bluetooth API's to register callbacks or Async operations.
  • Addressed issue with an NFC driver that becomes non-functional because of improperly tracked timer handles.
  • Addressed issue with Centennial apps that fail if they try to use the Payment Request API.
  • Addressed issue where the Disk Cleanup and the Storage Settings tool remove files from system32 when file paths exceed the MAX_PATH size; as a result, the machine cannot be booted.
  • Addressed issue to set the default cellular data roaming setting to "Don't roam" when upgrading to Windows 10 Version 1703.
  • Addressed issue that lead to the loss of functionality on certain third-party network adapters after upgrading to Windows 10 Version 1703.

Anniversary update PCs are also getting an update, pushing them up to build number 14393.1378 with their own lengthy batch of fixes (opens in new tab). Similarly, Windows 10 version 1511 and the original release version are also receiving their own, smaller updates, the changes for which you can find at Microsoft's support site (opens in new tab).

Updated June 27, 2017: Story updated following clarification from Microsoft that this update is only for those in the Windows Insider Slow Ring.

Updated June 28, 2017: Microsoft is now pushing this cumulative update for all Windows 10 PCs regardless of Insider status and including production release.

Dan Thorp-Lancaster
Dan Thorp-Lancaster

Dan Thorp-Lancaster is the former Editor-in-Chief of Windows Central. He began working with Windows Central, Android Central, and iMore as a news writer in 2014 and is obsessed with tech of all sorts. You can follow Dan on Twitter @DthorpL and Instagram @heyitsdtl. 

74 Comments
  • Mobile too I believe.  Or at least the phone has a new update coming in.
  • I too got a mobile update today.
  • What build mobuild did u get
  • I am on release preview.
  • .447 came to mobile. In RP.
  • I got 15063.447 on release ring
  • Whats the mobile build number
  • when they force creators update on me windows 10 is going into the bin. f... directx 12 Im going vulcan on linux..
  • yeah, you keep saying that - and yet here you are still whining about W10....
  • Get over it.
  • "We are no longer supporting TH1, but we'll release an update anyway"
  • ha so true but it not called windows as a service for nothing
  • Let's hope this fixes the BSODs (about one a day) and the occasional failure to recognize my monitors (after startup) that I've been having since that last update.
  • Do you happen to have a Lenovo device? I encountered something similar on my Thinkpad and it turned out to be a defective driver that was causing the BSOD whenever the update tried to come through. Deleting the driver (O2Micro Media Card Driver) fixed the problem.
  • The issue is on an HP desktop, although few of the parts are original (in 4 years I've upgraded basically everything except motherboard and processor). And the BSOD isn't tied to Windows Update or anything in particular - I can update everything, and the BSOD seems completely random, sometimes right after I turn it on before even signing in, sometimes I can last 12 hours or more with no issue, and lots in between. I do have a Lenovo laptop for work. There were a few weeks where it seemed to refuse to install new updates, but that's working again, and that's the only issue I've had with it in about a year.
  • My HP laptop fails to recognize the monitor properly when resuming from sleep. I have to power down and back on. To combat this I have had to prevent sleep mode on my laptop and manually place it into hibernation each time. It resumes fine from hibernate, but not sleep. Irritating as all get out. Yes, I hope if fixes it for me as well. Though I have had zero BSODs.
  • Surprised to see that Microsoft is still providing updates for systems running 1507 (original Win10 release). Thought it had reached End of Support as of May 9th.
  • Downloading on Mobile (Release Preview)
  • Getting it on mobile, but my PC doesn't see it.
  • My PC doesn't see it yet.
  • Same here, nothing on my up to date SP4 in release preview. My 950XL is getting it tho.
  • Oh, mine isn't. Well, it'll come.
  • Yay@ that modem error. Needed that.
  • When are going to fix the problem of the Edge browser freezing when you try to access the edge hub? 😒
  • Not seeing this on my PCs on Windows Insiders  release preview ring - at least yet. Still on .413
  • Has this got anything to do with the new ransomeware virus going around? Or was it scheduled regardless?
  • Nothing significant here security related. That is exploiting a known vector BTW that's already been patched.
  • Yes, it appears it is...
  • Not appeared on Windows update nor in the Update catalog
  • Can take a while to hit everyone but I'm downloading the mobile build now still waiting for pc build
  • I'm in UK, maybe it hasn't arrived here yet
  • OMG THEY FIXED NFC. I HAD THIS PROBLEM FOR MONTH !!! YAY!!!!
  • No update yet, here in Romania.
  • Strange that mobiles are getting this update but not PCs yet
  • Addressed issue where a Windows Phone experiences data loss (email, contact, SMS, etc.) caused by Unistore database corruption. yesss
  • I hope they fixed the phone crashing randomly on unlock, which causes the screen to be off and you can only force it to reboot out of it.
  • Is this a software bug? I was under the impression it was due to old batteries exhibiting vdroop.
  • Oh, is it due to old batteries? Has it happened to you, or is it a known issue? Because if it's the battery, I guess it's easy to fix getting a new one.
  • It happened to me even after changing the battery.
  • Well that's interesting to know, as I'm about to buy a new one. Seems consistent with an old battery scenario, I guess. Sigh.
  • Started with CU for me, so it could be related to software (too it on it's own)
  • Also, what is vdroop?
  • Sad to say your battery is dying. Happened to my 950xl and always blamed the update but it was the battery. I got 2 OEM batteries from rounded.com and both have been awesome. No more reboots and crashes so far. My phone can last for 2 days in a single charge with moderate use.
  • Thanks! I'll see if I can get one of those.
  • I checked the wear level in AIDA 64 and it shows 0% though. Shouldn't it show there if it was getting old?
  • I can say AIDA64 is not accurate detecting the physical wear and damage in the battery. Mind you my old battery was swollen slightly and aida64 still reported 0% wear. Don't rely on this. Try getting a new battery while still on stock. Trust me damaged battery is the culprit with these kind of issues.
  • Right, I only asked because one of the sellers I found locally mentioned it as a proof that the battery he's selling is new. I'll keep it in mind.
  • Well, clearly it is the update, at least in part, as it only happens after CU gets installed.  If the battery is in play somehow, something in the software is sensing something in the battery in a way that wasn't an issue before.
  • Right, I started getting these crashes after CU. Now that you mention, my wife's 640 gets these errors too, although not as frequently.
  • I went from L950 performing poorly in the normal fashion that all WP10 devices do (which is to say, it was laggy and buggy and crashy and all that), to absolutely useless due to constant restarting after CU.  Rolling back went to the normal state of suckage, and updating again made it a disaster again.  For sure, the battery is old, as I got my L950 at launch.  But also for sure, it's the CU. Rather than a new battery, I will just say, switch to a different phone and see the light.  It is insane to spend  single penny on anything W10 mobile, anymore.  I'm on an S8 now and can say without any hesitation that literally every single thing is better.  In 2017, there is not even the tiniest of ways in which WP10 is better than Android...nothing.  Android super easy to use, and of course, apps.
  • I agree in that newer updates shouldn't break things that worked in the past, like this. Then any phone or OS has it's problems. Besides that it's a matter of personal preference.
  • https://www.reddit.com/r/windowsphone/comments/6hzza6/w10m_cu_unsupporte...
  • Is that problem fixed in 15063.447 ? I am using it on lumia and i faced this problem multiple times on the last build 15063.414. Please let me know if it is fixed.
  • Pls let me know whether this issue is fixed in 15063.447. Just installed this build on my lumia today. Faced this issue multiple times on 15063.414
  • No updates yet for PC or Mobile - Chicagoland
  • L930 update notifications (email) not working again ! everything thing else ok. Nothing for PC's yet.
  • > Addressed issue where, after upgrading to Windows 10 RS2, modem dial-up fails with Error 633. Someone didn't get mail!
  • > Addressed issue to improve Bluetooth connectivity to wearable devices. Now maybe all our wearables will sync again!
  • I'm in release preview ring and I got the update.
  • No update for my Lumia 950xl and 950 in The Netherlands yet....
  • Still no update for Lumia 950's in the UK
  • I just received update 15063.447 on my Lumia 735 release preview
  • Got my Lumia 640 LTE updated last night, no problems & so far all apps still working which makes a nice change!
  • No sign of it, in UK, on my Lumia 950 😢
  • Getting this update now for my PC's and tablets.
  • Still no sign of it for our Lumia 950's in the UK at 16:30.
  • Still no update for our Lumia 950's in the UK and it's almost a day since Microsoft released .447 for mobile. 😢
  • Still no update yet in UK for the Lumia 950's to this build. If Nokia / HMD can do updates quickly for Android (on the Nokia 6 in China) as a start-up company why can't Microsoft with a smaller population of phones and a larger company!!!
  • "Addressed issue where the Disk Cleanup and the Storage Settings tool remove files from system32 when file paths exceed the MAX_PATH size; as a result, the machine cannot be booted" Quite a serious one, that!
  • That also caught my eye.
  • Now have the update on my Pc's and my L930 now running normal all good in Jersey C.I 😃 although don't see much change for me,c'est la même 😉.
  • Getting it on my dell 2 in 1,  and have my wife's dell 2 in 1,  searching.  should tag it this morning!
  • Hurray, battery drain (caused by last update) finally has been fixed! It feels like infinite battery now
  • Addressed issue where guest VMs bound to a wireless NIC can lose network connectivity if the guest does not send an Address Resolution Protocol (ARP) packet in the fixed timeout window (5 minutes).  Ha!  I reported this some time ago at work and even have a MS Ticket for this item.  So happy this is being addressed!! Addressed issue with NVIDIA drivers that stop working (Error 0x9f) when the system goes to sleep. This also causes a shutdown of Microsoft Surface Hubs. And this one will solve a problem on my Dell Desktop so i can finally turn on sleep mode again! Updates that will have impact to my PCs which is very welcome.