recent Win7 KB4566517 update failed to install

Topic

New Reply

Since purchasing a Windows 7 ESL in January I have been able to install all Windows 7 updates on my PC flawlessly. However, of the three “important” updates I was notified of two days ago, only two installed properly (KB4565354 – Servicing Stack Update and KB4565524 – Security Monthly Quality Rollup). Unfortunately, after several attempts, I am still not able to install KB4566517, the Security and Quality Rollup for .NET Framework. I’ve rebooted a couple times but still no installation.

For what they’re worth I am attaching screenshots  that show the failed installation as well as the update history and list of installed updates. I’ve never had issues with installing updates in the past, so I am stumped on what to do about this one. The “get help with this error” link on the failure screen only led to “0 results for WindowsUpdate…”. I have tried to get some insight into this issue on Microsoft’s website but can’t find support for Windows 7 updates.

I would appreciate any help anyone could lend.

Reply | Quote

Replies

I’m having the same problem with several of my computers with ESU Licenses.  This is the first issue since activating my ESU licenses.

Reply | Quote

Known Issues in https://support.microsoft.com/en-my/help/4566517/kb4566517 has just updated today :

On systems with .NET Framework 4.5.2 and above, you may observe a patch install failure with Error: 0x643, or error code 1603, when attempting to install this update on a system with a proper Extended Security Update (ESU) license installed.

We are working on a resolution and will provide an update in an upcoming release.

Also there are many reports from users that temporary disabling AV software during the installation of the June .Net patch, notably in case of AVAST/AVG, fixes the issue for them.

4 users thanked author for this post.

abbodi86, jsnyder925, Elly, Microfix

Reply | Quote

FYI, the removed “ESU_LOCK” workaround was originally ment to identify and validate Windows 7 Embedded systems (WES/POS/FES)
they replaced with different code to validate those systems, but it appear the new way is not working as expected

great analysis by DenizOzmen
https://answers.microsoft.com/en-us/windows/forum/all/net-update-kb4565636-fails-to-install-on-esu/6bc2c8ca-3b98-4ab3-b509-dc2bbf988a84?auth=1

1 user thanked author for this post.

Microfix

Reply | Quote

Yeah, so if MS cannot get their act together within a few days (since this .NET patch actually fixes an RCE) people with paid ESU subscription might consider using dotNetFx4 ESU Bypass by @abbodi86 et al. as temporary solution, to install this patch ASAP.

Reply | Quote

It’s reported that the bypass doesn’t work either for .NET 4.5.2 or greater so, it looks like it’s a waiting game.

If debian is good enough for NASA...

Reply | Quote

You mean the bypass doesn’t work when one has a valid ESU subscription or at all?

Reply | Quote

.NET4 doesn’t install, whether you have a valid subscription or you use the bypass.

Reply | Quote

I have not seen reports of dotNetFx4_ESU_Bypass failure (except those with Avast/AVG which interfere in the process)

however, the bypass is designed to handle normal Client/Server systems (i.e. not embedded)
so if the flawed ESUEngine.dll inside the .NET 4.x patches is mistakenly detecting some normal system as FES products, the bypass cannot help with that

1 user thanked author for this post.

Microfix

Reply | Quote

Would i be right in assuming that the patch for .NET 3.5.1 installs fine by itself? I’ve not tried any of them yet but i had no problem with this one back in may when using the bypass script. I hope we can all get these installed though given there’s a remote code execution vulnerability, though in my limited knowledge i am unable to determine how serious it is for the average user.

Reply | Quote

Using @abbodi86 ‘s script, the .NET 3.5.1 installs along with the Rollup/SO and IE11 CU.
.NET4 does not install in the same way. Try using the dotNetFx4 ESU Bypass by @abbodi86 et al for .NET4

Reply | Quote

When you say dotNetFx4 ESU Bypass do you mean this? I did that back in May so i’ll be sure to use it again when i try installing them.

Reply | Quote

[T]

Scratch that, i see that the ESU_LOCK workaround that no longer works has already been discussed. I’m with @Moonbear on this, the solution is way above my skill level and i’d rather not mess with the dotnetfx addon so guess i’ll take me chances which is fine, i knew the luck would run out at some point.

• This reply was modified 4 years, 7 months ago by T.

Reply | Quote

MS Re-REleased the KB today and it installs without the 643  or 1603 error.

Reply | Quote

Unfortunately, not for me.

The re-issued KB4565583 is still giving me the 1603 error. 🙁

Please see here: https://www.askwoody.com/forums/topic/standalone-installer-script-for-windows-7-esu-regardless-the-license/#post-2282849

Reply | Quote

[EP]

no probs installing KB4566517 on my end (I did it manually – no errors encountered); using the recent “revised” dotNetFx4 ESU Bypass pack (not the original one) from abbodi.

• This reply was modified 4 years, 7 months ago by EP.

1 user thanked author for this post.

7ProSP1

Reply | Quote

So that’s the trick, eh? This has been driving me absolutely batty since Patch Tuesday last week.

I used the revised version with the original version 1 of KB4565583 and it finally installed successfully. 🙂

Great work, once again, @abbodi86 !

Reply | Quote

Well, after numerous attempts since first posting the issue, I was just successful in installing the Win7 KB4566517 update. Microsoft issued a v2 update that fixed the problem. Thanks to everyone who contributed.

1 user thanked author for this post.

Paul T

Reply | Quote

I’ll also had my success at installing KB4565623 (Security and Quality Rollup .NET Framework 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, 4.7.2) using v2 for this and the bypass.

Reply | Quote