Windows 10: Has Windows some legal way to inject DLL into processes?

I want to modify behavior of applications. Coloring of caret depending of keyboard layout in particular. And i need for this purpose some possibility to load my DLL into the processes. AppInit_DLLs, AppCertDLLs actually don't work. SetWindowsHookEx() works with problems (i can not use 32-bit and 64-bit hook at the same time) and it is not enough. It looks like Microsoft plans to exclude this function from API.


Has to be, it's because of security. For preventing spyware. It's good, i agree. But what to do if developer needs some special behavior? Is there some legal way to do it? Crypto-signing is not enough, there are a lot of software developers with crypto-certificates, and Windows can not response for security of their actions. Maybe, solution is checking safety and signing by Microsoft? I mean, software developer makes his DLL, and gives it to Microsoft, for checking (for simplicity it can be source code in confidential way). Microsoft checks it, compiles and signs by it's special certificate for this purpose. And after this procedure this signed DLL can be used in mechanism similar to AppInit_DLLs. If security problem appears, signing of this DLL can be discarded. Registry must have two values - DLLs for 32-bit processes (WOW64) and DLLs for native 64-bit processes. Developer must have possibility to develop these DLLs without signing.


What do you think?


And for actual moment - how can i resolve this task by non-hacking way?

:)

 

User32.dll recognized as dll injection process.

Hello , I was actually trying to run a game on my computer (win10). This game has an anti dll injection software attached to it called xigncode. The problem is that this software detects user32.dll as a third party process and prevents the game from running.
But user32.dll is not a process that I can terminate in itself. How do I deal with this? Is user32.dll associated with any specific processes that may cause that issue ? Because it seems that this program recognizes a process running in the background as a
potential threat. By the way , I have all the services , except the microsoft ones , disabled , thus , the only thing that may cause this issue is a microsoft process. But I am really having a hard time finding which one and why.

***Post moved by the moderator to the appropriate forum category.***

 

.dll file injection

Is the dll you are trying to inject the 32bit version of the dll?

 

Cant inject DLLs

so im trying to inject a DLL with a DLL Injector but it doesn't work, I tried using other injector, its the same (I just reinstalled windows)