VxKex icon indicating copy to clipboard operation
VxKex copied to clipboard

KxNt.dll not found

Open OneForgottenMan opened this issue 1 year ago • 3 comments

Intro:

Recently all applications with VxKex broke showing error that they can't find the KxNt.dll. In log there is next error entries:

[‎30.‎08.‎2024 7:15:32 1064:1068 KexDll\dllpath.c:207 (KexpShrinkDllPathLength)] RtlFindCharInUnicodeString returned an error // NTSTATUS error code: STATUS_NOT_FOUND
[‎30.‎08.‎2024 7:15:32 1064:1068 KexDll\dllrewrt.c:125 (KexInitializeDllRewrite)] Failed to append Kex32/64 to the DLL search path. // NTSTATUS error code: STATUS_NOT_FOUND

Cause:

This is due to how app works and adds its own path to application DLL search path. It erases duplicate entries from PATH variable and replaces them with its own path, so the length of PATH is not changed.

Solution:

To avoid this error, you NEED to have duplicate entries in PATH environment variable. You can just pick last path in the PATH environment variable and duplicate it several times. How many times - depends on path in which the VxKex installed. The length of all those duplicates combined must be greater or equal to the length of VxKex own path, so it would fit in place of them.

OneForgottenMan avatar Aug 30 '24 04:08 OneForgottenMan

How do you solve that? I met the same problem.

bilibiliSilentH avatar Sep 19 '24 14:09 bilibiliSilentH

i tried to do what you said in the solution, so i took my original path

C:\VulkanSDK\1.3.296.0\Bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\ and duplicated the last entry a bunch of times

C:\VulkanSDK\1.3.296.0\Bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\WindowsPowerShell\v1.0\

this contains the last path 29 times, which is greater than the amount of characters VxKex is installed in

C:\Program Files\VxKex

yet i still get the same error when i try to launch the program im trying to install (in this case, the drivers for my gpu)

immagine

did i do something wrong?

thecaprisun avatar Jan 02 '25 20:01 thecaprisun

Linked to:

  • https://github.com/i486/VxKex/issues/87
  • https://github.com/i486/VxKex/issues/63
  • https://github.com/i486/VxKex/issues/45
  • https://github.com/i486/VxKex/issues/19
  • https://github.com/i486/VxKex/issues/11

For the moment, you can use:

  • https://github.com/YuZhouRen86/VxKex-NEXT

Neustradamus avatar Feb 26 '25 08:02 Neustradamus