VERSION: 2016.11.2.2261

[bob3160]

I suggest that you start your own topic and explain your problem.
It will probably be better for you and those that help in the Russian section of the forum:
https://forum.avast.com/index.php?board=28.0

[REDACTED]

I suggest that you start your own topic and explain your problem.
It will probably be better for you and those that help in the Russian section of the forum:
https://forum.avast.com/index.php?board=28.0

ок

[RejZoR]

To me it seems avast! team has to scrap entire current thing and start from scratch. This thing is way too broken and problematic on so many ends they don't even know how to fix it properly. Just scrap it and start from clean. Every program AV that did this so far showed great results. It seems avast! needs the same.

[bob3160]

I have 2 laptops one cant seem to reach the server to get to my Avast account

The other computer, 64 bit Dell has no problems
Refresh didn't help. Reboot didn't help
A Repair seems to have taken care of the problem.

[Staticguy]

I have 2 laptops one cant seem to reach the server to get to my Avast account

The other computer, 64 bit Dell has no problems
Refresh didn't help. Reboot didn't help
A Repair seems to have taken care of the problem.

I had that problem as well. First thought, it might the avast server having the issue(s). I tried couple of times at different times, same result. Repair did the fix.

[SimmonsTheMad33]

Startup seems a bit faster, about 2-3 Seconds shaved off the boot after POST. Quite a bit when you consider my PC boots in about 12 seconds. Other than that, no problems.

[REDACTED]

I updated two Windows 10 machines today to 2261 (one 32-bit and one 64-bit).  On both machines, the IE browser extension was unregistered after the update.  The file aswWebRepIE.dll still exists, but the corresponding registry entries are no longer present.  Is this a bug or a deliberate decision by Avast to remove this feature.  If so, why?

Thanks

Gary

[DavidR]

I updated two Windows 10 machines today to 2261 (one 32-bit and one 64-bit).  On both machines, the IE browser extension was unregistered after the update.  The file aswWebRepIE.dll still exists, but the corresponding registry entries are no longer present.  Is this a bug or a deliberate decision by Avast to remove this feature.  If so, why?

Thanks

Gary

Firstly, I don't use windows 10. But I found out something in the forums today relating to the AOS add-on/extension with windows 10. IE will only allow it if it gets it from the App Store, that is why it isn't being installed.

See https://forum.avast.com/index.php?topic=185597.0.

[bob3160]

The latest version of IE only allow add-ons through the Windows Store.
That will also hold true for extension added to Microsoft Edge.

[REDACTED]

Well, it was working just fine with IE this morning with the previous production build of Avast - so I find that hard to believe.

I understand Edge may be a different matter, but I'll worry about that if/when Microsoft finish it!

[bob3160]

I've reported this to Avast. Let's see if they have something to add.

[REDACTED]

I can now see from the update log that build 11.1.2253 logged registration of the IE add-on by calling regsvr32.exe to register these 32-bit dlls (and where appropriate, the 64-bit equivalents):

• AswWebRepIE.dll
• AswWrcIEBroker32.dll

The log for 11.2.2261 shows the same calls to regsvr32.exe, but adds the /U switch, ie de-registers the dlls.

I have now got the add-in back and working using the following simple scripts:

REM Use this script on 64-bit Windows
c:\windows\syswow64\RegSvr32.exe  "C:\Program Files\AVAST Software\Avast\aswWebRepIE.dll"
c:\windows\syswow64\RegSvr32.exe  "C:\Program Files\AVAST Software\Avast\aswWrcIEBroker32.dll"
RegSvr32.exe  "C:\Program Files\AVAST Software\Avast\aswWebRepIE64.dll"
RegSvr32.exe  "C:\Program Files\AVAST Software\Avast\aswWrcIEBroker64.dll"

REM Use this script on 32-bit Windows
RegSvr32.exe  "C:\Program Files\AVAST Software\Avast\aswWebRepIE.dll"
RegSvr32.exe  "C:\Program Files\AVAST Software\Avast\aswWrcIEBroker32.dll"

Gary

[REDACTED]

Since (auto)updating, I'm no longer able to create a rescue disk (USB) 
"Failed to create the rescue disk"
This happens if I try to overwrite the rescue usb created with previous version, or a new blank usb - both are Kingston DataTraveller 8GB.
Previous version (not updated) on other computer will still create rescue disk to both these usb, so confident that this is an Avast! problem, not usb problem.
Any suggestions?
Thanks

[bob3160]

Since (auto)updating, I'm no longer able to create a rescue disk (USB) 
"Failed to create the rescue disk"
This happens if I try to overwrite the rescue usb created with previous version, or a new blank usb - both are Kingston DataTraveller 8GB.
Previous version (not updated) on other computer will still create rescue disk to both these usb, so confident that this is an Avast! problem, not usb problem.
Any suggestions?
Thanks

It's a known problem and has already been reported to Avast.
Hopefully it will be fixed by the next update. 

[lukas.hasik]

Since (auto)updating, I'm no longer able to create a rescue disk (USB) 
"Failed to create the rescue disk"
This happens if I try to overwrite the rescue usb created with previous version, or a new blank usb - both are Kingston DataTraveller 8GB.
Previous version (not updated) on other computer will still create rescue disk to both these usb, so confident that this is an Avast! problem, not usb problem.
Any suggestions?
Thanks

No suggestions yet. Would you mind to provide more details - ideally submit support package (https://www.avast.com/en-us/faq.php?article=AVKB33#artTitle) and let us know the package ID. Or at least OS version would help...

Anyway, this workaround might help - turn off the Self defense.