KB4078130 Update to Disable Mitigation against Spectre, Variant 2

Page 3 of 5 FirstFirst 12345 LastLast

  1. Posts : 750
    Windows 10 Pro 64-bits
       #20

    Brink said:
    Hey Cliff, :)

    Correct. This update is for those that have been impacted by the “higher than expected reboots and other unpredictable system behavior”.

    If you're not having any issues, then you could skip this update if wanted.
    Evidently, there is an expected reboot rate with Windows 10 and probably in previous versions as well. What is the expected reboot rate in Windows 10? Knowing this rate would help determining, if the patch should be rolled back, or not.
      My Computer


  2. Posts : 30,120
    Windows 11 Pro x64 Version 23H2
       #21

    One thing to consider no matter how frequent, they said data loss. So I would think you lose what you are doing when the reboot occurs. Even if it is just a page of work it is unnecessary waste of time. One opinion.
      My Computer


  3. Posts : 55
    Windows 10 Pro
       #22

    On 13.01.2018,i've reinstalled Windows 10 version 1709 on my PC after i applied a new BIOS version with updated micro-code (yes intel fix for spectre),and since that,i don't experienced any issues with my PC,maybe a bit performance impact,but what is bother me now,is Intel who sayd that almost all OEM's producators should remove that BIOS who contain fix for spectre from their website,and wait to a better fix with even less impact of performance,and me i already applied that BIOS,install older version of BIOS over the newest one is a bit risky for me.

    LE: My system is Kaby Lake,i3 7100 with ASUS H110M-CS,i did not have any restarts on my PC with those intel fixes,so i guess i'm okay.
      My Computer


  4. Posts : 255
    Win 10 64bit
       #23

    Polo6RGTI said:
    The update changes the "FeatureSettingsOverride" setting from 0 to 1.

    Code:
    Windows Registry Editor Version 5.00
    
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management]
    "FeatureSettingsOverride"=dword:00000001
    "FeatureSettingsOverrideMask"=dword:00000003
    
    ; 3 = Disable both
    ; 2 = Disable meltdown (Kernel VA Shadow)
    ; 1 = Disable spectre (Branch Target Injection)
    ; 0 = Enable both
    ;
    ; FeatureSettingsOverrideMask is always 3
    We have a laptop that is experiencing frequent reboots so applied the fix. I have checked and both settings in the registry are set to 1.

    However, the frequent reboots are continuing. When the fix was run the file seemed to somehow lose the .exe extension which makes no sense to me but might this be significant?

    Plan B was to do a repair install but unfortunately the machine rebooted during the download of installation media. I am now downloading the media onto a USB drive and hope that will work.

    If not, any other suggestions would be welcomed...
      My Computer


  5. Posts : 2,666
    Windows 11 21H2 (22000.593)
       #24

    Cr00zng said:
    Evidently, there is an expected reboot rate with Windows 10 and probably in previous versions as well. What is the expected reboot rate in Windows 10? Knowing this rate would help determining, if the patch should be rolled back, or not.
    I think that would have been worded better if they had said "If you experience reboots that were not expected". So, yeah, nice gaffe on their part, eh?

    Caledon Ken said:
    One thing to consider no matter how frequent, they said data loss. So I would think you lose what you are doing when the reboot occurs. Even if it is just a page of work it is unnecessary waste of time. One opinion.
    Data loss is possible - not definite. I've rebooted in the middle of doing things plenty of times (forced reboot - aka reset button / forced power off) and not lost a thing.

    It's hit and miss, but the general rule of thumb is "The more times your machine abnormally and randomly reboots, the better your chances are for data loss." Which leads to the original rule of thumb: "Backup, backup backup."

    SaggyMaggyPoo said:
    We have a laptop that is experiencing frequent reboots so applied the fix. I have checked and both settings in the registry are set to 1.

    However, the frequent reboots are continuing. When the fix was run the file seemed to somehow lose the .exe extension which makes no sense to me but might this be significant?

    Plan B was to do a repair install but unfortunately the machine rebooted during the download of installation media. I am now downloading the media onto a USB drive and hope that will work.

    If not, any other suggestions would be welcomed...
    Try using GRC's InSpectre to see which you are patched for (and for the ones actually installed on your system, you can disable them and reboot and see if it makes a difference).

    That will be a lot faster than doing a repair install / clean install / reset / whatever...

    And even if you have downloaded it already before, download it again - it's small, for one thing, and he's still updating it, for another, so it's more than likely that any previously downloaded copy is out of date.
      My Computers


  6. Posts : 750
    Windows 10 Pro 64-bits
       #25

    johngalt said:
    I think that would have been worded better if they had said "If you experience reboots that were not expected". So, yeah, nice gaffe on their part, eh?
    Is that a "gaffe", or some dev/tech people wrote the release and it slipped by the PR department?
      My Computer


  7. Posts : 2,666
    Windows 11 21H2 (22000.593)
       #26

    Good point....
      My Computers


  8. Posts : 1,750
    Windows 10 HOME 64-BIT
       #27

    KB4078130 Update to Disable Mitigation against Spectre, Variant 2-blah.jpg

    Ehmmm......?
      My Computer


  9. Posts : 6
    Windows 7 U x64
       #28

    InSpectre instead sets those values to "3"., but here, they say, the values should be both "1" in order to disable it. What is right?
    Actually there is one more key got created by the "kb4078130_b86f0bf2dc0866a0e117ed2d4a5302fab0493a7b" but not mentioned nowhere named "041f1d33-a86a-4d7a-a2da-cf4b265131f9" value "0".
    Anybody knows what that means?
      My Computer


  10. Posts : 255
    Win 10 64bit
       #29

    johngalt said:
    Try using GRC's InSpectre to see which you are patched for (and for the ones actually installed on your system, you can disable them and reboot and see if it makes a difference).

    That will be a lot faster than doing a repair install / clean install / reset / whatever...

    And even if you have downloaded it already before, download it again - it's small, for one thing, and he's still updating it, for another, so it's more than likely that any previously downloaded copy is out of date.
    Did the repair install anyway which does seem to have solved the rebooting issue (though it's early days yet!). I also downloaded InSpectre and ran it on both our laptops and both say they are vulnerable for Spectre, giving the following information:

    This system's protection against the Spectre vulnerability has been deliberately disabled by system settings. Even if the system's hardware is able to manage the Spectre threat, the operating system's settings will need to be changed to enable Spectre protection.

    Windows' Spectre vulnerability protection (only) has been deliberately disabled by settings in this system's registry. Although overall system performance will be improved, this system will be vulnerable to Spectre attacks. Meltdown protection has not been disabled.

    I ran the KB4078130 update on both laptops initially, but then did a repair install on one, which presumably replaced the registry, so not sure why both would be showing vulnerabilities to Spectre.

    Assuming the reboot problem is fixed, is it possible (does it make sense) to change the registry setting(s) back to 0?

    Dell are advising not to update the BIOS yet so I guess we just have to wait and remember those back-ups!
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 06:06.
Find Us




Windows 10 Forums