2 instances of Avast UI running

[=Snake=]

1. I have yet to test that theory, which would require installing the latest version and either not installing the behaviour shield or disabling it.

2. So far on 18.5.2342 I don't see the unsecapp.exe in win XP task manager processes and no CPU Spikes.  I think avast really need to follow this up so this relation ship, CPU Spike, unsecapp.exe and behaviour shield so that it doesn't happen in XP on what is meant to be the last avast version supporting XP/Vista.

1: Would be fine to know the result. 
2: I confirm not seeing the unsecapp.exe, but I have no flickering desktop anymore! I won't miss it, I think.
Concerning unsecapp.exe, which belongs to Windows system (do you agree?), I never saw a cpu usage higher than 2% and only for a few seconds.

[DavidR]

<snip quote>
1: Would be fine to know the result. 
2: I confirm not seeing the unsecapp.exe, but I have no flickering desktop anymore! I won't miss it, I think.
Concerning unsecapp.exe, which belongs to Windows system (do you agree?), I never saw a cpu usage higher than 2% and only for a few seconds.

Yes it is part of the WMI and used for many purposes and called by another process and my thoughts now from this and other topic is it is called by the behaviour shield. 

It would appear that there is something new in the behaviour shield (what I don't know) that is having an adverse affect and in my case CPU Spikes in AvastSvc.exe.

[=Snake=]

<snip quote>
1: Would be fine to know the result. 
2: I confirm not seeing the unsecapp.exe, but I have no flickering desktop anymore! I won't miss it, I think.
Concerning unsecapp.exe, which belongs to Windows system (do you agree?), I never saw a cpu usage higher than 2% and only for a few seconds.

Yes it is part of the WMI and used for many purposes and called by another process and my thoughts now from this and other topic is it is called by the behaviour shield. 

It would appear that there is something new in the behaviour shield (what I don't know) that is having an adverse affect and in my case CPU Spikes in AvastSvc.exe.

Please let me know, what you'll find out.
 

[DavidR]

<snip quote>
1: Would be fine to know the result. 
2: I confirm not seeing the unsecapp.exe, but I have no flickering desktop anymore! I won't miss it, I think.
Concerning unsecapp.exe, which belongs to Windows system (do you agree?), I never saw a cpu usage higher than 2% and only for a few seconds.

Yes it is part of the WMI and used for many purposes and called by another process and my thoughts now from this and other topic is it is called by the behaviour shield. 

It would appear that there is something new in the behaviour shield (what I don't know) that is having an adverse affect and in my case CPU Spikes in AvastSvc.exe.

Please let me know, what you'll find out.
 

I can only assume data is going back to avast relating to behaviour shield analysis, etc.

I disabled the options AvastUI > Settings > Privacy - 'Participate in the community' and 'Allow usage data to be shared with 3rd parties analytics' thinking that may stop any potential data transmission by the behaviour shield.

I don't know if I will find out much more than my best guess, given that I have rolled back to 18.5.2342 and I'm in no hurry to experience the problems that caused me to roll back.

[=Snake=]

I can only assume data is going back to avast relating to behaviour shield analysis, etc.

I disabled the options AvastUI > Settings > Privacy - 'Participate in the community' and 'Allow usage data to be shared with 3rd parties analytics' thinking that may stop any potential data transmission by the behaviour shield.

I don't know if I will find out much more than my best guess, given that I have rolled back to 18.5.2342 and I'm in no hurry to experience the problems that caused me to roll back.

I see.
Right now Avast wants to restart my XP system. 

[DavidR]

I can only assume data is going back to avast relating to behaviour shield analysis, etc.

I disabled the options AvastUI > Settings > Privacy - 'Participate in the community' and 'Allow usage data to be shared with 3rd parties analytics' thinking that may stop any potential data transmission by the behaviour shield.

I don't know if I will find out much more than my best guess, given that I have rolled back to 18.5.2342 and I'm in no hurry to experience the problems that caused me to roll back.

I see.
Right now Avast wants to restart my XP system. 

If you don't know why it wants to restart check the About Avast and see if it still shows 18.5.2342 as the current version.  Also check the Notifications area and see if there is anything there that might indicate why a restart is required.

If you haven't already done so switch Program updates to Manual update.

[=Snake=]

I can only assume data is going back to avast relating to behaviour shield analysis, etc.

I disabled the options AvastUI > Settings > Privacy - 'Participate in the community' and 'Allow usage data to be shared with 3rd parties analytics' thinking that may stop any potential data transmission by the behaviour shield.

I don't know if I will find out much more than my best guess, given that I have rolled back to 18.5.2342 and I'm in no hurry to experience the problems that caused me to roll back.

I see.
Right now Avast wants to restart my XP system. 

If you haven't already done so switch Program updates to Manual update.

Too late. I've forgotten it, my fault.
I did another clean install and first of all I changed program update to manual.

[DavidR]

=== snip quotes ===
If you haven't already done so switch Program updates to Manual update.

Too late. I've forgotten it, my fault.
I did another clean install and first of all I changed program update to manual.

Remember, if you are/have done a clean install having changed previous settings to Manual Program Update would revert to the default Auto Program Update once you do the clean install.

[=Snake=]

=== snip quotes ===
If you haven't already done so switch Program updates to Manual update.

Too late. I've forgotten it, my fault.
I did another clean install and first of all I changed program update to manual.

Remember, if you are/have done a clean install having changed previous settings to Manual Program Update would revert to the default Auto Program Update once you do the clean install.

Yeah. Now it's part of my experiences. You learn everyday, your whole life.
 

[bob3160]

=== snip quotes ===
If you haven't already done so switch Program updates to Manual update.

Too late. I've forgotten it, my fault.
I did another clean install and first of all I changed program update to manual.
 

Remember, if you are/have done a clean install having changed previous settings to Manual Program Update would revert to the default Auto Program Update once you do the clean install.

Yeah. Now it's part of my experiences. You learn everyday, your whole life.
 

Always save your settings before doing a clean install and reset settings after the clean install.

[=Snake=]

Always save your settings before doing a clean install and reset settings after the clean install.

What's the best way doing it?

[bob3160]

Always save your settings before doing a clean install and reset settings after the clean install.

What's the best way doing it?

See if this helps you:
https://docs.google.com/document/d/1c1hKu2n1TNEnZ_pt2BjXtHd-0ixb4b00B2T12jHVGrU/edit

[DavidR]

Always save your settings before doing a clean install and reset settings after the clean install.

What's the best way doing it?

Whilst that is the best option in most cases and I would normally save my settings.  However in my case, I didn't want any possible hang over from the three previous updates (when going back) that might have been contributing to my issue.

[=Snake=]

Always save your settings before doing a clean install and reset settings after the clean install.

What's the best way doing it?

1. Whilst that is the best option in most cases and I would normally save my settings.
2.  However in my case, I didn't want any possible hang over from the three previous updates (when going back) that might have been contributing to my issue.

1: Yes, but nobody answered my question. 
2: For I went back like you, I agreed with you and it wasn't contributing for me.
    I only wondered, that I had to set back to 'manual' program update several times! 
    Why isn't it possible to set Avast to 'manual' during installation?

[DavidR]

<snip quotes>
1. Whilst that is the best option in most cases and I would normally save my settings.
2.  However in my case, I didn't want any possible hang over from the three previous updates (when going back) that might have been contributing to my issue.

1: Yes, but nobody answered my question. 
2: For I went back like you, I agreed with you and it wasn't contributing for me.
    I only wondered, that I had to set back to 'manual' program update several times! 
    Why isn't it possible to set Avast to 'manual' during installation?

1.  I thought Bob had answered this in one of his posts.
More direct answer - AvastUI > Settings > General - right down at the bottom of the page, Back up settings - see attached image.

2.  Like many settings Avast are having to look towards many different experienced users.  I don't know how long it might take to implement a program update after an off-line installation (if on-line). 

I was able to open the UI and set it to Manual update without it having detected a program update was available.  When you consider this was also on an XP install ant even with the off-line installation you need to be connected.