'Kernel memory leaking' Intel processor design flaw forces Linux, Windows redesign

Windows 10 Fall CU with Skylake i7 6700 (older, no K), I corrected above post, I thought I had a Haswell processor for some reason. I read this processor would see a 29% decrease in CPU performance once the various patches would be installed. This is the real relief, that the machine will remain zippy. Also, perhaps the Ashampoo checker runs the same commands as the Microsoft Speculative Execution Check via PS?

This is where I got the info about my CPU for the above older workstation. It may no longer be relevant since about a week has passed. These things can change overnight, right?

 

I would stay away from the Ashampoo checker. It crapped out in the middle of running on my AMD build with an "execution error." Had to be manually closed. Lucky for me, I double checked my Powershell ExecutionPolicy settings and current user was still set at "Bypass." To get it back to the default "Restricted" setting, you have to run the following command from admin level PowerShell:

Set-ExecutionPolicy -ExecutionPolicy Default -Scope CurrentUser

 

I ran it and all three of my machines are vulnerable to Spectre as expected and 2/3 probably will not receive a BIOS update.

 

Ashampoo Checker worked for my, but it also changed execution policy for my Win 8.1. Thanks for the info.

 

How do I check if I need to reset that now. Gees this bug is driving me nuts!

 

Unfortunately the CPU Checker from Ashampoo does not work on my system. I get a notification "Could not find the powershell executable" when I start the check.

 

Open admin level PowerShell. Then enter the following command:

Get-ExecutionPolicy -list

If Current User is set to "Bypass," then enter the command I previously posted.

 

Thank you @itman . Current User was set to Bypass and is now set to Restricted. I guess that is correct?

The other four lines all show as "Undefined".

 

On my Win 10 1709 build, local machine is also shown as restricted.

BTW - restricted means scripts cannot automatically execute.

 

So should of have typed "A" = Yes to all instead of just Y?

Edit: Or how do I change that?

 

I guess I really need to set PowerShell back to default. Is there a way to do that?

Thanks.

 

Will this work?

Code:

PS C:\> Set-ExecutionPolicy -Scope LocalMachine -ExecutionPolicy Restricted

Edit: This worked!

Code:

Set-ExecutionPolicy -ExecutionPolicy Default -Scope LocalMachine

 

I have this too. The first four entries are "Undefined".
The last one is set to "Restricted".

It should work. Further info: About Execution Policies

 

Worked for me also. Thank you @itman. and @mood.

 

Thanks mood.

I used:

Code:

Set-ExecutionPolicy -ExecutionPolicy Default -Scope LocalMachine

... And LocalMachine is set to to Restricted. Maybe not the default setting perhaps?

 

"Restricted" is the default policy. Setting a scope to "Restricted" or "Default" is basically the same.

 

The Ashampoo Checker worked for me no problem. I may luck out and get a BIOS update on January 24th from what I have read.

Here is my current PS settings.


Windows 10 x64 Enterprise 1709

 

If that's the default then all is good, except for the lack of firmware updates.

 

It all showed Undefined on my Windows 7 also. After setting them to Default they were set as Restricted. So Restricted is a "default" setting IMO.

 

Yep, you're right. It says so in 2nd line of your quote.

 

I changed Process scope also, but other 2 must be set through Gpedit (for which I can't find an option?).
I hope that all is covered.



EDIT: I just changed all to Undefined, it's easier.

 

Ashampoo Spectre Meltdown CPU Checker change the Powershell ExecutionPolicy.

SpeculationControl change the Powershell ExecutionPolicy.

SpecuCheck not change the Powershell ExecutionPolicy.

I propose to always use SpecuCheck.

P.S. With XP you get that layout using SpecuCheck because by default the Powershell Module is not present.
This even if the CPU is safe *

* = It's not on the Intel List.