vastrad.blogg.se

1. #Bad windows optional update woody leonhard for free#
2. #Bad windows optional update woody leonhard Patch#
3. #Bad windows optional update woody leonhard windows 10#

In a January 21, 2015, Windows Experience blog post titled The next generation of Windows: Windows 10, we learned that Windows 10 would be a free upgrade. (If you are interested, you can take a look at the official countdown here.)

#Bad windows optional update woody leonhard for free#

That is the one-year anniversary of the release of Windows 10, which means the ability to upgrade to the new operating system for FREE will soon expire. Find out what happens after the offer expires.ĭon’t look now, but July 29, 2016, is coming up fast. The deadline for a free Windows 10 upgrade is right around the corner. Thx, do you think about these mangled, useless patches? Join us on the AskWoody Lounge. On the other hand, if you have installed your vendor’s microcode update, and you’ve installed the January Windows patches (one or more of the gazillion on offer), and you’re having problems - your machine stops unexpectedly, or performance hit the bottom of a molasses sludge pit - then installing KB 4078130 may help. In particular, if you’ve followed my recommendations and avoided this entire Meltdown/Spectre upgrading debacle - haven’t installed any of this month’s patches, haven’t installed the latest BIOS/UEFI microcode - there’s nothing in KB 4078130 that’s of interest. So, the proverbial bottom line: Should you be concerned? Only Microsoft knows for sure, and Microsoft ain’t saying. More likely, the registry changes implement some sort of bypass within Windows itself to avoid using the dicey Spectre 2 part of the Intel microcode.

#Bad windows optional update woody leonhard Patch#

3 - they’re hardly new.īut how, you may ask, does KB 4078130 actually work? It probably doesn’t disable Intel’s BIOS/UEFI firmware (although there was one occasion I can recall, years ago, when a Windows patch did update Intel microcode ). The registry keys were originally documented on Jan. Steve’s program gives you the option to turn off Spectre protection. It appears that these are the same changes implemented weeks ago by Steve Gibson in his InSpectre program. "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management" /v FeatureSettingsOverrideMask /t REG_DWORD /d 1 /f "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management" /v FeatureSettingsOverride /t REG_DWORD /d 1 /f There aren’t any details, but apparently this patch - which isn’t being sent out the Windows Update chute - adds two registry settings that “manually disable mitigation against Spectre Variant 2”: While Intel tests, updates and deploys new microcode, we are making available an out of band update today, KB4078130, that specifically disables only the mitigation against CVE-2017-5715 – “Branch target injection vulnerability.” In our testing this update has been found to prevent the behavior described. On Friday night, Microsoft released a strange patch called KB 4078130 that “disables mitigation against Spectre, variant 2.” The KB article goes to great lengths describing how Intel’s the bad guy and its microcode patches don’t work right: If you’ve been paying attention, you also know that, on the software side, Microsoft has patched, bricked (more accurately, “rendered unbootable”), pulled, repatched and generally changed Windows patching from a once-a-month headache to an advanced persistent threat. You all know that Intel has acknowledged that its latest firmware patches can cause “higher system reboots after applying firmware updates” in essentially all modern versions of its chips.