Windows Client Guidance against speculative execution vulnerabilities

What an awful time to be a pc enthusiast. The latest revelations now kind of make me glad ASUS has not released a BIOS update addressing this yet for the z170 pro gamer as mine is a 6700k skylake machine

Likewise, Z170-P / 6700K Skylake here, presumably they now have to redo the microcode to fix the problem, this could go on for a long time!

Interesting times ahead.

Like I mentioned in one of my previous posts, that was one of my biggest fears. By being hasty in providing a microcode fix for this issue (Spectre & Meltdown), that could end up doing more harm than good. This is an excerpt from @johngalt's article above:

The bad news: Intel has previously warned that the microcode update it issued to provide some processor-based mitigation for some kinds of Spectre attack was causing machines with Haswell and Broadwell processors to reboot. It turns out that the problems are more widespread than previously reported: the chip company is now saying that Ivy Bridge, Sandy Bridge, Skylake, and Kaby Lake systems are affected, too.

Unless my olfactory sense is deteriorating, I am starting to "smell a rat" about the whole shebang. This problem with all processors has been around for more than 23 years, how come it has suddenly blown out of proportion just now?. Some articles about Spectre & Meltdown are even already talking about buying a new PC. I don't have the wherewithal to buy a new PC every 2-3 years..The one I am using right now was bought brand new in June 2015.

Hmmm Since I have a 6700k on a Z170 board and have applied the bios fix from Gigabyte 2 days ago, every thing seems to be running just fine. As far as performance, as far as I'm concerned, this cpu always idling in my machine. The only time I can get it generate any heat is to run Prime95.

I'm not convinced it's a good idea to announce existence of a major widespread PC problem before there's a workable fix for it. Hand wringing while we wait is of no benefit to anybody. Of course, I realize there are always those who take great pride in getting credited for finding flaws and will shout their discoveries from the rooftops.

I've tried to run this on both my main W10 PC and another running W8.1

In both cases I get the same errors. What am I doing wrong ?

Code:

Windows PowerShell
Copyright (C) 2014 Microsoft Corporation. All rights reserved.

PS C:\Windows\system32> Set-ExecutionPolicy Unrestricted -Scope Process -Force
PS C:\Windows\system32> Install-Module SpeculationControl -Force
Install-Module : The term 'Install-Module' is not recognized as the name of a cmdlet, function, script file, or
operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try
again.
At line:1 char:1
+ Install-Module SpeculationControl -Force
+ ~~~~~~~~~~~~~~
    + CategoryInfo          : ObjectNotFound: (Install-Module:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException

PS C:\Windows\system32>