Greg Lambert’s Patch Tuesday post for September is here. This September update cycle brings two zero-days and three publicly reported vulnerabilities in the Windows platform.
It is easy to get caught up in Microsoft’s marketing message that tells us application compatibility with Windows 10 isn’t an issue any more. In fact, Microsoft claims that 99% of all Windows 7 applications run on Windows 10 — based on its extensive telemetry data. As an IT manager responsible for migrating tens or even hundreds of thousands of users to Windows 10, you want to believe it because it would make our life so much easier. We all drank the Kool-Aid.
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.
The latest Windows 10 release from Microsoft has now been “released”. I am using quotes around “released” as Microsoft now has a staged development program called the Windows Insider Program that allows testers and enthusiasts to get an early preview months before the full release of the operating system software. This means that we get more stable updates from Microsoft and better upgrade experiences for all users: developers, enthusiasts and IT pros alike.
A few years ago, I founded a company called ChangeBase that developed a software product that helped assess and remediate compatibility challenges when migrating from Windows XP to Windows 7. ChangeBase was originally founded and developed to handle application packaging issues but when our team discovered the potential impact of moving applications from Windows XP to a more secure (by design) operating system – we knew that we could help.