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


Posts posted by greenhillmaniac

  1. 21 hours ago, win32 said:

    Though, while I'm at it, here are the missing functions in ntoskrnl required for Skylake graphics:

    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)

  2. On 6/21/2020 at 3:41 AM, win32 said:

    And getting WDDM 1.1+ drivers on Vista is going to be one difficult undertaking, but probably easier than porting WDDM 1.0 drivers to XDDM (Windows 2000 Display Driver Model).

    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.

    • Like 2

  3. 12 hours ago, genieautravail said:

    Nice, but do you have download links for already compiled drivers ? :w00t:

    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.

    12 hours ago, genieautravail said:

    I understand the purpose of the NVME or USB 3.0 drivers but what is the purpose of the WDF and storport.sys drivers ?

    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.

  4. 9 minutes ago, win32 said:

    So here is the first part of the Windows Vista x86 kernel extension tutorial. More functions are to come.

    Since the code will be much longer than before, we will use HxD along with CFF Explorer and ExportTableTester to speed up the process.

    Take the kernel32.dll from your X:\Windows\System32 folder (on x86 systems) or X:\Windows\SysWOW64 (on x64 systems) and copy it somewhere else. Open that copy of kernel32.dll in CFF Explorer and click "Section Headers [x]" on the left sidebar. Right-click on the table of sections and click the option to "Add Section (Empty Space)". Set the size to 0000B100, then name the new section .xdata. Set the characteristics to 60000020. Close CFF Explorer and open the file in HxD.

    While in HxD, copy the code below into your file by right-clicking at the beginning of your new section (which will correspond to 000D2600 or slightly below; the "Raw Address" of .xdata as given in CFF) and then clicking the "Paste write option".

    8B FF 55 8B EC 83 EC 30 56 8B 75 0C 85 F6 75 19 68 0D 00 00 C0 FF 15 68 05 D7 7D 50 FF 15 AC 0D D7 7D 33 C0 E9 8F 00 00 00 83 7D 10 28 73 04 6A 7A EB E9 83 7D 10 2C 57 6A 00 6A 30 8D 45 D0 50 6A 03 FF 75 08 1B FF 47 FF 15 20 05 D7 7D 85 C0 7D 12 50 FF 15 68 05 D7 7D 50 FF 15 AC 0D D7 7D 33 C0 EB 53 33 C0 85 FF 0F 95 C0 8D 04 85 28 00 00 00 89 06 8B 45 D8 89 46 04 8B 45 DC 89 46 08 8B 45 E0 89 46 0C 8B 45 E4 89 46 10 8B 45 E8 89 46 14 8B 45 EC 89 46 18 8B 45 F0 89 46 1C 8B 45 F4 89 46 20 8B 45 F8 89 46 24 85 FF 74 06 8B 45 FC 89 46 28 33 C0 40 5F 5E C9 C2 0C 00

    This code represents K32GetProcessMemoryInfo, taken from Windows 7 instead of Server 2019.

    Open ExportTableTester and drag-and-drop the file into its window. Click "Edit Exports" at the bottom of the window.

    Enter the offset corresponding to the "Virtual Address" value for .xdata in CFF Explorer, and then the function name K32GetProcessMemoryInfo below.

    Reopen the file in CFF Explorer, click "Rebuilder" on the left sidebar, select the checkboxes for "Rebuild PE Header" and "Update Checksum" then click "Rebuild" before saving.

    Shut down Vista and boot into another OS on your PC (or a Linux Live CD/USB if you don't multiboot). Go to your X:\Windows\System32 and rename your present kernel32.dll to kernel32.old (if you're doing it from another Windows, you will probably have to take ownership of the file and adjust the permissions accordingly). Then paste in your edited kernel32.dll before booting into Vista.

    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?

  5. 9 hours ago, mikey8811 said:

    Which of the updates from your repository should I install just to be as safe as possible given the outdated system?

    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).

  6. 13 hours ago, mikey8811 said:

    I presume by path you mean


    Where do i find the path where I downloaded the certificate? Or rather where should I "put" the certificate I downloaded?

    "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.

    13 hours ago, mikey8811 said:

    Also, I was of the impression that the error occurred because I had mistakenly installed some of your updates before this which superceded KB4014984 (Security and Quality Rollup for .NET Framework 2.0, 3.0, 4.5.2, 4.6 on Windows Vista SP2 and Server 2008 SP2: April 11, 2017). As a result an older update did not work.

    If that was the case the update would say that it didn't apply, not that the root certificate is not trusted (I think).

    • Like 1

  7. 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.


    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"


    • Like 1
    • Upvote 2

  8. 12 hours ago, dencorso said:

    Those in ESU won't be available unless by explicit unabashed deceit.

    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.

    • Like 2

  9. 1 hour ago, MrMADRYAN said:

    But will Vista shorten lifespan of the drive more quickly than Windows 7/8/10? As I said - no TRIM is required/supported.

    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.

  10. 26 minutes ago, MrMADRYAN said:

    Hi everyone!
    I want to buy and SSD for my Vista PC and I am interested in Intel X-25E 64GB (Intel SSDSA2SH064G1GN) - it is based on SLC memory and I can buy one for 20 US$ new. As I know, TRIM is not supported or required to use this SSD, moreover Vista does not support TRIM out-of-the-box. And I am interested of this SSD wear level under Vista - will it be more, than under any modern OS? Yep, I use Vista, 'cuz some of my cartography software does not run under any other OS + I am a huge fan of this OS. Of cource, SATA AHCI Mode is enabled and no data defragmenting/search indexing will be done on the boot drive. I use Windows Vista 64-Bit SP2 Ultimate 6.0.6003.20491.

    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.

    • Like 1

  11. 23 minutes ago, NoelC said:

    Not saying I definitely want to do an update, because up to now I've had no problems after having stopped Win Updates at December 2017 on my Win 8.1 system, but I'm just pondering...  If I should want to bring it up to date is there a relatively simple, direct way to use the updates you've curated here to do that?  Or is this all just for 8.0?  If you tell me to "read the whole thread" I'll go do so, though seeing that there are 26 pages is a bit daunting.

    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:

    31 minutes ago, NoelC said:

    Also, if it IS possible, are there trap doors?

    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]

    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 :)

    • Like 1

  12. 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 :)


    • Like 1

  13. 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.


    • Like 7

  14. 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 :hello:


    • Like 5
    • Upvote 2

  15. 10 minutes ago, Lambo said:

    Vistapocalypse said: "KB4019276 was superseded by KB4056564" --> I dont have KB4019276 installed but actually I have KB4056564. So all I have to do now is that I have to run the reg file? But the reg file name is: "Windows6.0-KB4019276-TLS-x64"

    Yeah, though I still need to revise it for x64.

  16. 16 hours ago, Vistapocalypse said:

    I'm noticing that the Reg files in the x64 and x86 folders appear to be identical, which concerns me because I believe x64 would require a somewhat more complex Reg file due to the presence of OSVersion values in Wow6432Node (see @WinClient5270's post here).

    I'll need to take a look at it, because I created that reg file on a XP installation I did recently.

  • Create New...