Here are the tests results after CPU Haswell-e Update µCode from "3A" to "3B":
1) Ashampoo Checker Tool does diagnostic no vulnerability, and this is confirmed by Mitigation Status Tool:


Nota: Checker Tool does warm 'internal error' is there is no internet connection during the test !

2) Performances does seem downgraded from 8% to 13% (Anvil benchmark) for the system disk.
Chris Win Index does also report a similar downgrade performance of the system disk.

@mbk1969, @Skello , @Lex
Here are some questions about the 2 tools I used to detect Meltdown/Spectre vulnerabilities on two different platforms:

1) Ashampoo Spectre Meltdown CPU Checker Tool v1.1.0
The requirements are:

Another requirement not reported is the need of a internet connection active.
Why ?
(If the PC is not connected you get an 'internal error'...)

This tool does work on Intel_X99_W10_64bit_RS3 platform with these .NET Frameworks and PowerShell versions installed and updated:


This tool does fail on antique AMD_Sempron_3000_W7_32bit_SP1 with these .NET Frameworks and PowerShell versions:


Is it because .NET Frameworks v5.1 is not installed ?
Is it because PowerShell v2.0 is obsolete ?
May be, but trying to install .NET Frameworks v5.1 (Win7_KB319566-x86 file) does offer a BSOD.
So, its egg and chicken .. this tool does require a MS piece of software which is not supported!
This does seem a conceptual bug.

Moreover, Lex reported me this Tool does seem bugged and does open the vulnerability of the PC because "It changes ExecutionPolicy in PowerShell to less secure. After use you probably need to execute:
Set-ExecutionPolicy -ExecutionPolicy Restricted -Scope CurrentUser
Set-ExecutionPolicy -ExecutionPolicy Restricted -Scope LocalMachine

Please can you explain in more details what does it mean ?
Any additional action to do after each time the Tool is run ?

It does seem a conceptual non sense that a such tool does open the vulnerability to check if the PC is vulnerable ?
If my PC is more vulnerable after running the tool than before, what is the interest ?

2) Mitigation Status Tool

This tool does work on Intel_X99_W10_64bit_RS3 Haswell-E CPU for µCode "3A" and "3B".
Does this tool also open the vulnerability of the Intel_X99 PC ?

This tool does fail on antique AMD platform as reported to mbk1969.
Is not it PowerShell version v2.0 instead of v5.1 ?
Is not it .NET Frameworks version problem ?
Does this tool also open vulnerability of the AMD platform ?

Zitat von 100PIER im Beitrag #17

---

@mbk1969, @Skello , @Lex
Here are some questions about the 2 tools I used to detect Meltdown/Spectre vulnerabilities on two different platforms:

1) Ashampoo Spectre Meltdown CPU Checker Tool v1.1.0
The requirements are:

Another requirement not reported is the need of a internet connection active.
Why ?
(If the PC is not connected you get an 'internal error'...)

This tool does work on Intel_X99_W10_64bit_RS3 platform with these .NET Frameworks and PowerShell versions installed and updated:


This tool does fail on antique AMD_Sempron_3000_W7_32bit_SP1 with these .NET Frameworks and PowerShell versions:


Is it because .NET Frameworks v5.1 is not installed ?
Is it because PowerShell v2.0 is obsolete ?
May be, but trying to install .NET Frameworks v5.1 (Win7_KB319566-x86 file) does offer a BSOD.
So, its egg and chicken .. this tool does require a MS piece of software which is not supported!
This does seem a conceptual bug.

Moreover, Lex reported me this Tool does seem bugged and does open the vulnerability of the PC because "It changes ExecutionPolicy in PowerShell to less secure. After use you probably need to execute:
Set-ExecutionPolicy -ExecutionPolicy Restricted -Scope CurrentUser
Set-ExecutionPolicy -ExecutionPolicy Restricted -Scope LocalMachine

Please can you explain in more details what does it mean ?
Any additional action to do after each time the Tool is run ?

It does seem a conceptual non sense that a such tool does open the vulnerability to check if the PC is vulnerable ?
If my PC is more vulnerable after running the tool than before, what is the interest ?

---

Name                           Value
----                           -----
PSVersion                      5.1.16299.98
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.16299.98
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
 

Value "PSVersion" gives you actual version of PS.

Now to "Set-ExecutionPolicy". It only sets PowerShell policy for execution of PowerShell scripts on your computer. You can decide whether to allow execution of PS scripts downloaded from network (allow, allow only to signed ones, disallow). So it is not a system wide setting.

Zitat von 100PIER im Beitrag #17

---

2) Mitigation Status Tool

This tool does work on Intel_X99_W10_64bit_RS3 Haswell-E CPU for µCode "3A" and "3B".
Does this tool also open the vulnerability of the Intel_X99 PC ?

This tool does fail on antique AMD platform as reported to mbk1969.
Is not it PowerShell version v2.0 instead of v5.1 ?
Is not it .NET Frameworks version problem ?
Does this tool also open vulnerability of the AMD platform ?

---

@mbk1969
Thanks for the information.

1) About W7 SP1 AMD platform.
Ashampoo Tool:
Yes, I am not familiar with WFM and .NET items.
Ashampoo Tool does need WFM v5.1.
Under W7 x86 WFM v5.1 is offered via "Win7-KB319566-x86.zip" file. As I said in my last post, trying to apply this KB does offer BSOD on W7 SP1 platform.
So, does it mean this tool does not work on any W7 SP1 platform ? (contrary to the listed requirements) ?
or
Do I have first install .NET v4.x over the native v3.5 on W7 SP1 ? and then may be WFM v5.1 is installable ?
Do I have also to upgrade native PS v2.0 to PS v5.x ?
Is there an order to respect to install these 3 components (.NET, WFM, PS) ?

Mitigation Status Tool:
Do you have validate your tool as well for W7 SP1 32bits ? I don't understand why the error code "0xC0000003"
If I understand your tool does need only .NET Frameworks v4.5 or upper (no PS, no WFM used).

2) About W10 platforms.
I have also tested the tools on a P8Z77-V Deluxe W10 x64 RS3 platform with Intel IvyBridge CPU.
Here are the screenshots:


BEFORE W10 Cumulative Updates January:


AFTER W10 Cumulative Updates January:


Why the "false" value for item (PCID performance) for CVE-5754 after W10 January updates for ?
On X99 Haswell-e the value is "true".

Zitat von 100PIER im Beitrag #19

---

@mbk1969
Thanks for the information.

1) About W7 SP1 AMD platform.
Ashampoo Tool:
Yes, I am not familiar with WFM and .NET items.
Ashampoo Tool does need WFM v5.1.
Under W7 x86 WFM v5.1 is offered via "Win7-KB319566-x86.zip" file. As I said in my last post, trying to apply this KB does offer BSOD on W7 SP1 platform.
So, does it mean this tool does not work on any W7 SP1 platform ? (contrary to the listed requirements) ?
or
Do I have first install .NET v4.x over the native v3.5 on W7 SP1 ? and then may be WFM v5.1 is installable ?
Do I have also to upgrade native PS v2.0 to PS v5.x ?
Is there an order to respect to install these 3 components (.NET, WFM, PS) ?

---

Zitat von 100PIER im Beitrag #19

---

@mbk1969
Mitigation Status Tool:
Do you have validate your tool as well for W7 SP1 32bits ? I don't understand why the error code "0xC0000003"
If I understand your tool does need only .NET Frameworks v4.5 or upper (no PS, no WFM used).

---

Zitat von 100PIER im Beitrag #19

---

Why the "false" value for item (PCID performance) for CVE-5754 after W10 January updates for ?
On X99 Haswell-e the value is "true".

---

@mbk1969
Thanks for the reply about PCID feature. It is clear.

On my antique AMD W7 platform .NET v4.7, v3.5, v3.0, v2.0 does coexist at the moment. Even .NET v4.7.1 update is properly installed. So, it is OK for .NET components.
However PS2 is installed. So I have to upgrade PS2 -> PS3 -> PS5. (may be i can found the different PS versions somewhere on MS site ?)
Then may be "Win7-KB319566-x66.zip" (WMF v5.1) will be installable and then may be Ashampoo Tool be working..

@100PIER

According to this page
https://docs.microsoft.com/en-us/powersh...=powershell-5.1
"The installation package for PowerShell comes inside a WMF installer. The version of the WMF installer matches the version of PowerShell; there's no stand alone installer for Windows PowerShell."

See section "Upgrading existing Windows PowerShell" (links are there)

Thanks,
I have succeed finally, with MS Tech support help, to get WMF v5.1 and PS v5.1 working on W7 SP1 32 bit (safe mode was a necessity to install , and also forget BSOD).
However, Ashampoo tool does not work:

@100PIER
Have you tried my tool on Win7 32bit? If it works then you can leave Ashampoo`s one. After all I just took source from original MS script, from MS developers themselves.

@mbk1969

1) Yes are the test results with your Tool under W7 SP1 32bits PowerShell v5, WMF v5.1, .NET Framework v4.7.1 running on a legacy antique MSI-AMD platform:


What do you think about ?

2) The purpose of your tool and Ashampoo tool is the same: does detect Spectre/Meltdown vulnerabilities of the PC.
Frankly, my preference is your tool because I don't understand why for the same purpose your tool does not need one internet connection and Ashampoo Tool does need one. Is it for spying/logging the results ?

What is your opinion ?

Zitat von 100PIER im Beitrag #25

---

@mbk1969

1) Yes are the test results with your Tool under W7 SP1 32bits PowerShell v5, WMF v5.1, .NET Framework v4.7.1 running on a legacy antique MSI-AMD platform:


What do you think about ?

---

Zitat von 100PIER im Beitrag #25

---

2) The purpose of your tool and Ashampoo tool is the same: does detect Spectre/Meltdown vulnerabilities of the PC.
Frankly, my preference is your tool because I don't understand why for the same purpose your tool does not need one internet connection and Ashampoo Tool does need one. Is it for spying/logging the results ?

What is your opinion ?

---

@mbk1969
Thanks for your comments.
1) Here is the link to the Complete List (Rev 4.0) of CPUS (Intel, AMD, ARM, Apple) concerned by the bug Meltdown/Spectre:

Complete List of CPUS concerned by Meltdown/Spectre

AMD is also concerned by the Spectre exploit 2:
AMD Spectre

2) Ashampoo Support does confirm a bug, a new release will delivered soon after fixing it.
The internet connection does seeem needed due to a MS "piece of software" only available by internet:
[u]the application needs an internet connection because the newest routines from Microsoft are needed, which are only available online. The problem in your case might be that there is a blank space in the path for either your user name or the temp folder. Our developers are working on a fix for this bug which should be solved soon. There will be a new version of the CPU Checker available after this problem has been solved.[/u]

Zitat von 100PIER im Beitrag #27

---

@mbk1969
Thanks for your comments.
1) Here is the link to the Complete List (Rev 4.0) of CPUS (Intel, AMD, ARM, Apple) concerned by the bug Meltdown/Spectre:

Complete List of CPUS concerned by Meltdown/Spectre

AMD is also concerned by the Spectre exploit 2:
AMD Spectre

---

The provided CPU List link does confirm AMD CPUs are not vulnerable to Meltdown bug.

Just to let you know that there is no need to install WMF v5.1 and using Ashampoo v1.1. Besides, there are some talks on the net that this tool is blocking and preventing the update patch from Microsoft to be installed in Windows. But that is not yet confirmed.

Bettter to use one of those two tools that provide more details anyway:

SpecuCheck This tool must be executed with CMD or PowerShell

Or...

The Microsoft tool script via PowerShell, here are the commands to run:

1- Set-ExecutionPolicy -ExecutionPolicy REMOTESIGNED (answer "Yes")

2- Install-Module SpeculationControl (Answer "yes" for all questions)

3- Import-Module SpeculationControl

4- Get-SpeculationControlSettings

5- (Optional) Set-ExecutionPolicy -ExecutionPolicy RESTRICTED (This set back the default policy. It is not recommended to run this command on a server because REMOTESIGNED is the default on a windows server)

Details on the output of this tool can be found here.