Reply to thread

Message

<blockquote data-quote="Deleted member 65228" data-source="post: 707296">Sorry for interrupting but I wanted to quickly ask, do you know if the NoVirusThanks OSArmor service was active when it wasn&#039;t working? The reason I ask is because maybe it didn&#039;t activate for whatever reason until after reboot. It automatically starts up because of a registry modification for the Services location, so on the reboot you did, Windows would have automatically started up the service for the kernel-mode device driver (and the user-mode service).If it stops working again in the same way as earlier, I recommend grabbing Process Hacker and doing the following steps.1. Open Process Hacker (with Administrator)2. Navigate to the Services tab3. Search for the file-name of the NVT -&gt; if nothing shows up then filter and check the list to see if you can locate NVT OSArmor services (I don&#039;t have it installed to check the name ATM)4. Check if the service/s are actually active or if they have been stoppedIf you cannot find the services at all then that would also be the cause of a problem (services not registered -&gt; deleted or bug in creation).Just food for thought which could help diagnose the issue if it can&#039;t be replicated but happens again in the future <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="Deleted member 65228, post: 707296"] Sorry for interrupting but I wanted to quickly ask, do you know if the NoVirusThanks OSArmor service was active when it wasn't working? The reason I ask is because maybe it didn't activate for whatever reason until after reboot. It automatically starts up because of a registry modification for the Services location, so on the reboot you did, Windows would have automatically started up the service for the kernel-mode device driver (and the user-mode service). If it stops working again in the same way as earlier, I recommend grabbing Process Hacker and doing the following steps. 1. Open Process Hacker (with Administrator) 2. Navigate to the Services tab 3. Search for the file-name of the NVT -> if nothing shows up then filter and check the list to see if you can locate NVT OSArmor services (I don't have it installed to check the name ATM) 4. Check if the service/s are actually active or if they have been stopped If you cannot find the services at all then that would also be the cause of a problem (services not registered -> deleted or bug in creation). Just food for thought which could help diagnose the issue if it can't be replicated but happens again in the future :) [/QUOTE]

Verification