Microsoft may be dodging coerced Win10 1803 upgrades on machines running Avast

Topic

New Reply

Although the proclamation doesn’t come from official sources, a mod on the Avast forum says MS has stopped 1803 upgrades on machines running Avast ant
[See the full post at: Microsoft may be dodging coerced Win10 1803 upgrades on machines running Avast]

1 user thanked author for this post.

Elly

Reply | Quote

Replies

I didn’t have Avast and was forced into 1803.  (see my Direct Message)  If I install Avast now will it delete my 1803 and put me back to what I want?

 

Reply | Quote

Installing Avast does NOT delete Win10 1803.

Supposedly you have 10 days to rool back to your previous version of Win10 after 1809 installs. After that, I believe the C:\Windows.old folder is removed.
Settings\Update and Security\Recovery and roll back to your previous version.

Reply | Quote

Could it possibly be that once the 10 day period is up (with Avast already on the system) the Windows.old removal is conflicting with the Avast security?

Suddenly a system folder is removed is call for concern in ANY system which is monitored by security applications

Windows - commercial by definition and now function...

Reply | Quote

I was just about to say thank you, but was giving my daughter the steps to uninstall 1803 when I saw that my computer was already 25% into re-installing 1803!  Anyway, thanks for trying to help.  Guess I’ll just have to live with it.  Grrrrr

Reply | Quote

Post by Moderator MartinZ on Avast Forums

Microsoft temporarily disabled the updates on version 1803 on PCs with Avast. We are working together with MS to find out the cause of this issue, but unfortunately right now neither MS nor us are able to reproduce the issue.

Windows - commercial by definition and now function...

Reply | Quote

Did you see this post about Avast quarantining something in the  $WINDOWS.~BT install folder?

1 user thanked author for this post.

Microfix

Reply | Quote

Just have thanks, cause for concern ouch!

Windows - commercial by definition and now function...

Reply | Quote

I use Avast and have for about 5 years without a problem. My computer did not upgrade from 1709. Whether Avast had anything to do with it or not doesn’t matter, I don’t want it anyway,

Reply | Quote

Right now, new update for 1803 (KB4100403 OS Build 17134.81):

https://support.microsoft.com/pt-pt/help/4100403/windows-10-update-kb4100403

Reply | Quote

Dodging?

It implies that Microsoft is the victim rather than the perpetrator.

 

 

1 user thanked author for this post.

Cybertooth

Reply | Quote

So now Avast is now effectively an antivirus that can block the bad windows update?

Reply | Quote

Steve Gibson’s Never 10 still working, who needs Avast!

Windows - commercial by definition and now function...

Reply | Quote

https://forum.avast.com/index.php?topic=219218.msg1463080#msg1463080

In cooperation with Microsoft we have identified an element of the latest Windows 10 1803 update that is incompatible with the Avast Behavior Shield, causing the aforementioned update to fail in some instances (related to a timing issue, Internet connectivity issue, etc). Luckily, we have found a way to prevent the problem and are now automatically pushing a VPS update to all customers which makes sure that the problem doesn’t happen. The VPS number is 180524-08; all users running this version (or later) should be 100% safe.

For people already screwed, in-place upgrade is the only option to revive their system (see the above post @Avast forums.

1 user thanked author for this post.

columbia2011

Reply | Quote