Jump to content

Guide - Vista extended kernel installation


TSNH

Recommended Posts


  • 2 weeks later...
On 2/28/2022 at 11:43 AM, TSNH said:

https://msfn.org/board/guidelines/ 1a

I cannot provide links to modified Microsoft binaries so all requests for that will be ignored

Quote

1.a This is not a warez site! Links/Requests to warez and/or illegal material (e.g., cracks, serials, etc.) will not be tolerated. Discussion of circumventing WGA/activation/timebombs/license restrictions, use of keygens, or any other illegal activity, including, but not limited to, requests for help where pirated software is being used or being discussed, will also not be tolerated. Offenders may be banned on first violation.

So it is allowed to talk openly about the KernelEx, how to install it, etc. but not allowed to talk about where you can find it?

This is not piracy or even "any other illegal activity", otherwise it shouldn't even be allowed to be discussed here.

Link to comment
Share on other sites

17 hours ago, kcznsk said:

So it is allowed to talk openly about the KernelEx, how to install it, etc. but not allowed to talk about where you can find it?

any windows version is closed-source

talking about something closed source is fine but directly sharing the files could lead to serious legal problems from microsoft

Edited by winvispixp
Link to comment
Share on other sites

  • 1 month later...

Installing Pale Moon on Windows Vista Extended Kernel:

  1. If you want to have a Start Menu folder and entires in "default programs" panel, then first install Palemoon version 27.9.4 and remove all contents of %programfiles%\Pale Moon folder
  2. Download current x64 version of Pale Moon (31.0.0 at the time of writing).
  3. Extract the installer with 7-zip and copy all contents of "core" folder to %programfiles%\Pale Moon
  4. Delete api-ms-win-core-memory-l1-1-0 in %programfiles%\Pale Moon
  5. Run palemoon.exe, enjoy

If you want to use Pale Moon on Windows XP or vanilla Vista, check @roytam1's fork called New Moon https://msfn.org/board/topic/182647-my-browser-builds-part-3/

 

Link to comment
Share on other sites

Hi all, I've decided to write my own batch installer for the extended kernel that automates a few steps. At the moment it should be able to:

  • Automatically trigger UAC to run as administrator
  • Check that you are installing on Vista x64 (but doesn't check that you have the required updates!)
  • Back up existing system files as *.bak
  • Replace system files at reboot to avoid 'access denied' problems
  • Set file permissions for the replacement files
  • Enable local DLL redirection automatically and fix problems with Windows Sidebar (by making it use the original ole32.dll)
  • Create OSVER.ini
  • Optionally install the Media Foundation Platform update (see below)
  • Optionally set x64 Windows Media Player as default for all users (if installing Media Foundation Platform)
  • Check for any errors in the process and safely roll back any changes if problems occur (obviously still a good idea to back up your system!)
  • Create a log for troubleshooting

The batch installer requires a different configuration file (attached) for each release of the extended kernel to be installed. These are named in the same date format as the zipped extended kernel .7z files.

To use:

  • Place SETUP*.bat in the same folder as the extended kernel installation files extracted from the .7z archive
  • Copy the corresponding version of the .cfg configuration file into the same folder (and rename as SETUP.cfg if using installer versions older than SETUP3.bat)
  • If installing the Media Foundation Platform, place the extracted MFPLATSETUP folder as a subfolder with the rest of the extended kernel files
  • Run SETUP*.bat and hope that it works...

The installer automatically creates a basic OSVER.ini (if none exists), but its contents can be customised in the config file (does not replace any existing OSVER.ini).

If Vista behaves oddly post install (e.g. Firefox failing with RtlQueryPerformanceCounter not being found), a second reboot should fix it. This is a limitation of the way this installer replaces system files at reboot, as certain files are loaded into memory before replacement and remain until the next reboot.

Update 31 Mar 2023:

  • Updated installer SETUP3.bat
    • Feb 2022 configuration info no longer embedded, but .cfg files no longer need to be renamed (as long as only one version is placed in its folder - can get confused if more than one .cfg file available!)
    • Makes copies of MUI files for the March 2023 extended kernel release
  • Added SETUP_03092023_x64.cfg and SETUP_03092023_x86.cfg for the March 2023 release / revision 1

Update 31 Oct 2022:

  • Renamed SETUP_10192022_x32.cfg to SETUP_10192022_x86.cfg :blushing:

Update 28 Oct 2022:

  • Updated installer SETUP2.bat (various minor bug fixes; no longer fails installation when running from read-only location; checks that file permissions are updated successfully)
  • Added SETUP_10192022_x32.cfg and SETUP_10192022_x64.cfg for the October 2022 release (see note below)

Download installer

SETUP3.bat for all releases - this is overdue a re-write, really. But for now I have amended it to work with the newest March 2023 release. Unfortunately extremely busy at the moment so this has had very VERY limited testing - please back up and use with caution!

setup3.bat

SETUP2.bat for old releases up to and including October 2022, that has had a bit more testing (at least, no-one's told me they've had any major issues...):

setup2.bat

By default, SETUP2.bat works with the Feb 2022 release of the extended kernel, but can be made to work with newer/older versions using configuration files (attached below). Simply rename the version you need as SETUP.cfg and place in the same folder as the batch file.

Configuration files

Note: the October 2022 and March 2023 Extended Kernel releases include too many files for the batch installer to handle at present, so the configuration files have been split in two for now. I would recommend installing the x64 files before x86 (reboot required in between). On first reboot after installing the x64 files, you may get a BSOD or crash with the 'Windows did not shut down properly' screen, but Windows will start up again normally after this, and the x86 files can be installed normally.

The March 2023 x86 configuration file should be used with SETUP3.bat to ensure MUI localisation files are copied.

setup_03092023_x64.cfg setup_03092023_x86.cfg

setup_10192022_x64.cfg setup_10192022_x86.cfg

Configuration files for older releases:

setup_07252022.cfg setup_06102022.cfg setup_02042022.cfg setup_10262021.cfg setup_05142021.cfg setup_02262021.cfg setup_12312020.cfg

If your Vista was installed using the MSDN iso, you may need to place Win32's replacement EXPLORER.exe with the rest of the extended kernel files and remove the ; at the start of the relevant line in the file list in SETUP.cfg (not required from the Feb 2022 release onwards).

Help for configuration files:

Config info.txt

Quote

Old versions

setup.bat

 

 

Edited by Bizzbob
Link to comment
Share on other sites

21 hours ago, Bizzbob said:

Hi all, I've decided to write my own batch installer (SETUP.bat attached) for the extended kernel that is hopefully a little safer and easier(?) to use. At the moment it is able to:

  • Automatically trigger UAC to run as administrator
  • Check that you are installing on Vista x64 (but doesn't check that you have the required updates!)
  • Back up existing system files as *.bak
  • Replace system files at reboot to avoid 'access denied' problems
  • Set file permissions for the replacement files
  • Enable local DLL redirection automatically and fix problems with Windows Sidebar (by making it use the original ole32.dll)
  • Create OSVER.ini (if not already existing)
  • Optionally install the Media Foundation Platform update (see below)
  • Optionally set x64 Windows Media Player as default for all users (if installing Media Foundation Platform)
  • Check for any errors in the process and safely roll back any changes if problems occur (obviously still a good idea to back up your system!)
  • Create a log for troubleshooting

By default, the batch works with the latest (at time of writing) Feb 2022 version of the extended kernel, but can be made to work with earlier versions using configuration files (attached). Simply rename the version you need as SETUP.cfg and place in the same folder as the batch file.

The installer will copy the extended kernel files from the same folder where the batch file is located, but this can be changed by specifying the SOURCEDIR in the config file.

To be able to install the Media Foundation Platform, place the extracted MFPLATSETUP folder as a subfolder with the rest of the extended kernel files.

The contents of OSVER.ini can also be customised in the config file.

**If your Vista was installed using the MSDN iso, you may need to place Win32's replacement EXPLORER.exe with the rest of the extended kernel files and remove the ; at the start of the relevant line in the file list in SETUP.cfg (this step does not seem to be required for the Feb 2022 version).

Edit: If Vista behaves oddly post install (e.g. Windows themes failing to load very occasionally during testing, or modern Firefox failing with RtlQueryPerformanceCounter not being found), a second reboot seems to fix these issues.

Config info.txt 1.96 kB · 2 downloads setup.bat 27.38 kB · 4 downloads setup_02042022.cfg 1.92 kB · 1 download setup_02262021.cfg 1.53 kB · 0 downloads setup_05142021.cfg 1.53 kB · 0 downloads setup_10262021.cfg 1.94 kB · 0 downloads setup_12312020.cfg 1.35 kB · 1 download

Hi, I've tried your installer on Vmware and at first got this error (maybe because I'm running Polish language version):

notvista.PNG.aa79e07f54505a2107c9302f79cdd6ee.PNG

After removing software checking part of the setup.bat, I was able to proceed with the installation.

On reboot(s) another error popped up:

accessrights.PNG.f662f6e9d231bc8b9486408cf577d839.PNG

So after making sure that all extended kernel files are in system32 directory, I booted my virtual machine into a Vista installation image and launched automatic startup repair. The tool not only solved the problem (probably by removing the installer from autostart), but also retested all permissions for system file back to their defaults, so I didn't have to do it myself :) and in the end the extended kernel was working as intended.

Good job @Bizzbob (no sarcasm) because it's definitely an improvement over the original installer, although it still need some tweaking. It's also highly possible that I'm getting all those errors just because I have Polish edition of Vista. I'll put a link to your post in the guide.

Link to comment
Share on other sites

Ah yeah, I hadn't thought about the version string output from 'ver' and file permissions being localised in different language editions of Windows. Will need to tweak it a bit and update it here once I've tested a bit more.

Edited by Bizzbob
Link to comment
Share on other sites

I've updated the attached batch file in the earlier post with one that should fix those issues. It should now hopefully work correctly with non-English versions of Vista. Didn't realise Windows localised CMD's version string and even usernames/groups used for file permissions (should have really -_-...)

The problem was with 'Wersja 6.0' not matching 'Version 6.0' and trying to set permissions with iCacls using 'Administrators' and 'System' etc. rather than using language-independent security identifiers.

Thanks for bringing to my attention! Please let me know if you catch any more bugs.

Link to comment
Share on other sites

15 hours ago, Bizzbob said:

I've updated the attached batch file in the earlier post with one that should fix those issues. It should now hopefully work correctly with non-English versions of Vista. Didn't realise Windows localised CMD's version string and even usernames/groups used for file permissions (should have really -_-...)

The problem was with 'Wersja 6.0' not matching 'Version 6.0' and trying to set permissions with iCacls using 'Administrators' and 'System' etc. rather than using language-independent security identifiers.

Thanks for bringing to my attention! Please let me know if you catch any more bugs.

I can confirm the new version works :thumbup

Link to comment
Share on other sites

  • 3 weeks later...
On 6/7/2022 at 12:08 AM, mina7601 said:

Download link of what exactly? The extended kernel? If that's the case, then it can't be provided, because:

what's the purpose of making a guide to something you can't download?

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...