Avast! file ngiodriver running during definition updates.

It can't be a remnant, because, as I've mentioned a few times in this thread... this is a FRESH install of 11.2.2262
Yes it can unless you removed avast completely before performing the install. And to do that, you will have to remove avast manually. Through control panel + avastclear is not gonna remove everything.
but this time, removing all traces of avast in any folder or registry entry
Did you also removed the files in the Windows folder ? How did you remove the legacy keys ?

Well once I use avastclear to remove avast, I pretty much use Windows search for anything associated with Avast! and delete it. Which I did… and I deleted the keys I could with CCleaner’s registry cleaner function.

Another thing I noticed today after doing a…like 5th fresh install. Whenever the setup.exe runs after I choose only the components I want and it starts to run… multiple instances of Instup.exe run at once and one process lingers for about a minute before disappearing… and the AvastEmUpdate process also runs multiple times… but one process stays behind indefinitely… so I’m going to assume that means that it failed… which is probably why it’s acting like this…

I’m not sure what’s causing the AvastEmUpdate process to fail though… I thought it may have been my Comodo Firewall blocking it’s access but I disabled it during the last fresh install and it still did the same thing.

Avast is not attacked at all on your computer, it is a precaution for someone who try to install avast on already infected computer.

You can’t get old behavior back how many times you try to reinstall, because it is changed for some reason by Avast, not by you or your computer.

So, as Eddy says, stop worrying and accept what it is now. Things are changing.

11.1.2262 still has NG inside. NG is removed since 12.1.2263.

P.S.
You wrongly added “EDIT:” into my post when you quote it, please be careful not to do that.

Avast is not attacked at all on your computer, it is a precaution for someone who try to install avast on already infected computer.

You can’t get old behavior back how many times you try to reinstall, because it is changed for some reason by Avast, not by you or your computer.

So, as Eddy says, stop worrying and accept what it is now. Things are changing.

I’ve checked for viruses/spyware before though, with Avast! itself and Malwarebytes Anti-Malware and it found nada. Is it really necessary for NG to activate on every update made though? Cause that’s what it seems to be doing… and the behaviour of the antivirus shouldn’t change, as long as you are on the same version of the program that worked before… and if it changes for the worst for no apparent reason then it’s just a bad product… no offence.

Mostly… Avast! has been a great product… never had many problems with it… this is one of the very few times I’ve had major issues with it.

11.1.2262 still has NG inside. NG is removed since 12.1.2263.

P.S.
You wrongly added “EDIT:” into my post when you quote it, please be careful not to do that.

Ahhh… but according to Eddy… NG has been around for a while in Avast! but I’ve not seen much activity from it in any previous versions of the program… nor did I see much activity of it in this version of the program when I first installed it from an older 2015 version.

Wonder why it’s decided to be so aggressive now. And it only seems to run it when instup.exe attempts to update the virus definitions automatically or manually.

Also… finally… what about this behaviour? Is this normal? doesn’t seem normal to me, Avast! keeps refering to parts of the product I initially refused to install such as Browser Protections…

As I said before, everything is working as it should.
There is no abnormal behavior anywhere.

It is just your mind playing tricks on you due to your lack of knowledge on how applications (avast) is working.
If you really would understand (a lot) more, start with learning programming.

Actually… my knowledge of computers is fairly good, programming isn’t my strong point, yes. You’re right but I’m not a noob when it comes to technological things… and that isn’t very nice, you know?

Isn’t this forum supposed to be a place where people come for help? Why the hostility? I’m just a bit worried is all, can you not sympathize?

Not trying to be a pain or anything… even though I’m sure I am… but can’t you tell me more about what’s going on? You seem to have better knowledge of this than I do. If this behaviour seems normal to you can you explain to me why it never happened in a previous installation (the first installation of 11.2.2262 from 2015) and how… programming-wise this can happen?

It is almost impossible to instantly detect whether there is any malware on the computer or not, that is why Self defense is always activated just in case there is some.

and the behaviour of the antivirus shouldn't change, as long as you are on the same version of the program that worked before... and if it changes for the worst for no apparent reason then it's just a bad product... no offence.
You mentioned "Emergency Updater" (AvastEmUpdate) thing before, that is exactly doing what you say "bad"; i.e. changing its behavior without changing major version number (internal versions of each file may be changed). And, in most cases, what has been changed is not disclosed. I think most of them are bugfixes, but I don't really know as there is little information about what is changed.
11.1.2262 still has NG inside. NG is removed since 12.1.2263.

P.S.
You wrongly added “EDIT:” into my post when you quote it, please be careful not to do that.

Ahhh… but according to Eddy… NG has been around for a while in Avast! but I’ve not seen much activity from it in any previous versions of the program… nor did I see much activity of it in this version of the program when I first installed it from an older 2015 version.

Wonder why it’s decided to be so aggressive now. And it only seems to run it when instup.exe attempts to update the virus definitions automatically or manually.


Most NG drivers are already there (kept installed when once installed), so you don’t see any “Aggressive” activities (installing driver everytime) as there is no need to do that.
NG is (was) part of the DeepScreen technology and when DS is triggered, NG is also activated (without installing drivers, because they are already there).

So, it is no doubt you did not see any driver-installing activities before.

Also.. finally... what about this behaviour? Is this normal? doesn't seem normal to me, Avast! keeps refering to parts of the product I initially refused to install such as Browser Protections...
The log says "Delayed installation", because you refused to install them. I think it is just a wording problem.
Why the hostility?
There is no hostility in this thread.
I'm just a bit worried is all, can you not sympathize?
As we said several times, stop worrying. I do have a lot of knowledge/experience with computers (both hardware and software) I don't know RejZor and NON personally, but I have no doubt at all that they have too.

Only start worrying if one of us tell you to do so.
If you see one of us worrying, it is time for a serious panic ;D

Although a version number of avast hasn’t changed, it doesn’t mean everything has stayed the same.
Sometimes (rare, but it happens), avast rolls out a (very) small update/change while they keep the version number the same.

NG isn’t activated on every update.
It is always running if you have the option for it enabled.
If you have the option disabled, there are still (at least) parts of it present in case it need to start running.

You mentioned "Emergency Updater" (AvastEmUpdate) thing before, that is exactly doing what you say "bad"; i.e. changing its behavior without changing major version number (internal versions of each file may be changed). And, in most cases, what has been changed is not disclosed. I think most of them are bugfixes, but I don't really know as there is little information about what is changed.

I know that occasionally… AvastEmUpdate can change certain things on the system, as I’ve seen it run before and setup things… but to this degree is a bit weird…

It is almost impossible to instantly detect whether there is any malware on the computer or not, that is why Self defense is always activated just in case there is some.

Well I’ve ran 3-4 different virus/malware scanners… Malwarebytes… Avast… Virustotal’s online scanner and the Windows Malicious Software removal tool, all full-scans and it never found anything… so isn’t that conclusive to say I don’t have any virus?

Most NG drivers are already there (kept installed when once installed), so you don't see any "Aggressive" activities (installing driver everytime) as there is no need to do that. NG is (was) part of the DeepScreen technology and when DS is triggered, NG is also activated (without installing drivers, because they are already there).

So, it is no doubt you did not see any driver-installing activities before.

So why is it doing it now then? I don’t think I’ve ever had NG run before when I had previous versions of the program… and I always had the Deepscreen option ticked. Because it’s supposedly bad to untick it.

I find it suspicious because it installs newly randomly generated services on every manual or automatic update… I see the logs every time Avast! updates the definitions and it always refers to 2 new services being loaded into the system… which are then shortly after removed… I don’t know why it sees the need to do this EVERY TIME. :confused:

The log says "Delayed installation", because you refused to install them. I think it is just a wording problem.

I dunno… it creates this same log every time Avast! tries to update as well. I have Avast! set to run the instup.exe every 120 minutes. (As I always have) and I checked the logs from every 2 hours ago and each one has the same wording and the mention of previously refused installations not made. Can’t say I’ve seen this activity in previous versions of Avast! via the logs either.

There is no hostility in this thread.

Well you were rather rude. I may not know anything about Avast! very much, but I certainly am not stupid when it comes to PC’s and such… but I do tend to have problems with stress levels… I have some problems, yes… And when things I don’t expect happen I usually can’t handle it very well…

As we said several times, stop worrying. I do have a lot of knowledge/experience with computers (both hardware and software) I don't know RejZor and NON personally, but I have no doubt at all that they have too. Only start worrying if one of us tell you to do so. If you see one of us worrying, it is time for a serious panic ;D

I appreciate that, I’m sure you have extensive knowledge with Avast! and programming and such other things but the difference to how Avast! was performing a week ago and now… there is a lot of differences that I can’'t help but notice and worry about… I’m pretty OCD about how my computer runs. And Yes… I’m also sure that Rejzor and NON have very good experience too… NON has been particularly helpful in calming me down a little…

Although a version number of avast hasn't changed, it doesn't mean everything has stayed the same. Sometimes (rare, but it happens), avast rolls out a (very) small update/change while they keep the version number the same.

You mean via AvastEmUpdate? I have seen this run many times before and am fairly aware that it can change settings for Avast! at any time, without your knowledge of it. But I’m not sure if this is the case in this situation. I’ve freshly reinstalled Avast! 4 times now in the past couple of days and whenever I do… it just does the same things as it does now. So I’m not sure if it may be a problem with the initial installation of Avast! because of some corruption or such thing so… meh.

NG isn't activated on every update. It is always running if you have the option for it enabled. If you have the option disabled, there are still (at least) parts of it present in case it need to start running.

Well it is for me… currently. Every time I do a manual check for updates via the AvastUI… the logs always state that 2 randomly generated services coming from the file “ngiodriver_64” were installed into the system, but they shortly disappear. instup.exe creates 2 processes when it checks for updates too so it’s blatantly related to it…

2 processes of instup.exe
2 services created by ngiodriver_64

It always does this when it actually updates too but not when doing a automatic check (with no update available)… which is weird.

What is the setting for it to be enabled? Deepscreen? I’ve always had that enabled, on every version and never saw anything like this.

Anyways, thanks for the replies.

I find it suspicious because it installs newly randomly generated services on every manual or automatic update
No, it doesn't. It is the same service every time. The name of the file is just changing to prevent malware from detecting/blocking/infecting it.

This is true. I mean that the service name changes every time to randomly generated 7 lower-case letters like…

Service Name: pbgnhwjz
Service Name: nldzifwh

But the file name is always C:/Windows/system 32/drivers/ngiodriver_64

This is also strange since I see no file in system 32 called this… ngiodriver_64 is in C:/Program Files/AVAST Software/setup folder.

Is it doing this because a virus/malware is trying to stop Avast! from updating? Or is this just something that it naturally does? Cause I could have swore it never used to do this before… I’ve done virus/malware scans though and found nothing. :confused:

update to beta and get rid of NG :wink:

SIGH

Accept the fact that there is nothing wrong.
Nothing is attacking avast on your system.
Stop running around in circles.

Alright… but can you at least explain why you think nothing is wrong and that everything I mentioned in this thread seems normal to you? If I can fully understand the situation then I won’t post here again.

Please?

We already told you.

You all did, yes. But didn’t really give an explanation as to why this is happening… if this were a common thing… everything one else’s systems would be doing the same as well. And the fact that no-one here has chipped in with this conversation probably means this ngiodriver_64 thing is only happening to me… which is worrying.

Unless someone else can say they also have the same behaviour and that the behaviour is normal.

I know you are probably getting annoyed at me, but you have to understand I have certain problems and unless I can be completely convinced that something isn’t wrong I will continue to worry… I’m sorry… it’s just the way I am. :frowning:

I’m starting to get very worried. I disabled the use of Deepscreen in Avast! and tried to manually update again and this ngiodriver problem still occurs. I thought that Deepscreen is what was possibly causing this since it’s directly related to NG?

I notice as well that the 2 instances of instup.exe that are running… the first initial one is the one that usually runs on any scheduled check for updates… but this .exe shuts down very shortly after it starts and another is started in it’s place. Does this mean that the first installer is crashing?

The reason I’m concerned is because I think this may have more to do with my current installation of Windows 7… it’s been acting very strange the past week or more… svchost processes that ran almost instantly on startup are now taking much longer to start… I assume Avast! relies heavily on particular windows files to update itself… anyone have any idea which files in Win 7 Avast! relies on to update it’s definitions on the system? Does it rely on svchost.exe (netsvcs)?

I noticed a couple more things in the Update Logs so I thought I’d post them here so that a tech-savvy person can look over them to see if everything is normal.

This is the log of the first instup.exe that appears upon a search for an update (whether it be manual or a successful update via automatic)

[2016-06-08 19:47:52] [info ] [instcont ] [ 4252: 4992] 2016/06/08 19:47:52 START: Avast installer/updater
[2016-06-08 19:47:52] [info ] [instup ] [ 4252: 4992] Command: ‘“C:\Program Files\AVAST Software\Avast\setup\instup.exe” /instop:update_vps /session_id:6’

What is this instup.exe /instop:update?

[2016-06-08 19:47:52] [info ] [instup ] [ 4252: 4992] Running module version: instup.exe - ‘11.2.2738.0’
[2016-06-08 19:47:52] [info ] [instup ] [ 4252: 4992] Running module version: Instup.dll - ‘11.2.2738.0’
[2016-06-08 19:47:52] [info ] [simutex ] [ 4252: 4992] Checking for the mutex ownership.
[2016-06-08 19:47:52] [info ] [simutex ] [ 4252: 4992] The mutex is signaled. We are owners of the mutex.
[2016-06-08 19:47:52] [info ] [instup ] [ 4252: 4992] Loading product state
[2016-06-08 19:47:52] [info ] [instup ] [ 4252: 4992] Guid = 07cd9ca6-4558-4625-abb0-c6fb948d546e, Created = 13:11:03 07.06.2016
[2016-06-08 19:47:52] [info ] [instup ] [ 4252: 4992] Persistent Guid = 1f4fcb05-35c0-45a6-bc4f-dee1e07c0a70, Created = 13:11:03 07.06.2016
[2016-06-08 19:47:52] [info ] [instup ] [ 4252: 4992] ProductId = ais
[2016-06-08 19:47:52] [info ] [instup ] [ 4252: 4992] Edition = 1
[2016-06-08 19:47:52] [info ] [instup ] [ 4252: 4992] Installed Part info:
[2016-06-08 19:47:52] [info ] [instup ] [ 4252: 4992] Part ‘iex’ = ‘iex’, 6 (0x00000006), 16:21:04 08.06.2016
[2016-06-08 19:47:52] [info ] [instup ] [ 4252: 4992] Part ‘jrog2’ = ‘jrog2’, 4351 (0x000010FF), 16:21:05 08.06.2016
[2016-06-08 19:47:52] [info ] [instup ] [ 4252: 4992] Part ‘program’ = ‘prg_ais’, 184682710 (0x0B0208D6), 12:22:11 27.04.2016
[2016-06-08 19:47:52] [info ] [instup ] [ 4252: 4992] Part ‘setup’ = ‘setup_ais’, 184682710 (0x0B0208D6), 12:22:12 27.04.2016
[2016-06-08 19:47:52] [info ] [instup ] [ 4252: 4992] Part ‘vps’ = ‘vps_win32’, 369494017 (0x16060801), 16:21:07 08.06.2016
[2016-06-08 19:47:52] [info ] [instup ] [ 4252: 4992] Latest Part info:
[2016-06-08 19:47:52] [info ] [instup ] [ 4252: 4992] Part ‘iex’ = ‘iex’, 6 (0x00000006), 16:21:04 08.06.2016
[2016-06-08 19:47:52] [info ] [instup ] [ 4252: 4992] Part ‘jrog2’ = ‘jrog2’, 4351 (0x000010FF), 16:21:05 08.06.2016
[2016-06-08 19:47:52] [info ] [instup ] [ 4252: 4992] Part ‘program’ = ‘prg_ais’, 184682710 (0x0B0208D6), 12:22:11 27.04.2016
[2016-06-08 19:47:52] [info ] [instup ] [ 4252: 4992] Part ‘setup’ = ‘setup_ais’, 184682710 (0x0B0208D6), 12:22:12 27.04.2016
[2016-06-08 19:47:52] [info ] [instup ] [ 4252: 4992] Part ‘vps’ = ‘vps_win32’, 369494017 (0x16060801), 16:21:07 08.06.2016
[2016-06-08 19:47:52] [info ] [partinfo ] [ 4252: 4992] SetInstalled: Part package part-iex-6.vpx is installed.
[2016-06-08 19:47:52] [info ] [partinfo ] [ 4252: 4992] SetInstalled: Part package part-jrog2-10ff.vpx is installed.
[2016-06-08 19:47:52] [info ] [partinfo ] [ 4252: 4992] SetInstalled: Part package part-prg_ais-b0208d6.vpx is installed.
[2016-06-08 19:47:52] [info ] [partinfo ] [ 4252: 4992] SetInstalled: Part package part-setup_ais-b0208d6.vpx is installed.
[2016-06-08 19:47:52] [info ] [partinfo ] [ 4252: 4992] SetInstalled: Part package part-vps_win32-16060801.vpx is installed.
[2016-06-08 19:47:52] [info ] [instupcore ] [ 4252: 4992] PkgLoadProductInfo: product GPB was successfully loaded.
[2016-06-08 19:47:52] [info ] [instupcore ] [ 4252: 4992] Product update has started.
[2016-06-08 19:47:52] [info ] [servers ] [ 4252: 4992] Server definition(s) loaded for ‘C:\Program Files\AVAST Software\Avast\setup\servers.def’: 29 (maintenance:0)
[2016-06-08 19:47:52] [info ] [servers ] [ 4252: 4992] ChooseServer: selected server ‘Download b9871595 AVAST9 Server’ with current url ‘http://b9871595.iavs9x.u.avast.com/iavs9x’ of type ‘URL_TYPE_DOWNLOAD_PROGRAM’.
[2016-06-08 19:47:52] [info ] [dldwrap ] [ 4252: 4992] HttpGet: ‘servers.def.vpx’ was successfully downloaded (ip: 104.86.110.121, size: 2576 bytes).
[2016-06-08 19:47:52] [info ] [dldwrap ] [ 4252: 4992] HttpGet: ‘servers.def.vpx’ was successfully verified.
[2016-06-08 19:47:52] [info ] [servers ] [ 4252: 4992] ChooseServer: selected server ‘Download l5010949 AVAST9 Server’ with current url ‘http://l5010949.iavs9x.u.avast.com/iavs9x’ of type ‘URL_TYPE_DOWNLOAD_PROGRAM’.
[2016-06-08 19:47:52] [info ] [dldwrap ] [ 4252: 4992] HttpGet: ‘prod-pgm.vpx’ was successfully downloaded (ip: 104.86.110.121, size: 445 bytes).
[2016-06-08 19:47:52] [info ] [dldwrap ] [ 4252: 4992] HttpGet: ‘prod-pgm.vpx’ was successfully verified.
[2016-06-08 19:47:52] [info ] [pkgproduct ] [ 4252: 4992] LoadPartInfo: program = prg_ais-b0208d6 returned 0x00000000
[2016-06-08 19:47:52] [info ] [pkgproduct ] [ 4252: 4992] LoadPartInfo: setup = setup_ais-b0208d6 returned 0x00000000
[2016-06-08 19:47:52] [info ] [pkgproduct ] [ 4252: 4992] LoadUatInfo: uat.vpx returned 0x00000000
[2016-06-08 19:47:52] [info ] [pkgengine ] [ 4252: 4992] LoadLatestProdAndParts: product file ‘prod-pgm.vpx’ was successfully loaded.
[2016-06-08 19:47:52] [info ] [pkguat ] [ 4252: 4992] UpdateLatestPartInfo: called, repo_id: ‘iavs9x’, part_id: program, installed_ver: b0208d6, latest_ver: b0208d6
[2016-06-08 19:47:52] [info ] [pkguat ] [ 4252: 4992] UpdateLatestPartInfo: called, repo_id: ‘iavs9x’, part_id: setup, installed_ver: b0208d6, latest_ver: b0208d6
[2016-06-08 19:47:52] [info ] [servers ] [ 4252: 4992] ChooseServer: selected server ‘Download g4628919 AVAST9 Server’ with current url ‘http://g4628919.ivps9x.u.avast.com/ivps9x’ of type ‘URL_TYPE_DOWNLOAD_VPS’.
[2016-06-08 19:47:52] [info ] [dldwrap ] [ 4252: 4992] HttpGet: ‘prod-vps.vpx’ was successfully downloaded (ip: 104.86.110.121, size: 456 bytes).
[2016-06-08 19:47:52] [info ] [dldwrap ] [ 4252: 4992] HttpGet: ‘prod-vps.vpx’ was successfully verified.
[2016-06-08 19:47:52] [info ] [pkgproduct ] [ 4252: 4992] LoadPartInfo: iex = iex-6 returned 0x00000000
[2016-06-08 19:47:52] [info ] [pkgproduct ] [ 4252: 4992] LoadPartInfo: jrog2 = jrog2-10ff returned 0x00000000
[2016-06-08 19:47:52] [info ] [pkgproduct ] [ 4252: 4992] LoadPartInfo: vps = vps_win32-16060801 returned 0x00000000
[2016-06-08 19:47:52] [info ] [pkgengine ] [ 4252: 4992] LoadLatestProdAndParts: product file ‘prod-vps.vpx’ was successfully loaded.
[2016-06-08 19:47:52] [info ] [pkgengine ] [ 4252: 4992] LoadLatestProdAndParts: part file part-iex-6.vpx was successfully loaded.
[2016-06-08 19:47:52] [info ] [pkgengine ] [ 4252: 4992] LoadLatestProdAndParts: part file part-jrog2-10ff.vpx was successfully loaded.
[2016-06-08 19:47:52] [info ] [pkgengine ] [ 4252: 4992] LoadLatestProdAndParts: part file part-vps_win32-16060801.vpx was successfully loaded.
[2016-06-08 19:47:52] [notice ] [instupcore ] [ 4252: 4992] There isn’t newer VPS version.
[2016-06-08 19:47:52] [info ] [submit ] [ 4252: 4992] Nothing to be sent.
[2016-06-08 19:47:52] [info ] [stats ] [ 4252: 4992] Downloaded files: 3 (3.40 KB)
[2016-06-08 19:47:52] [info ] [stats ] [ 4252: 4992] Download time: 1 s
[2016-06-08 19:47:53] [info ] [servers ] [ 4252: 4992] Server definition(s) loaded for ‘C:\Program Files\AVAST Software\Avast\setup\servers.def’: 29 (maintenance:0)
[2016-06-08 19:47:53] [info ] [servers ] [ 4252: 4992] ChooseServer: selected server ‘Download y7549610 AVAST9 Server’ with current url ‘http://v7.stats.avast.com/cgi-bin/iavs4stats.cgi’ of type ‘URL_TYPE_STATS2’.
[2016-06-08 19:47:53] [info ] [instup ] [ 4252: 4992] Saving product state.
[2016-06-08 19:47:53] [info ] [instup ] [ 4252: 4992] Persistent Guid = 1f4fcb05-35c0-45a6-bc4f-dee1e07c0a70, Created = 13:11:03 07.06.2016
[2016-06-08 19:47:53] [info ] [simutex ] [ 4252: 4992] Checking for the mutex ownership.
[2016-06-08 19:47:53] [info ] [simutex ] [ 4252: 4992] The mutex is signaled. We are owners of the mutex.
[2016-06-08 19:47:53] [info ] [dldwrap ] [ 4252: 4720] HttpPost: ok with http status: 204
[2016-06-08 19:47:53] [info ] [stats ] [ 4252: 4720] Statistics sent successfully.
[2016-06-08 19:47:53] [info ] [instcont ] [ 4252: 4992] 2016/06/08 19:47:53 END: Avast installer/updater, return code 40965 (0x0000A005) [No update available]

I’ve looked at this log in detail and from what I can see of it, there doesn’t appear to be any crash or interference of it searching for an update. As it ended with a valid return code… plus if it had crashed wouldn’t it have said so here?

Straight after the original instup.exe terminates another starts in it’s place and the next log begins there:

[2016-06-08 19:47:53] [info ] [instcont ] [ 4252: 4992] –
[2016-06-08 19:47:53] [info ] [instcont ] [ 4536: 3036] –
[2016-06-08 19:47:53] [info ] [instcont ] [ 4536: 3036] 2016/06/08 19:47:53 START: Avast installer/updater
[2016-06-08 19:47:53] [info ] [instup ] [ 4536: 3036] Command: ‘“C:\Program Files\AVAST Software\Avast\setup\instup.exe” /instop:change’

WHAT DOES THIS MEAN? IT HAS A COMPLETELY DIFFERENT VALUE THAN THE FIRST .EXE TO RUN… /INSTOP:CHANGE???

This part of the log is where things start to get a bit weird for me, it starts referring to NG and according to this log… NG isn’t even active because its stating it with a value of 0… which I assume means it is not active… so why is it running?

[2016-06-08 19:47:53] [info ] [instupcore ] [ 4536: 3036] PkgLoadProductInfo: product GPB was successfully loaded.
[2016-06-08 19:47:53] [info ] [instupcore ] [ 4536: 3036] Product pre-change has started.
[2016-06-08 19:47:53] [info ] [productcond ] [ 4536: 3036] IsNgSupported: IsAswVmmVirtualizationActive returned 0 (0x00000000) [The operation completed successfully.] and false
[2016-06-08 19:47:53] [info ] [system ] [ 4536: 3036] ServiceInstall: Service kgpkfhej successfully installed.
[2016-06-08 19:47:53] [info ] [system ] [ 4536: 3036] ServiceStart: Starting the service ‘kgpkfhej’.
[2016-06-08 19:47:53] [info ] [system ] [ 4536: 3036] ServiceStart: The service ‘kgpkfhej’ started successfully.
[2016-06-08 19:47:53] [info ] [productcond ] [ 4536: 3036] IsNgSupported: CPU type Intel
[2016-06-08 19:47:53] [info ] [productcond ] [ 4536: 3036] IsNgSupported: virtualization technology is probably disabled in BIOS
[2016-06-08 19:47:53] [info ] [system ] [ 4536: 3036] ServiceStop: The service ‘kgpkfhej’ stopped successfully.
[2016-06-08 19:47:53] [info ] [system ] [ 4536: 3036] ServiceUninstall: Attempting to uninstall the service ‘kgpkfhej’.
[2016-06-08 19:47:53] [info ] [system ] [ 4536: 3036] ServiceUninstall: The service ‘kgpkfhej’ successfully uninstalled.
[2016-06-08 19:47:53] [info ] [productcond ] [ 4536: 3036] IsNgSupported: IsAswVmmVirtualizationActive returned 0 (0x00000000) [The operation completed successfully.] and false
[2016-06-08 19:47:54] [info ] [system ] [ 4536: 3036] ServiceInstall: Service agaeoqmu successfully installed.
[2016-06-08 19:47:54] [info ] [system ] [ 4536: 3036] ServiceStart: Starting the service ‘agaeoqmu’.
[2016-06-08 19:47:54] [info ] [system ] [ 4536: 3036] ServiceStart: The service ‘agaeoqmu’ started successfully.
[2016-06-08 19:47:54] [info ] [productcond ] [ 4536: 3036] IsNgSupported: CPU type Intel
[2016-06-08 19:47:54] [info ] [productcond ] [ 4536: 3036] IsNgSupported: virtualization technology is probably disabled in BIOS
[2016-06-08 19:47:54] [info ] [system ] [ 4536: 3036] ServiceStop: The service ‘agaeoqmu’ stopped successfully.
[2016-06-08 19:47:54] [info ] [system ] [ 4536: 3036] ServiceUninstall: Attempting to uninstall the service ‘agaeoqmu’.
[2016-06-08 19:47:54] [info ] [system ] [ 4536: 3036] ServiceUninstall: The service ‘agaeoqmu’ successfully uninstalled.

Also… what is this part below? It’s also referring to products I refused to install upon the installation of the antivirus… I refused all but the basic shield protection.

[2016-06-08 19:47:54] [info ] [instup ] [ 4536: 3036] The group ‘ais_cmp_ara’ has been added to the auto-deployment blacklist
[2016-06-08 19:47:54] [info ] [instup ] [ 4536: 3036] The group ‘ais_cmp_bpc’ has been added to the auto-deployment blacklist
[2016-06-08 19:47:54] [info ] [instup ] [ 4536: 3036] The group ‘ais_cmp_gadget’ has been added to the auto-deployment blacklist
[2016-06-08 19:47:54] [info ] [instup ] [ 4536: 3036] The group ‘ais_cmp_grimefighter’ has been added to the auto-deployment blacklist
[2016-06-08 19:47:54] [info ] [instup ] [ 4536: 3036] The group ‘ais_cmp_hds’ has been added to the auto-deployment blacklist
[2016-06-08 19:47:54] [info ] [instup ] [ 4536: 3036] The group ‘ais_cmp_pwdman’ has been added to the auto-deployment blacklist
[2016-06-08 19:47:54] [info ] [instup ] [ 4536: 3036] The group ‘ais_cmp_pwdman_chrome’ has been added to the auto-deployment blacklist
[2016-06-08 19:47:54] [info ] [instup ] [ 4536: 3036] The group ‘ais_cmp_pwdman_ff’ has been added to the auto-deployment blacklist
[2016-06-08 19:47:54] [info ] [instup ] [ 4536: 3036] The group ‘ais_cmp_pwdman_ie’ has been added to the auto-deployment blacklist
[2016-06-08 19:47:54] [info ] [instup ] [ 4536: 3036] The group ‘ais_cmp_pwdman_ie_x64’ has been added to the auto-deployment blacklist
[2016-06-08 19:47:54] [info ] [instup ] [ 4536: 3036] The group ‘ais_cmp_rescuedisk’ has been added to the auto-deployment blacklist
[2016-06-08 19:47:54] [info ] [instup ] [ 4536: 3036] The group ‘ais_cmp_secdns_hlp’ has been added to the auto-deployment blacklist
[2016-06-08 19:47:54] [info ] [instup ] [ 4536: 3036] The group ‘ais_cmp_secureline’ has been added to the auto-deployment blacklist
[2016-06-08 19:47:54] [info ] [instup ] [ 4536: 3036] The group ‘ais_cmp_secureline_x64’ has been added to the auto-deployment blacklist
[2016-06-08 19:47:54] [info ] [instup ] [ 4536: 3036] The group ‘ais_cmp_sfzone’ has been added to the auto-deployment blacklist
[2016-06-08 19:47:54] [info ] [instup ] [ 4536: 3036] The group ‘ais_cmp_sfzone_x64’ has been added to the auto-deployment blacklist
[2016-06-08 19:47:54] [info ] [instup ] [ 4536: 3036] The group ‘ais_cmp_swhealth’ has been added to the auto-deployment blacklist
[2016-06-08 19:47:54] [info ] [instup ] [ 4536: 3036] The group ‘ais_cmp_webrep’ has been added to the auto-deployment blacklist
[2016-06-08 19:47:54] [info ] [instup ] [ 4536: 3036] The group ‘ais_cmp_webrep_chrome’ has been added to the auto-deployment blacklist
[2016-06-08 19:47:54] [info ] [instup ] [ 4536: 3036] The group ‘ais_cmp_webrep_ff’ has been added to the auto-deployment blacklist
[2016-06-08 19:47:54] [info ] [instup ] [ 4536: 3036] The group ‘ais_cmp_webrep_ie’ has been added to the auto-deployment blacklist
[2016-06-08 19:47:54] [info ] [instup ] [ 4536: 3036] The group ‘ais_cmp_webrep_x64’ has been added to the auto-deployment blacklist
[2016-06-08 19:47:54] [info ] [instup ] [ 4536: 3036] The group ‘ais_dll_egb_bpc’ has been added to the auto-deployment blacklist

[2016-06-08 19:47:56] [info ] [simutex ] [ 4536: 3036] Checking for the mutex ownership.
[2016-06-08 19:47:56] [info ] [simutex ] [ 4536: 3036] The mutex is signaled. We are owners of the mutex.
[2016-06-08 19:47:56] [info ] [instcont ] [ 4536: 3036] 2016/06/08 19:47:56 END: Avast installer/updater, return code 0 (0x00000000) [The operation completed successfully.]
[2016-06-08 19:47:56] [info ] [instcont ] [ 4536: 3036] –

Sorry for the huge logs… but I just want this sorted for good so I don’t have to post here and be annoying anymore. :slight_smile: Can someone look these over?

If you don’t do it already, go see a therapist.
We can only help you with computer (related) problems.
We (and others) can tell you hundreds of times the same thing, but if you can’t handle it there is nothing we can do for you.

I wish you all the best and hope you get it sorted out.

Wow, how rude… seriously…

It took me ages to get that log together and edit it so that people can see the main parts I’m concerned about and no-ones even gonna have a look at it?

Once someone tells me that log looks normal (including the parts I highlighted) then I won’t post any more. That’s all I’m asking for… my personal problems should have nothing to do with it. ???