Microsoft Replaces KB4093118 to Resolve Replaced NICs and Missing IP Addresses

After another embarrassing round of patches this month, particularly for KB4093118 which reintroduced a problem with replacing network information, Microsoft has now delivered a fix.

KB4093118 has now been replaced and refreshed and the glaring “known issues” section has been updated.

Microsoft says that a Resync is required to get newer revision of this KB for WSUS environment.

Microsoft was quick to resolve this problem this month. In past months the company has waiting until last light of the month or pushed fixes until it could solve them during the next Patch Tuesday.

 


Looking for an awesome, no-nonsense technical conference for IT Pros, Developers, and DevOps? IT/Dev Connections kicks off in Dallas, Texas in 2018!

IT/Dev Connections

Its Back: April 2018 Update Brings Back Issue that Replaces NIC Settings and Lost Static IP Addresses

UPDATE, April 13, 2018: Microsoft Replaces KB4093118 to Resolve Replaced NICs and Missing IP Addresses


Original article…

Like a bad odor in old fabric, Microsoft has reintroduced an issue that just won’t seem to go away. One that has caused many customers pains this year.

When first delivered on Patch Tuesday for April 2018, KB4093118‘s only known issues were only memory leaks and bluescreens, and that’s bad enough. However, Microsoft has now two days later updated the known issues list (KB4093118) to include the recurrence of the bad NIC problem.

  • A new Ethernet Network Interface Card (NIC) that has default settings may replace the previously existing NIC, causing network issues after you apply this update. Any custom settings on the previous NIC persist in the registry, but are unused.
  • Static IP address settings are lost after you apply this update.

 

Per Microsoft, the company is working on a resolution but won’t provide an update until except in a new release. It says that in the meantime, please apply KB4093108 (Security-only update) to stay secure, or use the Catalog release of KB4093118 to stage the update for WU or WSUS.

The issues affect Windows 7 Service Pack 1 and Windows Server 2008 R2 Service Pack 1.


Looking for an awesome, no-nonsense technical conference for IT Pros, Developers, and DevOps? IT/Dev Connections kicks off in Dallas, Texas in 2018!

IT/Dev Connections

Microsoft Releases Windows 7 and Windows Server 2008 Updates with Known Memory Leaks and Stop Errors

Microsoft is beginning to make its April 2018 Patch Tuesday security updates available for customers. But, there’s at least a couple caveats already that customers should be aware of going in to this month’s testing.

Microsoft has outlined a couple known gotchas for updates for Windows 7 Service Pack 1 and Windows Server 2008 R2 Service Pack 1:

  • After you install this update, SMB servers may leak memory.
  • A stop error occurs on computers that don’t support Streaming Single Instructions Multiple Data (SIMD) Extensions 2 (SSE2).

 

Both of these problems exist in KB4093118 (Monthly Rollup) and KB4093108 (Security-only update).  Microsoft says that it is working on a resolution and will provide an update in an upcoming release.

 


Looking for an awesome, no-nonsense technical conference for IT Pros, Developers, and DevOps? IT/Dev Connections kicks off in Dallas, Texas in 2018!

IT/Dev Connections

Microsoft Releases KB4099467 to Fix Stop Errors After Installing KB4088875 or KB4088878

If anyone in your organization is running Windows 7 Service Pack 1, Windows Server 2008 R2 Service Pack 1, Windows Server 2008 R2 Datacenter, Windows Server 2008 R2 Enterprise, or Internet Explorer 11 on Windows Server 2008 R2 IA64 and getting a Stop error 0xAB error message SESSION_HAS_VALID_POOL_ON_EXIT (ab) when logging off, Microsoft has a new fix that should solve the problem.

The new update is KB4099467 and is available through Windows Update.

Full support doc: Stop error 0xAB when you log off a Windows 7 SP1 or Windows Server 2008 R2 SP1 session


Looking for an awesome, no-nonsense technical conference for IT Pros, Developers, and DevOps? IT/Dev Connections kicks off in Dallas, Texas in 2018!

IT/Dev Connections

On March 27th Microsoft Adds a VBScript Prerequisite to a March 13th Rollup that Caused Pains for VMware Customers

Today, Microsoft has added a prerequisite to a rollup that it released two weeks ago.  At the time, the update was causing havoc with VMware customers and virtual machines and the company eventually stopped pushing it.

More interesting, is that the prerequisite comes in the form of a VBScript that must be run after backing up a registry key.

No way. Yep, seriously. Not only is a prerequisite released two weeks after the fact (which is contrary in terms), but it comes from a company dead bent on PowerShell proliferation.

The support doc says…

Follow these steps before you apply this update to a physical computer or a virtual machine

Check out the details: March 13, 2018—KB4088875 (Monthly Rollup)

This is a rollup for Windows 7 Service Pack 1 and Windows Server 2008 R2 Service Pack 1.


Looking for an awesome, no-nonsense technical conference for IT Pros, Developers, and DevOps? IT/Dev Connections kicks off in Dallas, Texas in 2018!

IT/Dev Connections

Microsoft Has Pulled KB4088875 to Save Customers Further Pain

Yesterday, we told you about an issue with KB4088875 and VMware. But, since then, even more insidious problems with this monthly rollup for Windows 7 SP1 and Windows Server 2008 R2 SP1 has surfaced.  And, these new issues are in addition to the known issues Microsoft already admitted to with this particular update.

Its difficult to imagine why,  with the known issues already reported in the original KB doc, that Microsoft decided to push this update on its customers anyway. If Microsoft’s customers weren’t leery enough of the long history of crappy updates, this is yet another reason to take a cautioned approach to the monthly stack of updates seeping out of the Redmond company’s network.

Microsoft has now pulled KB4088875. We hope to have some public apology statement soon.

 


Looking for an awesome, no-nonsense technical conference for IT Pros, Developers, and DevOps? IT/Dev Connections kicks off in Dallas, Texas in 2018!

IT/Dev Connections

Microsoft Includes Server 2008/2012 and Windows 7 x86 in Spectre/Meltdown Protection

As part of the March 2018 Microsoft Patch Tuesday, Microsoft has also delivered new guidance and new updates to help protect against the Spectre and Meltdown vulnerabilities that are part of the Intel processor security issues.

Full advisory: ADV180002 | Guidance to mitigate speculative execution side-channel vulnerabilities

The company has been slow to provide support for Windows Server 2008 and 2012 and the Windows 7 x86 architecture, but has finally delivered for both the Monthly Rollup and Security Only bundle for these affected systems.

NOTE: The antivirus registry key is still required this month so that affected systems can see and install the updates.

The updates install the mitigations, but they are not enabled by default. To enable the mitigations through registry edits, see:

Windows Server guidance to protect against speculative execution side-channel vulnerabilities


Looking for an awesome, no-nonsense technical conference for IT Pros, Developers, and DevOps? IT/Dev Connections kicks off in Dallas, Texas in 2018!

IT/Dev Connections

Microsoft Delivers Out-of-Band Update to Patch Intel Processor Flaw, But Gotchas Exist in AV Products

Promised to deliver at least by the first Patch Tuesday of 2018 on January 9, 2018, Microsoft has now delivered the update that is intended to compensate for the flaws in Intel’s processors that would allow attackers to compromise Windows PCs.

January 3, 2018—KB4056897 (Security-only update) – Windows 7 SP1 and Windows Server 2008 R2 SP1

January 3, 2018—KB4056892 (OS Build 16299.192) –  Windows 10/Windows Server 2016 1709

January 3, 2018—KB4056891 (OS Build 15063.850) – Windows 10/Windows Server 2016 1703

January 3, 2018—KB4056890 (OS Build 14393.2007) – Windows 10/Windows Server 2016 1607

January 3, 2018—KB4056888 (OS Build 10586.1356) – Windows 10 1511

January 3, 2018—KB4056893 (OS Build 10240.17738) – Windows 10 initial 2015 release

However, according to the Known Issue description:

Due to an issue with some versions of Anti-Virus software, this fix is only being made applicable to the machines where the Anti virus ISV have updated the ALLOW REGKEY.
Contact your Anti-Virus AV to confirm that their software is compatible and have set the following REGKEY on the machine.
Key=”HKEY_LOCAL_MACHINE”Subkey=”SOFTWARE\Microsoft\Windows\CurrentVersion\QualityCompat”
Value Name=”cadca5fe-87d3-4b96-b7fb-a231484277cc”
Type=”REG_DWORD”
Data=”0x00000000”

 


Looking for an awesome, no-nonsense technical conference for IT Pros, Developers, and DevOps? IT/Dev Connections kicks off in Dallas, Texas in 2018!

IT/Dev Connections

Expired auth.cab Causes Update Headaches for Microsoft’s Windows 7 Holdouts

A thread grew pretty quickly over the last few days on the Microsoft forums over an Error Code 80248015 that resulted in Windows 7 users being unable to continue to receive updates. The problem was that the auth.cab (the file Windows Update mechanism verifies against) expired on December 3rd. As usual, the problem led to many customers suggesting that Microsoft does these things to force Windows 7 users to upgrade to Windows 10.

The problem should now be resolved. Microsoft updated the auth.cab file on Monday.

 


Looking for an awesome, no-nonsense technical conference for IT Pros, Developers, and DevOps? IT/Dev Connections kicks off in Dallas, Texas in 2018!

IT/Dev Connections

Microsoft Delivers Windows Fix for Dot Matrix Printers

If you were thinking of taking off early for the Thanksgiving holiday, think again. Microsoft has delivered the fix for the problem it introduced in November updates that caused dot matrix printers to stop working (covered HERE).

Release on November 21, 2017, the fix is issued as KB4055038 and solves the problem for the following previously released updates:

 


Looking for an awesome, no-nonsense technical conference for IT Pros, Developers, and DevOps? IT/Dev Connections kicks off in Dallas, Texas in 2018!

IT/Dev Connections

Microsoft’s November Windows Updates Breaks Dot Matrix Printers

The monthly rollup for Windows 7 this month was the first update to cause a stir among those users who are still using dot matrix printers. The issue has escalated over the past few days (thread HERE), and though it effects a large majority of dot matrix printer brands, those with Epson printers seem to be impacted the most. Additionally, the issue impacts each of the following updates:

 

Microsoft just updated each KB article to reflect the dot matrix issue with the following:

After installing this update, some Epson SIDM and Dot Matrix printers cannot print on x86 and x64-based systems.

Microsoft and Epson have determined the cause of the issue and are working on a solution. This problem is not related to the printer driver, so installing current or older print drivers will not resolve the issue.

Microsoft will provide an update in an upcoming release.

The temporary solution while waiting on a permanent fix is to uninstall the updates.

 


Looking for an awesome, no-nonsense technical conference for IT Pros, Developers, and DevOps? IT/Dev Connections kicks off in Dallas, Texas in 2018!

IT/Dev Connections

Microsoft Publishes Details on the Update that Solves KrackAttack Vulnerability for Windows

Reported earlier, there’s a severe vulnerability in the modern Wi-Fi security layer, which will require firmware updates to routers, BIOS updates to PCs, and patches for software and platforms.

Microsoft has now made available details about a patch it is delivering for affected Windows systems:

CVE-2017-13080 | Windows Wireless WPA Group Key Reinstallation Vulnerability

Essentially, Microsoft delivered the patch for this vulnerability during the last round of Patch Tuesday updates the second week of October 2017, but waited until today to publicly announce it so the rest of the industry had time to catch up.

Incidentally, the updates available for Windows 7 and Windows Server 2008 for this particular security issue have been reported to introduce other issues. However, this security vulnerability is pretty serious and you might consider rolling out the update anyway and suffering through until Microsoft can supply fixes for fixes.

Microsoft has definitely created another Catch-22 scenario for some customers.


Looking for an awesome, no-nonsense technical conference for IT Pros, Developers, and DevOps? IT/Dev Connections kicks off in San Francisco in 2017!

IT/Dev Connections