What happened in the micro update from 17.2.2280 build 3419.64 to build 3419.69.

[DavidR]

The topic title pretty much says it all, micro updates don't get any mention in any release note or history.

I haven't got a clue what was in the micro update to 3419.69, but today MY XP system had been locking up solid. Unfortunately I couldn't even enforce a manual crash (to gather data) as no keys were working even the power off key on my keyboard.

I tried lots of things, disabling the enable hardware-assisted virtualization, uninstalling the Behaviour Shield and uninstalled MBAM. Finally I restored my backup image from Saturday and also disabled and removed the elements just mentioned.

I have just got VPS 170320-1 but since I haven't had a BSOD or that my effected system is XP Pro, I don't hold out much hope this would resolve anything and my concern is of a micro update to build 3419.69 (which we as users have no control to stop).

[mchain]

I've got micro-update .3419.64 running on Win 10 Anniversary 64-bit so not yet up to where you are currently. 

I also missed the ruckus caused by vps definition 170320-0 because I was not online at the time.  That corrupted definition update apparently only afflicted  Win 7 32-bit systems and I'm not seeing XP systems involved so far.

Seeing issues with this system - NOT. 

I did have issues on the 18th running into the 19th with lockups like yours where it locked up three different times and had to quit each time using the power button hold down feature.  Otherwise system was totally frozen.  Issues caused by heat.

Cleaning and removing the CPU heat sink and applying paste did the trick. 

[DavidR]

Well I still have build 17.2.3419.64 after restoring a drive image and the VPS update 170320-1 (now have VPS update 170322-1). I have now ventured back to installing the Behaviour Shield and enabling the hardware-assisted virtualization option and up until 1am this morning the XP system was stable.

I'm leaning towards this being related to the issue with 170320-0 on win7 32bit versions as the VPS update to 170320-1 would appear to have resolved that (

These sloppy VPS/streaming updates are undermining any prior good work.

The ruckus as you say, was with VPS 170320-0 on win7 32bit versions. I also missed it on my win7 32bit system as that too was off-line when all of this was going on. No adverse impact on my win10 64bit OS laptop I on at the moment.

[mchain]

Well, what happened to you demonstrates real needs to always have a current verified disk image just in case.     Not only do you save a lot of time, you don't lose all your files either.

I'm in agreement that some sort of release notes or history should be provided at each update.

[bob3160]

Well, what happened to you demonstrates real needs to always have a current verified disk image just in case.     Not only do you save a lot of time, you don't lose all your files either.

I'm in agreement that some sort of release notes or history should be provided at each update.

What I read into this is that you need to be as leery of your Antivirus as a virus.
Certainly not what any Antivirus program wants to be compared to. 

[DavidR]

Well, what happened to you demonstrates real needs to always have a current verified disk image just in case.     Not only do you save a lot of time, you don't lose all your files either.

I'm in agreement that some sort of release notes or history should be provided at each update.

I have been running disk imaging software even longer than the 13 years of running avast and it has saved my bacon on many occasions. But I use it for what some would consider trivial things, if whatever the problem is if it is likely to take longer than restoring the image, then I restore my last weekly image. In this case the last disk image was only 1¹/₂ days before.

However, in this case I did a lot of hunting and trying to gather information for avast in the hope it might help others, hours and not minutes as the restore image took.

It almost took longer to boot into the CDs recovery environment once in I just restored the C drive and that took just under 5 minutes.

I think comprehensive update notes are the way to go (not highlights), whilst most people won't look at them, many will.

[mchain]

Well, what happened to you demonstrates real needs to always have a current verified disk image just in case.     Not only do you save a lot of time, you don't lose all your files either.

I'm in agreement that some sort of release notes or history should be provided at each update.

I have been running disk imaging software even longer than the 13 years of running avast and it has saved my bacon on many occasions. But I use it for what some would consider trivial things, if whatever the problem is if it is likely to take longer than restoring the image, then I restore my last weekly image. In this case the last disk image was only 1¹/₂ days before.

However, in this case I did a lot of hunting and trying to gather information for avast in the hope it might help others, hours and not minutes as the restore image took.

It almost took longer to boot into the CDs recovery environment once in I just restored the C drive and that took just under 5 minutes.

I think comprehensive update notes are the way to go (not highlights), whilst most people won't look at them, many will.

Agreed.