Windows 10 Anniversary Update - Another Cumulative Update
On Aug 2, MS released the third cumulative update to Windows 10 Redstone 1 release (1607) build 14393 bumping the build 14393.10. This was a PC only update.
MS did not release any details about the update in the KB and did not place any information on the Feedback Hub about this update. So to the honest I can't say what this update addressed.
Over the weekend I used the Release Preview setting of Windows Insider on one machine that was running the Threshold 2 (1511) Build 11586.494 to upgrade to the Anniversary release which I noticed after boot came in as 14393.5 - meaning the 2nd cumulative update release on July 30 was integrated. Then on Aug 2 this third cumulative update was applied.
I applied the update to all of my current test machines and the update installed with no issues.
However on one of my machines that runs an AMD Radeon R7 240 video card - I received errors on startup regarding the AMDSettings.exe app. While I can't say 100% that the cumulative update caused the issue, I also noticed that I received an AMD Video Driver update on July 30 as well. However even after applying the latest drivers from AMD, the error continued, so the .10 update seems to be causing the problem.
Post release MS is continuing to move forward with both Redstone 2 and apps. Today MS announced the newest release of the MS Maps app (5.1608.2117.0) for PC that contained Ink support.
As we move forward with Redstone 2 we are also going to see another jump in Build numbers. According to buildfeed.net the latest posted builds start in the 14894+ range. While nothing has been released yet - my expectation is we will start seeing builds in that number range.
This was similar to what we saw last year after the Threshold 1 (1507) release based on build 10240 - then first jumping to 10525 as the Threshold 2 branch started on the way to release based on 10586 and then 11099 when Redstone 1 started.
One platform that missed the "Anniversary" update date was Windows 10 Mobile. While Insiders like myself have been running 14393.5 - there was no public release of this build to supported devices on 10586. This is expected on Aug 9. I'm not 100% on what the delay is unless something came up with the new HP and Acer devices.
Finally a couple of new items:
First - Some 5.5 years after Starbucks released their initial Mobile App for iOS in Jan of 2011, they finally release an official version for Windows Mobile. While it is certainly nice to see, one has to wonder about the motivation here. What is also odd is that while this supposed to be an UWP app - it was not released for PC.
Second - MS reduced the price the for the unlocked Lumia 950/950XL here in the US. The 950 was reduced $150 (27%) to $399 which included a free display dock - an additional $99 savings. The 950XL was reduced by $200 (30%) to $449. So the winding down of the Lumia line is accelerating. MS has always had a hard time selling flagship phones - so I expect the price to drop even further as well head into fall.
As I've stated in earlier posts - if MS really wants to get rid of the inventory - they need to give away these devices to Insiders to further test features and capabilities in Redstone 2. Less than 12% of Windows 10 Mobile devices are new 5 series devices and MS is going to loose it's feedback loop on those features if the Insider based isn't running the devices capable of running them.
MS did not release any details about the update in the KB and did not place any information on the Feedback Hub about this update. So to the honest I can't say what this update addressed.
Over the weekend I used the Release Preview setting of Windows Insider on one machine that was running the Threshold 2 (1511) Build 11586.494 to upgrade to the Anniversary release which I noticed after boot came in as 14393.5 - meaning the 2nd cumulative update release on July 30 was integrated. Then on Aug 2 this third cumulative update was applied.
I applied the update to all of my current test machines and the update installed with no issues.
However on one of my machines that runs an AMD Radeon R7 240 video card - I received errors on startup regarding the AMDSettings.exe app. While I can't say 100% that the cumulative update caused the issue, I also noticed that I received an AMD Video Driver update on July 30 as well. However even after applying the latest drivers from AMD, the error continued, so the .10 update seems to be causing the problem.
Post release MS is continuing to move forward with both Redstone 2 and apps. Today MS announced the newest release of the MS Maps app (5.1608.2117.0) for PC that contained Ink support.
As we move forward with Redstone 2 we are also going to see another jump in Build numbers. According to buildfeed.net the latest posted builds start in the 14894+ range. While nothing has been released yet - my expectation is we will start seeing builds in that number range.
This was similar to what we saw last year after the Threshold 1 (1507) release based on build 10240 - then first jumping to 10525 as the Threshold 2 branch started on the way to release based on 10586 and then 11099 when Redstone 1 started.
One platform that missed the "Anniversary" update date was Windows 10 Mobile. While Insiders like myself have been running 14393.5 - there was no public release of this build to supported devices on 10586. This is expected on Aug 9. I'm not 100% on what the delay is unless something came up with the new HP and Acer devices.
Finally a couple of new items:
First - Some 5.5 years after Starbucks released their initial Mobile App for iOS in Jan of 2011, they finally release an official version for Windows Mobile. While it is certainly nice to see, one has to wonder about the motivation here. What is also odd is that while this supposed to be an UWP app - it was not released for PC.
Second - MS reduced the price the for the unlocked Lumia 950/950XL here in the US. The 950 was reduced $150 (27%) to $399 which included a free display dock - an additional $99 savings. The 950XL was reduced by $200 (30%) to $449. So the winding down of the Lumia line is accelerating. MS has always had a hard time selling flagship phones - so I expect the price to drop even further as well head into fall.
As I've stated in earlier posts - if MS really wants to get rid of the inventory - they need to give away these devices to Insiders to further test features and capabilities in Redstone 2. Less than 12% of Windows 10 Mobile devices are new 5 series devices and MS is going to loose it's feedback loop on those features if the Insider based isn't running the devices capable of running them.
Comments
Post a Comment