More problems with this month’s patches

Topic

New Reply

The fun never ends. The Win8.1 Monthly Rollup, KB 4056895, now has an acknowledged bug: After installing this update, some systems running both PIC an
[See the full post at: More problems with this month’s patches]

7 users thanked author for this post.

walker, JDeC, HiFlyer, Tiernan, Elly, AJNorth, MrBrian

Reply | Quote

Replies

Security-only update also have the bug
https://support.microsoft.com/en-us/help/4056898/windows-81-update-kb4056898

so we should not blame the rollup model for it 😀

7 users thanked author for this post.

JDeC, HiFlyer, Elly, amraybt, woody, FakeNinja, MrBrian

Reply | Quote

This issue also isn’t fixed in the Windows 8.1 January 2018 Windows preview monthly rollup.

3 users thanked author for this post.

abbodi86, HiFlyer, woody

Reply | Quote

On a side note, the preview rollup fixes a 9-month old issue, since April 2017
https://support.microsoft.com/en-us/help/4015553

1 user thanked author for this post.

woody

Reply | Quote

A different issue regarding Edge recently documented for all January 3, 2018 Windows 10 builds: https://www.askwoody.com/forums/topic/january-patch-tuesday-overview/#post-160636.

2 users thanked author for this post.

HiFlyer, woody

Reply | Quote

woody wrote:

The fun never ends. The Win8.1 Monthly Rollup, KB 4056895, now has an acknowledged bug:

This might be a good sign in a round about way. “The first step in dealing with a problem is admitting you have one” It seems as though, in the past Microsoft has been reluctant to admit they screwed up. Is there such a thing as a 12 step program for a software company.   🙂

Dell, W10 Professional, 64-bit, Intel Core i7 Quad, Group A

HP, W7 Home Premium, 64-bit, AMD Phenom II, Group A

9 users thanked author for this post.

JDeC, Cascadian, GoneToPlaid, HiFlyer, SueW, Tiernan, Cartoonist Aaron, Elly, woody

Reply | Quote

That’s very true. The Office people learned more than a year ago that it’s better to spill the beans directly, rather than having them spilled for you.

Wonder if the Surface folks will ever get a clue?

4 users thanked author for this post.

Sparky, HiFlyer, Tiernan, flackcatcher

Reply | Quote

Naw, because Surface is supposed to be “perfect” and “the best” and with “above average” reliability in terms of all competing products.

Reply | Quote

? says:

maybe “they” are continuing to write “older” hardware out of the kernel (patches)? Linux started doing that to my APIC on k8 machines after kernel 3.13.

1 user thanked author for this post.

HiFlyer

Reply | Quote

I’m happy to report that there were no new patches distributed through the Windows Update Catalog yesterday, Saturday Jan. 20.

And I’m happy to report that with ONLY the January Internet Explorer patch in place on my Windows 7 and 8.1 systems my computing experience is still smooth, fast, and – amazingly – I have not been hit by malware!

-Noel

7 users thanked author for this post.

SueW, walker, HiFlyer, Pepsiboy, JDeC, wdburt1, rontpxz81

Reply | Quote

I have all the updates apart from 2018-01 Windows rollup installed for both Win 8.1 and Office 2007 – everything running smoothly as well here.

Fractal Design Pop Air * Thermaltake Toughpower GF3 750W * ASUS TUF GAMING B560M-PLUS * Intel Core i9-11900K * 4 x 8 GB G.Skill Aegis DDR4 3600 MHz CL16 * ASRock RX 6800 XT Phantom Gaming 16GB OC * XPG GAMMIX S70 BLADE 1TB * SanDisk Ultra 3D 1TB * Samsung EVO 840 250GB * DVD RW Lite-ON iHAS 124 * Windows 10 Pro 22H2 64-bit Insider * Windows 11 Pro Beta Insider

2 users thanked author for this post.

HiFlyer, Noel Carboni

Reply | Quote

Noel Carboni wrote:

I’m happy to report that there were no new patches distributed through the Windows Update Catalog yesterday, Saturday Jan. 20.

And I’m happy to report that with ONLY the January Internet Explorer patch in place on my Windows 7 and 8.1 systems my computing experience is still smooth, fast, and – amazingly – I have not been hit by malware!

-Noel

Noel,
Well, I got frustrated with IE 11 locking up. SSOOOOO, I installed the Jan update for IE 11, and like you there have been no problems (SO FAR). Just hoping here that things will get sorted out soon.
Dave

1 user thanked author for this post.

JDeC

Reply | Quote

Question for the whiz kids here: How can you determine if you have PIC and/or APIC, & whether 1 or both are running? My CPU is an Intel Pentium 2020M, with the Intel 7 Series/C216 chipset family. They’re in an ASUS X55A laptop I bought in February 2013 with Win 8 (since updated to Win 8.1).

Bought a refurbished Windows 10 64-bit, currently updated to 22H2. Have broke the AC adapter cord going to the 8.1 machine, but before that, coaxed it into charging. Need to buy new adapter if wish to continue using it.
Wild Bill Rides Again...

Reply | Quote

A question about the PIC and APIC interrupt controllers: are both enabled by default in the BIOS with the relatively more recent x64 Windows’ versions, e.g. 7 and up? Because, if they are, the solution to some real incompatibility between those settings (with some updates, such as the monthly S+Q rollout, as reported elsewhere in Woody’s) should be for MS to fix the patch, not for the user to tweak the BIOS, or shouldn’t it?.

Ex-Windows user (Win. 98, XP, 7); since mid-2017 using also macOS. Presently on Monterey 12.15 & sometimes running also Linux (Mint).

MacBook Pro circa mid-2015, 15" display, with 16GB 1600 GHz DDR3 RAM, 1 TB SSD, a Haswell architecture Intel CPU with 4 Cores and 8 Threads model i7-4870HQ @ 2.50GHz.
Intel Iris Pro GPU with Built-in Bus, VRAM 1.5 GB, Display 2880 x 1800 Retina, 24-Bit color.
macOS Monterey; browsers: Waterfox "Current", Vivaldi and (now and then) Chrome; security apps. Intego AV

1 user thanked author for this post.

WildBill

Reply | Quote

This came out 30 minutes ago.

https://finance.yahoo.com/news/intel-asks-customers-stop-using-185213327.html

If there was a EVER a better reason to hold off, this is a great one. Thanks Woody for your DefCon.

I just saw my Linux Mint laptop got a new Intel firmware patch served up. I think it is time to wait a few days to see what happens.

1 user thanked author for this post.

WildBill

Reply | Quote

Linux is in a different boat from Windows. Unless Broadwell or Haswell processors are present, there aren’t the widespread reports of problems which Windows users have had. My own core-i5 Skylake based NUC with Ubuntu 16.04 LTS is still getting the latest kernel updates for kernel 4.4 and 4.13, and I have experienced business as usual, no problems.

This in spite of Linus Torvald’s latest rants against Intel. Some Spectre mitigations are still pending, so I am not stopping Ubuntu Updates from supplying kernel updates. But cleaning up the older kernel versions is an issue if you take the latest updates as they are coming out.

-- rc primak

1 user thanked author for this post.

Cascadian

Reply | Quote

January 22, 2018 @ 3:40pm:

Just completed the installation of KB4074880 (a.k.a. re-release through Microsoft Catalog of KB4055532) for .NET Framework 4.7.1 to my Windows 7 SP1 system — I also manually installed via Microsoft Catalog download, as per your CW article, KB4054856 (prior to the install of KB4074880) — and, though I have not rebooted [not supposed to be necessary according to installers] my system, the error I receive when attempting to start the Powershell ISE (both 32- and 64-bit editions) remains the same as per the Windows Application Crash dialog:

Problem Event Name:    PowerShell
NameOfExe:    PowerShell_ISE.exe
FileVersionOfSystemManagementAutomation:    6.3.9600.18728
InnermostExceptionType:    System.IO.FileFormatException
OutermostExceptionType:    System.Reflection.TargetInvocation
DeepestPowerShellFrame:    indows.PowerShell.GuiExe.Internal.GPowerShell.Main
DeepestFrame:    System.RuntimeMethodHandle.InvokeMethod
ThreadName:    unknown
OS Version:    6.1.7601.2.1.0.256.48
Locale ID:    1033

If Microsoft believes they have resolved this issue…  it is my opinion that they need to think again.

Anyone know of a useful method to let Microsoft know that the issue persists and actually get a response that indicates they either know this ans are working on a fix for the fix, or are unaware and are interested in working with someone with the issue to find out why it persists (without taking a ding to the wallet)?

After all, at this point all was fine before these .NET Framework patches!

1 user thanked author for this post.

woody

Reply | Quote

Did you follow one of the solutions mentioned at https://github.com/dotnet/announcements/issues/53 ?

Reply | Quote

From Stop errors caused by spurious interrupt on systems PIC and APIC interrupt controllers:

“This update resolves the following issue:

Microsoft has received reports of some customers on systems running with programmable and advanced programmable interrupt controllers getting stop errors after installing one of the following updates:

January 3, 2018 – KB4056898 (Security-Only Update)
January 8, 2018 – KB4056895 (Monthly Update)
January 10, 2018 – KB4073576
January 17, 2018 – KB4057401 (Preview of Monthly Rollup)”

3 users thanked author for this post.

woody, abbodi86, WildBill

Reply | Quote

The best installation order for Windows 8.1 users this month is probably:

1. KB4077561 (manual installation)

2. KB4073576 (manual installation)

3. (January 2018 Windows monthly rollup) or (January 2018 Windows security-only update and Internet Explorer cumulative update)

1 user thanked author for this post.

WildBill

Reply | Quote

So we download KB4077561 from the Microsoft Update Catalog, & it will make sure that KB4073576 & the rollup or updates work? Cool Beans! Still, until Don Woody sez so, “Dis family Don’t Do Nuthin!”

Bought a refurbished Windows 10 64-bit, currently updated to 22H2. Have broke the AC adapter cord going to the 8.1 machine, but before that, coaxed it into charging. Need to buy new adapter if wish to continue using it.
Wild Bill Rides Again...

Reply | Quote

Right. The older updates shouldn’t install older files that overwrite newer files from the newer updates.

1 user thanked author for this post.

BobbyB

Reply | Quote

KB4077561 > KB4073576 (AMD fix) > KB4056898 (Security-Only)

KB4077561 is enough and covers both for Group B (with IE cumulative of course)

3 users thanked author for this post.

woody, WildBill, MrBrian

Reply | Quote

Indeed all of the catalog downloads of KB4073576 list KB4077561 as metadata-superseding it.

Revised comment:

The best installation order for Windows 8.1 users this month is probably:

1. KB4077561 (manual installation)

2. January 2018 Windows monthly rollup or January 2018 Internet Explorer cumulative update

2 users thanked author for this post.

woody, WildBill

Reply | Quote

Another revision:

The best installation order for Windows 8.1 users this month is probably:

1. KB4077561 (manual installation). Make sure before installing KB4077561 that this registry item has been set by your antivirus (if you use antivirus).

2. January 2018 Windows monthly rollup (through Windows Update, not manually, to ensure that the registry item mentioned in step 1 is present) or January 2018 Internet Explorer cumulative update.

1 user thanked author for this post.

woody

Reply | Quote

User James Bond 007 reports his/her experiences with KB4056898 and KB4077561 at https://www.askwoody.com/forums/topic/if-youre-thinking-win10-ltsb-may-solve-your-upgrade-treadmill-problems-think-again/#post-161960.

Reply | Quote

1/25/2018

I have added KB4077561 to the Group B patch list for Win8.1 in AKB2000003.

3 users thanked author for this post.

woody, WildBill, MrBrian

Reply | Quote

Late-to-the-party patch: KB4074906 Fix-it tool .NET Framework 4.7.1

It appeared late yesterday afternoon.

What is it and what does it do?

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

I assumed it appeared in the Windows Update Catalog & would be manually downloaded & applied. For Windows 8.1, currently not seeing it with KB4033369, the .NET Framework for 4.7.1 it supposedly fixes.

What is it and what does it do?

No clue yet…

Bought a refurbished Windows 10 64-bit, currently updated to 22H2. Have broke the AC adapter cord going to the 8.1 machine, but before that, coaxed it into charging. Need to buy new adapter if wish to continue using it.
Wild Bill Rides Again...

Reply | Quote

See https://support.microsoft.com/en-us/help/4074906/typeinitializationexception-or-fileformatexception-error-in-wpf-apps-t and https://blogs.msdn.microsoft.com/dotnet/2018/01/09/net-framework-january-2018-security-and-quality-rollup/.

4 users thanked author for this post.

geekdom, woody, AJNorth, WildBill

Reply | Quote

Looks like KB4074906 is a fix for Windows 7 SP1 & Windows Server 2008 R2 SP1, according to MrBrian’s 1st link. Since I have Windows 8.1, that’s why I don’t see it. Under Recommended patches, I see KB4033369, .NET Framework for 4.7.1. Clicking on Details shows this: “The Microsoft .NET Framework 4.7.1 is a highly compatible, in-place update for all the previous versions of .NET Framework 4.X. After you install this update, you may have to restart your computer.” (Italics mine.)

As Woody strongly suggests, I leave Recommended patches unchecked. On my machine, the 2 I leave unchecked every month are KB2976978 (the “Compatibility Update”, supposedly needed to upgrade to Win 10) & KB3080149 (Telemetry update). If no specific warnings apply like the above, I usually apply Recommended as well as Important updates. Recommended hasn’t bitten me before… or at least lately.

Bought a refurbished Windows 10 64-bit, currently updated to 22H2. Have broke the AC adapter cord going to the 8.1 machine, but before that, coaxed it into charging. Need to buy new adapter if wish to continue using it.
Wild Bill Rides Again...

1 user thanked author for this post.

AJNorth

Reply | Quote

“As Woody strongly suggests, I leave Recommended patches unchecked”

Group A installs Recommended updates that are ticked by default, unless Woody says not to for a specific update. Group B doesn’t install Recommended updates.

1 user thanked author for this post.

SueW

Reply | Quote

MrBrian wrote:

“As Woody strongly suggests, I leave Recommended patches unchecked” Group A installs Recommended updates that are ticked by default, unless Woody says not to for a specific update. Group B doesn’t install Recommended updates.

I guess I’m still in Group A, but I don’t default Recommended updates anymore, thanks to the 2 I mentioned above. And since the Preview Rollups for the upcoming month are Optional, I don’t touch them either.

Bought a refurbished Windows 10 64-bit, currently updated to 22H2. Have broke the AC adapter cord going to the 8.1 machine, but before that, coaxed it into charging. Need to buy new adapter if wish to continue using it.
Wild Bill Rides Again...

Reply | Quote

this morning at 3 am microsoft put 3 nasty updates on my machine…I got rid of one, but am unable to uninstall, delete, restore to an earlier time, or remove in safe mode the security patches kb4038777  or  kb4041681…I am running windows 7 and the computer ran fine until 3 am today, January 31, 2018…

any help would help this non techie person alot…

thank you

Reply | Quote

kb4038777 is the September 2017 Security Monthly Quality Rollup for Win7.
kb4041681 is the October 2017 Security Monthly Quality Rollup for Win7.

These are normal monthly patches released through Windows Update. They should be uninstallable.

Reply | Quote