Reply to thread

Message

<blockquote data-quote="davisd" data-source="post: 821923" data-attributes="member: 77647"><p>Unfortunately cannot replicate, Edge Dev and Chrome starting fine with 0 HIPS log entry warnings on 1903 + standard account + no extensions/default browser settings with &quot;Deny child processes from script executables&quot; rule created. My only guess now would be that OSA or Configure_Defender didn&#039;t revert to system defaults, or some extension is at fault you&#039;re using, but highly unlikely. Maybe post here some of the log events from HIPS when you tried to open Chrome/Edge Dev, as without those, it&#039;s hard to understand what you mean by &quot;HIPS going off like crazy&quot;, there should have been a precise prompt what exactly was going on at that given time, I&#039;m just interested as I haven&#039;t seen this particular Eset rule creating browser launching problems. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite120" alt="o_O" title="Er... what?&nbsp; &nbsp; o_O" loading="lazy" data-shortname="o_O" /></p></blockquote><p></p>

[QUOTE="davisd, post: 821923, member: 77647"] Unfortunately cannot replicate, Edge Dev and Chrome starting fine with 0 HIPS log entry warnings on 1903 + standard account + no extensions/default browser settings with "Deny child processes from script executables" rule created. My only guess now would be that OSA or Configure_Defender didn't revert to system defaults, or some extension is at fault you're using, but highly unlikely. Maybe post here some of the log events from HIPS when you tried to open Chrome/Edge Dev, as without those, it's hard to understand what you mean by "HIPS going off like crazy", there should have been a precise prompt what exactly was going on at that given time, I'm just interested as I haven't seen this particular Eset rule creating browser launching problems. o_O [/QUOTE]

Verification