Jump to content

[WIP] Windows Vista Extended Kernel


win32
 Share

Recommended Posts

5 minutes ago, gerona12 said:

It turns out that I can create xxxx.exe.local for any program that requires Vista Extended, for example Whatsapp?

Yes you can, though there are some limitations. Newer Firefoxes (above 64) will have some problems with videos and the address/search bars.

Link to comment
Share on other sites


1 hour ago, burd said:

whatever i do it refuses to load the OS :(

Even if you make a copy of your working boot entry with the MS files (with everything unchanged), as in my second suggestion? :dubbio:

 

Link to comment
Share on other sites

5 minutes ago, burd said:

It works unmodded with a copy of the bootloader

https://imgur.com/a/syTIhgm

Your Vista is UEFI? That changes everything. osloader.exe is a modified version of winload.exe which is intended only for MBR/BIOS systems, though you will be able to use the same ntkrnlmp as everyone else.

So I checked out winload.efi and it's indeed very similar to the MBR version. So hopefully the patched osloader.efi works.

So for UEFI users, just follow this instruction as opposed to the similar one for BIOS users:

bcdedit /set {91274567-89ab-cdef-00ff-nca000ffffff} path \Windows\system32\osloader.efi

  • Like 1
Link to comment
Share on other sites

2 minutes ago, win32 said:

Your Vista is UEFI? That changes everything. osloader.exe is a modified version of winload.exe which is intended only for MBR/BIOS systems, though you will be able to use the same ntkrnlmp as everyone else.

So I checked out winload.efi and it's indeed very similar to the MBR version. So hopefully the patched osloader.efi works.

So for UEFI users, just follow this instruction as opposed to the similar one for BIOS users:

bcdedit /set {91274567-89ab-cdef-00ff-nca000ffffff} path \Windows\system32\osloader.efi

Yea it is,do i need to rename osloader.exe to efi aswell? how does it work

Edited by burd
Link to comment
Share on other sites

12 minutes ago, burd said:

Yea it is,do i need to rename osloader.exe to efi aswell? how does it work

Delete osloader.exe and just download my osloader.efi that I just added to the extended kernel folder. Then replicate my bcdedit instructions (including the new one above).

Edited by win32
Link to comment
Share on other sites

Just now, win32 said:

Delete osloader.exe and just download my osloader.efi that I just added to the extended kernel folder. Then replicate my bcdedit instructions (including the new one above).

i get an error see above link :S

Link to comment
Share on other sites

9 minutes ago, burd said:

https://imgur.com/a/1guYVNq

can you view it now?

So there seems to be something wrong with my custom osloader.efi. Unfortunately there is no EFI hardware here for me to test it with, so any corrections will take awhile.

Does my ntkrnlmp.exe work with the regular winload.efi and nointegritychecks = 1 (yes) in the boot entry?

Though this could also be used in theory, but I need to test it:

https://github.com/Mattiwatti/EfiGuard

Edited by win32
Link to comment
Share on other sites

6 minutes ago, win32 said:

So there seems to be something wrong with my custom osloader.efi. Unfortunately there is no EFI hardware here for me to test it with, so any corrections will take awhile.

Does my ntkrnlmp.exe work with the regular winload.efi and nointegritychecks = 1 (yes) in the boot entry?

Though this could also be used in theory, but I need to test it:

https://github.com/Mattiwatti/EfiGuard

it doesn't work even with winload.efi same error

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
 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.


×
×
  • Create New...