Avast 2015 (10.3.2225) kills Office 2013

[CraigB]

I have Program version 10.3.2225 and when I open Office 2013 I get the error

The application was unable to start correctly (0xc0000005). Click OK to close the application

I uninstalled and reinstalled Office, still the same issue. Uninstalled Avast (while Office still installed) and it opened fine. Very frustrating having to uninstall and reinstall Avast whenever I need to use Office.

I'm on Windows 7 64-bit also

Read Bob's reply prior to your own, the issue has been addressed in the latest beta version.

[REDACTED]

I have Program version 10.3.2225 and when I open Office 2013 I get the error

The application was unable to start correctly (0xc0000005). Click OK to close the application

I uninstalled and reinstalled Office, still the same issue. Uninstalled Avast (while Office still installed) and it opened fine. Very frustrating having to uninstall and reinstall Avast whenever I need to use Office.

I'm on Windows 7 64-bit also

Read Bob's reply prior to your own, the issue has been addressed in the latest beta version.

Yes I had read that, but I wasn't able to download the beta version.
And when it finally went through Avast came up saying it was a virus,  so gg.

[REDACTED]

Absolutely livid that 3 weeks, a new SSD and a Windows 10 license only to find that this is a known issue that has not been shared with end-users for a critical application!

Sure, mea culpa for not considering that this product might have been a root cause and actively searching these forums for solutions but I appear to be overly trusting?...

Anyway, I can confirm the exact same issues reported by everyone else...

Windows 7 and 10 64bit all act in exactly the same way. What confuses things is that you find yourself trying the myriad of other solutions for 2013 such as disabling graphics hardware acceleration, recreating profiles, etc... And some of them work briefly here and there, then they don't...

Oh and disabling Avast does not resolve the issue as Avast is quietly continuing to block/break things despite being told not to. That's an interesting "feature"

The suggestion to update to the beta seemed like a good idea but with all the other issues like Macrium reflect conflicts, etc... that seems a little counter intuitive... For now I'm back to Win defender and applying a lot of common sense when clicking anything.

In all seriousness, Avast staff... You need to be highlighting this as a known issue and letting your customer base know.. Not waiting for more p*ssed off end-users to find out the hard way... Waiting 2-3 weeks with no notice except this forum post is just poor communication and won't do your product rep' any favours.

For now Avast is off my systems and I doubt I'll be reinstalling without a bit note to test everything 15 times before I update my main systems.

[bob3160]

To be fair, only some user had a conflict with Avast and Office 2013.
I was one of those that never had a problem. I didn't need the update to solve any Office 2013 problem.

[pk]

I can confirm there was a compatibility issue between Avast and Office 365 on 64-bit OSes. I couldn't reproduce it on my own computer, but we got some memory dumps and we fixed this problem. (28/6/2015) -- the fix is probably also included in Avast 2015 R4 Beta (https://forum.avast.com/index.php?topic=175753.0).

[REDACTED]

I have also been experiencing this issue and trying to troubleshoot the last several weeks. I've reinstalled office multiple times, disabled windows firewall and avast with no effect. Could this also be why my Adobe Creative Cloud apps can't communicate with Quicktime? because that started about the same time too! They use TCP to work with Quicktime. I also submitted a support ticket.

[bob3160]

I have also been experiencing this issue and trying to troubleshoot the last several weeks. I've reinstalled office multiple times, disabled windows firewall and avast with no effect. Could this also be why my Adobe Creative Cloud apps can't communicate with Quicktime? because that started about the same time too! They use TCP to work with Quicktime. I also submitted a support ticket.

Posting that support ticket would help for us to alert the Moderators.

[REDACTED]

The suggestion to update to the beta seemed like a good idea but with all the other issues like Macrium reflect conflicts,

First I heard of Macrium problems..........can someone post the thread link ?
I did a search and could not find.

[bob3160]

The suggestion to update to the beta seemed like a good idea but with all the other issues like Macrium reflect conflicts,

First I heard of Macrium problems..........can someone post the thread link ?
I did a search and could not find.

I think he was referring to this topic and as you can see, it turned out to be a Bluetooth mouse problem:
https://forum.avast.com/index.php?topic=173580.msg1243588#msg1243588

[REDACTED]

Just to add my experience with this.

Updated Avast 1 week ago to latest version as it was asking me to, a day later noticed that when I start PC Microsoft OneNote tells me its crashed.
Can't open any Microsoft Office 2013 applications as they error and crash.

I had some success getting only 1 Office application to open, if I stopped all Avast services, I could open OneNote 2013 sometimes, but no other Office apps like Excel or Word.

I re-installed Office after removing it and no change, my PC is fresh installed a month ago and doesn't have much else running.

Now I have Office2013 apps all working, but only as I uninstalled Avast. Shame as it was best anti-virus application I had used.

------------
Windows 7 Home Premium 64bit
Office 2013 64bit (downloaded using a business Office365 account)

[bob3160]

Just to add my experience with this.

Updated Avast 1 week ago to latest version as it was asking me to, a day later noticed that when I start PC Microsoft OneNote tells me its crashed.
Can't open any Microsoft Office 2013 applications as they error and crash.

I had some success getting only 1 Office application to open, if I stopped all Avast services, I could open OneNote 2013 sometimes, but no other Office apps like Excel or Word.

I re-installed Office after removing it and no change, my PC is fresh installed a month ago and doesn't have much else running.

Now I have Office2013 apps all working, but only as I uninstalled Avast. Shame as it was best anti-virus application I had used.

------------
Windows 7 Home Premium 64bit
Office 2013 64bit (downloaded using a business Office365 account)

You could have installed the latest beta as already mentioned. It addressed the Office problem.
https://forum.avast.com/index.php?topic=176033.0

[MayuraDeSilva]

I've been experiencing the same issue for Outlook 2013 (Office 365) on Windows 7 x64, but Office 2010 apps working flawlessly. Reverted back to avast! Antivirus 10.2.2215. Looking forward to a fix in next update.

[REDACTED]

Same problem windows 10 + oficce 2013 64x + avast I told to the cumstumer center and they said it was a problem of my o.s... I think they don`t pretened solve this issue...

there's no more avast in my p.c. .. I have payed for the premiun versión till April 2016.

and i will not recomended it anymore

[bob3160]

Have you installed the latest version of Avast
https://forum.avast.com/index.php?topic=176600.0

[REDACTED]

I had the same issue. Office 365 wouldn't open on 64-bit Windows 7 with Avast installed. I was getting error message 0xc0000005 popping up when I tried to open Word, Excel or Outlook. After weeks of calling Microsoft all kinds of unflattering it names, I found this thread and realised it wasn't Microsoft's fault (sorry MS). Thanks to everyone for posting about it. You've saved me a ton of headaches.

I've uninstalled Avast, and Office 365 is working fine. It's a shame because I liked Avast, but the ability to do my job is more important to me than Avast is, so it's gone until they fix it.

I also had a problem upgrading to Windows 10, which may or may not be related. When I tried the free Windows 10 upgrade, it locked me out of all my files by changing the permissions on them. The only fix Microsoft gave me was reverting back to Windows 7 and wasting two weeks of my life--an unplanned/unpaid holiday from work that I wouldn't recommend--changing the permissions back. Do you think Avast caused that too? I'm wary of trying to install Windows 10 again in case it screws everything up like last time, but if anyone else had the same issue and it was Avast, I'd love to find out.