To date, with the OP’s issues, I have only really focused on his violations of the forums policy as a Moderator. However, given what he has posted (insults aside) I felt that I should post something on what the OP has actually posted on technical issues.
The OP has asserted the following…
- CIS’s installation of COMODO Internet Security Helper Service as an interactive service is a “big mistake” and that Windows [Microsoft] “stopped allowing services to interact with the desktop long ago after discovering the negative affect that configuration had on PC Security”.
This is an incorrect assertion. Microsoft did not stop interactive services, they discouraged them under both Vista and Windows 7 (source: microsoft.com).
The OP’s assertion that security was issue is indeed correct, this was due the elevated privileges such services have and that malware had began to target such services. However, this was a perceived risk for normal applications, not for security software that is hardened and protected against such risks, such as CIS.
- CIS “violates the Windows AppInit_DLL mechanics by producing the same Wininit error 11”.
This assertion is posted in support of the OP’s first assertion. However, it is incorrect to bundle the service COMODO Internet Security Helper Service (CMDAGENT.EXE) and the AppInit load of GUARDnn.DLL (GUARD32.DLL & GUARD64.DLL) together since they are not directly related in the context the OP raises them.
AppInit DLLs are loaded by USER32.DLL (I’m uncertain of USER64.DLL, but I believe it’s the same) using DLL_PROCESS_ATTACH. This way CIS’s GUARDnn.DLL is loaded into every process as a protective measure for the process.
Since the AppInit method of loading DLL’s also have potential security concerns a warning event (Event 11) is raised a system boot. The Event 11 text reads…
Custom dynamic link libraries are being loaded for every application. The system administrator should review the list of libraries to ensure they are related to trusted applications.
.. and Microsoft also discourage their use. But, there is no violation of "[i]Windows AppInit_DLL mechanics[/i]", this is a false assertion on the OP's part. And since CIS is protected and hardened, there is no known security concerns with such an approach either.
- “Someone needs to do something about this issue because even though error 11 is a warning, it does affect performance.”
I have no doubt that loading a DLL into every process will inevitably impact performance to some degree or another. However, it is important to note the the OP does not attempt to quantify or measure that perceived negative performance impact, but merely uses it to support other, previously stated, assertions which are in doubt.
Unlike the OP, I would prefer not to cast doubt on the OP’s personal experience or knowledge (to put it politely), since it is merely a distraction of the issue (take note OP). So, I will not. But neither do I feel inclined to directly engage with someone who does. :-\
I did not look at the OP’s issues relating to GPT on SSD and CIS, since I have no personal experience of SSD’s and have no way of testing it either.