[bruh300]

Hey so I understand that using a "fake error message" feature on a keylogger, in addition to "add to startup" will cause an error message on every startup, which I dont want. How about if I bind it to a program that gives a fake error message (e.g an update file that is corrupted), then add it to startup. Would I still be getting an error on every startup?

[EmmDude99]

I had this problem too. I coded a keylogger in C#, and I coded a .bat file that copy/pasted the program into the startup folder, however i coded the .bat to recompile the keylogger, and get rid of the startup message. This means that the original keylogger (one on the desktop) runs an error message on startup, however the copy/pasted keylogger (one in startup fodler) Silently starts up.
Hope this helped!