Home Creators Posts Import Register Favorites Logout

Downloads

Content

This is an extensive patch to Windows Vista's NTOSKRNL (build 6003 - earlier kernel versions may not have enough room for the patch) which allows for AVX and AVX2 instructions to run without emulation on supported CPUs (AMD FX and up, as well as Intel 2nd gen Core and Xeon CPUs and up). Driver Signing Enforcement/Code Integrity must be disabled to use it.But even with those disabled, Windows still runs highly-privileged scheduled tasks that detect new drivers installed on the system and automatically disable them if unsigned. It does not disable them again once re-enabled, but to simplify the installation process and avoid a second reboot to realize the AVX support, the script will force a reboot within three seconds of completion. Make sure to save your work before running the script.I could also add the option of creating a boot menu with a second entry using the original, unpatched kernel, but I do not know what users would prefer, as the menu would slow down boot times and require the user to make additional key presses. The patcher contains many safeguards that should prevent a "bad" patch from occurring, including detection of kernels that cannot fit the patch.I have been testing this patch for over two months on systems with thousands of threads running simultaneously. The system is as stable as before the patch was added and it was able to run applications that did not run before, including AVX-optimized versions of llama.cpp, Counter-Strike 2 and more.Updated on 2026-10-19 (at 1318 UTC-4) to resolve an issue with the kernel patching that only presented itself on newer CPUs (including Ryzens).

Comments

Vasilian Sotirov

This is great, this allows me to try AVX-optimized Thorium on my HP 2570p

TheGeekeryGuide32

besides cs2, what other programs have you tested? does visual studio code latest version run now with this?

Templayer

The problem, as I have described months ago in a comment section to one of these patches, is that quite a few applications stop working. I don't think I ever got a reply to that comment. I think? For example, recording applications have problems - if I remember properly, Bandicam told me that I am using a debugger on the kernel, and refuses to run. Or was that Mirillis Action? Can't remember. If that was the same issue, but it sounds familiar, as I have tested everything to be running after a first restart, and several applications stopped working after a second restart, prompting me to sadly uninstall Second System, as I require those applications that failed to work with it enabled (even when they used a disabled profile for Second System, they failed to work until Second System was removed). Back in that comment, I made a detailed list of applications, and how they failed to work (even with Second System disabled profile - uninstalling Second System was the only solution to get them working again).

win32

Does Visual Studio Code require AVX now? I thought that the only issue was with opening terminals.

win32

I believe that there is an issue with the interactions between Second System and the many VxKex forks out there. Some of them were resolved by placing Second System's ntdlx.dll in the system32 directory, but I am not sure about the others. The latest version of Bandicam does work with either Second System disabled or in "shell" mode on a system with only Second System installed.

Templayer

That makes sense, as pretty much everything I used VxKex for failed too, if memory doesn't betray me. qbittorrent, HandBrake, Ocular,... (Win7 64-bit)

TheGeekeryGuide32

you know, im honestly not sure. i havent tested the latested version to be honest. i was hoping you have. im learning to use visual studio code 2010 and then hopefully 2012. also i had another question for you? do you know anything about the famous error on windows vista with it saying when you double click on a 64bit application on more then half of them before updates either on RTM, SP1 , SP2, it will crash and say this application is not a vaild win32application.

win32

Oh, Visual Studio 2010/2012 isn't Visual Studio Code (which is much newer and is Electron-based). I use VS2010 regularly, but haven't tried 2012. And there shouldn't be any issues with "invalid win32 applications" under Second System, unless the executable really is corrupted.