TSNH

Yesterday one of MSFN users posted a link to a YouTube video on this forum. You might want to take a look at it

You really could have said that earlier. Assuming those 2 reports of partial success are just placebo effects and that you have tested this on multiple Haswell boards, this information can be called "fake". Until now, no one has proved it to be true or false and I couldn't myself either as I don't have a proper hardware to do this.

This video is rather outdated. Follow the guide here: https://msfn.org/board/topic/183046-guide-vista-extended-kernel-installation/ Make sure you have all the necessary windows updates installed and don't forget about running the "bcdedit /set {current} nointegritychecks yes" command if you are replacing files manually. btw: Windows Vista has problems with running properly on Haswell or newer Intel CPUs (this includes i5 8250u), they are described here: https://msfn.org/board/topic/177509-windows-vista-intel-haswell-issues-documentation/ On Betawiki there is an information that those problems were solved/reduced in the 6003 version of hal.dll, but it's still not known if the information is correct. You are welcome to test this. KB4474419 is one of updates that contain the 6003 hal.dll (it requires KB4493730 to be installed first). You need a 6003 update to install the extended kernel anyway.

As earlier posts in this thread suggest that Haswell+ and Ryzen problems are caused by the same bug in HAL, I decided to test if the issue was solved in the 6003 version of hal.dll (see this: https://msfn.org/board/topic/181612-wip-windows-vista-extended-kernel/page/106/?tab=comments#comment-1206074) I installed KB4474419 and hal.dll was upgraded to version 6003. Result: Nothing changed, BSODs are still occurring as they were. This means that the article on Beta Wiki was indeed a fake news or (less likely) that Haswell+ and Ryzen problems are in fact unrelated. PC specs: AMD Ryzen 5 1600AF, B350 MB with April 2018 BIOS version, Nvidia 1050TI, Windows Vista x64

Running CPU-Z on Windows Vista Extended Kernel: Normally, if you have the extended kernel installed CPU-Z will stuck on 15% when loading. I've just found out that to solve this problem you can simply redirect cpuz.exe to a vanilla Vista kernel32.dll First apply the redirection reg file, then put vanilla vista kernel32.dll in the cpuz.exe.local directory (just like for Windows Sidebar)

To avoid making Service Pack 3 for Server 2008, Microsoft was repeatedly putting those updated 6003 files in every bigger update they released. As extended kernel requires 6003 system files, not a security fix of a single update, almost any monthly rollup (or just bigger update) released around September 2019 will allow you to install the Extended Kernel (SHA-2 support might be needed too, but I'm not sure)

It didn't work with 4.7.2 so I think Microsoft changed the system requirements on purpose. Updates that i had installed: all Vista updates till 2017 + KB4019478 - D3Dcompiler-x64 + SHA-2 updates KB4039648-v2,KB4493730, KB4474419 + Extended Kernel The "4.6.2" text next to "Server 2008 SP2" was added quite recently: http://web.archive.org/web/20210506200116/https://docs.microsoft.com/en-us/dotnet/framework/get-started/system-requirements http://web.archive.org/web/20211006034517/https://docs.microsoft.com/en-us/dotnet/framework/get-started/system-requirements

I can confirm everything that you are saying. First I tried with my old .NET 4.6.2 offline setup that was signed on 15.07.2016 with both SHA-1 and 256 and I got the "unsupported OS" error. Than i downloaded a new installer from Microsoft, and it worked! I'm going to try 4.7.2 next

I solved it by following this guide: https://www.reddit.com/r/techsupport/comments/6gajcs/fix_for_activation_context_generation_failed_the/ Here is my exported registry: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SMI\WinSxS Settings\amd64_microsoft-windows-settings_31bf3856ad364e35_none_5e7b0013834d1c8b\6.0.6000.16386\Settings] "disableTheming"="xsd:string" "dpiAware"="xsd:string" "autoElevate"="xsd:string" Note that numbers in the path might be different for you. Many dependences are still missing: user32.dll: CreateWindowInBand, GetCurrentImputMessageSource, GetWindowBand and there are tons of missing API-MS-WIN-CORE files:

I tried to run Windows 8 task manager (much better that Vista/7 one) on Windows Vista with extended kernel and got this error: Translation: Cannot launch the application, because it's simultaneous configuration is invalid. More details can be found in the application's event log. Event log screenshot: Translation: Cannot generate the activation context for [path]. The setting http://schemas.microsoft.com/SMI/2005/WindowsSettings^autoElevate is not registered. Does anyone know how to "register" this thing? (I have no idea what "simultaneous configuration" or "activation context" are ) EDIT: At first I thought that "WindowsSettings" is somehow UWP related, but it looks like it's not, because the website above was created in 2009 http://web.archive.org/web/20090625053858/http://schemas.microsoft.com/SMI/2005/WindowsSettings^autoElevate. It has been broken for 12 years now.

I used to have .net framework 4.7.2 installed on Vista. Some programs displayed an error "A programs has stopped working", but I could minimize it (not close) and the application worked fine (for example BlueStacks3), others like Visual Studio 2010 Express didn't run at all. Currently I use 4.6.1 (officially supported on Server 2008), but 4.6.2 is stable too. Most modern programs still support those versions.

Thanks for reply. It looks like i had a spelling error in my osver.ini file. No hex editing is needed!

Today i tried Firefox 91.3.0 ESR on Windows Vista with the new extended kernel. It looks like there is some problem with font rendering... (Same issue with Firefox 94, Firefox 78 works fine) Does anyone know how to solve this?

The problem seems to be connected directly to the fact that you don't have KB4039648-v2 or KB4493730 installed. https://support.microsoft.com/en-us/topic/windows-update-sha-1-based-endpoints-discontinued-for-older-windows-devices-10b58bd9-5ba2-b23d-498b-139ce5c709af Actually solutions on the internet suggest only using some random system scans/troubleshooters. Try disabling the internet connection Try clearing the Windows Update cache in %systemroot%\SoftwareDistribution\DataStore. If it doesn't help I have no other suggestions than to reinstall Windows :(

The link is the same as for the previous version. Do you have all the Vista updates till 2017 + KB4039648-v2,KB4493730 installed? You can find Vista updates till 2017 here: https://msfn.org/board/topic/181756-windows-vista-update-repository-until-april-2017/ and Server 2008 updates here: https://msfn.org/board/topic/176686-server-2008-updates-on-windows-vista/

Guide for the new version of the extended kernel is now complete!

Did you rename kernel32.dll.bak to kernelol.dll ?

@Strikker1can I reuse your error screenshots in https://msfn.org/board/topic/183046-guide-vista-extended-kernel-installation/ ?

Thanks for info. I actually never got the cmd installer to work. This is one of three SHA-2 updates. I don't think it is needed for the extended kernel itself, but I wanted to avoid situations where SHA-2 is "partially" supported. Like 4 months ago I installed all the updates till march 2019 or so (I don't remember at this point) and the extended kernel worked. I'll add an appropriate warning anyway. I'm going to add this later. I will have more time next weekend This section was meant for workarounds for programs like Windows Sidebar or CPU-Z. For now the Windows's default automatic root certificate updater works fine, so there's no need to install rootsupd yet. I'm not getting any certificate errors in Firefox.

Actually I noticed that one of KB4039648, KB4474419 or KB4493730 (SHA-2 updates) contains 6003 hal.dll too. Vmware is one of those must have programs for me. Maybe the problem reported by @Jaguarek62occurs only on certain hardware.

As there has been no step by step Extended kernel installation guide posted on MSFN, I decided to crate one: Feel free to post any suggestions you have. If you spot a grammar error please let me know (English is not my native language)

Unofficial Windows Vista x64 Extender Kernel step by step installation guide All the credits for the Extended Kernel go to @win32, not me. Disclaimer: I take absolutely no responsibility for any damage to your PC (or laptop or whatever) caused by following/misfollowing this tutorial. Backup everything before continuing. Special thanks to @winvispixp for guide improvement suggestions. List of Vista-unsupported programs that work with the extended kernel version 03092023 (current): Note: for best stability it's recommended to go for the October 2022 version (10192022) and only install 64-bit files (see step 8) Preparations: 1. Prepare a .7z extracting program (for example 7-zip). 2. Prepare Ubuntu or Linux Mint installation CD (for method 2 and uninsallation). 3. Update your Vista to 2017 EOL version (especially install sp1,sp2 and the platform update). 4. (Optional) You can install some server 2008 updates if you want. List of compatible updates by @LiptonAcer 5. (Optional but highly recommended) Install KB4019478 - D3Dcompiler-x64 update, .NET Framework 4.6.1 and 3.5, DirectX June 2010 redistributable and all the Visual C++ redistributables 64 and 32 bit. 6. Install SHA-2 Server 2008 updates in the following order: KB4039648-v2,KB4493730, KB4474419. 7. Backup your original files. 8. Extract the vistaexkernsetup_03092023.7z file (or vistaexkernsetup_10192022.7z if you are installing October 2022 version) into any folder you like (later called folder X). Method 1 - Automatic installation Method 1 involves using the Installer. If you are facing some problems, use alternative installer by @Bizzbob or method 2 instead. If you don't want to install 32-bit extended kernel, use method 2. 1. Copy your original kernel32.dll located in %systemroot%\syswow64, rename it to kernelol.dll and put the new file in syswow64 2. Run the setup.exe as administrator. (These steps do not apply to @Bizzbob's installer) 3. Follow the instructions on your computer’s screen. 4. Make sure that files like kernel32.dll are present in %systemroot%\system32. If they are not, use method 2. 5. Reboot the computer. 6. Repair file permissions. 7. Congratulations, enjoy Method 2 - Manual installation Method 2 involves using the Ubuntu live CD. The reason why we use Ubuntu and not another windows installation is because Ubuntu doesn’t support NTFS file permissions and thus ignores them completely making file replacing much easier. 1. Launch cmd.exe as administrator and run the following command without quotes: “bcdedit /set {current} nointegritychecks yes”. 2. Insert Ubuntu installation disk Either CD or USB (AKA live CD). 3. Reboot into the Ubuntu live CD. 4. Choose: “Try Ubuntu”. 5. On the top bar go to: Places\Computer. (This may differ depending on version of Ubuntu you have). 6. Locate folder X and copy all the dll and exe files from the folder X (EXCEPT setup.exe and files, that have filename ending with .wow64) to yourpartition:\windows\system32, click replace when prompted (make sure you have a backup). 7. If your Vista is UEFI, do the same for winload.efi. 8. (Optional) Move all the .wow64 files from the folder X to a different directory and remove .wow64 from their name, than copy them to yourpartition:\windows\SysWOW64, click replace when prompted (Right now 32bit extended kernel is in a very early stage of development, so personally I don’t recommend it for daily usage). 9. Shut down Ubuntu and boot Windows. 10. Repair file permissions. 11. Congratulations, enjoy Method 3 - Redirection If you don’t want to replace your system files, you can make specific programs use extended kernel dlls instead of vanilla Vista ones using local redirection. Unfortunately this method doesn’t let you run most of the new applications, that file replacing would do (for example there is a problem with exe files that spawn from another and many other). 1. Apply the DLLredirectionenabler.reg. 2. For each application you want to run with the extended kernel, do the following: 3. For exefilesname.exe create an exefilesname.exe.local folder. 4. Put files from folder X in the exefilesname.exe.local folder. 5. Congratulations, enjoy Repairing file permissions Automatic tool If you visit system32 after the installation you will probably notice that permissions for extended kernel files look like this: Obviously letting “Everyone” to modify your core system files causes a serious security issue so it is necessary to restore the default file permissions pattern: The owner should be: “nt service\Trustedinstaller”. Example: 1. Locate %systemroot%\system32\kernel32.dll 2. Open properties and under security tab click “Advanced”. 3. Make sure that “Include inheritable permissions from this object’s parent” checkbox is disabled. 4. Close the advanced window and click “edit” 5. Remove “Everyone” and other account that are not in the default pattern. 6. Add “Users” and “Administrators” accounts and set permissions for them to match the default pattern. The names have to be in your language. Look at other system files if you don’t know how to spell the words. 7. Add “SYSTEM” account and set permissions for it to match the default pattern. 8. Add “nt service\Trustedinstaller” account and set permissions for it to match the default pattern. They are different this time. 9. Click “OK”. 10. Open properties and under security tab click “Advanced” again. 11. Under “Owner” tab click “edit” than “Other users or groups”. 12. Enter “nt service\Trustedinstaller” without quotes. 13. Click “OK”. 14. Congratulations! Do the same for other files: If you have installed only 64 extended kernel than you have to restore file permissions only in system32 for the following files that you have replaced: ci.dll dwmapi.dll kernel32.dll ntdll.dll ntk32.dll ntoskrnl.exe ole32.dll powrprof.dll shell32.dll user32.dll uxtheme.dll winload.efi winload.exe api-ms-win-core-fibers-l1-1-0.dll advapi32.dll dxgi.dll dxgiext.dll api-ms-win-core-synch-l1-2-0.dll API-MS-WIN-CORE-WINRT-ERROR-L1-1-0.dll API-MS-WIN-CORE-WINRT-ERROR-L1-1-1.dll API-MS-WIN-CORE-WINRT-L1-1-0.dll API-MS-WIN-CORE-WINRT-STRING-L1-1-0.dll api-ms-win-shcore-scaling-l1-1-1.dll bcrypt.dll shcore.dll userenv.dll useren0.dll kernel33.dll jobsrv.exe gdi33.dll gdi32.dll dwritent60.dll dwritent10.dll DWrite.dll api-ms-win-core-memory-l1-1-6.dll api-ms-win-core-memory-l1-1-5.dll api-ms-win-core-fibers-l1-1-0.dll api-ms-win-core-delayload-l1-1-1.dll api-ms-win-core-delayload-l1-1-0.dll If you have installed 32 bit extended kernel than you also have to restore access rights in syswow64 too (for the following files that you have replaced): kernel32.dll powrprof.dll ole32.dll shell32.dll user32.dll uxtheme.dll dwmapi.dll ntext.dll powrprof.dll shellnew.dll ntk32.dll miscstubs.dll ws2_33.dll ws2_32.dll user33.dll shell33.dll shcore.dll These are the final names for those files, remember that some of them have to be renamed during the installation as described in the guide. Optional Extended Kernel components d3d12.dll - This is DirectX 12 for Windows 7. You can copy it to system32. It does not work on Vista, but can be useful for Windows 8 users. Windows 7 Media Foundation Platform - This is needed for video codec support in some programs like Firefox. Making the Windows 7 mfplat system wide by installing it causes problems with Windows Media Player and Dremscene, so it's recommended to use redirection method instead: 1. Apply the DLLredirectionenabler.reg. 2. For each application you want to run with the Windows 7 mfplat, do the following: 3. For exefilesname.exe create an exefilesname.exe.local folder. 4. Extract the mfplatsetup.7z and copy all the dlls it contains to the exefilesname.exe.local folder. 5. Congratulations, enjoy 378.66_Vista and 398.11_Vista - Modfied Nvidia drivers for Vista. More details: https://msfn.org/board/topic/184056-breakthrough-p2-new-pascal-special-microsoft-nvidia-driver-port-for-vista-x64/ Windows Version Spoofer Version spoofer allows you to fool programs into thinking that you are running a newer version of Windows! Create an empty file called "osver.ini" (without quotes) in the %systemroot% folder. Put contents of the template below in your file. Adjust the template depending on your needs. Template: [Path to an exe file] Commandname=1 [Path to another exe file] Commandname=1 [global] Commandname=1 List of supported commands: Enabled (this one is always needed) MajorVersion MinorVersion BuildNumber CSDVersion PlatformId (2 is used to indicate that the OS is Windows NT. 1 represents 9x and 0 represents Win32s) to spoof Windows 7 sp1, use: Enabled=1 MajorVersion=6 MinorVersion=1 BuildNumber=7601 Windows 8.0 Enabled=1 MajorVersion=6 MinorVersion=2 BuildNumber=9200 Windows 8.1 Enabled=1 MajorVersion=6 MinorVersion=3 BuildNumber=9600 Windows 10 (the build number depends on the Windows 10 version, that you want to spoof) Enabled=1 MajorVersion=10 MinorVersion=0 BuildNumber=19044 Windows 11 (the build number depends on the Windows 11 version, that you want to spoof) Enabled=1 MajorVersion=10 MinorVersion=0 BuildNumber=22000 Example: [C:\Program Files\Mozilla Firefox\firefox.exe] Enabled=1 MajorVersion=6 MinorVersion=1 BuildNumber=7601 [global] Common errors If you're using an ISO from MSDN you may encounter an error "The ordinal 899 could not be located in the dynamic link library SHELL32.dll" while booting. you need to swap the explorer.exe from C:\Windows with the one called "replacement explorer". This error appears, when winload.exe's signature is different from the one expected by Windows. Make sure you have run this command: “bcdedit /set {current} nointegritychecks yes” and that you have replaced all of the required files. Make sure you have all the necessary updates installed. List of Vista-compatible programs that don’t work with the extended kernel. Windows Sidebar (resolvable): 1. Apply the DLLredirectionenabler.reg. 2. Create a "sidebar.exe.local" folder in %programfiles%\Windows Sidebar\ . 3. Copy your backup ole.dll to the "sidebar.exe.local" folder. 4. Congratulations, enjoy CPU-Z (old Extended Kernel version) - https://msfn.org/board/topic/183046-guide-vista-extended-kernel-installation/?do=findComment&comment=1207488 Kaspersky antivirus - https://msfn.org/board/topic/181612-wip-windows-vista-extended-kernel/page/112/ VirtualBox (as a host) - VirtualBox checks if system files were signed by Microsoft. (it is called "hardering") Windows Live Photo Gallery (only if you install 32-bit extended kernel) Feel free to report other programs. How to uninstall the extended kernel? Method 1 If you used Method 1 durning installation, the dlls were automatically backed up as [nameofdll].dll.bak. You just need to delete the extended kernel dll and then change the name of the vanilla one (delete the .bak extension; it should look like [nameofdll].dll after) Repair File permissions Method 2 Follow the Method 2 steps, but instead of copying extended kernel files, put your backup files back in system32 (or SysWOW64 if you are uninstalling the 32bit extended kernel) Repair file permissions. Method 3 Alternatively, file replacement can be done using Windows Vista PE. Boot from CD or USB Choose your keyboard layout and on the next screen click "Repair my Computer" and choose CMD. You can use 7-Zip or Notepad's "save as" dialog as GUI Put your backup files back in system32 (or SysWOW64 if you are uninstalling the 32bit extended kernel) Repair file permissions Old versions

Here are official MSI 6.0-signed AMD USB3 drivers. https://www.msi.com/Laptop/support/GX60-1AC.html#down-driver&Win7 64 Choose 'driver\Win7 64\VGA\ATI Richland VGA' Unfortunately they are from 2012 so i would be quite surprised if they work on modern hardware.

Today i've tested Vmware player on Windows Vista 6003. Here are the results: (I used an old Windows Vista virtual machine that had no updates installed) First I installed Vmware player 6.0.4, than KB4493458 (not KB4493471). Hal.dll got upgraded to version 6003. After the installation had finished i launched a ready Windows ME virtual machine inside the Vista VM: It worked with no visible errors. I left it running for a few minutes and everything seemed fine. Of course I still don't know if it works on real hardware and all the updates between Vista EOL and KB4493458 installed. On boot an "The "vmStatsProvider" can not be initialized. "vmGuestLib" returns error "VMware Guest API is not enabled on the host" (3)." error gets logged, but this is likely because i'm running one virtual machine inside another.

Good point, I'll edit the main post.