XPHomeSP3

I was thinking along the lines of 60 GB as well, but I’m wondering if I could get away with 40 GB instead? Also, would the decision to install the 64 bit vs. the 32 bit version of Vista have any impact on the ultimate size of the partition?

I am considering installing Vista into a dual-boot environment on an older laptop that currently has Win 10 on it. What size would you or any other readers here recommend I create for the partition that will have the Vista install? I don't want to have wasted space since very little besides the OS will be installed on this partition but I also don't want to have the bare minimum required for the install either.

Were you able to successfully install any of the Server 2008 SP2 ESU updates from 2022-04, 2022-05 or 2022-06?

Just curious if you or anyone else here has had continued success installing the monthly Server 2008 updates on Vista since August 2021.

Just to be clear, and even though it may indeed be a moot point anyway, are you looking for KB968730 for Server 2003? If so... If you scroll down the page, both the x86 and x64 versions are available for Server 2003.

Correct. MS did not release KB4507704 through WU but after doing some digging I was able to confirm they did in fact end up producing it for those XP/POSReady 2009 users who were/are currently paying for MS Premium Support. Any further information beyond this would have involved opening an expensive custom support ticket which I politely declined to do. Thank you but that's really not necessary. I'm fully aware of and completely remember my comment. It may be helpful for anyone currently reading this thread who may be unfamiliar with it though. Yes, this is sadly true and shame on MS for not caring enough about their customers enough to correct it and avoid any further potential confusion regarding it's availability. Thank you for the clarification on this, @erpdude8 , as the distinction between XP x86 and XP x64 wasn't explicitly made in @WinFX's comment. I'm sure you can appreciate then why I may have thought the URL for the KB4507704 update might have been included in amongst the lists provided by @abbodi1406.

I have searched these lists until my eyes have crossed and the last update I can find for Windows XP is KB4501226-x86-embedded from June 2019 (aka 2019-06) which is for the DST changes in Windows for Morocco and the Palestinian Authority. Am I not looking in the right folder or something? I would love to be able to install any newer updates for Windows XP that were released after June 2019, such as KB4507704 which deals with the DST changes in Windows for Brazil and Morocco. This update was released on July 15, 2019 for Windows Embedded POSReady 2009 et al but was never made publicly available for this variety of Windows XP.

As usual, please forgive my ignorance Windows XP gurus but I have two questions: 1. Is there a preferred method to easily check the dates of both the Root Certificates and Revoked Certificates list that are currently installed on your Windows XP system? 2. Is there a significant risk in continuing to use Windows XP without continuing to update both the Root Certificates and Revoked Certificates list?

As there has been no information shared for the past few months, I'm curious if there has still been success installing the monthly Server 2008 updates on Windows Vista? If so, what updates have been installed? If not, what updates have been troublesome?

Just to expound upon this for a moment, the above link refers to KB4519108 which is for DST changes in Windows for Norfolk Island and Fiji Island; however, after clicking on the above link I noticed something "new" that hadn't caught my eye before: When you expand the Applies to: section at the top of the page for KB4519108 by clicking on the More link, lo and behold, Windows Embedded POSReady 2009 appears at the end of the list. Scrolling further down the page to the How to get this update section and specifically under the Prerequisites section it says: There are no prerequisites to install this update on Windows 10, Windows Server 2016, Windows 8.1, Windows Server 2012 or Windows Embedded POSReady 2009. (emphasis mine) Of course, there are no working methods to obtain KB4519108 for Windows Embedded POSReady 2009 as there are for all the other OS's listed, but I do nevertheless find the inclusion of it interesting. Yet another oversight on the part of MS, I guess. And last but not least, a big thanks to @win32 for your custom cumulative DST rollup update and always quick turnaround time.

Here is a correction that was incorporated into today's Patch Tuesday updates for those versions of Windows which are still receiving support: As a result of the October 8, 2020 order from the Fijian Government, Daylight Saving Time (DST) in the Republic of Fiji will begin at 02:00 on December 20, 2020 instead of November 8, 2020. Since I presume those who are currently paying for MS Premier Support for Windows XP would have also received this correction in their November 2020 update(s), I am kindly requesting that @win32 (if you don't mind, of course) please incorporate this into your custom DST .reg file at your earliest convenience. After all, we don't want the cash registers at our chain of supermarkets in Fiji to go haywire, eh?

As always, a big thanks to you @win32 for both your efforts and quick turnaround time as they are much appreciated.

I apparently missed this announcement, but if you're once again so inclined, @win32 : DST Correction in Windows for the Fiji Islands: October 13, 2020 https://support.microsoft.com/en-us/help/4578623/dst-correction-for-fiji-islands Details: This update makes a daylight saving time (DST) end date correction in Windows for the Fiji Islands whereby at the end of daylight saving time (DST), the Fiji Islands will return to Fiji Standard Time on Sunday, January 17, 2021 at 03:00. (The current erroneous DST end date for the Fiji Islands is Saturday, January 10, 2021 at 03:00.)

With all due respect, @Vistapocalypse, the above referenced thread doesn't sound like baloney to me. While it is indeed a peculiar hypothesis, it may very well be peculiar to only that individual who is experiencing the problem. Their attempt at updating to build 6003 only seems to cause a black screen of death on their Vista system which is running an NVIDEA GeForce GT 640 graphics card, not on all Vista systems with NVIDIA cards.

What version of WSUS Offline are you using to download updates to Vista?

WOW, that was fast! As I've said before, it's too bad MS wasn't as responsive to their customers' needs and requests as you are. Thank you!

Once again, it looks like you're going to have to work your magic, @win32 : DST changes in Windows for Yukon, Canada: September 8, 2020 https://support.microsoft.com/en-us/help/4566371/dst-changes-in-windows-for-yukon-canada The relevant details: On the occasion of the end of daylight saving time (DST) on November 1, 2020, Yukon is making the following changes: Yukon will not adjust its clock on November 1, 2020 to move back by an hour and will continue to remain on local time. Yukon customers will now move to a new time zone "(UTC-07:00) Yukon" through this Windows Update on Sunday, November 1, 2020, at 02:00. Microsoft made sure they didn't mention this update applies to Windows Embedded POSReady 2009 this time either.

I guess what I should have asked was whether the Server 2008 updates that can be applied to Vista suffer from telemetry being baked in to their Security Monthly Quality Rollups like Windows 7 and 8.1 do. Microsoft began this behavior in September 2018 by backporting the Unified Telemetry Client and Microsoft Compatibility Appraiser from Windows 10 and making them part of both the 7 & 8.1 Security Monthly Quality Rollups. I thought (erroneously, perhaps) because 7 and Server 2008 are both in extended support until 2023 that they both suffer from this. I will gladly take your advice and search the Server 2008 Updates on Windows Vista thread for any mention of this.

One further question: Does Vista suffer from telemetry being baked in to the Security Monthly Quality Rollups like Windows 7 and 8.1 are victim to? The way to avoid this with 7 & 8.1 is to install the monthly Security Only Quality Updates instead and I'm wondering if this is the preferred way to proceed with Vista as well.

Thanks again, @Vistapocalypse ! I have both the July and August 2020 wsusscn2.cab files downloaded and can also confirm that it is only the July 2020 version which is both SHA-1 and SHA-256 signed; the August 2020 version is SHA-256 only.

Thank you both very much for your prompt and most informative responses, @Vistapocalypse and @jaclaz ! I think it would be wise for me to study your suggestions regarding the multi-boot setup before proceeding. This may end up being a fall project after all. Regarding the old version of wsusscn2.cab, has a definitive version of said old copy been established? Would it be prudent to download the current version of it and squirrel it away to be used with Windows Update MiniTool? In any case, even though it may prove to be somewhat more labor intensive, I sincerely appreciate the efforts that have been put forth to add all relevant Vista updates to an external repository should MS decide to obliterate them entirely from the Update catalog. I assume all relevant Server 2008 updates that may be applied to Vista will continue to be made available from the MS catalog until at least 2023?

Two questions: 1. Concerning the above, which of these three scenarios would be the best one and which would you personally recommend? 2. With all the recent discussion concerning the move by MS from SHA-1 to SHA-2 signatures, will WU still work with Vista prior to installing the KB4039648, KB4493730 SSU and KB4474419-v2 SHA-2 compatibility updates or will all updates now have to be downloaded directly from the MS catalog? Please forgive me as I guess that's actually three questions.

What I find interesting about the 2025 comment is I thought MS was discontinuing any further updates for OS's that only used SHA-1 support as all updates for newer OS's are only signed with SHA-2? If this is the case, then there must be an update for Windows XP to allow it to receive any future SHA-2 updates. I'm with you though, I too would dearly love to get my hands on this and all Windows XP updates that have been issued since April 2019. I'm guessing that's the reason why he posted anonymously. As for 0patch, thanks for the clarification. I'm still trying to figure it all out but, this aside, it certainly is one of the most useful security-minded programs to come along to help us all stay protected.

I was wondering if anyone was going to go the 0patch Pro route or not, so I'm glad to hear it @FranceBB Are you able to provide another screenshot (if you don't mind, of course) as according to the one you provided, you had neither 0 patches applied and 0 applications that were patched with your version of Windows XP at that time. Also. were you aware of/did you receive the new 0patch Agent that was released? It is now on v20.06.18.10800 and the details are here: https://blog.0patch.com/2020/08/new-0patch-agent-is-released-version.html Finally, I think I may have found evidence of someone who is currently paying for Microsoft Premier support for Windows XP and plan on doing so until 2025! Unfortunately, since they posted anonymously there is no way to contact them: https://www.askwoody.com/forums/topic/fbi-private-industry-notification-win7-is-a-leaky-boat/#post-228686

Nice work, @Usher. Unfortunately, I already installed KB4501226 but thankfully @win32 graciously provided us with customized registry fixes for both KB4507704 and KB4557900. The only thing that would make this better is if we could somehow obtain the official KB4557900 MS update from someone who is still receiving XP updates from the MS Premium support program.