Windows 10 Build 14905 - Redstone 2 for Mobile Appears

Just 4 business days after releasing the first Redstone 2 branch build for PCs, MS released Windows 10 Build 14905.

 This is the first Redstone 2 build that supported Windows 10 Mobile as well.  

 For both PC and Mobile there were a handful of improvements/fixes around Edge, Sketchpad and some call actions.

 As always I installed on a PC, Laptop, Tablet and Phone and all installed with no issues.  

 As with 14901 - MS called out that Adobe Reader would fail in 14905 on PC, but yet on one of my machines it is working fine.  The difference is that on that machine I have Visio 2013 installed.  My other machines which do NOT have Visio 2013 installed - Adobe fails.  So obviously Adobe see's some library or function was installed with Visio 2013 that allows it to run.  There is no Adobe issue on Mobile.

 I was happy to see that my lowly Lumia 735 is still supported on Redstone 2.  To be honest I was expecting an updated announcement from MS on supported platforms for Redstone 2 - with another wave of legacy devices removed from support.

 As i've mentioned before though, while I may see some performance improvements via the updates to OneCore, many of the new features in Redstone 2 I just won't be able to test since the 735 doesn't have the supported hardware.   

 But I do expect to see a number of app improvements, especially with Office, Cortana, Edge, etc.    

 I have noticed a little crisper performance on my 735 with 14905.  Nothing earth shattering, but better than 14393.  

 Nothing much else to report on this build - So now it's just settling into the rhythm of Redstone 2 builds and see how this branch progresses over the next 9 months.










Comments

Post a Comment

Popular posts from this blog

Solar Storage - 2023 Update

  A few years back I published a 2 Part post discussing Solar Energy systems.  The discussion focused on all the due diligence and prep work needed and what were some of the key considerations around designing and implementing a solar system. One of the discussion points was around solar storage or batteries.  What were the use cases for batteries and if they were a good investment and should you incorporate them into your design. Back in 2020 - the math around batteries said no - that you wouldn't be able to break even on the cost of a storage system over its normal warranty life of 10 years. So here we are three years later and so I figured it was time to revisit.   There are two primary uses cases for solar storage.    First is what's called peak offset or peak shifting.  This is a concept where you utilize stored solar generation to run your home during what many utilities call Peak Periods that are part of a general category of rate plans known as Time of Day (TOD) plans.
Read more

ASUS RT-AC68U Router & WDS - a nice solution for a large home.

I recently had a newer Asus RT-AC87U Router die.  The wireless chipset never seemed to work well and first the 5Ghz bands started to fail and then the 2.4Ghz failed leaving my 25 wireless device household high and dry. So after some due diligence I decided to replace with 2 of the older RT-AC68U and implement a Wireless Distribution System (WDS) configuration. In the past - I've mentioned an open source router OS called DD-WRT.  The Asus routers come pre-installed with their version of DD-WRT.  Asus does utilize their own UI overtop DD-wrt and overall I do not like nearly as much as the traditional UI - but core dd-wrt capabilities are there.   Additionally you can flash the RT-AC68 with native DD-WRT if your so inclined. In my previous configuration I was also using an older Linksys 4200 running dd-wrt configured in Client Bridge mode that allowed clients to connect to the Linksys as well as use some of the bands to connect back to the RT-AC87U. While it worked - I felt that
Read more

Home Automation Platforms + Matter - Early Observations

For those of us who have been involved in automating homes by adding "smart" devices from light switches to thermostats, cameras, sensors, controllers, etc - there was always a challenge with managing the wide range of devices. While each OEM had their own app that would allow you to control their devices - you'd often end up with anywhere from 4 - 10 apps that were required to manage the entire home.  And depending on your product choices you also had to have hubs to communicate from your Wifi network to other RF networks like Zigbee or Z-Wave.  With many of these "hubs" they had native support across multiple vendors or you had to add plugins or provide specific OEM support. Some OEM apps were great, some sucked, but it became challenging to provide a solution for a client where they could easily manage their home on their own.  Between having to maintain multiple credentials/logins across the apps and even communicating which app controls what - it sometimes
Read more