Native windows API hooked by ProcessGuard

which Native APIs should be hooked by ProcessGuard?

The reason I'm asking is that I used to test several security software that might fight for the same things, I uninstalled most of them , but i'm afraid the ones I settled on in the end, might have somehow got damaged.

 

Simply because two programs may watch over the same native functions doesn't necessarily imply there'll be problems - hooked functions can themselves be hooked. You seem to be worrying about something that might happen rather than something which is happening.

Damaged how? Any changes made by such security programs are made in memory only, not on disk. In other words, even if two programs don't get on well together in memory, it doesn't exactly cause any "damage" - just an incompatibility preventing both programs from being used at the same time, which more often than not is completely harmless.

Best regards,
Wayne

 

Wayne:

Is it a secret which functions are hooked? (You do not directly answer the question.)

Would you mind if I posted the functions which I believe to be hooked?

 

I doubt it's a secret, it's just that we lowly users don't really need to know the such technical details!

 

I think it makes sense to know which API functions are hooked. For example, this allows you to compare competing products ...

 

This is a help & support forum, it is not a place to discuss the inner workings of software, and unless you're reverse engineering the software such information is of no use to you or anyone else here, and as Peter said, if you're worried about any possible conflicts then feel free to download and use the free trial versions that we have available. Thankyou for your co-operation.