Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


  • Content Count

  • Donations

  • Joined

  • Last visited

  • Days Won


Everything posted by XPHomeSP3

  1. 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.
  2. 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?
  3. As always, a big thanks to you @win32 for both your efforts and quick turnaround time as they are much appreciated.
  4. 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.)
  5. 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.
  6. What version of WSUS Offline are you using to download updates to Vista?
  7. 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!
  8. 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.
  9. 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.
  10. 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.
  11. 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.
  12. 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?
  13. 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.
  14. 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.
  15. 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
  16. 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.
  17. I concur. I sincerely appreciate the efforts anyone puts into keeping Windows XP updated and as safe as it can possibly be for those of us who continue to use it on a regular basis. It’s easy for anyone to get behind a keyboard and hide behind the anonymity of the Internet and criticize others but it is the hard work and dedication of individuals like you that is truly what matters.
  18. Forgive my ignorance, but does all this mean if you are running Windows XP and you simply want to update your Root Certificates and Revoked Certificates list all you have to do is run @heinoganda‘s Cert_Updater.exe after unzipping it from the applicable .rar file?
  19. OK, here's a crazy thought... I'm considering turning this project into a Win 8.1/Vista dual boot scenario. 1. Are there any pitfalls to avoid? 2. Is there a specific order in which the OS's should be installed? As always, thanks for any and all expertise, suggestions and advice you may have.
  20. Well done, @win32 ! Can you imagine if Microsoft was this responsive to their users’ requests?
  21. I'm sure you saw this already but, if you're so inclined, it looks like you're going to have to work your magic again, @win32 : DST changes in Windows for Morocco: May 2020 In a nutshell: On the occasion of the holy month of Ramadan, the Kingdom of Morocco will observe the following daylight saving time (DST) changes: Morocco will return to Greenwich Mean Time (GMT) on Sunday, April 19, 2020, at 03:00. After the month of Ramadan, clocks will be set forward one hour (to GMT+1) on Sunday, May 31, 2020, at 02:00. Microsoft made sure they didn't mention this update applies to Windows Embedded POSReady 2009 this time.
  22. Thank you so much for your timely, informative and concise reply @TigTex as this is exactly the type of information I was looking for. I hope to install the 64 bit version of Vista so I will make sure I have at least 4 GB of RAM available.
  23. I have decided to install Vista (which I have never previously used as an OS) from scratch on an older system I have for the benefit of enhancing my computer knowledge. All necessary prerequisites for a (hopefully) successful install of Vista have been met and I am seeking advice on the following: 1. Should I install the 32 or 64 bit variety? 2. After successfully installing the base files, do I have to install SP1 and then SP2 or can I just install SP2 on its own? 3. Is there a particular order for installing all the post SP2 updates up until Vista's April 11, 2017 EOS date? 4. I plan on installing all the Post-EOS Vista-applicable Server 2008 R2 updates discussed in the Server 2008 Updates on Windows Vista thread. Should these be installed in chronological order? Thank you in advance for any and all expertise, suggestions and advice you are able to provide.
  24. I'm not sure how many times I've read the 0patch blog post I referenced previously, but after re-reading it again I apparently glazed over this line: "Renaming ATMFD.DLL or disabling ATMFD via registry makes the vulnerability unreachable even for a local attacker who has ability to execute low-privileged arbitrary code on the computer." Personally, I'm not a fan of modifying the registry because I don't want to mistakenly cause serious damage. For me, renaming the ATMFD.DLL file seemed like a less risky choice to do and then undo if necessary.
  25. There's two reasons why: 1. I read on the 0patch.com blog entry for March 26, 2020, entitled "Micropatching Unknown 0days in Windows Type 1 Font Parsing", that renaming the ATMFD.DLL file reliably blocks all remote and local attacks using these vulnerabilities. The article specifically says, "This is the most effective mitigation, because it eliminates the vulnerable code." As I understand it, your suggestions, while certainly effective, only block remote attacks. Correct? 2. I didn't realize that Windows XP didn't behave the same way as Windows 7 and Windows 10 does when renaming a protected file such as ATMFD.DLL. In hindsight, I would not have done so if I had known this. Knock on wood, I'm not experiencing any problems so far as a result of my actions, but I still don't have the answer to my questions: 1. Am I still unprotected despite using the command prompt commands listed above to rename ATMFD.DLL in Windows XP? 2. How can I restore the ATMFD.DLL file to v. (the version it was before I renamed it and it subsequently auto-repaired)? Thank you. P.S. One more thing, what does "the specific 3D" mean?
  • Create New...