Woody Leonhard's no-bull news, tips and help for Windows, Office and more… Please disable your ad blocker – our (polite!) ads help keep AskWoody going!
Home icon Home icon Home icon Email icon RSS icon
  • What’s wrong with the Win10 1709 January Delta package?

    Posted on March 16th, 2018 at 09:11 woody Comment on the AskWoody Lounge

    Just saw this from Bogdan Popa on Softpedia.

    KB 4088776 — for the Win10 1709 March Cumulative Update — has been modified to include this warning:

    Users with Windows 10 Version 1709 Enterprise that have installed the January 2018 Delta package may encounter failure issues when installing the February and March 2018 updates from the Microsoft Update Catalog. Specifically, the Windows 10, version 1709 February Delta Update may silently fail.

    Microsoft is aware of this issue and has expired the following Windows 10 version 1709 Delta Update KBs on the Microsoft Catalog on March 13, 2018:

    KB4056892 – January 2018

    KB4074588 – February 2018

    KB4088776 – March 2018

    Microsoft recommends that users uninstall the Windows 10 version 1709 January KB4056892 Delta Update package and install the March 2018 full latest cumulative update, KB4088776. Customers may resume using Delta Update packages with the April 2018 Windows 10 version 1709 monthly cumulative update.

    So… does anybody know what happened to the January Delta update?

  • Words of wisdom

    Posted on March 16th, 2018 at 07:23 woody Comment on the AskWoody Lounge

  • Buggy Windows 7 Monthly Rollup KB 4088875 — no acknowledgment from Microsoft

    Posted on March 15th, 2018 at 07:24 woody Comment on the AskWoody Lounge

    Microsoft no longer installs the Win7 March Monthly Rollup automatically, but KB 4088878 is still available in the Update Catalog. Aren’t you glad you held off on patching this month?

    Computerworld Woody on Windows.

    UPDATE: Microsoft now acknowledges the IP address setting bug. From KB 4088875:

    A new Ethernet virtual Network Interface Card (vNIC) may be created with default settings in place of the previously existing vNIC, causing network issues after applying this update. Any custom settings on the previous vNIC are still persisted in the registry but unused.

    Apply the resolution documented in KB3125574 (Convenience Rollup) for Known issue 1:

    IP address settings are lost after applying this update.

    Microsoft is working on a resolution and will provide an update in an upcoming release.

    You really have to wonder who’s testing this stuff.

  • Patch Lady – Excel KB 4011727 registry keys

    Posted on March 15th, 2018 at 01:28 Susan Bradley Comment on the AskWoody Lounge

    Susan here, in the latest Excel 2016/2013 security update they have added an additional registry key to better protect you from malicious macros.  Note this also impacts Excel click to run versions as well.

    Newly added to the registry is the following settings:

    A new registry key has been added to provide more control over object macros security. The “RestrictObjectMacros” DWORD registry key under HKCU/Software/Microsoft/Office/16.0/Excel/Security supports the following values:

    0 (or not present) – Default behavior
    1 – Strict
    2 – Lenient
    3 – None (not recommended)

    The default – of no value set is what you see on my 2016 click to run install at home.

    It appears this setting is in addition to the normal “don’t trust macros from the web” setting that is already in the Security trust center settings.

    What isn’t clear and isn’t well documented in the KB as to what exactly those registry keys bring to the table in addition to what we already have as macro settings as set in the Office trust center.  I think what the registry keys bring to the table is to granularly adjust Excel’s macro settings unique to Excel so that you can have parts of the Office suite have more restrictive macro settings rather than the security center settings.

    I think.

    Needless to say I’ll be trying to find out more about this setting.  For now just leave it as is.

  • Patch Lady – Networking issues and KB 4088875

    Posted on March 15th, 2018 at 00:11 Susan Bradley Comment on the AskWoody Lounge

    As Woody pointed out earlier today there are some reports of networking issues after the install of this month’s Server 2008 r2 and Windows 7 patch.  The issues are not widespread and they appear to be limited to two scenerios:

    Scenerio 1 – VMware.  As noted on a reddit post a new virtual Ethernet network card is installed/enabled after the update.  The side effect has occurred before with other convenience rollups and a workaround was previously posted to this KB and a script is provided to fix the issue.  It is not impacting all servers, it appears to be impacting virtual machines on VMware.

    You can see more threads here.

    Scenerio 2 – workstations.  This one is a bit more fuzzy and not clear cut.  I’ve seen reports where workstations with static IPs may be impacted with this update.  There are definitely enough credible reports of chipsets being reset and losing their networking IP addresses.

    Note that I’m seeing this more in businesses than in consumer/peer to peer settings.

    On my Windows 7 (my old machine that we keep around for older programs), I’m seeing this update unchecked:

    Which normally means that Microsoft is throttling the patch while they monitor issues.

    What is honestly a bit more concerning is this documented side effect:

    After installing this update, SMB servers may leak memory. Microsoft is working on a resolution and will provide an update in an upcoming release.

    If you run a file server, you may want to run tests and determine if you do see THIS side effect as that one may impact.

    More on this as I see issues.

  • Patch Lady – following up on Office update KB4011730

    Posted on March 14th, 2018 at 20:51 Susan Bradley Comment on the AskWoody Lounge

    Susan here, following up on the Office patch that was talked about here.

    Office 2016 Click to run:  You will not see this issue as you get your updates as a bundle.

    Office 2016 received via volume license are the only folks that receive individual updates these days.  The side effect whereby a Word document can’t be opened directly from Explorer appears to be as a result of only installing Security updates and not installing the non security updates.

    As now noted in the KB4011730

    Known issues in this security update

    • Symptoms
      After you install this security update, you may be unable to open or save a Word document.

      To work around this issue, install the March 6, 2018 update for Office 2016 (KB4018295)

      Microsoft is researching this problem and will post more information in this article when the information becomes available.

    Showcasing that sometimes you do want to install those optional updates.

  • Insider trading charge leveled at Equifax CIO

    Posted on March 14th, 2018 at 11:59 woody Comment on the AskWoody Lounge

    Remember how three Equifax execs sold $1.8 million in Equifax stock, after the company was hacked but before the hack was announced?

    The SEC just nailed one of them:

    Jun Ying, who was next in line to be the company’s global CIO, allegedly used confidential information entrusted to him by the company to conclude that Equifax had suffered a serious breach.  The SEC alleges that before Equifax’s public disclosure of the data breach, Ying exercised all of his vested Equifax stock options and then sold the shares, reaping proceeds of nearly $1 million.

    Let’s see what happens.

  • Massive March Patch Tuesday relaxes antivirus restrictions, but there are problems

    Posted on March 14th, 2018 at 08:17 woody Comment on the AskWoody Lounge

    With 74 separately identified plugged holes, every version of Windows and Office gets goosed. No known exploits for any “Critical” vulnerabilities, but there’s a report of more forced upgrades.

    Computerworld Woody on Windows.

    UPDATE: Win7/Win2008 R2 Monthly Rollup KB 4088875 and Security-only KB 4088878 are causing problems on Server 2008 R2 because the updates blow away virtual Network Interface Cards (VMWare hit bad) and on Win7 because it overwrites static IP addresses. Discussion on Reddit and an apprently related post on KB 3125574.

    ANOTHER UPDATE: It looks like the Word 2016 security patch KB 4011730 causes Word 2016 to crash when you double-click on a file with a DOCX filename extension. Uninstalling the patch fixes the problem.

    ANOTHER UPDATE: We’re getting reports that the beleaguered Win7 Monthly Rollup, KB 4088875, now appears in Windows Update as unchecked. It’s still available through the Microsoft Update Catalog, however.