Microsoft Updates the Shipping Versions of Windows 10, Again

Posted on June 28, 2017 by Paul Thurrott in Windows 10 with 61 Comments

Microsoft Updates the Shipping Versions of Windows 10, Again

For the second time this month, Microsoft has delivered cumulative updates for each of the shipping versions of Windows 10. Get ready to reboot your PC yet again.

This rapid release thing is becoming problematic, frankly. I seem to recall that the goal was for fewer reboots, but we seem to be rebooting Windows 10 PCs more than ever as we move forward. In fact, those on the shipping version of Windows 10 are forced to reboot their PCs almost as much as those on the Fast Ring in the Windows 10 Insider Preview.

Anyway, you may recall that Microsoft last issued cumulative updates for the shipping versions of Windows 10 on June 13, which is the normal, if outdated, Patch Tuesday schedule. The cumulative update issued to those on the Creators Update, or Windows 10 version 1703, bumped the build number to 15063.413.

This week’s update, KB4022716, bumps the build number to 15063.447. Like previous cumulative updates, it doesn’t provide any new features, but it does add security and quality fixes. Microsoft lists the following.

  • 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.
  • Addressed 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 a reliability issue in Windows Search.
  • Addressed issue that lead to the loss of functionality on certain third-party network adapters after upgrading to Windows 10 Version 1703.

There are similar updates for the other supported versions of Windows 10, of course.

Have fun rebooting.

 

Join the discussion!

BECOME A THURROTT MEMBER:

Don't have a login but want to join the conversation? Become a Thurrott Premium or Basic User to participate

Register
Comments (62)

62 responses to “Microsoft Updates the Shipping Versions of Windows 10, Again”

  1. ncn

    ... have fun rebooting? And in the next breath complain about how all those people suffering from ransomware deserved it because they couldn't be bothered to update or upgrade.

  2. DaddyBrownJr

    Speaking of updates; when is this site going to get updated so that the comments section is actually usable?


    This is a rhetorical question, since I'll never know if someone responds or not.

  3. Polycrastinator

    So let me be the lone voice agreeing with Paul: users hate updates, and they hate forced reboots. They ignore, them, and then their computers restart unexpectedly overnight, and they hate that. Every time security updates come out, that shows the bad guys where the flaws were, and those flaws get exploited quickly after the updates go out. But users sit on their hands and refuse to reboot until they're forced to. Companies have to go through validation processes and test. More updates means more testing. It's an inconvenience at best, at worst it's a problem.

    • Dashrender

      In reply to Polycrastinator:

      I'm not really sure where you're going with this? I'd rather have updates applied as soon as MS becomes aware of a problem. Sadly that means that when MS releases the update, the bad guys know about it.


      But we have to remember, that bad guys (NSA anyone) already know about some of these security issues, but MS does not know about them. So Patch patch patch I say.


      I understand users don't like rebooting - to that I say I'm sorry. I guess it's your choice - do you want a paycheck or not? If we don't patch, and you get infected and now payroll can't happen/is delayed - you're OK with that, right?

  4. EZAB

    KB4022725. The printing a Frame Issue was a huge issue on Windows 7 and 8.1 computers, not just Windows 10. What ever happened to rebooting to clear out the memory? I thought only Mac users never reboot, leave 10 programs open and then wonder why their machines are so slow!

  5. rlcronin

    Personally I'm happy that Microsoft is updating Windows 10 regularly. Rebooting is just not an issue for me. It takes less than 30 seconds.

  6. Allen

    I'm with those who actually don't mind, but I only manage my 5 PCs. As long as updates don't add any new, unsuspected layouts or change how things get done, my wife doesn't even notice when they happen - though some times she does wonder why her start up process looks different sometimes.

  7. gregandrews

    Good thing! Windows search was VERY buggy since the last update as evidenced by many public posts and my painful first-hand experience. This update appears to have fixed the issues as described in Microsoft's list. I am happy to reboot to fix what I believe to be the most useful feature of Windows.

  8. Steve Martin

    Microsoft seriously needs to learn from Linux and loadable modules. Very few changes should require a reboot. And fixing or upgrading Edge/IE most definitely should not.

  9. warren

    Microsoft has been indeed shipping reboot-required updates to the Creators Update about every two weeks. I wonder if this is going to be the new normal, or if's a temporary thing while they iron out bugs.


  10. Angusmatheson

    I just wish I always had a choice. I just grabbed a windows 10 laptop because I was running somewhere. I turned it on, saw it had almost no charge and then went to turn it off to save what little battery it had: only options update and restart and update and shutdown. So I had to update and shut down praying it had enough power and wouldn't die. It didn't, but it put itself to sleep and as soon as I opened it it started installing again. So I had to find power so it wouldn't die, and still couldn't do what I needed to do on it. I don't know why I don't have the choice to shut it down and update tomorrow. I am really good about updates. Linux, MacOS, iOS, and android don't force me to update when I want to use it (I don't think I have even gotten an update on my android phones or tablets - and that is a different problem).

  11. Dashrender

    Frankly I've been waiting for this update since the one on June 13. We've been unable to print via IE because of the 404 issue. Glad that MS didn't wait until July for this.


  12. Waethorn

    In reply to mbsnl:

    They have no QA anymore. QA is literally Windows Insiders now. They laid all the Redmond employees off.

  13. brettscoast

    wow that's quite a list. I was under the impression too that with the latest version of Windows 10 ver 1703 there would be less need for reboots, its quite the opposite in fact which is a bit disconcerting but as long as Microsoft are being proactive providing security updates and other fixes quickly then its not the end of the world and given these recent cyber security attacks going on all over the world its more important than ever to keep your system up-to-date.

  14. pbeiler1

    After I applied the update to my surface pro 4, the display quit coming on when coming out of sleep. I have to reboot to get the screen back.

  15. matsan

    I don't mind the updates and reboots, but I do hate the automatic reboots! It is no longer possible to leave your machine overnight and expect to pick up the work again. As a software developer I have multiple VMs in VirtualBox and terminal windows open. When Windows automatically reboots overnight I need to spend a good time running fsck on the VMs and fix database corruptions that happens when Windows forcefully shuts everything down.

    My solution is now to pause updates and do the update when it is convenient for ME.

    • lightbody

      In reply to matsan:

      For your average idiot though, its much better now... i have a friend who never used to update their laptop at all, and it drove me mad - on windows 7 it was always sitting asking to be allowed to update. Since windows 10 though, any time I check it, its all up to date and he doesn't know how it happened.

  16. Steven Ball

    I don't understand the outrage against rebooting. I understand that is annoying to have to stop what you are doing and reboot, but if you only have to do it once or twice a month that isn't bad. Plus I'd rather have to reboot more frequently and know my computer is being updated than not get updated and get ransomwared.

  17. jclarytx3

    Another broken MS update. Breaks external monitors when unlocking.

  18. Daekar

    Paul... you're starting to confuse me, man. What makes you think that they aren't trying to reduce required reboots? And why is it such a big deal to restart a computer? They've given us tools to manage when this process happens. Seriously, it's not like anyone who needs a computer that never restarts is using Windows 10 in the first place.

  19. wolters

    It also fixes an indexing problem with Outlook. This one's huge for us as it affected our business.

    • Waethorn

      In reply to wolters:

      Not me, but clients definitely have. No problems with Gmail here. I have a client that uses Gmail for business with Outlook (desktop software), and they haven't complained about it either, but I don't know if they do a lot of heavy searching either.

  20. Martin Pelletier

    I close my PC every night. So I will reboot twice today

  21. RamblingGeek

    I don't understand why this is bothering you so much? What are you expectations, MS don't update, update without rebooting? You used to dev software... so you know reasons more than most...

  22. jrswarr

    What is the big deal? Just let the system reboot after hours. Mission Accomplished.

    It's just the nature of the architecture of the PC beast that reboots are required - and up to now we have not been very receptive to Microsoft changing that basic architecture - starts off a different set of howling.

  23. DaddyBrownJr

    If Microsoft has 38 fixes ready to roll out, I don't see the logic in waiting 2 weeks in order to fit into some artificial schedule. Give me the fixes when they are ready; I can live with a couple of reboots a month.


    Edit: It took 2 minutes 45 seconds to reboot. Am I supposed to be outraged by this?

  24. brduffy

    I guess I don't mind a couple more frequent updates after a large update like the Creators Update. There will always be regressions after a large update. It should settle down after this. It looks like some of those things should have been caught before releasing the creators update though.

    • Spineless

      In reply to brduffy:

      Some of the fixed issues are a bit obscure, like the SCSI corp network issue, but I would expect that all of the sources of the defects have made it into various test plans, scenario tests or unit tests, in order to avoid future regressions.


      While reboots are often unfortunately timed, I personally prefer to see these fixes sooner rather than later.

  25. bsquarednc

    Wow, I am so outraged...my Surface Pro took all of 2 minutes to update/reboot.

  26. skane2600

    IMO, the ease of delivering updates has enabled sloppy work not just for MS, but the industry as a whole. Doing it right the first time is so last century.

    • warren

      In reply to skane2600:

      Computers are significantly more complicated nowadays and your expectations of them are vastly, vastly higher. So yeah, it's harder to get things right the first time. That shouldn't be a surprise.

      • skane2600

        In reply to warren:

        There's a difference between an expectation of new capabilities and an expectation of quality work. If a software product is not so complicated that it can't be fixed, then it's not too complicated to ship correctly in the first place. The industry has become infatuated with continuous delivery and similar strategies. You should deliver when the product is ready.

  27. DemBones

    You could drop a million dollars on Paul's head and he would complain about the paper cuts.

  28. MacLiam

    The oddest thing about this update is that it floated into two eligible Insider-RP mobiles as soon as it was released, but nothing happened on a new Surface Pro and Surface Book until later in the day, after Dona Sarkar's message made me enroll one device in the insider program slow ring and move the other one, already an insider device, from release preview to slow. Why the ring distinction between mobile and PC versions? I kind of get the concept behind staggered or targeted releases once an update is ready to go, but I feel underinformed about the details and benefits of this new policy. Why mess around with the long-time meanings of the different ring levels if the only change is to delay or accelerate user receipt of a releasable update? Rings were always an indicator of comparative system reliability. Now they seem also to be valves to smooth out release rates.

    As much as I like and trust Microsoft's products, sometimes their decisions leave me wondering. Befuddlement as a Service.

    I don't care about the reboot thing. I rarely let any of my PCs go more than a week without a reboot anyway, and some of them get power-cycled more often than that.

  29. Patrick3D

    KB4022725 hit our organization hard with IE problems. A data management platform we use relies heavily on ActiveX and that update was causing everything from failures printing to crashes. A few users also experienced the Windows Search problem and were unable to do searches in the Office365 version of Outlook 2016. Considering it took 15+ minutes to uninstall the bad update per machine this is going to save us a lot of time.

  30. michael

    I wonder how long I will be stuck at 63%

  31. glenn8878

    This fixes reliability issues. How is that a bad thing? I recall having the first issue of printing a page and encountering the 404. More updates please.

  32. Bart

    Paul: I can't use Egde, they need to update / add features for it to be useable


    Microsoft updates Windows for a better experience; Paul: Get ready to reboot your PC yet again


    ;)

  33. jclarytx3

    This post no longer applies. MS has now withdrawn this update for the shipping version. I refreshed a Win 10 machine on ver 1703 and the cumulative update only got to 15063.413. They have posted a fix to the display problem for slow ring, but nothing for shipping versions.

Leave a Reply