Reply to thread

Message

<blockquote data-quote="Andy Ful" data-source="post: 700783" data-attributes="member: 32260">After reading your comments, I retested ReHIPS and could not replicate this strange behavior. So, I am sure that it was rather my testing mistake. EagleGet starts also another executable EGMonitor.exe. I think, that I allowed EagleGet and did not allow EGMonitor.exe. So in fact, EagleGet was started showing the program window, and ReHIPS blocked&nbsp; EGMonitor.exe . Sorry for a stupid mistake.<img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite118" alt=":oops:" title="Oops!&nbsp; &nbsp; :oops:" loading="lazy" data-shortname=":oops:" />The second testing supports your posts about suspending processes by OSArmor and ReHIPS.<img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite109" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" /></blockquote>

[QUOTE="Andy Ful, post: 700783, member: 32260"] After reading your comments, I retested ReHIPS and could not replicate this strange behavior. So, I am sure that it was rather my testing mistake. EagleGet starts also another executable EGMonitor.exe. I think, that I allowed EagleGet and did not allow EGMonitor.exe. So in fact, EagleGet was started showing the program window, and ReHIPS blocked EGMonitor.exe . Sorry for a stupid mistake.:oops: The second testing supports your posts about suspending processes by OSArmor and ReHIPS.:) [/QUOTE]

Verification