Patch Lady – Mr. Metadata got fixed

Topic

New Reply

Remember this post?  Last night in addition to a new update for 1709, KB4093118 for Windows 7 got refreshed.  It appears that once it’s metadata got f
[See the full post at: Patch Lady – Mr. Metadata got fixed]

Susan Bradley Patch Lady/Prudent patcher

7 users thanked author for this post.

Cascadian, OldBiddy, Elly, Mr. Natural, abbodi86, woody, ch100

Reply | Quote

Replies

groub b, win7 64bit:

I did rollback to december, uninstalled these three updates in this order:
kb4074587 (february), kb4073578 (january), kb4056897 (january)
but after reboot all three of them still show up in update history.
of course, not available in “installed updates” section anymore.

Remaining windows updates installed 2018 are:
kb4056568, kb4054998 (january) and kb4074736, kb4088835 (february), some of them ie, I assume;
office 2010 updates from january and february, 2018-01 security-/quality rollup for .net (january only),
and of course msrt from january and february. that’s it, I think.

So now I should be “safe” regarding total meltdown, I assume?

There are no March windows updates installed at all, even no updates for office 2010 or msrt…

Reply | Quote

Thanks for the info.

How does the client get the new metadata? Does it become part of the update catalog and gets pulled with a subsequent scan against wsus?

Reply | Quote

KB4093118 update.
KB4093113 update.

On permanent hiatus {with backup and coffee}
offline▸ Win10Pro 2004.19041.572 x64 i3-3220 RAM8GB HDD Firefox83.0b3 WindowsDefender
offline▸ Acer TravelMate P215-52 RAM8GB Win11Pro 22H2.22621.1265 x64 i5-10210U SSD Firefox106.0 MicrosoftDefender
online▸ Win11Pro 22H2.22621.1992 x64 i5-9400 RAM16GB HDD Firefox116.0b3 MicrosoftDefender

Reply | Quote

Having the same question. Have installed 4093118 prior to April 23rd; do I have to remove and install the new one?

Reply | Quote

You should not have to reinstall KB4093118. The metadata was change to prevent the continuous reinstallation of the update. The function of the update was not changed.

Reply | Quote

I noticed that KB4093118 was showing a new date of 23 April 2018. I decided to install it and KB890830 this morning (25 April Sydney Australia) on both PCs and having no problems. All that is left now are 3 updates for Office 2010 (KB4018362, KB4018311 and KB4018359.

Reply | Quote

@Pierre77: so you did not get offered KB4018357 (https://support.microsoft.com/en-us/help/4018357/description-of-the-security-update-for-office-2010-april-10-2018), the one that plugs a hole in which the Outlook preview Pane is an attack vector? I did not get it offered as well. When I downloaded it form the catalogue and wanted to install it manually, it said it was not applicable to my pc. Strange, because I do have the necessary prerequisite (Note To apply this security update, you must have the release version of Service Pack 2 for Office 2010 installed on the computer.). But somehow it is always sort of comforting to learn you are not the only one who has a specific WU-problem …

~ Annemarie

Reply | Quote

Hi, All!

We have a very annoying issue installing update KB4093118, it reverts after restart.
But not on all our workstations (it is on about 700 computers for now).

We are approved 202 revision of KB4093118 form 23 of April,
Error is 0x80070057 (In Windows System log Event ID 20)

I started a thread on Technet forum

Maybe someone can help here?

1 user thanked author for this post.

MrBrian

Reply | Quote

Anton Karlan wrote:

Hi, All! We have a very annoying issue installing update KB4093118, it reverts after restart. But not on all our workstations (it is on about 700 computers for now). We are approved 202 revision of KB4093118 form 23 of April, Error is 0x80070057 (In Windows System log Event ID 20) I started a thread on Technet forum Maybe someone can help here?

I think I found the solution:
I found it here. Michael_1995 answer helped a lot:

We experienced this same issue. We had almost the exact same errors in the CBS.log as MichaelHackman. We discovered that in our enterprise environment we had carried over creating a legacy registry key from the Windows 7 days:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EventLog\Microsoft-Windows-PrintService/Operational

We had created this key to allow us to up the MaxSize value (increase the number of print events could be stored in the event log before it rolled)

When the Windows 10 September 2017-09 Monthly Rollup and the Rollups after that ( 2017-10 and 2017-11 Monthly Rollups ) came out, they attempt to migrate this event log from the old location in the Event Viewer (root of Application and Services Logs) to it’s proper location of Application and Services Logs > Microsoft > Windows > PrintService > Operational. So, for example, when we tried to apply KB4048954 to our Windows 10 1703 boxes… the KB tries to migrate the event location and errors out when it hits this strange key and rolls it back even after it get’s past 100%.

The resolution was to simply delete the legacy key.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EventLog\Microsoft-Windows-PrintService/Operational

You may have additional legacy keys that need removed, such as…

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EventLog\Microsoft-Windows-PrintService/Admin

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EventLog\Microsoft-Windows-PrintService/Debug

Hope this helps.

After deleting registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EventLog\Microsoft-Windows-PrintService/Operational

Update was installed successfully:
Hope that help someone.

2 users thanked author for this post.

Elly, columbia2011

Reply | Quote

I have the same problem with installing KB4093118 on some PCs, but didnt’t found any keys of Microsoft-Windows-PrintService in registry. Strange issue.

Reply | Quote