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 greenhillmaniac

  1. I've also used that post for my own Vista installs! Thanks.
  2. Is it possible that GPU drivers have a hard coded OS check at the sys level? I say this, because AMD drivers on Windows 8.0 completely BSOD, while they work just fine on Windows 7 (maybe there could be a similarity to Intel's Vista approach)
  3. How would you go about in implementing this in a conceptual view? UWP seems so linked to the way Windows 10 handles all of its subsystems, it seems like an impossible task.
  4. With that it would be possible to use newer AMD and nVidia GPUs, which would be a dream come true Do keep on posting updates, this is an extremely interesting project.
  5. That's actually where I got it originally! When I made the post I forgot about its origin. Thanks.
  6. As you can guess, there could be some legal trouble in sharing modified MS driver files, so having instructions on how to do it is the best way. WDF = Windows Driver Foundation has functions that allow newer drivers to work properly. WDF 1.11 was released with Windows 8.0 and as an update for Vista and 7. storport is a storage related driver that allows the generic AHCI drivers and NVMe to work.
  7. Don't programs load DLLs that are available on the same path as the executable first? Would it be possible to put the modified kernel32 in the program folder so it could use the extra functions it needed? EDIT: Found this interesting article: https://docs.microsoft.com/en-us/windows/win32/dlls/dynamic-link-library-search-order
  8. Just a thought. Is it possible to fool programs to look for the modified kernel32 instead of actually modifying the system file? For example, renaming the updated file to kernel33 and changing some attributes in the executable to look for that file?
  9. The minimum required should be the Servicing Stack update and the Monthly Rollup. Don't forget about the SHA-2 update to install updates newer than September 2019 (though it renders WU useless, since it bumps the build number to 6003). I actually need to update the repository with January's MR (you can just get it from here for now).
  10. "C:\cacert.cer" is just an example of the path where the certificate could be placed. Choose the one you want. BTW, after running the command the certificate will be in your certificate store, so you can delete the downloaded file after. If that was the case the update would say that it didn't apply, not that the root certificate is not trusted (I think).
  11. That happened to me in Windows 7 when also trying to install recent .NET updates. I think W7 actually received some update about outdated certificates as opposed to Vista. I solved it by importing a MS certificate that Vista and 7 don't ship with. http://download.microsoft.com/download/2/4/8/248D8A62-FCCD-475C-85E7-6ED59520FC0F/MicrosoftRootCertificateAuthority2011.cer Run the following command with Admin rights to install it (replacing the path with the one where you downloaded the certificate) certutil -addstore "Root" "c:\cacert.cer"
  12. Yeah, they upgraded the Chromium release used in the Launcher. Is there any way to restore the old version so the game is still playable on Vista?
  13. Actually, WES7 will still be supported until the end of the year, more or less:
  14. Actually, they will be available in the Update Catalog and documented in the Windows 7 Update History page. The only thing the bypass does is tell the Windows servicing stack that indeed the system does have the ESU bit turned on. No licenses are faked or bypassed. WU won't be able to fetch the ESUs. That will be up to the user (in the same fashion we've been doing with Vista and 8.0). Still, if it's a moderation decision that we won't have any more discussion on the issue, I won't speak about it ever again.
  15. If you disable the disk hungry services, such as the ones I mentioned, you should get just about the same wear level as Windows 7. Though I will admit I've never run Vista on a SSD, but I'm sure other members will share their experiences.
  16. You should also disable Superfetch/Prefetch, since Vista can be quite aggressive with those (it was made in the time when PCs had not a lot of memory but plenty of HDD space). You can use the instructions in this article: https://www.thewindowsclub.com/disable-superfetch-prefetch-ssd Additionally, you can also disable Windows Search, but that one shouldn't be as taxing on the SSD: https://www.howtogeek.com/howto/10246/how-to-disable-search-in-windows-7/ If TRIM is not needed on that SSD, you should be good otherwise.
  17. My update repository is only applicable to Windows 8.0, but I use Windows 8.1 on my daily desktop machine, so I can brief you in how to stay up to date and avoid any undesirable effects . Since you stopped updating in 2017, it should be easy to bring your system up to date again. You'll need: Servicing Stack: KB4524445 (http://download.windowsupdate.com/d/msdownload/update/software/secu/2019/11/windows8.1-kb4524445-x64_a8a5b5fd641b016e8ee0636c1dde808e98656d3a.msu) Monthly Rollup: KB4530702 (http://download.windowsupdate.com/d/msdownload/update/software/secu/2019/12/windows8.1-kb4530702-x64_8a3d5f3eb996149590805699de1e65c37c57a5f1.msu) Flash Player: KB4516115 (http://download.windowsupdate.com/c/msdownload/update/software/secu/2019/09/windows8.1-kb4516115-x64_0d9f83c866638da6434b4f93779faf007d00c774.msu) .NET Framework Updates (I don't know which version of .NET you have installed on your system. By default, Windows 8.1 only has .NET 4.5.2. It's possible to enable .NET 3.5 and install .NET 4.8. I'll leave a link to the latest Security and Quality Rollup) Well, all updates apart from the Servicing Stack are uninstallable, unless you run /resetbase with Dism. The Servicing Stack update is not uninstallable because it updates core servicing components of Windows 8.1. It's perfectly safe to update, with no issues reported. The biggest offender in terms of unwanted side effects are the Monthly Rollups. By default they install telemetry components and enable CPU mitigations that slow down performance. Of course, there are workarounds to these issues. In terms of CPU mitigations, they can be disabled by importing this: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management] "FeatureSettingsOverride"=dword:00000003 "FeatureSettingsOverrideMask"=dword:00000003 And the telemetry can be disabled by following this guide on Askwoody: https://www.askwoody.com/forums/topic/2000012-neutralize-telemetry-sustain-win-7-8-1-monthly-rollup-model/ This is what I use on my system, and I'm very happy with the results. Mind you, I use a Ryzen CPU, so I also need to have this installed to bypass the Windows Update block MS implemented. Hope this helps
  18. I also created a thread related to this topic. You can find some more information there:
  19. Holiday updates for all! Replaced Monthly Rollup with the new KB4530691 (located on the root directory of the repository) Replaced Servicing Stack with the new KB4532920 (located on the root directory of the repository) Replaced Flash Player update with the new KB4516115 (located on the root directory of the repository) Added Security Only Updates, KB4516062, KB4519985, KB4525253 and KB4530698 (located in the folder "/Security Only (Post September 2016)") Replaced Internet Explorer Cumulative Update with KB4530677 (located in the folder "/Security Only (Post September 2016)") Replaced .NET Framework Security and Quality Rollups: KB4514370 for .NET Framework 3.5 SP1 (located in "/.NET Framework 3.5 Updates/Security and Quality Rollup"); KB4514368 for .NET Framework 4.5.2 (located in "/.NET Framework 4.5.2 Updates/Security and Quality Rollup"); KB4533010 for .NET Framework 4.6.x and 4.7.x (located in "/.NET Framework 4.6x-4.7.x Updates/Security and Quality Rollup"); Added new September .NET Security Only updates: KB4514349 for .NET Framework 3.5 SP1 (located in "/.NET Framework 3.5 Updates/Security Only Updates"); KB4514342 for .NET Framework 4.5.2 (located in "/.NET Framework 4.5.2 Updates/Security Only Updates"); KB4514337 for .NET Framework 4.6.x and 4.7.x (located in "/.NET Framework 4.6x-4.7.x Updates/Security Only Updates"); I'll need to investigate .NET Framework 4.8 and see if it is actually installable on Windows 8.0. For everything else, there's not much to report on. Next month marks the last release of a security update for IE10. Merry Christmas and a Happy New Year to everyone https://mega.nz/#F!ExhDEbDA!pUhzXKVp5-hgzvylW_btfQ
  20. As I've posted in a previous thread, it is possible to get Ryzen working on Vista, but drivers are kind of a pain to get working. Windows 7 USB3 drivers do work on Vista, but don't try and slipstream them, because they're not signed for NT 6.0. I would recommend first installing using a PS/2 keyboard and a DVD, if possible.
  21. It's been a long time, but I finally managed to update the repository: Replaced Monthly Rollup with the new KB4530695 (located on the root directory of the repository) Added Security Only Updates, KB4516051, KB4520009, KB4525239 and KB4530719 (located in the folder "/Security Only (Post August 2018)") Added Servicing Stack Update KB4531787 (located on the root directory of the repository) Replaced Internet Explorer Cumulative Update with KB4530677 (located in the folder "/Security Only (Post August 2018)") Updated SHA2 update KB4474419 to v4 (located in the folder "/SHA2") Replaced .NET Security and Quality Rollups: KB4507003 for .NET Framework 2.0 and 3.0 (located in "/NET 2.0 SP2/Security and Quality Rollup"); KB4507001 for .NET Framework 4.5 (located in "/NET 4.5.2/Security and Quality Rollup"); KB4533012 for .NET Framework 4.6 (located in "/NET 4.6-4.6.1/Security and Quality Rollup"). Updated the TLS 1.1 and 1.2 enabling reg file to include x64 (located in "/Extras") I hope I didn't miss any updates. This should cover the 4 months of updates missing. I think all of these updates require SHA2 support, so be sure to first install the Servicing Stack and SHA2 updates found in the "SHA2" folder. After Server 2008's EOL there might be a chance to use Extended Security updates on Vista until 2023, thanks to @abbodi1406's "Bypass Windows 7 ESU" hosted on MyDigitalLife forums, though I don't think anybody has tested the bypass on an actual Vista install. Merry Christmas, happy New Year and here's to 3 more years of patching https://mega.nz/#F!txxRyLzC!1vBMGzMHiL864f3bl1Rj1w
  22. Yeah, though I still need to revise it for x64.
  23. I'll need to take a look at it, because I created that reg file on a XP installation I did recently.
  24. Are you sure? When it throws that error it's usually already on the system.
  • Create New...