My summary: What you’re witnessing is a colossal “Sky is Falling” routine, aided and abetted by folks who are going to make money from the havoc. Don’
[See the full post at: January Patch Tuesday overview]
|
There are isolated problems with current patches, but they are well-known and documented on this site. |
-
January Patch Tuesday overview
- This topic has 265 replies, 37 voices, and was last updated 5 years, 7 months ago.
AuthorViewing 82 reply threadsAuthor-
Sound advice as ever from @woody some of us who have been around these “infernal machines” a long time are truly bewildered as to the amount of speculation, conjecture, “falling sky predictions”.
I my self am just going to use the tried and trusted “Patch Prohibition” Woody style until the situation clears and hard facts and figures emerge and a raising of the “Defcon”. It seems, however, there may be a performance hit coming as inevitable consequence. -
Likely some performance hit with the Windows patches, but I’d be surprised if you even noticed.
And if your three-year-old computer turns to sludge, be of good cheer. We now have decent alternatives, like Chromebooks.
NO! Put DOWN that brickbat. <gd&rvvvf>
1 user thanked author for this post.
-
I’m more worried about the CPU possibly slowing down after updating, since Microsoft claims that “Ohh Windows 7 and 8.1 users will have it worse”, what a coincidence, right? I don’t believe a word that comes from Microsoft, if this is true, they are probably doing it on purpose to force people to Windows 10, it wouldn’t be the first time. If my CPU really does slow down, I don’t even know if it’s worth updating my system. Please post your thoughts on this when we know more.
5 users thanked author for this post.
-
Given GWX, etc. I too do not believe it is intentional.
That said, I bet the corporate marching orders say nothing about trying to avoid degrading Win7 or Win8.1 user experiences.
1 user thanked author for this post.
-
-
Forgive me if this question has already been answered in the myriad of info. on this topic. Does the MS Security Only patch for Group B’ers contain the Meltdown/Spectre/processor patch too? I hope it does or we’ll all be forced into Group A.
Thanks so much for keeping us informed on this and all the other things Woody.
Being 20 something in the 70's was much more fun than being 70 something in the 20's.1 user thanked author for this post.
Thanks for the article, Woody, a good read as always.
My concerns on all of this are not to do with any threat posed by Meltdown or Spectre, but the threat posed by the supposed fixes to any such threat. My two home desktops comprise an Intel machine with an AMD Radeon graphics card and an AMD Phenom II machine (with a Nvidia card) so I could end up being bricked in both cases. Add to that my natural reluctance always as a faint-hearted amateur to contemplate such dramatic and usually irreversible changes as a BIOS update and you can begin to see where my concerns are coming from.
I shall continue to sit back and do nothing except keep abreast of the advice and recommendations offered here, so far as both what to do and when to do it are concerned!
On both this 10 year old 32 bits Single core Intel Atom N280 (-HT-) clocked at 1666 Mhz Kernel~4.14.0-12.1-liquorix-686-pae i686 and on my other 4 or 5 years old Intel i3, I’ve beta tested the Windows 8.1 Security Only January updates.
I’ve had no problems and I haven’t noticed much slowdown because I barely use Windows on them.
Either way, I’ve uninstalled the updates on both machines because I think I’ll lose more with the performance slowdown compared with the potential exploitation risk AT THIS MOMENT.
I’ve saved the update files on a backup HDD, just in case for the future.
On Linux Mint Debian Edition 2 I use everyday on them, I’ve installed the 4.14.0 Kernel that still hasn’t implemented the software workarounds for Specter and Meltdown. There again, on this very old and very usable laptop, any performance tick is squeezed up to the maximum as this is still a very usable “typewriter” and I don’t want the ~5 – ~30% performance drop. I don’t want to spend money on a new laptop that still has a faulty CPU. NO!
I wonder if Intel is selling their affected CPUs on a ~5 – ~30% price discount…
No bitcoins to steal here, Sir Hacker. Please keep moving on, dear Sir…
1 user thanked author for this post.
From Woody’s article:
Your three-year-old PC isn’t going to turn into a pile of sludge, in spite of what Microsoft says.
In fact, doesn’t it seem more likely at this point that it will become less functional if you rush to apply the patches right away?
I’ve seen graphs of system usage from enterprise monitoring systems. They show a drop in efficiency and an increase in CPU usage after the patches are applied. This is not happy news; it’s going to cost people real money.
Something I’ve not seen discussed (probably mostly because I’m not all knowing and have a lot of other things to do than browse the web scouting for Meltdown and Spectre info):
Let’s say you take the update (not a BIOS update, just the current crop of Windows updates)… Furhter, presume you see a definite loss in performance. Can you uninstall the update(s) and get back the lost performance? Or is this a trap door?
-Noel
-
Good question. I assume you can roll back the Windows updates, but not the firmware changes.
But I haven’t tried. Anybody out there know for sure?
1 user thanked author for this post.
-
One user, in the previous thread, posted a link to a discussion about using the vmware cpu microcode update driver for windows, freely downloadable.
I guinea pigged it, works like a charm ( my cpu seems has no ucode fix yet, but it got updated with an older fix from some years ago correctly ), it’s loaded/applied on installation .. then on reboot … gives the same advantages of the linux way of doing firmware patching, and can be removed in seconds.
If removed, the cpu simply reverts to the latest microcode in the bios.my 2 cents, avoid the bios update and go this way… it’s not invasive, works as well as with a bios update, and can be reverted without hassles or reboots
3 users thanked author for this post.
-
When I went to the MS Update Catalog, the January patches did say they were able to be removed.
You are so correct in your implication about BIOS/firmware updates.
Firmware and especially BIOS updates are far more risky. In the past, I have found BIOS installs and rollbacks are like baseball, you hit, miss or have a foulball. In the real world this works out to you successfully are able to install the new BIOS or firmware. However lets say the new BIOS or firmware update gives an unforseen problem on your system. You “may be able” to try re-installing the older BIOS or firmware update to fix the a problem. It may also be impossible (or at least have dire warning from the manufacturer) that installing an older version is not allowed. Therefore you cannot regress back and you have to live with the new BIOS. The foulball is when you attempt it and you brick the system into an unusable or unrepairable state.
BIOS updates and many firmware updates are not in my mind an average user thing, especially when they read the support literature cautions and are justifiably nervous. Sure there are now Windows based installs that are easy and usually reliable, and some even save a backup of the old BIOS, but if there is an error and you can no longer boot it gets pretty scary. I never race to install any BIOS or firmware update, and research as many sources as I can first. In fact most MB manufacturers caution against BIOS updates if your system is running well and has not exhibited the issues in the change log.
My experiences with UEFI is much more limited, and have been smooth, but I have read of some problems.
In a nutshell, if I did a BIOS or firmware update and it slowed the PC, I would either learn to live with it, or at least have a backup PC for use, before I even attempted to try to undo any update. SInce all the support info is now net based (oh, you did go to the OEM website and download the technical manuals first, right? Oh, they were dated 3 years prior… oops.), not having a backup PC or device to research how to fix it is like not having a life jacket in a boat.
I’ll let you know about the patches, when I get the courage to apply them. I take images daily, so they should be easy to roll back from if the performance hit is ridiculous.
But as far as the hardware microcode or BIOS stuff, I’m not expecting anything from my mobo maker, since I am running a 6 year old 3rd gen Intel Core system…
Windows 10 Pro 22H2
Great summary as always, Woody. But: Why Monday…?
1 user thanked author for this post.
-
OOOOPS. Trying too hard, I guess. Thanks!
1 user thanked author for this post.
-
-
-
-
-
That’s because it’s easy for me to change the main blog header – and devilishly difficult to change the header at the top of this page.
Fixed! 😉
-
-
-
-
-
1 user thanked author for this post.
-
I went your suggested way, yesterday (even if my cpu has no recent patch. Still got applied one from a few years ago, happily).
I think it’s a safer and more practical method to get all our cpus updated without incurring in side effects or risks.
And we have full control of the revision of the microcode we want to use ( bios, removing the driver, or any newer of choice, assuming it exists, by just using the package with the preferred month/year from intel )1 user thanked author for this post.
-
-
-
-
@Mr. Brian: I’ve been under the weather so am just now trying to get caught up, and there is so much here to try to understand I may be unable to get caught up. I’m not familiar with a lot of what is being referred to (e.g. spectre variant 2). Unless each person posting references their OS, Group, etc., it is difficult to know what they are specifically referring to.
Not a “complaint” per se, however from my perspective it is difficult to tie these all together at times. Thank you for all of the information you disperse to all of this Forum’s users. It is all very much appreciated, and I’m hoping to get caught back up again one of these days. I have no clue where we stand with the .Net Framework updates either.
Your diligent and flawless information is appreciated, as always. 🙂
1 user thanked author for this post.
-
-
-
-
The patch you installed, KB 4056892, is the Cumulative update that is usually released on Patch Tues. It was released early because of the Meltdown/Spectre vulnerabilities. The other patches were normal Patch Tues patches.
There were a bunch of other patches released for different versions of Windows, Office. .NET, etc. If they did not apply to your machine, you would not get them.
1 user thanked author for this post.
It’s possible to update the microcode in Windows or Linux without a BIOS/UEFI update. In this case, the microcode update is temporary. See Intel has released microcode update v20180108 with Meltdown/Spectre fixes.
Got a VMware Workstation Pro 14.1.1 update today that claims to pass through more of the pertinent hardware info to the guest OSs, so I decided to try testing the latest crop of updates in my suite of VMs (Win 7, 8.1, 10).
I had to put the registry entry in place in my Win 7 and 8.1 VMs, as in those I’m not running an AV package. Without the registry entry the January update was not offered through a Windows Update “Check for Updates” run.
I benchmarked each setup before and after the update using PassMark PerformanceTest. Since PC systems – especially if run in a virtual machine – are prone to doing what they want when they want, I actually was not able to measure a statistically significant slowdown after vs. before the updates. This seems hopeful.
I haven’t done Win 10 VM testing yet, nor am I anywhere NEAR convinced to update my actual hardware systems yet.
-Noel
4 users thanked author for this post.
-
Office CtR is supposed to update itself. My guess is that, in the case, Microsoft’s running a bit behind.
1 user thanked author for this post.
-
-
When I manually check for updates, by clicking this
button it sends me to This Page which tells me to use Windows Update. Windows Update does not update Office 2010. So what gives. Is there another way to manually check for updates? Microsoft Update Catalog perhaps.Dell, W10 Professional, 64-bit, Intel Core i7 Quad, Group A
HP, W7 Home Premium, 64-bit, AMD Phenom II, Group A
-
-
-
@Sparky
There do appear to be 6 updates, depending on which modules you have installed. However, for each of those KBs on the catalog, there are a number of language options to choose from for each “bitness”, as you probably found.i.e. for KB4011610
I feel it is probably more helpful to use Method 3 to download from the Microsoft Download Center link, which gives you simpler language selection access than the MS Update catalog does. However, there is a caution about .msi updates not suiting all versions of installation, so this may not be suitable.
Good luck!
-
-
-
When I manually check for updates, by clicking this
button it sends me to This Page which tells me to use Windows Update. Windows Update does not update Office 2010. So what gives. Is there another way to manually check for updates? Microsoft Update Catalog perhaps. This happened to me a couple of years ago, after a WU repair – that was in the old days before I discovered the prudence of installing only security updates. I lost all the tickboxes on the WU settings page and could only update my MO etc. via the catalogue. I won’t comment on the joys of that procedure! Then I decided to change my antivirus and installed MSE and a miracle happened: all the tickboxes came back and I have since been able to update all my MS products the old-fashioned way, via WU. It is actually much easier, as long as you keep your setting to ‘Never’ alternated with ‘Notify but don’t download’. So installing MSE will fix it, if you want to go down that route: there may well be alternative fixes I don’t know about.
-
-
PKCano,
I have never Edited the Registry so I’m a bit hesitant to venture into the unknown. With that said here is as far as I went:
Am I suppose to change the blue highlighted number 14a384d to the number 0 and click OK ?Dell, W10 Professional, 64-bit, Intel Core i7 Quad, Group A
HP, W7 Home Premium, 64-bit, AMD Phenom II, Group A
-
That doesn’t look like the same registry entry, so I would not change that value (note the difference in the left hand column of the right panel).
First word of caution with doing any registry edit: always do a backup first! Go to File>Export and save a copy you can use to import should something go wrong 🙂
-
You are in the right place in the Registry. (See mine)
Write down the current information that is highlighted so you can change it back if necessary.
Change the blue highlighted to 0 (zero not oh)
Close the Registry
Open Word – choose “install updates only”
Close Word and open Windows UpdateChange settings
There should be a check box with “Updates for other MS Products” checked.
Be sure WINDOWS UPDATE IS NOT ON AUTOMATIC.
(If the check box is not there, try rebooting.)
Search for updates – uncheck whatever you don’t want to install and install all the Office patches. You may have to recheck several times to get all of them.
-
Just to let you know this is what WU Change Settings looks like right now before doing anything with the registry.
“Updates for other MS Products” Box is checked. This is how it has looked from the day I purchased the computer Feb 2011. It is showing 14.0.7160.5000 which is October 13, 2015 version, so it has been updating up until that date.What is interesting when I do the below:
“If you would like to update Office but can’t open any of your Office apps, try repairing your Office suite:
A. Go to Control Panel > Programs > Uninstall a program.
B. Find and select your version of Microsoft Office on your computer.
C. In the bar above, click Change.”
When I click on Change it tells me I have to be connected to the internet, I am connected. It is like the program can’t tell if there is a internet connection. WowDell, W10 Professional, 64-bit, Intel Core i7 Quad, Group A
HP, W7 Home Premium, 64-bit, AMD Phenom II, Group A
-
On my system (which may differ from yours), I get an option to Repair Office, by right-clicking (see below). Have you tried that, if you have the option? It may possibly help…
My apologies if you’ve already done this 🙂
-
When I click on Change it tells me I have to be connected to the internet, I am connected. It is like the program can’t tell if there is a internet connection. Wow
There are some errors that can occur with CTR that relate to being unable to open (I struck it about 12mths ago on a different machine, so I’m working from memory). It related to disabled services.
You could try typing Services into your Win search box (it may need right-click Administrator rights to edit entries), and check for items marked Office or CTR, to make sure they are enabled.
-
I Fixed the update problem by doing the below:
Your Internet provider may have silently enabled IPv6. This is what happened to me. Apparently the Click to Run Manager doesn’t like IPv6. I went to my network adapter settings and unchecked that protocol and I was able to repair Office Starter. Link
It was as simple as A,B,C,D,E
Apparently Click to Run Manager doesn’t like IPv6 for some reason.
I selected “Use recommended settings” but that changed WU to “Install Update Automatically” which I changed back to “Never check for updates” I also rechecked the IPv6 box after MS Office Starter 2010 Updated. Maybe from now on when ever there is a new office update I’ll have to do it again.
Dell, W10 Professional, 64-bit, Intel Core i7 Quad, Group A
HP, W7 Home Premium, 64-bit, AMD Phenom II, Group A
-
WOW! Good sleuthing !!
1 user thanked author for this post.
-
PKCano,
I was wondering if you or anyone has seen anything like this.
While trying to solve the MS Office Starter 2010 update problem and before fixing it, I noticed in the Event Viewer, hundreds if not thousands of errors (amdkmdag 62464) . These go back as far as the Event Viewer stores info 12-22-17. After researching, it has something to do with a piece of video that has not passed HDCP checks. That seems to jive because the error is created when I play a video online or offline. This is strange because it must have started happening within a few months. I really don’t know what started causing this from happening. Other than taking up Event Viewer space, there are no video problems. This Link is what have found to disable it and suppress the messages. Unless it has something do with recent patches. Any thoughts Appreciated.
Isn’t great when you’re trying to fix one problem and you find another.Dell, W10 Professional, 64-bit, Intel Core i7 Quad, Group A
HP, W7 Home Premium, 64-bit, AMD Phenom II, Group A
-
-
-
-
KB4033342 is the .NET 4.7.1 installer for Win7.
To receive the Jan Rollup, your anti-virus program has to be up to date and has to put a ALLOW Regkey in your Registry. If the key is not there you will not be offered the Jan update through Windows Update. You can find out if your AV program is compatible here.
Also, the Jan update is causing BSODs with certain AMD processors. Microsoft has blocked the update temporarily from computers with those processors until the problem can be resolved.
Either one of those reasons may be why you did not receive the Jan Rollup.
-
-
-
-
I just rechecked the McAfee Consumer Support site and found the following:
Windows Product Compatibility for McAfee Products
McAfee has performed validation testing on the following products and found them to be compatible:- McAfee LiveSafe (MLS)
- McAfee All Access (MAA)
- McAfee Total Protection (MTP)
- McAfee Internet Security (MIS)
- McAfee Anti-Virus Plus (MAV+)
- McAfee Anti-Virus (MAV)
- McAfee Cloud AV
-fm
Edit to remove HTML
1 user thanked author for this post.
-
-
-
Unbootable state for AMD devices in Windows 8.1
released in MU catalog only
-
-
This new update probably doesn’t help with recovery if you installed one of the faulty updates. From just looking at the file sizes of https://www.catalog.update.microsoft.com/Search.aspx?q=KB4073576 vs https://www.catalog.update.microsoft.com/Search.aspx?q=KB4056898, perhaps the new update should be considered the replacement for the security-only update?
-
-
-
An update is available to fix the following issue that occurs after you install January 3, 2018—KB4056898 (Security-only update) or January 8, 2018—KB4056895 (Monthly Rollup): AMD devices fall into an unbootable state.
In a month full of falling-down-the-rabbit-hole comments, this one has to take the cake. A fix for a bug that renders a machine unbootable.
Either somebody’s badly delusional, or they have a tremendous sense of humor.
-
-
-
Any official superecedence?
1 user thanked author for this post.
-
-
-
abbodi86 has reported a problem with this month’s .NET monthly rollup for .NET Framework 4.7.1 at https://blogs.msdn.microsoft.com/dotnet/2018/01/09/net-framework-january-2018-security-and-quality-rollup/.
-
abbodi86 has reported a problem with this month’s .NET monthly rollup for .NET Framework 4.7.1 at https://blogs.msdn.microsoft.com/dotnet/2018/01/09/net-framework-january-2018-security-and-quality-rollup/.
Wow, that’s a problem, especially since I’m planning to upgrade from .NET 4.6.1 to .NET 4.7.1 in the not too distant future. I have hidden KB4055532 until Microsoft gets this straightened out.
-
-
Jan K. said:
I’ve installed that .net update. Haven’t experienced any problems, but good to know if/when it should happen.If you fulfill ALL of the following conditions:
- MS .NET Framework 4.7.x
- KB4055002: MS .NET 4.6.x/4.7.x quality & security rollup patch (Jan 2018)
- Win 7 — the only affected OS so far
… you could try running a .NET-dependent program & change its font to see if you can trigger it to crash.
Afterall, that’s the primary purpose of Microsoft pushing out the patch. 🙂
Lennart Bauer:
Removing KB4055002 solves this. Microsoft need to employ some testers …Stephen Hogan – Progress Systems Limited :
I think *we* are the testers …Edit to remove content. Please stay on topic.
-
According to that same page in the comments, Pavel Drtil offers a solution.
Replacing files from a working machine will fix the problem too:
c:\Windows\Microsoft.Net\Framework64\v4.0.30319\WPF\Fonts\GlobalUserInterface.CompositeFont
c:\Windows\Microsoft.NET\Framework\v4.0.30319\WPF\Fonts\GlobalUserInterface.CompositeFont
I assume that “working machine” can also mean your machine before applying the update. So, perhaps copying these two files to another location before installing KB4055002 (or this month’s NET rollup), installing the update and then copying those files back and overwriting the new (corrupted) font files should fix the issue, too.
1 user thanked author for this post.
-
Yes, that would work, or from Windows Installer backup cache
C:\Windows\Installer\$PatchCache$\Managedwhile this will solve the visible issue with GlobalUserInterface.CompositeFont, KB4055002 has more underlying issues
as example, clr.dll will be reverted to 4.7.2117.0, as wel as many files
so you basically will have franken 4.7/4.7.1 installation1 user thanked author for this post.
-
-
-
-
If you fulfill ALL of the following conditions:
- MS .NET Framework 4.7.x
- KB4055002: MS .NET 4.6.x/4.7.x quality & security rollup patch (Jan 2018)
- Win 7 — the only affected OS so far
… you could try running a .NET-dependent program & change its font to see if you can trigger it to crash.
Afterall, that’s the primary purpose of Microsoft pushing out the patch.
This concerns me. I’ve got Win 7 and I plan to install .NET 4.7.1 soon.
I already hid the Jan .NET roll-up patch based on early reports, but the situation seems to be even worse than it first appeared.
-
-
alpha128 said:
I’ve got Win 7 and I plan to install .NET 4.7.1 soon. I already hid the Jan .NET roll-up patch based on early reports, but the situation seems to be even worse than it first appeared.Are you planning to install .NET v4.7.1 over v4.7, or over an older v4.x version ?
I’ve .NET v4.7 installed on Win 7 x64 since Jul 2017, & have not encountered any problems. I was holding out on installing .NET v4.7.1 because it has a few issues. but these are apparently resolved with the recently-released .NET v4.7.1 Update, which seems to be stable (no reported problems so far). So my plan is to upgrade to .NET v4.7.1 in the near future.
KB 4054856: .NET v4.7.1 Update (09 Jan 2018):
https://support.microsoft.com/en-us/help/4054856
https://www.microsoft.com/en-us/download/details.aspx?id=56480Note that this .NET v4.7.1 Update is not a standlone .NET installer. It requires .NET v4.7.1 to be installed first.
As such, if you are going ahead to install .NET v4.7.1, remember to also install the .NET v4.7.1 Update, followed by Jan 2018’s Security Only patch.
-
Are you planning to install .NET v4.7.1 over v4.7, or over an older v4.x version ? I’ve .NET v4.7 installed on Win 7 x64 since Jul 2017, & have not encountered any problems. I was holding out on installing .NET v4.7.1 because it has a few issues. but these are apparently resolved with the recently-released .NET v4.7.1 Update, which seems to be stable (no reported problems so far). So my plan is to upgrade to .NET v4.7.1 in the near future. KB 4054856: .NET v4.7.1 Update (09 Jan 2018): https://support.microsoft.com/en-us/help/4054856 https://www.microsoft.com/en-us/download/details.aspx?id=56480 Note that this .NET v4.7.1 Update is not a standlone .NET installer. It requires .NET v4.7.1 to be installed first. As such, if you are going ahead to install .NET v4.7.1, remember to also install the .NET v4.7.1 Update, followed by Jan 2018’s Security Only patch.
I did install .NET 4.7.1 over 4.6.1 just today. I checked for updates afterwards and the only .NET update that is being offered to me via Windows Update is Security and Quality Rollup for the .NET Framework 3.5.1, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, and 4.7.1 updates for Windows 7 SP1 and Windows Server 2008 R2 SP1 (KB 4055532). It has already been noted elsewhere in this topic that Windows 7 users running .NET 4.7.1. should NOT install this update, as it overwrites 4.7.1 binaries with older 4.7 versions. KB4055532 was originally offered to me as a checked update. When I unhid it, it had changed to an unchecked update. I have hidden it again.
1 user thanked author for this post.
-
-
The .NET 4.7.1 reliability Update will not be offered separately on Windows Update
it’s bundled with the .NET 4.7.1 entry itself as companion update (hidden)and if you manually installed .NET 4.7.1 previously (when it was released), then you also need to install the Update manually
the Update is separate because it’s specific for .NET 4.7.1, whereas the Rollup targets all 4.6 > 4.7.1 versions
-
-
-
-
-
Articles KB4055002 and KB4055532 have modified with a known issue that links to “TypeInitializationException” or “FileFormatException” error in WPF applications that request fallback fonts after you install the January 9, 2018, .NET Security and Quality Rollup (KB4055002): “Windows Presentation Foundation (WPF) applications that request a fallback font or a character that is not included in the currently selected font return the following error messages:”
I was offered KB 4033342 as an important unchecked update by Windows Update on the 9th of January. Tonight I notice I’m no longer offered that.
It’s the .NET 4.7.1 upgrade for Win 7, so maybe MS recognizes the problem.
Win 7 Pro sp1 x64 core i-3
1 user thanked author for this post.
-
-
Have you installed the .NET 3.5.1 rollup KB4054998?
what’s the size shown on the .NET rollup?1 user thanked author for this post.
-
-
.NET updates are not offered separately, each entry represent all bundled .NET rollups
so even if you don’t have any .NET 4.x product installed, KB4055532 will be offered bundling .NET 3.5.1 update KB40549981 user thanked author for this post.
-
-
I was offered KB 4033342 as an important unchecked update by Windows Update on the 9th of January. Tonight I notice I’m no longer offered that. It’s the .NET 4.7.1 upgrade for Win 7, so maybe MS recognizes the problem. Win 7 Pro sp1 x64 core i-3
I checked, and when I first looked at Windows Update it said my system was up-to-date! Then I clicked “Check for Updates” and it immediately came back with 2 Important and 2 Optional updates. KB4033342 was being offered to me as a third optional update yesterday.
I wonder if Microsoft intended to re-release KB4033342, this time with the correct files to harden it against Meltdown.
-
.NET 4.7.1 itself has no problems, and KB4033342 still have the same binaries
it’s KB4055002 rollup that holds the security fixes, and issues
1 user thanked author for this post.
-
.NET 4.7.1 itself has no problems, and KB4033342 still have the same binaries it’s KB4055002 rollup that holds the security fixes, and issues
I wonder then if Microsoft pulled the .NET 4.7.1 installer to prevent Windows 7 users from installing the .NET January roll-up on top of it and wreaking havoc.
But when the dust settles, and Woody changes the MS-DEFCON rating to 3, what I’m going to want is the one thing Microsoft is telling me I can’t have – a version of .NET 4.7.1 on Windows 7 that is hardened against Meltdown.
-
-
-
Maybe because QualityCompat registry is required to get .NET updates too but i see that security fixes in .NET 4.7.1 rollup/security-only is dated 2017-11-22 that’s older than Windows security fixes, most are 2018-01-02
Yes, because the January .NET roll-up requires the QualityCompat registry key, I assumed that the 4.7.1 updates it contains were to harden it against Meltdown. But perhaps it’s not the case after all.
At this point, I’m strongly tempted to let Paint.NET update itself, which will install both version 4.0.20, and .NET 4.7.1.
-
-
-
.NET 4.7.1 itself has no problems, and KB4033342 still have the same binaries it’s KB4055002 rollup that holds the security fixes, and issues
Today I upgraded my Paint.NET to version 4.0.20, and it first installed .NET 4.7.1, as that was a requirement. Both upgrades went smoothly.
1 user thanked author for this post.
-
From https://blogs.msdn.microsoft.com/dotnet/2018/01/09/net-framework-january-2018-security-and-quality-rollup/: “Please avoid installing this update on Windows 7 or Windows Server 2008 R2.”
From https://github.com/dotnet/announcements/issues/53:
“The root cause of this problem is a MSI setup interaction between the .NET Framework January 2018 Rollup (KB4055002) and an already installed version of .NET Framework 4.7.1 product. The Rollup installer unexpectedly overwrites the 4.7.1 version of the GlobalUserInterface.CompositeFont file. This causes WPF operations that need this font file to fail.
All updates are extensively tested before they are provided to you. We are investigating the gap in our testing and will resolve that for our next release.”
-
All updates are extensively tested before they are provided to you. We are investigating the gap in our testing and will resolve that for our next release.”
Should that be chasm or abyss instead of gap?
5 users thanked author for this post.
-
-
Well, I guess that might explain why, after several days of being offered the rollup update (KB4055532 for Win 7) as a checked, important update by Windows Update, it suddenly this afternoon went from being checked to unchecked.
Could be. I hid KB4055532 when the first reports of trouble came in.
Jan 9, 2018 4:31 AM (Meltdown & Spectre)
I received a fix from MS to Win 10 pro. it slows down my computer significantly. I attached results. Software used for testing was PerformanceTest 64 bit by Passmark. Hardware is Lenovo Thinkpad T440s model 20ARS04W00. First test was right before installing update. Next 3 after update. I could not first believe my eyes. But you can see results…
So Intel says that affect is not noticed by average user. That simply is not true.
Everybody who uses his/her computer every day like I do, will see (and pay) for the difference ;-(
5 users thanked author for this post.
-
Thank you; I’m hungry for real test results.
That particular set is alarming, however Passmark PerformanceTest (or any benchmark) is known to show quite variable results for disk testing. That’s the nature of PC systems; they do a lot of different things all the time. I’ve had run to run variances of 2 to 1 just doing subsequent tests. I’d really like to see a whole SERIES of before/after benchmarks. Also, PerformanceTest has some advanced tests that would be good, such as some real world simulations of disk loads…
I’ve benchmarked all my systems before and after updates for years. I’ve accumulated enough that if/when I install these latest patches I’ll be able to document a trend with statistical certainty. I’m also accumulating data doing other real world operations.
I’ve already found that I cannot sense a speed difference in virtual machines after vs. before the installation. But this may well be a situation where it HAS to be tested on the actual hardware to yield real results.
If I can find evidence that removing the Windows Update can be a fallback to restore prior performance I’ll go ahead and test it on my less critical system. Until then, like most here, it’s wait ‘n see.
-Noel
-
NVIDIA GeForce Driver 390.65 WHQL Security Update
https://www.ghacks.net/2018/01/08/nvidia-geforce-driver-390-65-whql-is-a-security-update/
-
Be wary of installing the new Nvidia graphics driver 390.65, there is a lot of adverse feedback on the official forums from people reporting slower game performance and BSODs etc. with this driver. The slower performance is ironic given that, according to one poster’s understanding, the new driver doesn’t provide additional security as Nvidia GPUs are not affected by the current concerns, but is instead intended to counter any impact on performance from other software patches for Meltdown and Spectre. I’ve no idea how true that understanding is.
For the moment, however, I’d advise relying on the same advice for new drivers that we apply to other updates – keep a watching brief for a few days but let others be the guinea pigs! That is, of course, in addition to the usual advice on replacing effective drivers – if it ain’t broke, don’t fix it!
-
-
-
It could also be because your anti-virus program has not set the Registry key to confirm compatibility.
1 user thanked author for this post.
-
-
I have one Windows 7 SP-1 Pro machine showing the KB4056894 Monthly Rollup available for download and install.
The AV I am running there is Bitdefender Free, and it has set the required registry value.
On my other two computers running Windows 10, they have the registry flag set by the AVs running in them, Avira Pro and Avast Free, respectively. Good to go!
But not gonna apply any patches just yet though… 😉
Windows 10 Pro 22H2
-
If you are familiar with editing the Registry, yes, you can create the key.
Use caution editing the Registry.
1 user thanked author for this post.
-
The January updates removed Equation Editor 3.0.
1 user thanked author for this post.
-
-
-
Good morning, Woody.
No, I haven’t installed the January Office patches yet. I was going to edit my registry to disable the Equation Editor. That’s when I found that I did not have the registry entries referenced by the Microsoft article: https://support.microsoft.com/en-us/help/4055535/how-to-disable-equation-editor-3-0
1 user thanked author for this post.
-
-
-
From https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/ADV170021: “**Update: ** On 1/9/2018, Microsoft released an update for Microsoft Office that adds defense-in-depth configuration options to selectively disable the DDE protocol in all supported editions of Microsoft Excel.”
2 users thanked author for this post.
About that Equation Editor and its issues:
Power Point also has one. Any indication there is the same problems with it?
Thanks.
Ex-Windows user (Win. 98, XP, 7); since mid-2017 using also macOS. Presently on Monterey 12.15 & sometimes running also Linux (Mint).
MacBook Pro circa mid-2015, 15" display, with 16GB 1600 GHz DDR3 RAM, 1 TB SSD, a Haswell architecture Intel CPU with 4 Cores and 8 Threads model i7-4870HQ @ 2.50GHz.
Intel Iris Pro GPU with Built-in Bus, VRAM 1.5 GB, Display 2880 x 1800 Retina, 24-Bit color.
macOS Monterey; browsers: Waterfox "Current", Vivaldi and (now and then) Chrome; security apps. Intego AV1 user thanked author for this post.
-
Yes, latest update kills it
they propose another ways
https://support.microsoft.com/en-us/help/4057882/error-when-editing-an-equation-in-office -
There are other better ways than what MS suggests. Check out this and a few posts beneath it for my recommendations.
https://www.askwoody.com/forums/topic/january-security-patches-are-coming-shortly/#post-158044
-
-
-
You can insert and edit new equations using the editor built into Office version 2007 or later. For more information about inserting and editing equations, see Write, insert, or change an equation. However, you will not be able to edit existing equations that were inserted using Equation Editor 3.0 in that manner.
Alternatively, the third-party app MathType enables you to edit Equation Editor 3.0 equations without security issues. MathType is now part of the Wiris Suite. You can download a free MathType 30-day trial at: http://www.wiris.com/equation_editor/microsoft
-
-
According to the linked page, Equation Editor 3.0 was included in versions of Office older than 2007. Since v.2007, the function of Equation Editor has used a new native Equation Editor.
Check this answers.microsoft MVP answer for details (hope that helps).
So I understood that “Resolution” to say that using v.2007 or later (2007 – 2016), you can use the new native Equation Editor to create new equations and to edit equations made by the new native Equation Editor, but anything that had already been created using the old Equation Editor 3.0 could not be edited using the new native Equation Editor.
4 users thanked author for this post.
-
Thanks Kirsty, I learned something new today.
I never knew before that Word 2007 had TWO ways to insert equations. And the one that’s being removed seems to be the one that I never knew existed!
1 user thanked author for this post.
-
-
-
From Unbootable state for AMD devices in Windows 7 SP1 and Windows Server 2008 R2 SP1:
“An update is available to fix the following issue that occurs after you install January 3, 2018—KB4056897 (Security-only update) or January 4, 2018—KB4056894 (Monthly Rollup):
AMD devices fall into an unbootable state.”
This update can probably be considered a replacement for the January 2018 security-only update.
-
I have an Intel core i-3 and Intel HD graphics; i.e., no AMD chips to the best of my knowledge. Does it matter which update I install, KB 4056897 (security only) or KB 4073578, which I presume is also security only? I’m going to wait until Defcon 3; just trying to stay even with the game.
1 user thanked author for this post.
-
I think I’m convinced it’s a replacement. But I do wish they would get rid of the old one and just have one security only update that would work for all machines whether Intel or AMD. I’m assuming the new one does in fact work for both brands of processor.
I wonder if MS has incorporated the changes they made in the new security only update into the January Rollup.
1 user thanked author for this post.
-
MS certainly has added to the confusion by inserting “This update does not replace a previously released update.” In both “Unbootable state for AMD devices” articles.
Both of the Security-only patches (KB4073578 for Win7 dated 1/12/18 and KB4073576 for Win8.1 dated 1/10/18) revised for unbootable AMD have been added to AKB2000003.
-
Both of the Security-only patches (KB4073578 for Win7 dated 1/12/18 and KB4073576 for Win8.1 dated 1/10/18) revised for unbootable AMD have been added to AKB2000003.
While waiting for Defcon 3 and Woody’s instructions…..
Should we consider installing ONLY these two new patches for AMD cpus? (to avoid boot problem)
Are either the earlier SOQUs for the month (4056897, 4056898) or these new ones equally o.k. for Intel cpus?
Or choose the new ones only?
-
Hmmm. Good question.
There is an ongoing discussion (above) about whether KB4073576 and KB4073578 replace the previous Security only patches or not. Read the MS pages (which are vagur) and the above discussion (see quotes from the pages) – and toss a coin?
-
Hmmm. Good question. There is an ongoing discussion (above) about whether KB4073576 and KB4073578 replace the previous Security only patches or not. Read the MS pages (which are vagur) and the above discussion (see quotes from the pages) – and toss a coin?
I’m in no hurry…..Let Little Mikey go first.
-
-
-
-
The new update probably works fine with Intel processors. I’ll test this briefly on my Intel-processor computer within the next few days. If the old update works fine on your computer, then there probably is no compelling reason to install the new update. What we don’t know is whether the new update has problems that the old update doesn’t have.
-
As a test, I installed KB4073578 on two computers with two different Intel CPU models. I then rebooted and logged into a user account on each computer. There were no apparent problems. Since I am not in Group B, I then got rid of this update on both computers.
-
-
-
-
Just a quick question. Do you have the MSPowerpoint Viewer, the MSWord viewer, or the Office Compatibility Pack installed or showing in Installed Software? I have found that even if you uninstall MSOffice, these programs remain and will trigger certain Office updates in Windows Update.
Most of these are older programs (from either Office 2007 or 2010 era) that had to be installed manually if I remember correctly.
On one machine I dropped Office and went to LibreOffice, yet kept getting WU Office updates. I uninstalled all and the WU Office updates stopped.
1 user thanked author for this post.
Tweet from Kevin Beaumont: “CVE-2018-0802 (new Equation Editor exploits) in wild now. Exploit which embeds any .exe and runs, using OLE Packager.dll function […]”
From Microsoft: CVE-2018-0802 | Microsoft Office Memory Corruption Vulnerability.
3 users thanked author for this post.
-
Proof-of-concept video: Exploiting CVE-2018-0802 Office Equation Vulnerabilty.
1 user thanked author for this post.
-
It could be the MSWorks install. Some versions of Works included a de-featured version of Word. I forgot to put that in my post as I once found that was an issue, but that was back in the XP or Vista days.
Another possibliky is there is still an unactivated image (or part thereof) of Office that was loaded by your OEM when you bought the PC.
There is something that uses core Office components that is triggering it. MS has pushed out some security updates for out of support Office versions. I have still gotten them on my XP machine a few months ago. That machine is not usually connected online, but I went to see if the Office 2007 patches would download and they did.
1 user thanked author for this post.
At some point today my main machine is showing that the .Net Framework update for Windows 7 (KB4055532) has become unchecked…
Keep everything on hold folks, this story of ” An Everyday Month in the Life of Windows” still has a few chapters yet to be written!
1 user thanked author for this post.
@mazzinia and @Seff. Same exact thing happened to me a day or so ago.
My current status is I’m no longer offered 4.7.1 at all and the rollup (KB4055532) is now important but unchecked.
Every patch I’ve been offered in January has either been yanked or changed from checked to unchecked. Some of the yanked ones have come back, some haven’t. Even the group B patches seem to show up and disappear and then show up again in the Microsoft catalog. I keep thinking patch Tuesdays can’t get any worse, but this one is insane.
McAfee finally got their act together, and my employer pushed the January roll-up for Windows 7 (KB4056894) to my work computer today.
No BSOD, and no slowdown detected after installing the patch.
However, if you’ve disabled libraries, this is one of those months where you’re going to want to re-enable them before installing the updates. Otherwise, you’ll lose the ability to rename folders in Windows Explorer.
1 user thanked author for this post.
The most recent 4 KB articles at Windows 10 and Windows Server 2016 update history now have this issue listed: ‘After installing this update, servers where Credential Guard is enabled may experience an unexpected restart with the error, “The system process lsass.exe terminated unexpectedly with status code -1073740791. The system will now shut down and restart.” […]’
1 user thanked author for this post.
Windows 10 updates released today:
January 18, 2018—KB4073291 (OS Build 16299.201)
1 user thanked author for this post.
The files ndp47-kb4074880-x64[…].exe and ndp47-kb4074880-x86[…].exe currently in the catalog for KB4055532 (January 2018 .NET Framework monthly rollup for Windows 7) have a digital signature of January 11, 2018, which is newer than the original release date. Also, despite the fact that I installed the January 2018 .NET Framework monthly rollup for Windows 7 on Monday (I have .NET Framework 4.7), it is being offered again in Windows Update (it’s ticked).
From CVE-2018-0792 | Microsoft Word Remote Code Execution Vulnerability and CVE-2018-0797 | Microsoft Word Memory Corruption Vulnerability: “01/18/2018 To address a known issue with installing security update 4011021, Microsoft is announcing the availability of security update 4011022 as a replacement. Customers who experienced problems installing 4011021 should install 4011022.”
Important changes today to these articles:
4 users thanked author for this post.
From https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/ADV180002: “01/18/2018 On January 5, 2018, Microsoft re-released KB4056898 (Security Only) for Windows 8.1 and Windows Server 2012 R2 to address a known issue. Customers who have installed the original package on 1/3/2018 should reinstall the update.”
From https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/ADV180002: ’01/18/2018 Microsoft has released security update 4073291 to provide additional protections for the 32-bit (x86) version of Windows 10 Version 1709 related to CVE 2017-5754 (“Meltdown”). Microsoft recommends that customers running Windows 10 Version 1709 for 32-bit systems install the update as soon as possible. Microsoft continues to work to provide 32-bit (x86) protections for other supported Windows versions but does not have a release schedule at this time. The update is currently available via the Microsoft Update Catalog only, and will be included in subsequent updates. This update does not apply to x64 (64-bit) systems.’
1 user thanked author for this post.
From CVE-2018-0764 | .NET and .NET Core Denial Of Service Vulnerability and CVE-2018-0786 | .NET Security Feature Bypass Vulnerability: “01/18/2018 To address a regression issue after installing security update 4055002, Microsoft has released security update 4074880 for Microsoft .NET 4.6/4.6.1/4.6.2/4.7/4.7.1 installed on supported editions of Windows 7 and Windows Server 2008 R2. Customers who have already installed KB4055002 should install KB4074880 to be protected from this vulnerability.”
January 19, 2018—KB4057400 (Preview of Monthly Rollup) (applies to Windows 7 Service Pack 1 and Windows Server 2008 R2 Service Pack 1)
Issue has been added to Windows 8.1 January 8, 2018—KB4056895 (Monthly Rollup), Windows 8.1 January 3, 2018—KB4056898 (Security-only update), and Windows 8.1 January 17, 2018—KB4057401 (Preview of Monthly Rollup): “After installing this update, some systems running both PIC and APIC interrupt controllers may experience system crashes.”
1 user thanked author for this post.
Today’s new or updated .NET KB articles:
https://support.microsoft.com/en-us/help/4055532/security-and-quality-rollup-for-net-framework-3-5-1-4-5-2-4-6-4-6-1-4- Security and Quality Rollup for .NET Framework 3.5.1, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, and 4.7.1 updates for Windows 7 SP1 and Server 2008 R2 SP1 (KB 4055532)
https://support.microsoft.com/en-us/help/4055267/security-and-quality-rollup-for-net-framework-2-0-sp2-3-0-sp2-4-5-2-an Security and Quality Rollup for .NET Framework 2.0 SP2, 3.0 SP2, 4.5.2 and 4.6 updates for Windows Server 2008 SP2 (KB 4055267)
https://support.microsoft.com/en-us/help/4055000/description-of-the-security-and-quality-rollup-for-the-net-framework-4 Description of the Security and Quality Rollup for the .NET Framework 4.6, 4.6.1, 4.6.2, 4.7, and 4.7.1 for Windows Server 2012 (KB 4055000)
https://support.microsoft.com/en-us/help/4055266/security-and-quality-rollup-for-the-net-framework-3-5-sp1-4-5-2-4-6-4- Security and Quality Rollup for the .NET Framework 3.5 SP1, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7 and 4.7.1 updates for Windows 8.1, RT 8.1, and Server 2012 R2 (KB 4055266)
https://support.microsoft.com/en-us/help/4055002/description-of-the-security-and-quality-rollup-for-net-framework-4-6-o Description of the Security and Quality Rollup for .NET Framework 4.6 on Windows Server 2008 SP2 (KB 4055002)
https://support.microsoft.com/en-us/help/4054999/description-of-the-security-and-quality-rollup-for-the-net-framework-3 Description of the Security and Quality Rollup for the .NET Framework 3.5 SP1 for Windows 8.1, RT 8.1, and Server 2012 R2 (KB 4054999)
https://support.microsoft.com/en-us/help/4054995/description-of-the-security-and-quality-rollup-for-the-net-framework-4 Description of the Security and Quality Rollup for the .NET Framework 4.5.2 for Windows 7 SP1, Windows Server 2008 R2 SP1 and Windows Server 2008 SP2 (KB 4054995)
https://support.microsoft.com/en-us/help/4054998/description-of-the-security-and-quality-rollup-for-the-net-framework-3 Description of the Security and Quality Rollup for the .NET Framework 3.5.1 for Windows 7 SP1 and Server 2008 R2 SP1 (KB 4054998)
https://support.microsoft.com/en-us/help/4054996/description-of-the-security-and-quality-rollup-for-the-net-framework-2 Description of the Security and Quality Rollup for the .NET Framework 2.0 SP2 and 3.0 SP2 for Windows Server 2008 SP2 (KB 4054996)
https://support.microsoft.com/en-us/help/4054993/description-of-the-security-and-quality-rollup-for-the-net-framework-4 Description of the Security and Quality Rollup for the .NET Framework 4.5.2 for Windows 8.1, Windows RT 8.1, and Windows Server 2012 R2 (KB 4054993)
https://support.microsoft.com/en-us/help/4055001/description-of-the-security-and-quality-rollup-for-the-net-framework-4 Description of the Security and Quality Rollup for the .NET Framework 4.6, 4.6.1, 4.6.2, 4.7 and 4.7.1 for Windows 8.1, Windows RT 8.1 and Windows Server 2012 R2 (KB 4055001)
https://support.microsoft.com/en-us/help/4054170/description-of-the-security-only-update-for-net-framework-4-5-2-for-wi Description of the Security Only update for .NET Framework 4.5.2 for Windows 8.1, Windows RT 8.1, and Windows Server 2012 R2 (KB 4054170)
https://support.microsoft.com/en-us/help/4054994/description-of-the-security-and-quality-rollup-for-the-net-framework-4 Description of the Security and Quality Rollup for the .NET Framework 4.5.2 for Windows Server 2012 (KB 4054994)
https://support.microsoft.com/en-us/help/4055270/security-only-update-for-net-framework-3-5-sp1-4-5-2-4-6-4-6-1-4-6-2-4 Security Only update for .NET Framework 3.5 SP1, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7 and 4.7.1 updates for Windows Server 2012 (KB 4055270)
https://support.microsoft.com/en-us/help/4054171/description-of-the-security-only-update-for-net-framework-4-5-2-for-wi Description of the Security Only update for .NET Framework 4.5.2 for Windows Server 2012 (KB 4054171)
https://support.microsoft.com/en-us/help/4054177/description-of-the-security-only-update-for-net-framework-3-5-sp1-for- Description of the Security Only update for .NET Framework 3.5 SP1 for Windows 8.1, Windows RT 8.1, and Windows Server 2012 R2 (KB 4054177)
https://support.microsoft.com/en-us/help/4054997/description-of-the-security-and-quality-rollup-for-the-net-framework-3 Description of the Security and Quality Rollup for the .NET Framework 3.5 SP1 for Windows Server 2012 (KB 4054997)
https://support.microsoft.com/en-us/help/4054174/description-of-the-security-only-update-for-net-framework-2-0-sp2-and- Description of the Security Only update for .NET Framework 2.0 SP2 and 3.0 SP2 for Windows Server 2008 SP2 (KB 4054174)
https://support.microsoft.com/en-us/help/4055271/security-only-update-for-net-framework-3-5-sp1-4-5-2-4-6-4-6-1-4-6-2-4 Security Only update for .NET Framework 3.5 SP1, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, and 4.7.1 updates for Windows 8.1, Windows RT 8.1, and Windows Server 2012 R2 (KB 4055271)
https://support.microsoft.com/en-us/help/4055272/security-only-update-for-net-framework-2-0-sp2-3-0-sp2-4-5-2-and-4-6-u Security Only update for .NET Framework 2.0 SP2, 3.0 SP2, 4.5.2, and 4.6 updates for Windows Server 2008 SP2 (KB 4055272)
https://support.microsoft.com/en-us/help/4054172/description-of-the-security-only-update-for-net-framework-4-5-2-for-wi Description of the Security Only update for .NET Framework 4.5.2 for Windows 7 SP1, Windows Server 2008 R2 SP1, and Windows Server 2008 SP2 (KB 4054172)
https://support.microsoft.com/en-us/help/4055265/security-and-quality-rollup-for-the-net-framework-3-5-sp1-4-5-2-4-6-4- Security and Quality Rollup for the .NET Framework 3.5 SP1, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7 and 4.7.1 updates for Windows Server 2012 (KB 4055265)
https://support.microsoft.com/en-us/help/4055269/security-only-update-for-net-framework-3-5-1-4-5-2-4-6-4-6-1-4-6-2-4-7 Security Only update for .NET Framework 3.5.1, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, and 4.7.1 updates for Windows 7 SP1 and Windows Server 2008 R2 SP1 (KB 4055269)
https://support.microsoft.com/en-us/help/4054183/description-of-the-security-only-update-for-net-framework-4-6-4-6-1-4- Description of the Security Only update for .NET Framework 4.6, 4.6.1, 4.6.2, 4.7, and 4.7.1 for Windows 7 SP1 and Windows Server 2008 R2 SP1 and .NET Framework 4.6 for Windows Server 2008 SP2 (KB 4054183)
https://support.microsoft.com/en-us/help/4054182/description-of-the-security-only-update-for-net-framework-4-6-4-6-1-4- Description of the Security Only update for .NET Framework 4.6, 4.6.1, 4.6.2, 4.7, and 4.7.1 for Windows 8.1, Windows RT 8.1 and Windows Server 2012 R2 (KB 4054182)
https://support.microsoft.com/en-us/help/4054181/description-of-the-security-only-update-for-net-framework-4-6-4-6-1-4- Description of the Security Only update for .NET Framework 4.6, 4.6.1, 4.6.2, 4.7 and 4.7.1 for Windows Server 2012 (KB 4054181)
https://support.microsoft.com/en-us/help/4054176/description-of-the-security-only-update-for-net-framework-3-5-1-for-wi Description of the Security Only update for .NET Framework 3.5.1 for Windows 7 SP1 and Windows Server 2008 R2 SP1 (KB 4054176)
https://support.microsoft.com/en-us/help/4054175/description-of-the-security-only-update-for-net-framework-3-5-sp1-for- Description of the Security Only update for .NET Framework 3.5 SP1 for Windows Server 2012 (KB 4054175)1 user thanked author for this post.
-
So, just to recap/confirm, when safe to do so, to update .NET Framework 4.7/4.7.1 on Win 7 Pro x64 will include:
– KB4033342 offline installer for .NET 4.7.1
– KB4074880 rather than, OR in addition to, KB4054183 within the KB4055532 bundle??
– KB4054856 ‘hotfix’1 user thanked author for this post.
Issue added to Windows 10 Version 1703 January 3, 2018—KB4056891 (OS Build 15063.850): “After installing this update, some users may experience issues logging into some websites when using third party account credentials in Microsoft Edge.”
Blog post .NET Framework January 2018 Security and Quality Rollup was revised on January 21, 2018.
-
When Woody gives the go-ahead to install the January 2018 updates, if you follow the Group A instructions, the .NET Framework January 2018 update will probably be installed.
1 user thanked author for this post.
-
@Mr.Brian: Thank you very, very much for the guidance. Without your expertise, outstanding knowledge, and dedication to providing help to all of us here, I know I could never function to keep my head above water. I am very grateful, along with many other members who appreciate your assistance more than words can say. 🙂 🙂
1 user thanked author for this post.
-
From January 22, 2018, update for Outlook 2016 (KB4011123): “This update fixes an issue in which some attachments to plain text messages are removed when you forward the message.”
1 user thanked author for this post.
-
I assume your wife is on 1703 with something less than Build 15063.850
My suggestion would be this.
Set your Internet connection to metered. Run wushowhide and hide KB4056891.
If not on Build 15063.786, download and manually install Build 15063.786 KB4053580.
Confirm that KB4056891 is still hidden.
Install other updates (IE11 Flash, Servicing stack,etc)If you are brave, you can try KB4057144 Build 15063.877
Read the fixes on the MS pages.If you are not brave, you might disable WU temporarily (I didn’t say that, did I?)
1 user thanked author for this post.
-
-
I suggested Build 15063.786 KB4053580 because I have it installed on two VMs and it seems (relatively) OK.
What I’ve done with my VM’s, and it’s made updates better (but longer) is to set Group Policy for no Delivery Optimization.
Windows Components\Delivery Optimization\Download Mode Enabled = 99 (simple download, HTTP, no DO)
also
WindowsUpdate\Configure Auto Update Enabled = 2But if you manual download/install you don’t have to worry about DO
1 user thanked author for this post.
-
Thanking MrBrian for yesterday’s update (#162022) on his comprehensive posting on the current .NET situation.
And hoping that is the last word ever on this most disappointing issue, although who can say that for sure anymore?
Ex-Windows user (Win. 98, XP, 7); since mid-2017 using also macOS. Presently on Monterey 12.15 & sometimes running also Linux (Mint).
MacBook Pro circa mid-2015, 15" display, with 16GB 1600 GHz DDR3 RAM, 1 TB SSD, a Haswell architecture Intel CPU with 4 Cores and 8 Threads model i7-4870HQ @ 2.50GHz.
Intel Iris Pro GPU with Built-in Bus, VRAM 1.5 GB, Display 2880 x 1800 Retina, 24-Bit color.
macOS Monterey; browsers: Waterfox "Current", Vivaldi and (now and then) Chrome; security apps. Intego AV1 user thanked author for this post.
From https://support.microsoft.com/en-us/help/4078130/update-to-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.”’
-
I would guess that this update merely sets the existing registry items that Microsoft documented weeks ago to disable CVE 2017-5715 mitigation in Windows. Reasons: a) tiny update size b) same update for multiple operating systems.
1 user thanked author for this post.
-
Test results: This update indeed does set the registry values documented by Microsoft. This update doesn’t appear in the list of installed updates. This update needs admin privileges to function properly.
1 user thanked author for this post.
-
From that link (my bolding):
‘Intel has reported issues with recently released microcode meant to address Spectre variant 2 (CVE 2017-5715 Branch Target Injection) – specifically Intel noted that this microcode can cause “higher than expected reboots and other unpredictable system behavior” and then noted that situations like this may result in “data loss or corruption.” Our own experience is that system instability can in some circumstances cause data loss or corruption.
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. For the full list of devices, see Intel’s microcode revision guidance. This update covers Windows 7 (SP1), Windows 8.1, and all versions of Windows 10, for client and server. If you are running an impacted device, this update can be applied by downloading it from the Microsoft Update Catalog website. Application of this payload specifically disables only the mitigation against CVE-2017-5715 – “Branch target injection vulnerability.”’
3 users thanked author for this post.
-
I can think of two reasons one might run KB4078130:
1. Recently updated microcode, in conjunction with the January 2018 Windows updates, has caused issues on your computer that Microsoft mentions in KB4078130.
2. Recently updated microcode has caused, in conjunction with the January 2018 Windows updates, too much of a performance decline.
-
MrBrian,
Thank you. Your answer makes it clear that someone in my situation does not have to install this out of band update, unless that person then goes inexplicably ahead and installs one of those problematic microcode updates.
Ex-Windows user (Win. 98, XP, 7); since mid-2017 using also macOS. Presently on Monterey 12.15 & sometimes running also Linux (Mint).
MacBook Pro circa mid-2015, 15" display, with 16GB 1600 GHz DDR3 RAM, 1 TB SSD, a Haswell architecture Intel CPU with 4 Cores and 8 Threads model i7-4870HQ @ 2.50GHz.
Intel Iris Pro GPU with Built-in Bus, VRAM 1.5 GB, Display 2880 x 1800 Retina, 24-Bit color.
macOS Monterey; browsers: Waterfox "Current", Vivaldi and (now and then) Chrome; security apps. Intego AV1 user thanked author for this post.
-
Issue added to January 18, 2018—KB4073291 (OS Build 16299.201): “Because of compatibility issues with some versions of antivirus software, this update causes stop errors or abrupt reboots.” Speculation: The issue occurs only in x86 version because “This update provides additional protections for 32-Bit (x86) version of Windows 10 1709.”
Issue added to January 3, 2018—KB4056890 (OS Build 14393.2007): ‘Editing some group policies using GPMC or AGPM 4.0 may fail with error “The data present in the reparse point buffer is invalid. (Exception from HRESULT: 0x80071128)” after installing this update on a domain controller.’
1 user thanked author for this post.
I’m not updating Windows ever again! The January Patch Tuesday borked my start menu and Cortana.
1 user thanked author for this post.
-
As an anonymous poster your replies must be moderated and may not appear immediately. You do not need to repost.
1 user thanked author for this post.
-
KB4078130 does not install or uninstall. It merely runs. Also, you need to make sure that you run it elevated. You can check if Spectre variant 2 mitigation is disabled by (after restarting computer) running InSpectre or a similar program. Here is a topic about KB4078130: https://www.askwoody.com/forums/topic/yet-another-surprise-patch-kb-4078130-for-all-versions-of-windows-disables-part-of-the-meltdown-spectre-patches/.
-
KB4078130 was not issued through Windows Update for a reason. It is offered in the MS Catalog as a manual download ONLY for those who installed the faulty Intel firmware microcode. It does not “install” it only executes. It does not therefore show up in the “installed updates” and you cannot “uninstall” it from there.
It sets Registry values to disable only the mitigation against CVE-2017-5715. Users who do not have the affected Intel microcode do not have to download this update. You can read about it in the Microsoft pages here or in the blog post on this site. The latter mentions the Registry values set.
“Neither I nor the Microsoft Support Agent (who remotely accessed by PC for well over 30 Minutes looking for it) could find the bl*%#y thing.” #163951 anon.
“KB4078130 does not install or uninstall. It merely runs.” #163961 MrBrian
The M$FT support guy spent more than 30 minutes looking for it.
Suspicions confirmed. (big guffaw)
January 2018 Preview of Quality Rollup (for .NET Framework) (January 26, 2018)
-
He need to add 1709 cumulative KB4058258 too 🙂
1 user thanked author for this post.
“Are you sure?”
Reasonably sure. Compare the file sizes at https://www.catalog.update.microsoft.com/Search.aspx?q=KB4056897 vs. https://www.catalog.update.microsoft.com/Search.aspx?q=KB4073578 and also see the Windows 8.1 update discussion.
