Windows 10 Builds 17110 & 17112.1 - Some late cycle breakage

MS released two builds this week to rs4-release branch Fast Ring insiders.  First was 17110 on Feb 27, then 17112.1 on March 2.  Again there was no Skip ahead release.

 With the Redstone 4 branch nearing completion MS often releases multiple releases as it works down bug lists.  17110 contained about 15 fixes and 17112.1 contained less than 10.   

 But both builds broke stuff.   17110 broke the MS Store app.   The issue was quickly identified in the feedback forums and a Powershell command was published to correct the issue.

 Build 17112.1 broke Mixed Reality.   MS in fact warned Insiders at the top of the 17112.1 release notes of the issue as well as possible issues with Store, OneDrive and even potential boot loops.   

 To me I always question - if MS knew of these issues then why release the build?  

 Sure 17110 contained some last minute enterprise deployment updates - but explorer capabilities like being able to proper display and run the Store app are pretty basic.   

 Similarly with MR - the feature should have been pretty much locked down for release - so unless some other "fix" broke it there is really no excuse.  But items line OneDrive and Boot Loops shouldn't be showing up this late in a build cycle.

 Considering the version MS has posted with these builds is 1803 - meaning 2018 - March - and we are in March of 2018 - there really shouldn't be these kinds of breaks.

 In my mind we are less than 20 builds away from release (i've guessed 17120 - 17130).   Considering that the new ARM based Always Connected PCs from HP, Asus and Lenovo will all be available for order 1 week from today on March 9, tells me that MS is planning on releasing RS4 pretty soon.   So these kinds of issue always surprise me.

 Let's see what next week brings...


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