Windows 10: Big Change is the New Normal

Well, here we are. Its 2017 and we’re talking about Windows 10 compatibility issues. It wasn’t supposed to be this way.

Furthermore, we’re not talking about the potential compatibility challenges when migrating from an ageing platform like Windows 7, or even moving from a more modern platform like Windows 8.x. These potential application breaking changes have been raised against the migration effort of moving from one version of Windows 10 to a later branch or release of Windows 10.

Here is a high level overview of the “breaking changes” that Microsoft has introduced with Windows 10 1709:

  1. Microsoft Outlook support has been removed: this shouldn’t cause too many issues for modern applications, but some legacy code has hard-wired references for this legacy email client
  2. TCP Offloading Engine (TOE) deprecation: This means that a select number of hardware applications that utilized a lower portion of the TCP/IP networking stack may not function as intended.
  3. Trusted Platform Module (TPM) changes: there have been a number of changes (and more changes to come) that will affect some specific security focused applications (e.g. identity management software).
  4. Deprecated printer API: a small number of older hardware (printer/scanner) drivers are no longer supported
  5. Changes to the Microsoft ReFS Filesystem: this change may affect some server and disk management applications.

You can read more about the Windows 10 Release 1709 breaking changes here. And, with Microsoft’s accelerated lifecycle for Windows 10, you must be able to test all your applications each month and at least twice a year for significant feature updates.

Individually these Windows 10 changes may not create much of a problem for most organizations. However in aggregate and over many Windows 10 releases combined with rapidly changing security and numerous reported application vulnerabilities, there is now a problem. A testing problem that requires significant resources to respond to the nature and number of changes.

The problem is now how to rapidly respond to these changes without incurring the larger cost of manual application testing or assuming the risk of making untested changes and large-scale deployments.  The solution must be able to deliver a timely solution that produces enough insight, enough guidance for modern IT systems to respond to a rapidly changing environment.

The bottom line: your way of managing change must now change.

Greg Lambert

CEO, Product Evangelist

Greg Lambert is the CEO and product evangelist for Application Readiness Inc. Greg is a co-founder of ChangeBASE and has considerable experience with application packaging technology and its deployment.

Leave a Reply