Author Topic: 10.3.2508  (Read 28647 times)

0 Members and 1 Guest are viewing this topic.

REDACTED

  • Guest
Re: 10.3.2508
« Reply #15 on: December 03, 2015, 06:10:41 PM »
I've to disable its "internet module" to load any page in one of my systems:

Windows 10 - 8.1 - 7 => internet module on = works flawlessly;  ;D
Windows Vista Business => internet module on = no way!!!  :o

REDACTED

  • Guest
Re: 10.3.2508
« Reply #16 on: December 03, 2015, 07:42:51 PM »
Sent a message to the chat support but to make things known here, since updating to 10.3.2508 our office 2013 programs (outlook/word/excel/etc...) all crash when trying to open. Error code 0xc0000005.

Hoping for a fix soon, I have had to disable automatic updates to prevent this spreading to the rest of our company.

REDACTED

  • Guest
Re: 10.3.2508
« Reply #17 on: December 03, 2015, 11:57:18 PM »
@WALLONN7
If you mean WebShield, double check you have the latest Network Interface drivers available for your system.  My problems were fixed by that, and if the problem happens for Vista it's probably the drivers you have currently are a bit old.

@Alex412
Those sorts of crashes are often caused by out-of-date video drivers.  Have a look and see if you have the latest.  Its not uncommon for a Microsoft Update patch to cause this too which might have installed in the same reboot as the Avast update, might be worth checking this avenue as well.  I believe KB3097877 recently had some problems with some Office apps, and confirm you have the latest Office service pack.

REDACTED

  • Guest
Re: 10.3.2508
« Reply #18 on: December 04, 2015, 11:47:47 AM »
@WALLONN7
If you mean WebShield, double check you have the latest Network Interface drivers available for your system.  My problems were fixed by that, and if the problem happens for Vista it's probably the drivers you have currently are a bit old.

Thanks, but...
I'm obsessed with keeping everything up to date!! So we're not talking about an outdated system.  ;)

Additional information:

* wired connection =     Realtek chipset  = 10613 driver          => webshield on = connected but pages won't load;
* wireless connection = Linksys AE2500 = 5.100.243.6 driver => webshield on = connected but pages won't load.
* note: they do not work at the same time. One of them is always disabled.
« Last Edit: December 04, 2015, 11:54:37 AM by WALLONN7 »

REDACTED

  • Guest
Re: 10.3.2508
« Reply #19 on: December 04, 2015, 01:47:16 PM »
On my two test machines, I've upgraded them to 2508.  Both running Windows 10 Pro.  Both get an error during restart:

taskhostw.exe
Exception unknown exception (0xc000008) software exception...

The only option is to close the program.  A few times the machine then sits at "Restarting..." and never does.  Most times it then restarts normally.

I have the exact same issue on a windows 10 Pro machine, on shutdown the error, and one without the error, the machine just sat there "restarting"

REDACTED

  • Guest
Re: 10.3.2508
« Reply #20 on: December 06, 2015, 07:07:15 PM »
 >:(   Adding my thread I posted on MS forums.

"Hello ClarkConsultants.net,

A thread that you are following on Microsoft Community has received a reply from Carminus.
Title: taskhostw.exe error when doing a shut down?

Reply:
The problem on my end was with Avast. Uninstall it and the message will go away. Reinstall it and it comes back. Sadly, Avast is not longer what it once was.
https://forum.avast.com/index.php?topic=179357.0


Read this reply on Microsoft Community. "


AVAST NEEDS TO ADDRESS THIS ISSUE ASAP

Offline Jeff.S

  • Moderator
  • Jr. Member
  • *
  • Posts: 82
Re: 10.3.2508
« Reply #21 on: December 07, 2015, 07:25:15 PM »
Hi Everyone,

We are investigating the taskhostw and office issues, if you are having this issue use the live chat or support option to create a ticket as we may need to collect some logs. I think the issues have been identified, but we want to get tickets created so taht we can see the severity of these issues.


Thanks!

REDACTED

  • Guest
Re: 10.3.2508
« Reply #22 on: December 08, 2015, 06:35:29 AM »
Just to let you know that I have the same issue on 2 of my home PC's, Taskhostw.exe pops up every time I attempt to shutdown.

REDACTED

  • Guest
Re: 10.3.2508
« Reply #23 on: December 08, 2015, 08:08:37 AM »
I am also having this task host issue. If I uninstall Avast!, the error does not display on shutdown. If I re-install Avast, the error comes back.

REDACTED

  • Guest
Re: 10.3.2508
« Reply #24 on: December 08, 2015, 04:49:04 PM »
The taskhostw.exe error prompt on shutdown is still evident on the November release of Windows 10 Pro, which I have just clean installed on a new laptop to test. I even tried disabling Windows Defender prior to install to no avail.

There is a second more serious bug with the latest Avast for Business that affects 'Click to Run' Office 365 2013 and 2016 installs and causes the applications to error when run, and even sometimes interferes with the 'Mail' app in control panel causing it to not load at all. We have witnessed this error on Windows 7 and Windows 10 PCs with 2013 and 2016 click to run versions both affected.

When Avast is removed, all the issues and errors disappear.

We have not seen any issues with Avast for Business and versions of Office installed from local media.
« Last Edit: December 08, 2015, 05:37:18 PM by Alex424 »

REDACTED

  • Guest
Re: 10.3.2508
« Reply #25 on: December 10, 2015, 10:55:14 AM »
I also got this Problem on one of my machines, the other ones are working fine! Both running latest Windows 10 with all updates applied. Is disabled hardware virtualization causing this issue, i think it is only disabled on the machine having problems (taskhostw.exe error on shutdown)

REDACTED

  • Guest
Re: 10.3.2508
« Reply #26 on: December 10, 2015, 11:14:40 AM »
We are finding that the taskhostw.exe error on shutdown occurs only on PCs that have been clean installed with the latest November update to Windows 10, and then have the Avast for Business suite installed fresh. If Avast was already on a machine running an older version of Windows which is then updated to the November release, the taskhostw.exe error does not show up.

REDACTED

  • Guest
Re: 10.3.2508
« Reply #27 on: December 10, 2015, 12:19:31 PM »
Good morning,

We have the same Office error Error code 0xc0000005 in all our computers that works with Windows 7. Opposite, the computers that we have updated to W10 don't has problems.

The problems appears after update Avast to the versiĆ³n 10.3.2508 and, for the moment, we don't have discovered the reason.

Please, have you any news?. Fot the moment I has needed to unintall Avast in the W7 computers   ???

Thanks in advance for your help for to solve as soon as possible.


Sent a message to the chat support but to make things known here, since updating to 10.3.2508 our office 2013 programs (outlook/word/excel/etc...) all crash when trying to open. Error code 0xc0000005.

Hoping for a fix soon, I have had to disable automatic updates to prevent this spreading to the rest of our company.
« Last Edit: December 10, 2015, 01:30:29 PM by Vicente21 »

REDACTED

  • Guest
Re: 10.3.2508
« Reply #28 on: December 11, 2015, 06:33:55 AM »
I'm not really able to contribute, but reading this thread it seems Error code 0xc0000005 has common product:  Office 365.  Nobody seems to have reported Office desktop (full version) as a problem?

I wonder has anyone tried some exclusions on the Office binaries, or turning off individual Avast features to see if there is a behavioral change?  Leaving an Avast feature off might be better than completely removing it until the real cause is determined.  Office 365 uses a lot of internet, maybe the Avast Web filter is playing havoc.

REDACTED

  • Guest
Re: 10.3.2508
« Reply #29 on: December 11, 2015, 10:20:34 AM »
I am currently running the November release of Windows 10 and Office 365 2016. I had the Office errors and managed to resolve them by taking ownership of the Office folders in file explorer, but this doesn't always seem to work so it may have been coincidental. When working with many users in a busy office, it is simpler to just remove Avast for now until they resolve the conflicts and errors.