Windows 11 KB5095093 prevents Ultimate ASI Loader from loading (Crimson Desert)

[GanksterNG]

After installing Windows 11 update KB5095093, Ultimate ASI Loader stopped working completely.

Environment:

• Windows 11
• Ultimate ASI Loader (latest available version)
• Crimson Desert
• Game version unchanged
• Mods and ASI files unchanged

Symptoms:

• No ASI plugins are loaded.
• No runtime log is created.
• Renaming the loader to winmm.dll, version.dll, dinput8.dll, dsound.dll, and xinput1_3.dll makes no difference.
• The game launches normally, but the loader never appears to initialize.

Troubleshooting performed:

• Reinstalled the loader.
• Tried every supported proxy DLL name.
• Verified the game files.
• No changes to the game installation.

Important finding:
After uninstalling Windows update KB5095093 and rebooting, Ultimate ASI Loader immediately started working again without changing anything else.

This seems to indicate that KB5095093 changes something related to DLL proxy loading or loader initialization.

Can anyone confirm this behavior or investigate whether a compatibility update is needed?

[tornado559]

I confirm that KB5095093 update is ruining everything

[flibdev]

We're having a similar issue with Cyber Engine Tweaks for Cyberpunk 2077, but only for games installed to roughly the default path for each Store (GOG/Steam/Epic) and not for all users (I can't replicate it myself)

• Changing the game path fixes it
• Removing KB5095093 seems to fix it
• Checking the Disable fullscreen optimizations checkbox in the EXE compatibility tab sometimes fixes it

[0x-FADED]

for crimson desert rename the asi loader to winhttp.dll and it'll work.
on my testings this has nothing to do with the asi loader, when "Disable fullscreen optimizations" is checked our local version.dll from game directory will get ignored by windows and original dll from system32 will get loaded and when it's unchecked windows loader behaves normally and loads the version.dll from local directory.

[ThirteenAG]

If the game stops loading the chosen dll for any reason, there's nothing I can do. Renaming the dll is the only solution in such case, as the previous post mentions.
I don't have the game, so if anyone familiar with it can help in case of an issue within the asi loader, pull requests are welcome.