Cannot print Office Starter Word/Excel

I have installed a new PC with Office Starter (Click to Run) and the latest AVAST free anti virus (6.0.1000). I have discovered that when the avast shield is active I cannot print from either the Office Starter Word or Excel application. I can print from any other application. If I disable the shield I can immeidately print without a problem.

Are there any settings that would help?

Does any of the printer processes are running sandboxed? You can check into Additional protection > Autosandbox > Settings.
If you disable the Behavior Shield, will the printer work?

Have (or did) you another Anti-Virus installed in this system, if so what was it and how did you get rid of it ?

Many new systems come with either another AV pre-installed or a Trial version pre-installed. I have seen this conflict issues with printers from having another AV installed or remnants of your previous one.

I have avast 6 pro, win7 64bit, office starter activated, 2 printers installed and test print ok, but office starter word does not print.
If the shields are disabled, the printers work ok.
It looks like other AV forums have similar problem reported.

@ martyswan,

Can you tell us what version of Avast 6 you have, and answer the questions to the post above yours in your next post so that we have more information to assist you? Thank you.

Is there a resolution to this issue? I don’t see that it was resolved.
I have the same issue: just bought a wireless printer today and docs from word or excel starter edition won’t print. Has definitely to do w/ Avast since I was able to print when I disabled the shields temporarily. Since this doesn’t make sense, how do I fix it?

You could download and run MSFT Printing Specific Fix It and see if will fix the problem.

http://answers.microsoft.com/en-us/office/forum/office_2010-office_install/microsoft-office-starter-2010-will-not-print/e1362fd6-5c7f-44ba-8902-0b9457a30161

Try in the Behaviour Shield
under Expert Settings to add under Trusted Processes:
WINWORDC.EXE
EXCELC.EXE

nils please take note of the date of the posts before replying.

At least he was trying to provide an answer… Note, however, that the proposed fix does not work with Click to Run due to the Q: drive…

This issue has been around for 10 months, and still no answer from avast…

In the MS forums, there are many who have had luck simply by uninstalling avast and switching to MSE… I’d prefer to keep avast, but obviously, this needs to be fixed.

Maybe it was resolved internally meanwhile…!?! :wink:

I am not able to print with Office Starter, but if I disable avast it works fine…

Considering I have an up to date version of avast, and that none of the release notes have implied this has been fixed, and the reality that I have seen nothing indicating avast even admits this is a problem, it has not been resolved.

Please open a ticket here: http://support.avast.com/index.php?_m=tickets&_a=submit

I know this an old post but it seems a lot of people are having issues with this. I am not. I have win 7 all updates, avast free latest version, and office starter oem installed… Printing to a networked printer works just fine with avast running all shields…I have no special win firewall rules…the only thing I have done was to uninstall the trial version of office…not sure I tried printing before I did that…if I can answer any questions to help please let me know
lloyd ;D

Like you, my Windows and avast are both up to date. In looking around, it seems the Starter version (trial version) with Click to Run is the one people are having problems with. I understand Click to Run is a new concept, but I also would have expected avast to account for it.

Thank you for at least acknowledging that there are people having this problem.

I just checked on my Lenovo S10-3. I have Office 2003 Professional on this machine (only because it has narrower toolbars) so I normally don’t use the cut-down 2010 Starter at all.

Windows 7 Starter 32bit
Word 2010 Starter
avast! Pro 6.0.1367(default settings)

No printing problems. Could be a 64bit issue.

As the OP said, the issue is with the way avast handles (or, realistically, cannot handle) Office Starter’s Click to Run…

Your problem, as mentioned in your other thread :
http://forum.avast.com/index.php?topic=91965.0
Has been referred to a Moderator for someone from Avast to have a look.
Two threads on the same topic only confuse and make it harder to resolve an issue.

Thanks.

Your welcome. :slight_smile:
Hopefully someone from Avast will have an answer for this problem.