Replies

Thanks for suggesting this, i was at my wit’s end wondering why it wouldn’t install (failed with error code – 2146762495) until i saw your comment, changed my system date to a month ago and it worked. I also noticed that it’s a known issue on the .Net 4x pages but i’m pretty sure i’ve installed .Net 4x updates outside of their release month previously so presumably the required certificate in the .Net package would not have matched the system time then either.

https://support.microsoft.com/en-us/topic/security-only-update-for-net-framework-4-6-4-6-1-4-6-2-4-7-4-7-1-4-7-2-for-windows-7-sp1-and-windows-server-2008-r2-sp1-and-windows-server-2008-sp2-kb4601090-582f84bd-c341-83c9-e428-eac9b50f021e

Nibbled To Death By Ducks wrote:

I’ve said it before, and I’ll say it again, after seeing all the howling, agonized shrieks of wounded Win 10 users on this and so many other forums, I’m just going to putter along as best I can for as long as I can.

Same. I endorse this completely. Why is it that we’re all not clamouring to get on the Win10 bus until we’re forced to? No, it’s not a long term strategy but then neither is staying on a relatively stable version of 10 until they drop support for it. Win10 is… 5 years old now? One of the latest updates for it was eating hard drives when running chkdsk, a tool that’s supposed to help the user recover from problems not start them. It’s completely unacceptable that we’re this far into release and have to deal with a product that’s eternally in beta.

Please don’t anyone castigate users for clinging to the lifeboat of 7 for as long as possible.

4 users thanked author for this post.

Nibbled To Death By Ducks, Cybertooth, Charlie, LHiggins

Was quite a shock to read this this morning but of course one’s health and family do come first so i wish you all the best in your retirement. This has been my go to place daily for a few years now ever since Microsoft really dropped the ball with their update strategy and i love that you saw through the corporate fluff pieces when many sites swallowed it hook, line and sinker so i do hope that continues. I know the place is in good hands but i also hope that the diminishing but still large Win7 userbase still has a place here.

1 user thanked author for this post.

woody

For the first time in recent memory, there were none at all for Internet Explorer

Wow. I had to reread this sentence twice because I thought my eyes were being cheated. I don’t ever recall this happening before, does anyone remember? I’m still sceptical that explorer could have zero vulnerabilities exposed in the last month when it’s as leaky as Flash.

I fully expected to be treated like a digital leper at some point for continuing to use an end-of-life OS but i didn’t quite expect it to happen so soon. For instance, i visit the Steam forums a fair bit and if someone dare question whether such and such a game works on Win7 you can guarantee there will be several immediate responses shaming or making fun of that person and i’m fed up with it. There are a myriad reasons we can’t or don’t want to downgrade to Win10 and people should respect that, i understand that’s not the point of this article and i agree that business users need to take stricter precautions but it speaks to the wider FUD that gets thrown about whenever this topic comes up.

14 users thanked author for this post.

Kranium, Elly, Nibbled To Death By Ducks, Charlie, lanceboil, lurks about, jburk07, Microfix, BobT, Cousinjack, Cybertooth, wdburt1, Seff, Canadian Tech

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.

No idea why my comments keep getting deleted but glad you got it sorted.

Hold on… what happened to the rest of my comment? Did i say something inappropriate or was it because it wasn’t strictly on topic?

…have you tried the built-in windows system image tool under Backup and Restore? I’m surprised nobody mentioned it but that’s what i used and it worked for me. I don’t want to add to your complexity but if Macrium keeps throwing up that error then it’s worth a try. Of course then you need to purchase some external storage on which you save the system image but you should have one of those for backup anyway and i highly recommend one of the little WD portable drives. I have a WD My Passport Ultra 1TB but i didn’t restore from that because i have a desktop PC and restored from an internal WD Black drive.

Hope you get it sorted out.

[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, 10 months ago by T.

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.

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.

Wonderful! Thank you.

Apologies for dragging this up again but i just tried this method and it worked great for the security only update kb4552951 (.NET Framework 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, 4.7.2) but failed on security only update kb4552952 (.NET Framework 4.5.2) with the error message – ‘Software Update KB4552952 Installation Wizard does not apply, or is blocked by another condition on your computer.’

I have all the prerequisites otherwise i assume kb4552951 would have failed so my question is, does .net 4.6-4.7.2 replace 4.5.2 and therefore the update is no longer applicable? That was my assumption but i was curious what you thought.

Sitting on vulnerabilities is why we get ransomware like wannacry which took down entire hospitals, yes it was likely used by script kiddies but the vulnerability was stockpiled by a well known 3 letter security agency so they could weaponise it – https://en.wikipedia.org/wiki/Eternalblue

You might think that keeping vulnerabilities under wraps forever means they’ll never be discovered but that’s very much a NOBUS (NObody But US) way of thinking. These things are always discovered and exploited at some point and the state have been shown to be not as smart as they think they are when amassing exploits.

1 user thanked author for this post.

GoneToPlaid