Microsoft will kill some Windows 7 and 8.1 support in April (Apr 10 Patch Tuesday)

InfoWorld ^ | Mar 23, 2017 | Woody Leonhard

[dayglored]

Mark your calendar: Microsoft's promise to cut off Win7 and 8.1 support for the latest PCs will cause howls of pain next month

Events of the past week have drawn into sharp focus the likely result of next month's patching cycle. If you have a Windows 7 or 8.1 PC that you bought, built, or upgraded in the past year or so, it would behoove you to understand exactly what Microsoft plans.

Many people -- I'll raise my hand here -- thought that Skylake-based computers would continue to receive Windows 7 and 8.1 patches until the respective end-of-life. We are wrong.

Let's start with the basics. Intel introduced its so-called 6th Generation Skylake processor in August 2015. It slowly replaced the older Broadwell series, all of which will continue to work with Win7 and 8.1. Skylake now is slowly being replaced by 7th Generation Kaby Lake processors, which will not get Win7 or 8.1 support from Microsoft. To date, Intel has released 50 or so different Skylake processors. There are also dozens of Kaby Lake processors, which were introduced in August 2016.

On the AMD side there's a distinction made between the older Opteron series, the APU series (which includes Kaveri, Carrizo, and Bristol Ridge processors, named Athlon, Sempron, A4, A6, and E4) and the brand-new Ryzen processors, which are only now appearing on store shelves. Most observers say that 7th Generation AMD chips start with the Bristol Ridge APUs, which appeared in May, 2016. There's no change at all between the core architecture of the Carrizo and Bristol Ridge chips.

As I'll explain later, the distinction between 6th Generation Carrizo and 7th Generation Bristol Ridge is pivotal. To see if you have a Bristol Ridge chip, as opposed to a Carrizo chip, use Speccy to find your APU model number, then look up your APU model number for Bristol Ridge desktop processors or portable processors.

Where the troubles began

The whole Windows 7/8.1 support mess started in January of last year, when Windows honcho Terry Myerson declared that "as new silicon generations are introduced, they will require the latest Windows platform at that time for support." At first, Myerson promised:

Through July 17, 2017, Skylake devices on the supported list will also be supported with Windows 7 and 8.1. During the 18-month support period, these systems should be upgraded to Windows 10 to continue receiving support after the period ends. After July 2017, the most critical Windows 7 and Windows 8.1 security updates will be addressed for these configurations, and will be released if the update does not risk the reliability or compatibility of the Windows 7/8.1 platform on other devices.

Screams from enterprise customers reached all the way to the hallowed halls of Redmond. The promised demise of Win7 on Skylake machines changed later in January, then in March 2016, and in August 2016 they changed again. As of August, Microsoft exec Shad Larsen promised:

This policy change primarily applies to our commercial customers who are currently managing deployments with Windows 7 and Windows 8.1, and does not apply to customers running Windows 10 ... future silicon platforms, including Intel's upcoming 7th Gen Intel Core (Kaby Lake) processor family and AMD's 7th generation processors (e.g. Bristol Ridge) will only be supported on Windows 10, and all future silicon releases will require the latest release of Windows 10....

6th Gen Intel Core devices on Windows 7 and Windows 8.1 will be supported with all applicable security updates until the end of support for Windows 7 and Windows 8.1.... This change is made possible through the strong partnership with our OEM partners and Intel who will be performing security update validation testing and upgrade testing for 6th Gen Intel Core systems running Windows 7 and Windows 8.1 through the end of support dates.

On the same day, Microsoft updated a list of Skylake systems supported on Windows 7 and Windows 8.1 that includes links to manufacturer's websites, listing specific model numbers that the manufacturer commits to support with Windows 7 and 8.1 updates. The 12 deputized manufacturers and the links provided by Microsoft are:

• Acer
• ASUS
• Dell
• Epson (in Japanese)
• Fujitsu
• HP
• Lenovo
• LG (a Korean-language site that doesn't contain any model numbers)
• MouseComputer (in Japanese)
• NEC (in Japanese)
• Panasonic
• Positivo (in Brazilian Portuguese)
• Samsung
• Toshiba
• Wortmann (in German)
• VAIO (in Japanese)

Sites like Dell's are just as confused as I was. Dell says, "Microsoft originally indicated Skylake support would end in 2017. Microsoft has now extended Skylake support for Windows 7 through January 14, 2020 and for Windows 8.1 through January 10, 2023."

That isn't quite true. Microsoft has said that Dell will extend support for its listed Skylake systems through end-of-life for Win7 and 8.1.

Here are the conclusions that I draw from Microsoft's statements:

• If you have a custom built machine with a Skylake processor, you're out of luck. Since the machine doesn't appear on this list of anointed PCs, Microsoft won't support Win7 or 8.1 on your machine.
• If you upgraded a machine to a Skylake processor, you're out of luck.
• If you bought a machine from a different manufacturer, or your specific machine doesn't appear on the manufacturer's indicated website, you're out of luck.
• Most people -- most manufacturers -- don't understand this. I didn't.

I don't know what Microsoft intends to do with AMD chips. The way the announcements stand, AMD Bristol Ridge PCs won't have Win7 or 8.1 support, and there's no magic list of manufacturers or machines that are exempt from the ruling.

Where does that leave you?

So if you're running a recent-vintage PC and using Windows 7 or 8.1, what happens if you run afoul of the patch police? It's all well and good if Win7 is "no longer supported" on your PC, but what does that mean in real terms? Will your PC halt and catch fire?

Thanks to several reports that I talked about yesterday, including the tales of woe from folks who installed a Monthly Rollup Preview, I'm willing to bet that the blockade will unfold like this:

Step 1: April 10 rolls around, and about noon, Microsoft pushes its usual Patch Tuesday updates out the automatic update chute.

Step 2: Those gullible (or trusting) enough to have Win7 or 8.1 Automatic Update turned on will get the April Monthly Rollup (that is, the "April 2017 Security Monthly Quality Rollup"), which will install the next time the machine's rebooted.

Step 3: The Monthly Rollup installs itself and makes changes to Windows Update Agent, effectively preventing Windows Update from running again on this machine. The installer displays this message: IDG

The machine won't be destroyed, if this scenario plays out the way I think it will. Your PC will just have Windows Update disabled. (Which some people view as a feature, not a problem, but I digress.) We're still poking and prodding on the AskWoody Lounge to see what, exactly, gets disabled. None of this is documented anywhere, of course.

It's important to note that machines connected to a corporate Update Server (WSUS, SCCM, or the like) will only get the Monthly Rollup if it's pushed out by the admin. Even if Windows Update gets clobbered, it's unlikely that domain-managed PCs will suffer any ill effect, as they don't use Windows Update the same way most of us do. I have no idea how Microsoft intends to block Win7 updates on recent PCs attached to an update-managed domain.

This scenario brings up an obvious question: Will your machine get update-kneecapped? I don't know. There's no program I know of that you can run (short of a Monthly Rollup Preview, which I never recommend) that will definitively say, "If you install the Monthly Rollup in April, Windows Update will get disabled."

At this point, there's no warning either. No "Click here to install the Monthly Rollup and disable Windows Update going forward" safety net. All you get is a loud thud and that Unsupported hardware notice.

Will Microsoft go ahead with this latest push to get well-heeled customers, with the latest hardware, to change to Windows 10? Microsoft's under no obligation to support Windows 7 and 8.1 on any hardware that appears at a future date. I think. But this approach, if it unfolds in this manner, is sure to rankle more-advanced users who have paid for both Windows 7 and for a shiny new CPU.

We should know a lot more on April 10.

[LouieFisk]

>> Is there anything out there that could replace MS10 on current PC’s?<<
==
“Sure: Linux.”
==
Right now I’m using Linux - Lubuntu 16.04 themed with Win XP desktop/startbar & Win 10 icons. I have it dual booting with Win7 on the other drive.
Running Linux isn’t hard - a person just has to get used to the change from Windows. One change that’s great is the operating system and software are free. There are a lot of version to try out. And there are versions of Linux designed specifically for people coming over from Windows. (Versions are called “distros” in Linux-speak.)

The curious can check out different distros here:
https://distrowatch.com

I’ll have to study this Windows issue a bit more, might be dumping Windows before I planned! Ain’t gonna go with Win10.

[nopardons]

I have less than NO idea what CPU or "architecture" means and no way of finding out.

I have three different anti-virus programs.

I don't want windows 10; I don't do well trying to learn "NEW" things/ways with computers. Actually, I stink utterly at everything other than what I know how to do on one. That's not a problem for me, because I only do a few things on a computer or laptop...until faced with this HUGE problem.

So....just to make certain that I understand this....this means that as of April 10th, I can still use my laptop, won't lose anything, but CAN get "infected"/hacked?

[nopardons]

I don't know what either of those lake things are.

AFAIK, I have neither.

[dayglored]

I don't run Windows on "bare metal" much anymore -- all but one of my Windows machines are VMs (virtual machines), running under VMware, VirtualBox, or Xen, on either a Linux or Mac host.

So here's what I wonder:

Suppose you have a Linux box with Skylake or Kaby Lake, and you run a Windows 7 VM under that. Can Windows tell that the host is a given architecture? I wonder if that is hidden from the VM, and only a generic CPU abstraction is presented.

Gotta look into that... Anybody here know??

[dayglored]

> This just about begs for a “get a mac” reply.

Yeah, but we're not gonna say that out loud.

[PAR35]

1. Set a restore point now; when the update trashes your machine, try to restore to March 25. Maybe it will work.

2. Shut off all M$ updates now. Win7 should have its biggest holes patched by now; make sure you have good virus and malware software, and keep it up to date.

3. Upgrade to Mint.

[McGruff]

More Fake News.

[LouieFisk]

“Windows now requires more work arounds than Linux and it isn’t worth the trouble.”
==
On Win7 I have probably 8 diff security programs to handle the various threats. On Linux, I just use a firewall and an on-demand scanner, both free. It’s a lot less worry that way.

[dayglored]

We can do this the easy way. How old is your laptop?

If it’s older than a couple years, chances are very good it’s safe. These new CPUs only started appearing in retail products within the last two years or less.

[PAR35]

this means that as of April 10th, I can still use my laptop

I'm not sure that that has been established. The update may very well be malware.

[LouieFisk]

“Sadly, there simply is some software that won’t run under Linux (a lot of Adobe like Premier, Photoshop, etc).”
==
I assume you mean using Wine to run Windows progs?

[nopardons]

Yes, my laptop and the computer are over two years old.

But WILL I get Windows 10, forced down my throat? That would be as bad as getting Malware on it. :-(

[dayglored]

> More Fake News.

How so? Every statement in the article that is presented as known fact is true. There is also some speculation and some questions.

I didn't find anything in this article to be false. I don't want to be posting things that aren't true.

Please identify the false statements you found, and cite your evidence for their incorrectness.

[LouieFisk]

“I have three different anti-virus programs.”
==
In Windows the paid version of Malwarebytes (Premium) is a great investment.

[nopardons]

And IF I refuse to take the Windows 10 ( which I shall do! ) update....what then?

[Still Thinking]

Well, if Microshaft is that determined that they don’t want my business, I can’t really force it on them. Not that they’re currently fielding anything is but anyway, so they haven’t really lost anything.

[dayglored]

> But WILL I get Windows 10, forced down my throat? That would be as bad as getting Malware on it. :-(

NO.

Microsoft was forcing Win10 on people during the year it was "free". But now they make you pay for it. So they're not automatically downloading it for you and installing it for you. As far as I know.

On the other hand, they ARE trying to get you to switch to it. So beware any "offers" to try it out.

[LouieFisk]

“If it’s older than a couple years, chances are very good it’s safe. These new CPUs only started appearing in retail products within the last two years or less.”
==
I suspect I’m safe for awhile then: Dell Optiplex 960 came out in 2009, Intel Core 2 Duo CPU,

[swhiteman]

This is why I run Linux.

[McGruff]

Unless you have one of these 6th Generation Skylake processors it doesn't affect you, does it?