Windows 10 Hotfix Repository

ohhh thanks a lot man! you're a genius!

Cheers

 

Didn't we discuss this here before?
From here down:
https://forums.mydigitallife.net/th...o-for-workstations.74909/page-51#post-1404803

&

https://forums.mydigitallife.net/th...o-for-workstations.74909/page-51#post-1404848

 

[*snip.

 

@abbodi1406

Thanks your w10ui script very useful.

Could you enhance detact alrady patched flash and the patch folder have new flash monthly to remove old one first?

now using the 4.1 to make own latest wim file have 2 different flash patch in remove list

 

You mean just flash player update? maybe

 

the rollup cu could replace the old one. Ex 16299.192 replace 16299.125. But the flash will list after that. Now show 17 Dec and 18 Jan

next monthly will have 3...

 

I always start from a blanc "first release" of a build, every month. I.e: "16299.15, 15063.0, 14393.0 etcetc", no previous updates present.

 

It only present in monthly flash update

 

M$ say this:

(to enable)
set FeatureSettingsOverride to 0
set FeatureSettingsOverrideMask to 3

(to disable)
set FeatureSettingsOverride to 3
set FeatureSettingsOverrideMask to 3

 

This (from quote above) disables the Meltdown and Spectre mitigations within Windows. Not a good idea to disable all.

set FeatureSettingsOverride to 1
set FeatureSettingsOverrideMask to 1

Setting those values to 1 disables only the Spectre mitigation which is caused by the faulty microcode. This way the problem is temporarily resolved, while you still retain OS level mitigation for Meltdown.

 

Afaik, the second one should always be 3: https://forums.mydigitallife.net/th...o-for-workstations.74909/page-51#post-1404848

 

It is quite confusing and messy on Microsoft's end because, you are right, their own documentation suggests always set at 3 for the Mask. But their actual patch (and details with patch) suggest 1 for both and the patch sets 1.

However, upon much testing, with the mask set at 1 or 3, the issue is solved either way and SpecuCheck reports accurately based on mitigations.

 

Not for the case of deactivating the Spectre v2 mitigation applied on BIOS level. Otherwise you're correct.

 

I give up on those patches/settings

 

That lately introduced fix should only be applied if the BIOS update to mitigate Stectre v2 was applied and causes errors.

 

I know, that's why i asked myself if it really was a hotfix for this thread

 

It was . Only needs to read the instructions about the usage scenario carefully .

 

so for this patch -- as final verdict, what's the best registry settings that impacts system performance minimally, especially for normal users...?

 

You need to login to view this posts content.

 

Here are my findings for the Spectre Variant 2 Critical Patch:

1. If the registry entries does not exist the update will create the FeatureSettingsOverride and FeatureSettingsOverrideMask entries and set both to 1.
2. If FeatureSettingsOverride was set at 0 and FeatureSettingsOverrideMask at 0 the update will change both to 1.
3. If FeatureSettingsOverride was set at 1 and FeatureSettingsOverrideMask at 1 the update will make no changes to these two entries.
4. If FeatureSettingsOverride was set at 0 and FeatureSettingsOverrideMask at 3 the update will change only the FeatureSettingsOverride to 1 while still leaving FeatureSettingsOverrideMask at 3.
5. If FeatureSettingsOverride was set at 1 and FeatureSettingsOverrideMask at 2 the update will change only the FeatureSettingsOverrideMask to 3 while leaving FeatureSettingsOverride set at 1.
6. If FeatureSettingsOverride was set at 1 and FeatureSettingsOverrideMask at 3 the update will make no changes to these two entries.
7. If FeatureSettingsOverride was set at 2 and FeatureSettingsOverrideMask at 2 the update will change both to 3.
8. If FeatureSettingsOverride was set at 3 and FeatureSettingsOverrideMask at 3 the update will make no changes to these two entries.