Microsoft January 2018 Security Updates

The January security release consists of 56 CVEs, 16 are listed as Critical and 38 are rated Important, 1 is rated Moderate and 1 is rated as Low in severity. The updates address Remote Code Execution, Tampering, Security Feature B y p a s s , Information Disclosure and Denial of Service. The release consists of security updates for the following software:

ESET indicates Y and Y on the spreadsheet you linked to, Corrine. However, the registry key is not present on my mother's windows machine. ESET shows up-to-date on virus signature and product module. I'm a little confused about whether I could install the MS patch on her machine. I'm not ready to do it yet anyway (like to see some of the bugs shake out first), but I'd kind of like to know where it stands. I've talked her into letting me install NoScript and her FF is the latest version, so I think she's relatively safe for now.

ESET was among the first A/V's to provide the reg update. It was released late in the day on January 3. What OS is your Mother's machine? Since Microsoft states that "Customers using Windows client operating systems including Windows 7 Service Pack 1, Windows 8.1, and Windows 10 need to apply both firmware and software updates.", have you checked the OEM for an update? I gather it is Intel and not a newer AMD processor (at least post 1995).

Please Note: If your system received the out-of-band January 3, 2018, security update, most likely, only the Flash Player and MSRT updates were installed yesterday for Windows 10. To confirm that your system is up to date, go to Windows 10 update history.

Select the Windows 10 version you are at. For example, the Fall Creators Update is Windows 10 Version 1709 and the Creators Update is Version 1703.

The current Build for Windows 10 Version 1709 is OS Build 16299.192, with KB4056892, dated January 3, 2018, installed.

The current Build for Windows 10 Version 1703 is OS Build 15063.850, with KB4056891, dated January 3, 2018, installed.

To check your version go to Settings > System > About and scroll down to "Windows Specifications".

The OS Build under Windows Specifications will match the Windows 10 Version.

I read that ESET pushed an update out to all customers to automatically create the registry key, but I also know that sometimes anti-malware software doesn't apply all changes immediately in some circumstances, like pending operating system updates. In cases like those, rebooting the computer and letting the operating system apply the updates usually resolves things.

Regards,

Aryeh Goretsky

ebrke, on 09 January 2018 - 06:35 PM, said:

EDIT: As of a few minutes ago, the reg key has been created by ESET.

ESET indicates Y and Y on the spreadsheet you linked to, Corrine. However, the registry key is not present on my mother's windows machine. ESET shows up-to-date on virus signature and product module. I'm a little confused about whether I could install the MS patch on her machine. I'm not ready to do it yet anyway (like to see some of the bugs shake out first), but I'd kind of like to know where it stands. I've talked her into letting me install NoScript and her FF is the latest version, so I think she's relatively safe for now.

Everything is good--reg key is now present, so whenever I decide to install the updates I should be okay. I'm still sticking to manual installs, not using WU except for things like .NET updates. I'm going to wait and see how everything shakes out, though. If I bork my mother's machine, I'll never hear the end of it.