Welcome to Patch Thursday – KB 4052232 is supposed to fix the Jet database problem, but only for the old Fall Update, version 1511

[woodyDa Boss]

Maybe Microsoft’s trying to minimize the screams. All I know for sure is that there’s a new patch for 1511 that just hit the Catalog. Yes, Microsoft d
[See the full post at: Welcome to Patch Thursday – KB 4052232 is supposed to fix the Jet database problem, but only for the old Fall Update, version 1511]

1 user thanked author for this post.

MrBrian

[MrBrianAskWoody MVP]

These are the November 2, 2017 Windows updates for this issue:

https://support.microsoft.com/en-us/help/4052231 (Win 10 v1607)

https://support.microsoft.com/en-us/help/4052232 (Win 10 v1511)

https://support.microsoft.com/en-us/help/4052234 (Win 7)

https://support.microsoft.com/en-us/help/4052233 (Win  8.1)

https://support.microsoft.com/en-us/help/4052235 (Win Server 2012)

 

• This reply was modified 9 months, 2 weeks ago by  MrBrian.
• This reply was modified 9 months, 2 weeks ago by  MrBrian.

2 users thanked author for this post.

walker, woody

[abbodi86]

Well, it’s not a “security” update for 1511, so MS announcement stands still 😀

2 users thanked author for this post.

Microfix, woody

[abbodi86AskWoody MVP]

They made the same mistake like in Windows 7 OOB update KB4039884

they made 4052234 (Win 7) & 4052233 (Win 8.1) part of the monthly rollup series
but both are small partial rollups

installing them will cause a lot of old components (files) to be active instead the latest components in full rollups (security or preview)

BTW, only one component seems to be new (msexcl40.dll)
could not they just release it in a normal small update instead this fiasco?

4 users thanked author for this post.

walker, Microfix, Woody posting as an MVP, MrBrian

[MrBrianAskWoody MVP]

Windows 7 and 8.1 users interested in these updates should avoid installing them until they are reissued due to the issue that abbodi86 mentioned. Also, these fixes will be included in the November 14, 2017 updates.

3 users thanked author for this post.

walker, Microfix, Woody posting as an MVP

[MrBrianAskWoody MVP]

For Windows 7 or 8.1 users that already installed the defective update, you should uninstall it as soon as possible.

3 users thanked author for this post.

walker, Microfix, woody

[ch100AskWoody MVP]

I think this issue is more widespread than it appears to be.
I did an Office 2016 64-bit test installation and found that after installing Skype for Business Security Update KB4011159 released in October 2017, the old Security Update for Skype for Business from August 2016 KB3115408 was reactivated. KB4011159 is supposed to include and supersede KB3115408. This is only for the 64-bit version, but it seems not to be the case for the 32-bit version.

1 user thanked author for this post.

woody

[MicrofixAskWoody MVP]

Via the normal Windows Update, there is no patch so, no need to look for it in W8.1 Group A. This is where Group B can potentially run into problems via the catalog.

Thanks for the heads-up Abbodi86 🙂

| 2x Group A- W8.1x64 | Group A+ Linux x64 Hybrid | Group B W7x64 Pro | Group W XP Pro

No problem can be solved from the same level of consciousness that created IT - AE

1 user thanked author for this post.

walker

[Author]

Posts