Windows 10 Cumulative Update - 14393.5 - Why Now ?
Monday afternoon MS released another Windows 10 Cumulative update to Fast Ring Insiders for PC & Mobile. This update bumps the build to 14393.5
My biggest question is why ?
The updated seems to have addressed just two or three issues with some repeats of 14393.3 listed items. Here is the official list:
And while the update installed fine on all of my test platforms, I am missing something with this approach that MS taking.
As I wrote last week regarding the 14393.3 Cumulative update, I can't understand why MS would take the approach of releasing the Anniversary Upgrade (1607) based on build 14393, then immediately ask the user to apply a Cumulative update. This effectively adds another reboot to the update process.
If that's not the case and the 14393.5 updates are going to integrated into the Anniversary Build, then in theory it's no longer 14393. MS did something similar with the original Windows 10 (1507) release distributing several Cumulative updates in the first 3 weeks. I was hoping not to see that repeat with this release.
Sure I understand that MS Windows operations teams need time to stage a release for a broad distribution and therefore may have needed the final build a little earlier than normal, but considering how highly distributed MS's Content Delivery Capabilities are and how much more improved they are versus a few years ago, it doesn't make sense to me to deploy a multi-part upgrade.
To me this is especially true since throughout July Insiders often received full new builds that addressed small numbers of fixes.
Bottom line is this. MS released another Windows 10 Cumulative Update to Redstone (1607). I still believe that MS needs to consolidate all of this into a single build that can easily be downloaded as an ISO and avoid having users perform an update to an upgrade immediately after installation.
My biggest question is why ?
The updated seems to have addressed just two or three issues with some repeats of 14393.3 listed items. Here is the official list:
- We have improved reliability and performance of Microsoft Edge with AdBlock and LastPass extensions enabled. These extensions should continue to work after installing other extension updates from the Store.
- We fixed an issue causing battery to drain due to runaway CPU processes while a device is idle. We also fixed a battery life issue due to the proximity sensor always running on some devices.
- We fixed an issue causing Store apps to stop launching due to a licensing issue.
- We have fixed an issue that results in Windows Updates being delayed on systems with Connected Standby.
- We fixed an issue where the Korean IME would not have the correct composition on some custom TSF3 edit controls on PC.
- We fixed an issue where you might not be able to type in text into Search or some Store apps without having to restart the process.
- We have fixed an issue where keyboard input on some Windows tablet devices would not rotate to landscape normally.
And while the update installed fine on all of my test platforms, I am missing something with this approach that MS taking.
As I wrote last week regarding the 14393.3 Cumulative update, I can't understand why MS would take the approach of releasing the Anniversary Upgrade (1607) based on build 14393, then immediately ask the user to apply a Cumulative update. This effectively adds another reboot to the update process.
If that's not the case and the 14393.5 updates are going to integrated into the Anniversary Build, then in theory it's no longer 14393. MS did something similar with the original Windows 10 (1507) release distributing several Cumulative updates in the first 3 weeks. I was hoping not to see that repeat with this release.
Sure I understand that MS Windows operations teams need time to stage a release for a broad distribution and therefore may have needed the final build a little earlier than normal, but considering how highly distributed MS's Content Delivery Capabilities are and how much more improved they are versus a few years ago, it doesn't make sense to me to deploy a multi-part upgrade.
To me this is especially true since throughout July Insiders often received full new builds that addressed small numbers of fixes.
Bottom line is this. MS released another Windows 10 Cumulative Update to Redstone (1607). I still believe that MS needs to consolidate all of this into a single build that can easily be downloaded as an ISO and avoid having users perform an update to an upgrade immediately after installation.
Comments
Post a Comment