@orbitbooster @Auen Fred This file is only needed when using one of the options I have highlighted. Software I tested, did not use these options.

 

thank you for the info

 

Original VxKex dev seems to be mostly gone.

Both dotexe and i486 are legit.

dotexe has the latest original code and exe, which we got.

i486 is improving it with CopperFR:
"CopperFR has been actively contributing to VxKex over the past few months by sharing precompiled binaries.
Some notable fixes by CopperFR include: Adding a ConsoleHandle workaround for newer Go applications. Providing Python 11+ support by adding PathCchCanonicalizeEx. Introducing several other APIs and stubs, fixing various apps."
https://github.com/i486/VxKex

Meanwhile there's a fake impersonator tryin to push a fake version into 2.0..


-And there seems to be yet another Kernel Extender project, in this very same Discord:

Oranż Metylowy - kernel22
https://github.com/kuba2k2/kernel22

Spoiler: kernel22

"there's actually quite a notable difference between my project and VxKex
VxKex only allows to redirect entire DLL files, while my project allows rewriting specific functions to something else,
which gives much more flexibility and things like process patching or function hooks are now easily possible with this

this works by replacing the entire DLL importing process that ntdll normally does
but I still have to work out why certain programs crash while loading

mostly because it actually is a completely different mechanism of dll importing
it goes through the import table of every loaded DLL and resolves each symbol manually

while VxKex only goes through the import table once, just to change the DLL names and then lets ntdll do the rest

here for example I changed the winver patch to 9999
also, this is something you can't do in VxKex, which is patching .EXE files to load the custom DLL, instead of using verifier DLLs

and also you can just run an .EXE with the custom DLL once, via a program loader
so this allows to make a "portable" EXE with the patches applied

for now I'm testing on apps that normally work on Win7, because I need to make sure that the DLL import rewriting works before I begin actually adding new missing functions and so far:

1. • I've tested some x64 applications that I could find on my drive, most of them work fine
   • msys2/cygwin applications don't work, they use a different runtime which could be doing something incompatible
   • .NET apps seem to work too (I've only tested one, but hey, that's something), also I'm not a .net developer so I know nothing about it
   • firefox doesn't run, which could be caused by ESET antivirus (e.g. preventing an external DLL being injected into the process)
   • internet explorer seems to work, crashes after a bit when using the "developer tools" - caused by a missing DLL, probably something related to PATH env var
   
   so I'm pretty much satisfied with the results so far
   
   It's not ready yet, It doesn't have any real functionality
   
   I prefer to work out a solid codebase, make every feature stable so far,
   before continuing the work and making it usable by non-developers"

​

 

I tested it on an imaged Win7 x64 (dll was flagged as virus of course), not sure if I had to run also setup with it, however if quarantined it didn't work at all, when restored Traktor 4 (I chose that) with kex enabled didn't run (getwindowsizeblahblah error) more or less the same error all win10 apps give without kex.

So for the moment FOR ME (unless updated or something else is developed) is a no go.

 

Last edited: Aug 12, 2024

I’m still on live 10 suite and I’m on windows 11 I don’t wanna pay for it anymore Abletons too expensive so I just use what I have

 

@orbitbooster You obviously did it wrong, you have to manually add the program to the KexCfg.exe file that you want to run, only then you will see the results

 

Last edited: Aug 12, 2024

Oh my (bad), I'll test it again.
I thought that you just right click on exe and enable Kex from tab (but shouldn't it be the same btw?).
What about setups? Do you have to enable them as well?

 

@orbitbooster It depends on whether the installer requires it, but yes, you have to test it yourself.

 

I retested - nope, same error, kind of -getgdiwindow cannot find entry point-.
Maybe I'll do some other test, but I'm afraid it won't work for me.

 

@orbitbooster I tested VxKex only on music production software, games may not work, tell me what program doesn't work for you?

 

I'm not much interested in games.

 

I didn't see that, NI stuff doesn't work because I also tested Kontakt 7 too, other things work though, we would have to make a list of programs what works and what doesn't

 

Correct, imo it should be a different thread, with a pinned link to this one.

BTW it's not sure in my case that T4 is not compatible with Kex at all, it should be tested on different PCs to be sure, as well for other sw.