Yesterday, Thursday, a date that will live in infamy, Microsoft unleashed rags for 5 versions of Windows. They were ostensible to repair a widely reported bug in all of a mainstream Oct Windows confidence rags that gave arise to a fraudulent “Unexpected blunder from outmost database driver” message.
It’s too early to consider all of a damage, though reports from many corners contend installing these new rags brings behind old, unpatched versions of many files. If we commissioned one of a rags from yesterday, best to uninstall it. Now.
Patch Thursday, Nov. 2, brought 5 Windows updates (thx, @MrBrian):
- KB 4052234 for Windows 7 SP1 and Server 2008 R2 SP1
- KB 4052235 for Windows Server 2012
- KB 4052233 for Windows 8.1 and Server 2012 R2
- KB 4052232 for Windows 10 Fall (“November”) Update, chronicle 1511
- KB 4052231 for Windows 10 Anniversary Update, chronicle 1607, and Server 2016
That’s an peculiar list for dual reasons.
First, it includes Windows 10 Fall Update, chronicle 1511, that was ceremoniously announced end-of-life final month. As a official proclamation says: “After Oct 10, 2017, Windows 10 inclination using chronicle 1511 will no longer accept confidence and peculiarity updates.” Except, well, here it is Nov 2, and there’s a bonafide peculiarity refurbish — Microsoft-speak for a bug fix. So most for Windows 10 end-of-life announcements.
Second, it doesn’t embody Windows 10 Creators Update, chronicle 1703, a most-used chronicle of Windows 10. we have no thought because Microsoft skipped it, though I’d be peaceful to assume that Microsoft wanted to exam a waters before unleashing this hulk crock on a Win10 masses.
Ends up, that was a intelligent move.
Patches not prejudiced of Windows Update
All of these rags are accessible usually if we download them from a Catalog and manually implement them. They are not prejudiced of Windows Update, they weren’t rolled out a Automatic Update chute.
All of these rags are categorically destined during regulating a bug introduced by Microsoft as prejudiced of a Patch Tuesday rollout on Oct. 10. we warned we about it on Oct. 12 and gave full details on Oct. 17. (Yet another reason to equivocate automobile updates, yes?)
In short, programs that import and trade .xls files — programs that have worked for many years — unexpected incited belly-up with a foolish “Unexpected blunder from outmost database driver” blunder summary after receiving a Oct confidence update.
Each of yesterday’s rags has this explanation:
Improvements and fixes
This refurbish includes peculiarity improvements. No new handling complement facilities are being introduced in this update. Key changes include:
- Addressed emanate where applications formed on a Microsoft JET Database Engine (Microsoft Access 2007 and comparison or non-Microsoft applications) destroy when formulating or opening Microsoft Excel .xls files. The blunder summary is, “Unexpected blunder from outmost database motorist (1). (Microsoft JET Database Engine)”.
If we commissioned progressing updates, usually a new fixes contained in this package will be downloaded and commissioned on your device.
Again, “quality improvements” in Microsoft-speak means “bug fixes.”
New rags re-enable aged Windows confidence patches
Just one tiny problem. Installing any of those 5 new updates can re-enable comparison Windows confidence patches, that might have problems of their own. As @abbodi86 says on AskWoody.com:
They done a same mistake like in Windows 7 OOB refurbish KB4039884. They done 4052234 (Win 7) 4052233 (Win 8.1) prejudiced of a monthly rollup series, though both are tiny prejudiced rollups. Installing them will means a lot of aged components (files) to be active instead a latest components in full rollups (security or preview).
To modernise your memory, KB 4039884 is a botched Aug. 28 hotfix that was ostensible to repair a problems introduced by Microsoft’s cart Aug Windows 7 confidence rollup. It, too, brought behind aged files from a grave. Microsoft yanked a patch a day later. It looks like now, dual months after a Walking Dead part for Windows 7, we’re being treated to a same, uh, knowledge — solely now it’s for all Windows versions (other than 1703 and 1709).
Abbodi86 goes on to say:
BTW, usually one member seems to be new (msexcl40.dll). Could they not usually recover it in a normal tiny refurbish instead of this fiasco?
Lounger ch100 gives a specific example:
I did an Office 2016 64-bit exam designation and found that after installing Skype for Business Security Update KB4011159 expelled in Oct 2017, a aged Security Update for Skype for Business from Aug 2016 KB3115408 was reactivated. KB4011159 is ostensible to embody and substitute KB3115408. This is usually for a 64-bit version, though it seems not to be a box for a 32-bit version.
The end is clear: If we got suckered into installing one of these 5 patches, uninstall it now. Wait for Microsoft to get a act together. Don’t be too astounded if all of a rags get yanked from a Catalog soon, usually as MS did with KB 4039884 behind in August.
On a meta level, I’m removing fed adult with all of these botched patches. we gamble we are, too. Perhaps Windows has turn too aged and unmanageable — a Decrepit Operating System. Every month we think, some-more and more, that Windows should simply be put out to pasture.
Is it time for an Old Yeller ending?
The contention continues on AskWoody.com