Jump to content

Server 2008 Updates on Windows Vista


Jody Thornton

Recommended Posts

Nothing that uses windows installer works, I have tried all the solutions that I can find on the web. I've  run sfc and done a restore. Unfortunately my oldest restore point was after I installed all of the .msu files from the MEGA site.

I give up, probably don't need any new windows software anyhow.

Link to comment
Share on other sites

  • 2 weeks later...

On 5/2/2021 at 3:13 PM, Vistapocalypse said:

After further thought, it seems likely that @greenhillmaniac never noticed that KB4020507 for .NET 4.5.2 was replaced by KB4345682, apparently in August 2018. (There is no mention of it in greenhillmaniac’s detailed August 23, 2018 post, nor is the update in the repository.) You may want to try installing it from this Catalog link to see if you have better luck. It was apparently never replaced. (The same update evidently replaced a Vista-era .NET 2.0 update, KB3142023.)

Edit: There was actually a discussion between VistaLover and greenhillmaniac on Page 2 as to whether KB4020503 (which, again, was the 4.6.x equivalent of KB4020507 for 4.5.2) should be included in the repository, with VistaLover arguing against it.

 

 

you guys have limited time to upgrade .NET to 4.6.2 before April 2022 (forget these .NET updates for 4.5.2).  MS will be dropping support for old .NET 4.x versions like 4.5.2, 4.6 & 4.6.1 by then [just to give you Vista users out there the heads up]

Quote

Support for .NET Framework 4.5.2, 4.6, and 4.6.1 will end on April 26, 2022.

 

Edited by erpdude8
Link to comment
Share on other sites

16 hours ago, erpdude8 said:

you guys have limited time to upgrade .NET to 4.6.2 before April 2022 (forget these .NET updates for 4.5.2).  MS will be dropping support for old .NET 4.x versions like 4.5.2, 4.6 & 4.6.1 by then [just to give you Vista users out there the heads up]

I do not have an ESU license for Server 2008 SP2 and have not personally attempted to install any ESU updates on Windows Vista, but the .NET updates reportedly cannot be installed anyway, so Vista’s .NET is already effectively unsupported, including 4.6.2. Even if that obstacle can be circumvented, why would Microsoft continue to release .NET updates for Server 2008 SP2 after April 2022 when 4.6.0 was the last .NET version that officially supported it? :dubbio:

Edited by Vistapocalypse
Link to comment
Share on other sites

@erpdude8 : Most of "us" guys (you probably mean fans of the Windows Vista OS) are probably already aware of M$'s .NET FW deprecation plans... :angry:

No panic actions should be called for, just some preservation plan in advance...

First thing to do is probably download from M$ and archive somewhere the Full standalone (off-line) installers for .NET FW 4.5.2/4.6/4.6.1 ...
4.5.2
https://download.microsoft.com/download/E/2/1/E21644B5-2DF2-47C2-91BD-63C560427900/NDP452-KB2901907-x86-x64-AllOS-ENU.exe
4.6.0
https://download.microsoft.com/download/C/3/A/C3A5200B-D33C-47E9-9D70-2F7C65DAAD94/NDP46-KB3045557-x86-x64-AllOS-ENU.exe
4.6.1
https://download.microsoft.com/download/E/4/1/E4173890-A24A-4936-9FC9-AF930FE3FA40/NDP461-KB3102436-x86-x64-AllOS-ENU.exe

Then, someone on a clean Vista SP2 install will have to restore a functioning WU (while it's still possible - at least one solution is known to work, but its "legality" is grey... :whistle:) and then (first) install 4.5.2 and let WU fetch all applicable updates up to Vista's EOL and then, additionally, up to WS2008's EOL - finally, make a list of those updates and share it for others to fetch and archive manually from M$'s Update Catalog...

The same will have to be done for 4.6.0; as correctly pointed out, that's the very last WU supports officially on Vista; the list of updates that'd be produced for 4.6.0 is also applicable to 4.6.1, which is the last one to install out-of-the-box on Vista SP2 (but updates for it must be downloaded and installed manually) ...

I'm afraid I'm not allowed to discuss 4.5.2/4.6.0 updates past WS2008's EOL, since those are governed by ESU plan and reserved only for paying customers... It is my understanding the ESU cycle will end on Jan 2023, so that probably means 4.6.0 on WS2008 will reach deprecation as planned on Apr 2022, some 8 months before the OS's ESU cycle ends... Unless, of course, M$ make an exception and continue releasing security-only updates for 4.6.0/WS2008, for the duration of those 8 months... Even if they don't, my experience so far has shown that the "family" of 4.6.x .NET FWs gets updated by the same (or, mostly, compatible) "update" files; so if a 4.6.2 security-only update is released come May 2022 for Win7 SP1, there's a good chance it will install on (ESU-eligible) 4.6.0/WS2008...

8 hours ago, Vistapocalypse said:

why would Microsoft continue to release .NET updates for Server 2008 SP2 after April 2022 when 4.6.0 was the last .NET version that officially supported it?

https://docs.microsoft.com/en-us/lifecycle/faq/dotnet-framework

Quote

Beginning with version 4.5.2 and later, .NET Framework is defined as a component of the Windows operating system (OS). Components receive the same support as their parent products, therefore, .NET Framework 4.5.2 and later follows the lifecycle policy of the underlying Windows OS on which it is installed.

There is no change to the lifecycle policy for .NET Framework 4.x and its updates which continue to be defined as a component of the OS and assume the same lifecycle policy as the Windows version on which it is installed.

The above quotation isn't 100% clear, but to me it sounds like .NET FW 4.6.0 (> 4.5.2), the last to be officially supported on ESU WS2008SP2, should be eligible for security-only updates until the end of ESU support for said OS... How do others read this? :dubbio:

Edited by VistaLover
Link to comment
Share on other sites

Forgive the disturbance friends, just yesterday 0Patch has published the fix for a vulnerability that also affects I.E.9:

 

https://blog.0patch.com/2021/05/micropatch-for-remote-code-execution.html

https://msrc.microsoft.com/update-guide/vulnerability/CVE-2021-26419

The patch on Microsoft Update Catalog is KB5003165.

 

Edited by Sampei.Nihira
Link to comment
Share on other sites

On 5/19/2021 at 6:16 PM, Sampei.Nihira said:

Forgive the disturbance friends, just yesterday 0Patch has published the fix for a vulnerability that also affects I.E.9:

 

https://blog.0patch.com/2021/05/micropatch-for-remote-code-execution.html

https://msrc.microsoft.com/update-guide/vulnerability/CVE-2021-26419

The patch on Microsoft Update Catalog is KB5003165.

 

32bit:

http://download.windowsupdate.com/d/msdownload/update/software/secu/2021/04/windows6.0-kb5003165-x86_6934e71bbdd55abf9d13b4c1799463e7c8e66f49.msu

64bit:

http://download.windowsupdate.com/d/msdownload/update/software/secu/2021/04/windows6.0-kb5003165-x64_f1d972f3a9fbdc5fbfefbfdb0a67e86e5d8dde6e.msu

 

For the x64 update, you can install the IE part of it with a workaround:

- start cmd as administrator
- change location to the folder that contains the msu file, example cd /d C:\updates
- copy/paste and execute these commands (preferably one by one)

	mkdir .\tmp

	expand.exe -f:*Windows*.cab *kb5003165-x64*.msu . >nul

	expand.exe -f:* *kb5003165-x64*.cab .\tmp >nul

	start /w PkgMgr.exe /ip /m:"%cd%\tmp\package_2_for_kb5003165~31bf3856ad364e35~amd64~~6.0.1.1.mum" /quiet /norestart

	start /w PkgMgr.exe /ip /m:"%cd%\tmp\package_3_for_kb5003165~31bf3856ad364e35~amd64~~6.0.1.1.mum" /quiet /norestart

	del /f /q *kb5003165-x64*.cab

	rd /s /q tmp
Edited by nicolaasjan
Link to comment
Share on other sites

1 hour ago, nicolaasjan said:

For the x64 update, you can install the IE part of it with a workaround...

You gave that workaround two months ago on page 28 of this thread, so don’t be offended if I don’t “like” it a second time. :)

As for myself, I think I can manage to avoid visiting a “specially crafted website” with IE9, since I never use it at all anymore.

Edit: I almost forgot to ask, Have you had any success installing .NET Framework updates for Server 2008 SP2 that have been released in the last year or so?

Edited by Vistapocalypse
Link to comment
Share on other sites

15 hours ago, Vistapocalypse said:

Edit: I almost forgot to ask, Have you had any success installing .NET Framework updates for Server 2008 SP2 that have been released in the last year or so?

 

There is no .NET Framework installed here, so I really can't tell...

Besides, In Vista I install the Server 2008 updates, not the Server 2008 SP2 ones (I thought these were not applicable?). (stupid mistake)

Edited by nicolaasjan
Link to comment
Share on other sites

2 hours ago, nicolaasjan said:

In Vista I install the Server 2008 updates, not the Server 2008 SP2 ones (I thought these were not applicable?).

Server 2008 SP2 = Server 2008 + SP2

I think you just confused it with Server 2008 R2 (and Server 2008 R2 SP1), which is Win7 (and Win7 SP1) based... ;)

Link to comment
Share on other sites

33 minutes ago, VistaLover said:

Server 2008 SP2 = Server 2008 + SP2

I think you just confused it with Server 2008 R2 (and Server 2008 R2 SP1), which is Win7 (and Win7 SP1) based... ;)

Ah, sorry, you're right of course, I wasn't fully awake I guess, haha.

Link to comment
Share on other sites

  • 3 weeks later...
  • 3 weeks later...
  • 3 weeks later...
  • 4 weeks later...

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...