As I originally suggested, manually disabling/killing things in Windows often has negative downstream effects
I think I mentioned in some previous comment that I also think so now , I just couldn't get why it works on some devices and not on others. That always made me think that there has to be more than just the fact that I disable it, since disabling it seems to had no effect on some devices when re-installing (but did before, leading to the re-install).
I doubt seriously it was corrupting files but I have no doubt what you were doing was causing an issue.
It is corrupting files. It did about five years ago when first using W10 (or at least deleted them) and does it now. As soon as it looks onto the installers, it trys to "clean" them, resulting in a corrupted .exe I can't use anymore. But when I then disabled it and downloaded the one program again, or used the .exe of the same version of the second program I had in another folder, they run without any issues.
And as said, I am not even talking about weird scripts or the tool to disable Defender, as that defenetly can be considered a virus when used by an attacker. I am talking about the official Nvidia Experience for example. That's why I consider Defender a virus: It is nearly impossible to get rid of, comes bult in into Windows and deletes many false positives, so you can't use your programs anymore.
And yes, ClickMonitorDCC is supposed to be in startup. But Defender always claims that the programs would infect other files or crap like this.
and you attempt to do just that and their response is "well not like that". That it is beyond frustrating because it always ends up in a long drawn out situation where eventually they end up listening and you solve their issue but only after hours of time
I know exactly what you mean. As I said, I didn't say that I don't believe you guys when you said that I shouldn't tinker with system files. I just couldn't get why it then runs on other systems and on some it works not. That was the thing I wanted to figure out, and when I want to figure something out, I am always stubborn until I found it. So I continued to search, not because I don't believe you. I just didn't think that's all. Now I know that either Defender corrupted the files or it was because I disabled Defender when it was still working on the files. Since it then couldn't finish and got force-killed by the script, the files got corrupted (again, this is proved as the same exe downloaded again without Defender works fine and the other one in the other folder as well). And that was the thing I was looking for. I still don't know why it then worked on other devices, but that doesn't matter as long as I now stay rid of this pesky error code. And there is no way to know for sure what happend on the other devices, as too much time has passed. So I am not going to continue saying it works on the other devices, maybe I will figure it out at some time, maybe not.
I am not at all trying to be ugly, I am not trying to insult your intelligence or question what you know. I am just trying to help you understand how you got here and why it's taking so long to solve. If you feel I am being an a-hole, I get it, but that's not my motive. Just trying to help you is all.
Don't worry, I don't consider
you an a-hole at all. You always tried to explain everything you said in normal words instead of starting to throw angry comments after some time without even knowing what I did and how I came to my conclusions.
I will update this thread once I know more about AppInit, if it also exists on the other devices and if my theory how it gets created is true or not. But 0xc0000005 can be considered solved for know. I will also update this thread when I wiped my laptop to let you know if the code appeared there as well or not.