Jump to content

[WIP] Windows Vista Extended Kernel


win32

Recommended Posts


30 minutes ago, Win10-Hater said:

Install rootsupd.exe. It will fix this error

Installed a rootspud and open chromium failed

Edited by mohsad
Link to comment
Share on other sites

I am create a chrome.exe.local and copy

Kernel32.dll

ole32.dll

user32.dll

uxtheme.dll

shell32.dll

dwmapi.dll

To Chromium location 

And Don't work on Windows vista

What should I do?

Link to comment
Share on other sites

9 hours ago, gerona12 said:

I have installed ExKernel Febrary Release on Windows Vista with 2017+ updates. But the system gives such a mistake. How do I fix it?

KHaiP4w5Zb4.jpg

The MEGA folder has a new winload.exe, winload.efi and ntoskrnl.exe that must be used with 2018 or later updates.

Because of the new incompatibilities, the target will be moved from April 2017 to March 2019 (SHA-2 code signing update).

Link to comment
Share on other sites

20 hours ago, Vistafand said:

is there a changelog of what changed between 12312020 and 02262021

New patched versions of winload.exe/efi were introduced to bypass code integrity checks. The installer also automatically sets bcdedit /set {current} nointegritychecks yes for them to work.

To bypass all protections on ntdll.dll and win32k.sys, ci.dll was patched. ntext is now deprecated and the RtlQueryPerformanceCounter function is now in ntdll, so Firefox executables no longer need to be modified.

Link to comment
Share on other sites

3 hours ago, mohsad said:

I am create a chrome.exe.local and copy

Kernel32.dll

ole32.dll

user32.dll

uxtheme.dll

shell32.dll

dwmapi.dll

To Chromium location 

And Don't work on Windows vista

What should I do?

Unsure. I had this happen before on an older install, but never found the cause. What version of Chromium is it? You may want to launch it with the parameter --no-sandbox.

Link to comment
Share on other sites

12 minutes ago, win32 said:

The MEGA folder has a new winload.exe, winload.efi and ntoskrnl.exe that must be used with 2018 or later updates.

Because of the new incompatibilities, the target will be moved from April 2017 to March 2019 (SHA-2 code signing update).

What's meant is:

April 2017 + KB4474419

However, patching up to March 2019 with everything else is probably fine too

Link to comment
Share on other sites

4 hours ago, win32 said:

The MEGA folder has a new winload.exe, winload.efi and ntoskrnl.exe that must be used with 2018 or later updates.

Because of the new incompatibilities, the target will be moved from April 2017 to March 2019 (SHA-2 code signing update).

I replaced new version files, Windows Vista not starting.. File CLFS.sys error 0xC000008

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