Avast WEBforum
Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: hrova on January 17, 2012, 07:06:45 PM
-
There have been a few threads about this issue, but no verified answer from avast.
I have Windows 7 (64 Bit) with Office Starter Click to Run. Bottom line, avast blocks the printing from Word and Excel. With avast disabled, it prints fine.
This issue has been discussed on these forums here:
http://forum.avast.com/index.php?topic=74144.0 (http://forum.avast.com/index.php?topic=74144.0)
It has been discussed in Microsoft forums here:
http://answers.microsoft.com/en-us/office/forum/office_2010se-word/word-starter-will-not-print/8a40ff2a-8726-4bb8-8774-7cdb009d2595?page=2 (http://answers.microsoft.com/en-us/office/forum/office_2010se-word/word-starter-will-not-print/8a40ff2a-8726-4bb8-8774-7cdb009d2595?page=2)
The only confirmed solution has been to uninstall avast and switch to MSE, but I can't believe avast hasn't fixed this issue yet or at least provided a reasonable workaround.
Any suggestions?
-
Delete your firewall rules that are related to web browsers and /or related to avast (even if your firewall is disabled). Save the changes and reboot.
Then your firewall should eventually ask you to re-create anew the rules. Allow the creation of them. Avast should then be able to update and your web browser should let you open web sites.
If there is any kind of firewall rule related to your printer, delete it too, reboot and let it re-create.
Once you successfully tested avast's connection and web site access, test the printer.
Please report back (so we can provide you with additional avast settings if necessary).
-
1.) I have set up no firewall rules.
2.) When I disable avast, things print fine, so I am confused as to why you are pointing to the firewall.
3.) Avast already updates fine.
4.) I am able to view web pages with no problem.
Based on things on this forum and others (as I linked above) this is clearly an avast issue. I wa shoping someone from avast could address this with a simple solution. As I sadi in my original post, the only verified solution has been to uninstall avast.
I would hope avast can come up with something better than that solution.....
-
2.) When I disable avast, things print fine, so I am confused as to why you are pointing to the firewall.
we have had many cases here where there have been problems surfing the net.....and as soon as they disable avast webshield, surfing works fine
and then of course they say it is a avast problem. ::)
However as soon as they deleted the avast rules in the firewall and rebooted, everything was working normal
often happen with comodo and zonealarm firewalls
-
often happen with comodo and zonealarm firewalls
-
I am not using a thrid party firewall - just the Windows 7 built in firewall. Trying to defer the blame from avast is not the answer - if you read the link I provided to the MS forums, the problem went away when they deleted avast and installed MSE... Note that the firewall, its settings, etc... stayed the same, and things began to work fine....
Since this seems like a pretty major issue (not being able to print due to avast) I was hoping for an actual answer, not some list of various things to try. I guess I assumed avast would have already figured this one out - the thread I lionked i nmy original post goes back to March of 2011.....
Is there any official word from avast on solution or workaround for this?
-
As I already wrote, my post was a "first step" and not the last one. I'm not saying avast is not related. I'm just saying that the firewall rules (built in firewall in Windows, a hardware firewall or whichever you have, enabled or not) is the first step for this type of cases IMHO.
The web shield settings would be the second step, but only after the firewall rules.
We have seen enough cases, so there is a chance a couple of relatively simple steps can resolve the issue, while avast by itself can't resolve automatically every and any situation (which depends not only on avast's installation, but it is still related to it).
Now, if you don't want to try to follow the suggestions, that's up to you. I'm not related to avast, other than being a simple user, so I can't guarantee you that the whole set of steps will effectively solve your problem.
I'm not going to post a full article of all the possible steps to follow. The solution may depend on many different things, so I posted the first steps I think may be part of the solution to your problem.
I'm not surprised that MS would suggest using MSE, for almost any question posted about any other security tool. They may be correct in some specific case.
I'm glad you find a workaround, even if it means using a different antivirus. Good luck.
-
Wow...
Not to be ubgrateful, but it appers you have not read my posts... In this case, specifically my second one replying to your suggestions... I DO NOT have any fireweall rules set up, and I DO have an updated avast and I CAN connect to the internet.... You make it sound as if I'm iunwilling to try your suggestiosn, but I've already said there was nothing in that post for me to try...
Yes, it is logical the MS forums would recommend MSE, but that doe snot change the fact that deleting avast and using MSE instead solved the problem for many users on that thread. I brought it up to counter your placing the blame on the firewall or its settings... Firewall was not an issue at all. It is clearly something with avast, but avast does not seem to want to hear that.
Years ago, there were avast knowledgeable people here, actually some of its developers if I recall correctly. Do they not participate oin these forums anymore? Have these just become user to user forums with little / no oversight?
-
You said you have Windows firewall, and I said whether enabled or disabled, delete the relevant firewall rules anyway. In addition, you may have a hardware firewall with some configuration (for example, in a router).
So, yes, I read your posts correctly, and you were not willing to at least try it (which is fine with me). It would have been finished by now and we would had been able to go to the next step, but anyway...
As I said, I don't have any problem at all with your decision using MSE instead of testing the suggestion, reporting back and waiting for the next steps. Really, it's fine with me.
Since you already took out avast and are happy with MSE, I don't really know what are we talking / discussing about now.
-
afy4um....
"So, yes, I read your posts correctly"
"Since you already took out avast and are happy with MSE, I don't really know what are we talking / discussing about now"
Perhaps you are reading my posts, but it is clear you are not understanding them. I never said I had decided to use MSE, nor did I say I had installed it. If that were the case, I wouldn't even bother wasting my time here... I am trying to keep avast, which I have used for over seven years, but would like to be able to print in MS Office Starter..... If MSE is the only solution (and from the lack of help here, that appears to be the case) I will switch, but again, I'd prefer not to....
Thanks for trying, and I believe your intentions are good, but you seem stuck on a firewall issue, which is not the answer.
I'd be happy to try other possible solutions. Sadly, it seems as if avast is just sticking their heads in the sand about this issue by pointing fingers elsewhere. They are losing users who WANT to use avast but are getting no help with this problem....
-
Just FYI, Click to Run in the starter edition of Office 2010 has other issues as well. It can cause corruption in Windows restore points that makes them unusable. It has to do with the virtualization features and that mysterious Q drive that is created on your machine. I had problems and wound up uninstalling Office Starter completely and going with my Enterprise edition of Office 2007. That has no problems at all with either Avast or System restore. Unless you really need the Click to Run functionality, I would uninstall that part and see what happens.
-
Yes, it is logical the MS forums would recommend MSE, but that doe snot change the fact that deleting avast and using MSE instead solved the problem for many users on that thread.
It also eliminates any rules set up in the firewall regarding avast!. Same as having uninstalled avast!
Removing all rules in the firewall that link to avast will force new rules to be written based on your answers when avast! requires internet access.
-
Sadly, it seems as if avast is just sticking their heads in the sand about this issue by pointing fingers elsewhere. They are losing users who WANT to use avast but are getting no help with this problem....
Would it really shock you if they were not even aware of it? I mean, this company essentially serves up a customer base of millions with a skeleton crew (more or less) and does it quite well. So things can fall through the cracks, thats the downside.
Ady4um is telling you to check your FW for a reason. You must have FW rules if you have WinFW turned on, otherwise nothing would be able to connect. The Avast! Web Shield functions as a transparent proxy at port 12080 on your FW. Recently, the Web Shield got a feature added where it now scans not just browser processes, but other HTTP traffic as well. He is trying to narrow down what the root cause of the problem is.
But since you seem unwilling to play ball, at least without a detailed "Why?" for each step you are asked, maybe you should try submitting a support ticket instead, as was suggested in the other thread you posted in.
-
I am uncertain why I am being accused of not "playing ball." It is simply not a firewall issue. If me stating that fact is not "playing ball," then so be it. I guess I could argue he is not "playing ball" by offering other help when I say it is not a firewall issue.... I am unsure what exactly I can do to prove to you guys that point - it seems like you have this little club and, right or wrong, you are supporting the answer you all agree is reasonable... I am surprised you did not recommend a repair install of either Office Starter or avast... or Windows 7...
About avast and , this has been posted on their very own forums as far back as March of 2011. Do they not monitor these forums?
-
Since we can't help or reason with you, maybe the support ticket is your best option. :(
-
"Since we can't help or reason"
I think we agree that some here cannot reason.... ;D
You are treating me as if I am not open minded on this issue. But all of the replies are focused on only one thing...
The only advice given thus far has been firewall related... What do you want? Screen shots of a disabled firewall and Office Starter still not printing? I mean, seriously, you are all high and mighty that I am not playing along with your little game... What exactly would it take to prove - or even make one of you consider - that it is NOT a firewall issue?
-
Hrova,
Why have have you disabled the Win 7 firewall ?
Greetz, Red.
-
Screen shots of a disabled firewall
You never said once you disabled the FW, all you said was
1.) I have set up no firewall rules.
and
I am not using a thrid party firewall - just the Windows 7 built in firewall.
None of those implies it was disabled.
You are getting real chippy now, with comments like this
I mean, seriously, you are all high and mighty that I am not playing along with your little game...
Its not a game.....its is looking like you never wanted help from the users to begin with, all you want is a company man/woman to talk to, and we showed you the ticket option for that......for the first time, I am seriously tempted to send someone to iYogi. ::)
And yes, they monitor the forums, but I have my doubts they check every last thread, especially ones that have responses. The devs need to be free to develop, this is not the infant software company it once was. So if you want to officially report something and make sure it is not missed (it might have been the first time, or it might be something that was fixed but came back), as was said, the ticket is a better option.
-
@hrova,
As pointed out, we are not avast employees.
I also mentioned (more than once now) that the firewall rules deletion and re-creating (for web browsers, avast, and printer drivers / software) is only the first step so to narrow down the source of the problem. That means that the firewall itself is probably not the source of the issue, but it is yet part of the troubleshooting steps.
AFTER the firewall steps (including reboot and re-creating of rules, if the firewall requests them), comes the web shield settings, and the possible configuration of the specific port of the printer (which could be seen by Windows, for example, as an IP port, independently of the real hardware).
Who knows, the problem could be in the specific version of Office, or in the specific Windows version. We haven't even got to questions like "Are you able to print web pages?", just as an example.
One troubleshooting possibility "could" be uninstalling everything involved (avast, office, the printer and its driver and its software and any and all security tools like MSE), cleaning the remnants (http://singularlabs.com/uninstallers/security-software/ (http://singularlabs.com/uninstallers/security-software/)) and reinstalling the latest stable versions. I don't know if you need to get to that extreme.
Sometimes avast (or some other software) may not be the real source of a problem, but only it "shows" you that there is some issue behind. Since I'm not an avast developer, I have no way to tell you, with the info I / we have right now. If the bottom line problem is (or isn't) avast.
Installing additional security tools can complicate the problems, as seen MANY times here in the forum, even when a user states he is an experienced technician and knows what he is doing. (Please, don't misunderstand me. I'm actually writting about a real case that just happen today in another topic.)
So, there is no need (nor goal) for any kind of aggression, in any level at all, from anyone to anyone. I think the minimal suggestions here were sincere, and opening a ticket request may be the best way to point the attention of the developers to this issue (and to find out whether avast is the real source of the problem, or it is just a coincidence of many little things altogether).
-
"Since we can't help or reason"
I think we agree that some here cannot reason.... ;D
You are treating me as if I am not open minded on this issue. But all of the replies are focused on only one thing...
The only advice given thus far has been firewall related... What do you want? Screen shots of a disabled firewall and Office Starter still not printing? I mean, seriously, you are all high and mighty that I am not playing along with your little game... What exactly would it take to prove - or even make one of you consider - that it is NOT a firewall issue?
I suggest that if you quote someone, you not take things out of context. >:(
-
Sorry if this is repeat..in middle of a post my editor dissapperad...any way I said I don't have a solution but I do have win7 with avast free and office starter and I can print just fine. My printer is networked on a pc server and I print mostly from my wifii laptop. I set no special rules in win7 firewall...The only thing I did do was uninstall microsoft office trial version...
So any way this configuration has worked well for me....
-
So many responses to reply to... Nice to see there is so much interest in this issue, but, like me, it seems you are all stumped....
I will try to reply to all relevant comments, but if I miss yours, don't take it personally. I have been busy trying to figure the actual issue out...
Unless you really need the Click to Run functionality, I would uninstall that part and see what happens.
If I understand correctly, as a user of Office Starter, if I uninstall Click to Run, it will take away my use of Word and Excel in Office Starter. When I try to Uninstall just Click to Run, it warns that Office Starter will also be uninstalled.
Since we can't help or reason with you, maybe the support ticket is your best option. :(
Thank you for at least admitting you can't help and that a ticket is the best option.
Hrova,
Why have have you disabled the Win 7 firewall ?
Greetz, Red.
Some around here wanted me to eliminate the firewall as a possibility. For the record, I did temporarily disable both Windows 7 firewall and my router's firewall, with no change, which I why I kept saying it was not a firewall issue.
You are getting real chippy now, with comments like this
I mean, seriously, you are all high and mighty that I am not playing along with your little game...
Its not a game.....its is looking like you never wanted help from the users to begin with, all you want is a company man/woman to talk to, and we showed you the ticket option for that......for the first time, I am seriously tempted to send someone to iYogi. ::)
I stated several times it was not a firewall issue. I did come here for help, but so far no one has really listened to what the problem is, but rather wanted to follow some script of steps to take, even when I've clearly stated that certain parts of what was being asked (the firewall) was not the issue.
Sorry you felt my comment was chippy. Perhaps you missed the tone of the non help I've received thus far. Hardly welcoming or helpful. Your own comment about recommending iYogi is exactly the tone of people here that is not only not helpful and equally chippy, but it seems you somehow find that acceptable.
I suggest that if you quote someone, you not take things out of context. >:(
Guess what? I have a suggestion of my own. I would suggest people not talk down to those asking for help. They were implying I was not being reasonable, I was just trying to get the message back that many of you were not being reasonable, either. I had said several times it was not a firewall issue, but people kept stuck on that issue. Regardless, thank you for your suggestion.
And finally, about the last post from lloydc. I am glad it is working for you. Based on your post in the other thread, it appears you are not using Click to Run.
Moving on to the actual issue... I've spent the last several hours trying to narrow the problem down. I have made some progress on it. I am glad to provide you this information if the question comes up again.
Previously, I eliminated the firewall as a possibility and found the problem went away by disabling avast. Moving forward, rather than disable all avast shields, I tried them one by one and found the issue is with the Behavior Shield (verified on two separate computers here). Going even further, in the Expert settings, if I switch it to Ask (as opposed to auto-decide), it does not actually ask, though it does prevent printing. Seems like one bug there...
Beyond that, I tried unchecking the various options under the Expert Settings in the Behavior Shield. The only one that changed things was unchecking "Monitor the system for unauthorized modifications." Again, that held true on two different machines here.
So now I can at least print from Word and Excel, but I apparently do not have the full protection of avast. I suspect there must be something I could add in trusted processes to get going... Winwordc.exe and exelc.exe, as recommended in another thread, did not work. Still, there must be some process that can be added to that trusted processes list that would work.
I hope that avast will, at some point, work to make that an unecessary step so its users can enjoy the full protection avast offers and print at the same time. I don't think that is asking too much.
Any suggestions are still welcome - unless you are still stuck on a firewall issue.
-
In still searching, I found this thread:
http://answers.microsoft.com/en-us/office/forum/office_2010se-word/printing-problem-office-starter-edition-with-avast/1fa7189e-c8de-48f0-ade4-2aef5fa840b2 (http://answers.microsoft.com/en-us/office/forum/office_2010se-word/printing-problem-office-starter-edition-with-avast/1fa7189e-c8de-48f0-ade4-2aef5fa840b2)
It says that the auto sandbox is the problem.
I do not have access at the moment to the computers with this issue, but I do have a question....
Assuming things work if I disable auto sandbox, would you recommend I disable auto sandbox and allow all of the behavior shield? What would give me better protection? Disabling that one piece of the behavior shield (Monitor the system for unauthorized modifications) or disable the auto sandbox feature?
Either way,I would hope avast fixes things so neither needs to be disabled to do something so simple as to print a Word or Excel file....
-
If the autosandbox is at fault, I doubt you need to fully disable it. A simpler and safer solution would be to switch it to "Ask" mode, then the next time the program it is snagging needs to run, it will ask you via a dialog box.....allow it to run normally, and tick the "remember my answer" box....this should enter needed exclusion/s.
Location of relevant settings; Open Avast! UI>>Real Time Shields>>File System Shield>>Expert Settings>>Autosandbox
-
If the autosandbox is at fault, I doubt you need to fully disable it. A simpler and safer solution would be to switch it to "Ask" mode, then the next time the program it is snagging needs to run, it will ask you via a dialog box.....allow it to run normally, and tick the "remember my answer" box....this should enter needed exclusion/s.
Location of relevant settings; Open Avast! UI>>Real Time Shields>>File System Shield>>Expert Settings>>Autosandbox
Agreed that the ask method would be helpful, but for the behavior shield, that did not work.
I cannot access computers with this issue at the moment. I'll play around more tomorrow and test things and post update.
In the meantime, if I must disable one, would you recommend Behavior shield or auto sandbox?
-
Some around here wanted me to eliminate the firewall as a possibility. For the record, I did temporarily disable both Windows 7 firewall and my router's firewall, with no change, which I why I kept saying it was not a firewall issue.
I did NOT requested to disable the firewall!!! I requested to delete the relevant rules of any and all firewalls, whether the firewall is enabled or not. I don't understand why I keep repeating myself. Maybe I imagine I wrote things, but I haven't wrote them really ???.
I also would like to point out that no really relevant info was provided until now. Is the printer seen in Windows as connected to an IP port? Is there any router / firewall (hardware) involved? Can you print from your web browser?
BTW, I don't understand why you think users here are denying (you) something / anything. We keep offering you suggestions / comments and no one said that avast is for sure not related to the issue (which may or may not be).
Have you tried web shield -> expert settings -> exclusions and excluding the relevant processes (printer software and drivers, word and excel) and / or IP addresses (of the printer port). (Although, this would be the second step in the series, and not the last one either.)
I mean, all this long "discussion"; when it would had been much simpler to delete the relevant firewall rules and reboot as FIRST step from a series of troubleshooting procedures (NOT as the last and only step).
BTW, please stop double posting.
-
In the meantime, if I must disable one, would you recommend Behavior shield or auto sandbox?
Nothing was said about disabling anything. Please re-read Gargamel 360's post.
By the way, ask was/is the default settings so you obviously made some setting changes without knowing the consequences.
The default settings are usually designed for smooth operations under most conditions. :)
Changes to the default settings should only be made if the default settings present a problem.
-
In the meantime, if I must disable one, would you recommend Behavior shield or auto sandbox?
Nothing was said about disabling anything. Please re-read Gargamel 360's post.
By the way, ask was/is the default settings so you obviously made some setting changes without knowing the consequences.
The default settings are usually designed for smooth operations under most conditions. :)
Changes to the default settings should only be made if the default settings present a problem.
You just keep it coming, don't you? I will not debate whether ask is or is not the default setting or whether I changed anything. Obviously, that is not the point since the fact is that it didn't ask either way it was set up. For the record, however, in the behavior shield, I DIDN"T change anything and it was set up to auto decide by default... The autosandbox was / is still set to its default of ask, but you guys seem so stuck with somehow making this an issue that the user caused, apparently not reading the links I've provided and ignoring the fact that this is happening to many people who have given up and moved on to other AV's... If we (Or if I, I guess, as it is turning out)can solve this, it will help not just me, but avast overall....
On to the actual issue...
Perhaps you missed my post where the only way I have been able to print so far was to disable avast, which I then narrowed down to the behavior shield, then narrowed it down to the one particular item in the expert settings.
I agree that in most cases the default settings do / should work. That is obviously not the case here.
Some around here wanted me to eliminate the firewall as a possibility. For the record, I did temporarily disable both Windows 7 firewall and my router's firewall, with no change, which I why I kept saying it was not a firewall issue.
I did NOT requested to disable the firewall!!! I requested to delete the relevant rules of any and all firewalls, whether the firewall is enabled or not. I don't understand why I keep repeating myself. Maybe I imagine I wrote things, but I haven't wrote them really ???.
I also would like to point out that no really relevant info was provided until now. Is the printer seen in Windows as connected to an IP port? Is there any router / firewall (hardware) involved? Can you print from your web browser?
BTW, I don't understand why you think users here are denying (you) something / anything. We keep offering you suggestions / comments and no one said that avast is for sure not related to the issue (which may or may not be).
Have you tried web shield -> expert settings -> exclusions and excluding the relevant processes (printer software and drivers, word and excel) and / or IP addresses (of the printer port). (Although, this would be the second step in the series, and not the last one either.)
I mean, all this long "discussion"; when it would had been much simpler to delete the relevant firewall rules and reboot as FIRST step from a series of troubleshooting procedures (NOT as the last and only step).
BTW, please stop double posting.
I never said that YOU said to disable the firewall. Nor was that my first / only step in trying to solve this, but it WAS the focus of the issue by many people here despite me saying it was not a firewall issue several times.. You all just refused to believe me... No biggie, but hopefully you can at least learn from this so you don't beat up the next poor user who comes along here.....
I am glad you agree that this information was helpful. These things could have been figured much more quickly if people were not so bent on the firewall, which I had said SEVERAL times was not (and, is not :P ) the issue.
Just so I don't get accused of playing along with you, here are some answers to your questions:
1.) We have two printers, one networked, one not. Even on the one connected directly tot he computer, avast blocks its access when trying to print from Word / Excel in Office Starter 2010. There is a router involved for one printer, but obviously not the one directly connected to the computer. Of course i can print web pages fine... The issue is with printing from MS Office Starter 2010.
Finally, I have considered the exclusions list (not web shield though, the issue is with the behavior shield - again, I stated that in a previous post), which is why I already brought it up. However, at this point I do not know which process it is...
Thanks for all your time... Like I said, once I took time off from defending myself on these forums, I made some progress... Now I just need to find the particular process or avast needs to by default let people print from that program...
-
I don't know if you'll ever get you personal problem solved but,
You are managing to write a book.
Arrogance is also not the way to continue to receive any attempt to solve your problem.
Since the problem in your mind at least, must be avast!'s fault, there is a simple solution. ;D
We've already had a reply from another user who has the same program and uses avast! and has no problems.
Maybe it's time to find out the differences between your way of using avast! and the Office Starter program and the way lloydc uses these two programs without any conflict ???
-
I don't know if you'll ever get you personal problem solved but,
You are managing to write a book.
Arrogance is also not the way to continue to receive any attempt to solve your problem.
Since the problem in your mind at least, must be avast!'s fault, there is a simple solution. ;D
We've already had a reply from another user who has the same program and uses avast! and has no problems.
Maybe it's time to find out the differences between your way of using avast! and the Office Starter program and the way lloydc uses these two programs without any conflict ???
Resorting to personal digs while providing no help? I am not surprised.
To keep the focus on the problem, the other user is NOT using Office Starter 2010 with Click to Run. I pointed that out in my post, which brings up part of my frustration here. People don't seem to read or believe what I am saying. You are all out to make it a user caused issue..
Disabling the one part of behavior shield allows me to print. How is that NOT an avast issue?
-
Then I guess you'll have to wait for one of the Avast people to
get back to you.
I have alerted them to this thread.
Did you ever send in a support ticket ???
-
I was considering "clearing" some points from previous misunderstandings (which are still "rolling"), but I find it a complete waste of time already.
Since you are able to print in at least one printer from other programs, then I don't understand why is avast the main source here. I mean, even if for some reason avast is blocking the print function from specific programs (but evidently not for all programs in your system), then by:
1_ "resetting" the suspect settings (behaviour shield, autosandbox, safezone, whatever); and THEN
2_ turning all of them into "ask" (so to be aware of "everything" avast decides to do),
should help you narrow down the problem (if it ONLY depends on avast and the specific programs).
In addition, you could set the printer software / driver to "pause" the printer pool (as oppose to print directly). By this, you could actually double check if the printer is at least receiving the action sent by the program (office / word / excel / whichever).
-
I was considering "clearing" some points from previous misunderstandings (which are still "rolling"), but I find it a complete waste of time already.
Since you are able to print in at least one printer from other programs, then I don't understand why is avast the main source here. I mean, even if for some reason avast is blocking the print function from specific programs (but evidently not for all programs in your system), then by:
1_ "resetting" the suspect settings (behaviour shield, autosandbox, safezone, whatever); and THEN
2_ turning all of them into "ask" (so to be aware of "everything" avast decides to do),
should help you narrow down the problem (if it ONLY depends on avast and the specific programs).
In addition, you could set the printer software / driver to "pause" the printer pool (as oppose to print directly). By this, you could actually double check if the printer is at least receiving the action sent by the program (office / word / excel / whichever).
Again,. I have tried the ASK, but it didn't ask while at the same time blocking access to the printer.
I suspect it has to do with the way Click to Run is a virtual app that avast is blocking.
Also, to clarify, I can print in both printers from any other program. It is just the Click to Run that is giving avast issues.
-
When you set to ASK, is for further actions. But, if avast is somehow blocking those specific programs and avast is not asking about it, then it would mean that avast is already deciding by itself to block it, or it already has some "don't ask me again, as the user somehow already set this specific action from this specific program to be blocked, every single time).
In other words, either "automatically" or by some other previous order, avast is ALREADY blocking (according to your reports) the specific action from the specific program.
That's why I say that, somehow, there is a need to "reset" this specific settings (behaviour shield, autosandbox, or whatever you think is part of the problem here). Then avast, still with ASK, should start again asking the user to decide "everything" again. So avast should ask you again for permission for this specific action that is being blocked.
Since 1 of the printers is on some IP port, the easiest way for now to narrow down the problem is to concentrate the efforts on the printer that is currently directly connected to the computer. Once the source of the problem is solved, you con continue with the other (IP connected) printer.
-
it would mean that avast is already deciding by itself to block it, or it already has some "don't ask me again, as the user somehow already set this specific action from this specific program to be blocked, every single time).
Well logically, I get what you are saying, but it is not correct.
Please stop trying to blame the user.
-
@ady4um,
Let someone from Avast deal with it. :(
-
Again,. I have tried the ASK, but it didn't ask while at the same time blocking access to the printer.
I suspect it has to do with the way Click to Run is a virtual app that avast is blocking.
Also, to clarify, I can print in both printers from any other program. It is just the Click to Run that is giving avast issues.
As I said before, the fact that Click to Run is a virtual app that runs on a virtual drive is the source of other problems, some within Windows itself, it's not solely an Avast issue. The fact that it does play well with MSE is not surprising at all since I'm sure MS thoroughly tested that beforehand. Avast may very well have a problem with how the print routines are set up but since there are other problems being reported it also is a Microsoft problem which they should fix.
-
As I said before, the fact that Click to Run is a virtual app that runs on a virtual drive is the source of other problems, some within Windows itself, it's not solely an Avast issue. The fact that it does play well with MSE is not surprising at all since I'm sure MS thoroughly tested that beforehand. Avast may very well have a problem with how the print routines are set up but since there are other problems being reported it also is a Microsoft problem which they should fix.
I think I was pretty clear from my first post that the issue was with avast's handling of the Click to Run. I knew that....
But it is not solely an MS issue, as I have searched many threads about this problem, and the only AV that comes up over and over again as the culprit is avast. Most AV's work around the various programs on a machine.... Expecting a program to be written around the AV used is not the way things work.
-
As I said before, the fact that Click to Run is a virtual app that runs on a virtual drive is the source of other problems, some within Windows itself, it's not solely an Avast issue. The fact that it does play well with MSE is not surprising at all since I'm sure MS thoroughly tested that beforehand. Avast may very well have a problem with how the print routines are set up but since there are other problems being reported it also is a Microsoft problem which they should fix.
I think I was pretty clear from my first post that the issue was with avast's handling of the Click to Run. I knew that....
But it is not solely an MS issue, as I have searched many threads about this problem, and the only AV that comes up over and over again as the culprit is avast. Most AV's work around the various programs on a machine.... Expecting a program to be written around the AV used is not the way things work.
They work both ways. Most developers will test their offerings with all of the security apps to ensure compatibility (the malware writers certainly do- :-[). In this case, MS may only care if things work with MSE. I didn't say it was only a MS problem but given other reported problems with Click to Run, it may be a factor.
-
I will concede that the whole Click to Run conept and implementation has not been good, I do think it would be in avast's best interest to figure this out. There are people leaving avast over this issue... I waould rather stay with avast and get it resolved....
-
And I agree that it needs to be resolved. It may take a cooperative effort but it should be fixed.
-
And I agree that it needs to be resolved. It may take a cooperative effort but it should be fixed.
Avast has been alerted. It's now their problem to resolve.
http://forum.avast.com/index.php?topic=91965.msg731588#msg731588 (http://forum.avast.com/index.php?topic=91965.msg731588#msg731588)
-
I do have click to run installed (Q drive OEM install), I just refer to it as office starter as I thought they were one in the same. I have the default setups for avast free with some minor exceptions I put in from this forum to prevent avast and mbam scanning at the same time. So I'm not sure why mine works...If there is something I can look at for you let me know.
lloyd
-
I should also mention I have the 64 bit version of win 7 if that is relevant.
-
Quoted from other thread you posted in:
"..the only thing I have done was to uninstall the trial version of office..."
I guess that sentence made me think you had uninstalled Starter, which some people refer to the trial version...
What version of Office are you actually using? Where did you get it? I did not get any trial version, only the Starter version...
-
my computer came with the microsoft office (full version trial) and click to run microsoft office starter pre-installed. When the trial version of office ran out I uninstalled it and just kept using the starter version. I don't recall if I ever printed from the full version during the trial period. I have a samsung RV511 laptop win 7 64bit service pack 1, 4meg RAM..My printer is networked on a desktop running xp sp3 that I print to via my wiifi connection on the laptop. I have a very vanilla setup on my avast free, so I just can't imagine what might be different about my config. I wonder if the networked printer might be what's unique??
-
my computer came with the microsoft office (full version trial) and click to run microsoft office starter pre-installed. When the trial version of office ran out I uninstalled it and just kept using the starter version. I don't recall if I ever printed from the full version during the trial period. I have a samsung RV511 laptop win 7 64bit service pack 1, 4meg RAM..My printer is networked on a desktop running xp sp3 that I print to via my wiifi connection on the laptop. I have a very vanilla setup on my avast free, so I just can't imagine what might be different about my config. I wonder if the networked printer might be what's unique??
Thanks for the input.
One difference is the fact that you had a full version of office at one point. Not sure what that would effect, but it is a difference.
I also wonder if having it go through an XP machine to print may make a difference. We have two printers - one networked and one hard wired to desktop, but on the laptop with the exact issue, it is networked for both printers. I don't suspect a network configuration error there, as everything other than the Click to Run products prints without issue. I also have a basically default set up for avast, so I suspect any difference would be outside of that.... But, just to clarify, do you have all shields running? And the auto sandbox?
For now, we are running avast with the Expert Setting in the Behavior Shield slightly changed by unchecking the 'Monitor the system for unauthorized modifications' box. Perhaps leaves us a small amount unprotected, but all the other shields are fully running, so we still have a reasonable amount of protection... And we can print from Office Starter now....
If anyone cares, the auto sandbox disabling did not make a difference. It was set up to Ask, but it never brought up a dialogue box about the printing, and even disabling it made no difference as far as allowing printing. The only work around I have found is the behavior shield mentioned above....
Again, thanks for posting. I know I could just switch to MSE, but I have used avast for about 7 years and do like it. I also know I could simply switch to Open Office.... But by switching, that would be like giving up, which I really am not ready to do yet.
-
For now, we are running avast with the Expert Setting in the Behavior Shield slightly changed by unchecking the 'Monitor the system for unauthorized modifications' box. Perhaps leaves us a small amount unprotected, but all the other shields are fully running, so we still have a reasonable amount of protection...
That is not too dangerous of a thing to do....the Behavior Shield is very passive anyway, unless you change it to "ask"....this is much better than totally disabling it, as you would by proxy also turn off the Script Shield, as it is dependent on the Behavior Shield.
I also know I could simply switch to Open Office.... But by switching, that would be like giving up, which I really am not ready to do yet.
Slightly OT heads-up....Open Office is dead, if you did switch, you would want LibreOffice.
-
Slightly OT heads-up....Open Office is dead, if you did switch, you would want LibreOffice.
Thanks for that info... I have been using OO on my laptop for years now... The desktop I use and the laptop my son uses are the ones with Click to Run problem.
-
I went thru my avast setting and The few changes I made were to enable PUP scanning and exclude the Q" drive (click to run) from scans...I kept getting password protect scann errors on Q...pretty sure I did that way after I printed from word and excel though...Ihave all shields enabled fully including behavioral, and have auto sandbox on..again not sure of the relavance but I did not install chrome with avast...I did however just install it a couple weeks ago...again no change before or after that...sorry i can't help much...
lloyd
maybe I should offer to sell my computer to avast so they can figure it out.. ;D ;D
-
I went thru my avast setting and The few changes I made were to enable PUP scanning and exclude the Q" drive (click to run) from scans...I kept getting password protect scann errors on Q...pretty sure I did that way after I printed from word and excel though...Ihave all shields enabled fully including behavioral, and have auto sandbox on..again not sure of the relavance but I did not install chrome with avast...I did however just install it a couple weeks ago...again no change before or after that...sorry i can't help much...
lloyd
maybe I should offer to sell my computer to avast so they can figure it out.. ;D ;D
Interesting that you excluded scanning the Q drive...
I am guessing there is some exclusion I could make in the behavior shield that would allow things to work and lave all protection on, but I haven't found it... Nor, it seems, has anyone else. Unless, maybe, I exclude the whole Q drive in the expert settings of the behavior shield. Any input on that? Not even sure it would work for me, but...
I submitted a ticket earlier this week regarding this issue, but haven't heard back yet. Things are fine with the changes I made earlier. I'll leave it be until I hear back or come up with a better solution.
Regardless, lloydc, thanks for hanging in there as I try to sort this out...
-
Just reaching for straws but wonder if this has any bearing:
http://forum.avast.com/index.php?topic=1480.msg349807#new (http://forum.avast.com/index.php?topic=1480.msg349807#new)
Remember, it may not have anything to do with it but worth a look. :)
-
Hi,
Yeah, a have a hunch a straw may someday be the answer.... This one was not it, but thanks.... I understand the solution may be obscure because the problem itself is kind of obscure....
In the big picture, I am glad I have gotten this far... When the issue showed up I had no clue as to what the issue may have been... Suffice it to say avast was not on my list of possible culprits, but after many online searches, it came up....
Maybe something in avast 7 will make it work....
Anyway, thanks.
-
I'm thinking more and more that it may have to do with a conflict between Click to Run's virtualizations and the Avast sandboxing and behavior monitoring features.
-
I'm thinking more and more that it may have to do with a conflict between Click to Run's virtualizations and the Avast sand boxing and behavior monitoring features.
One thread I read mentioned disabling the auto sandbox as a fix. I tried that, with no luck. It is strange that I've seen various solutions posted to this...
One frustrating thing is that once it 'finds' the printer, it appears to remember it for a few days. For example, it sees the printers now. If I turn all of the behavior shield back on, it will see still see the printer for a bit, then lose it. For convenience, I am now just leaving that one thing unchecked...
-
Disabling the Behavior Shield has worked for someone else:
http://forum.avast.com/index.php?topic=92134.msg733038#msg733038 (http://forum.avast.com/index.php?topic=92134.msg733038#msg733038)
If it works for the rest, then try rebooting your system and see if the printing
now works without any changes to avast!.
-
Turned off the behavior shield, try to print.
If that works, turn the behaviour shield back on and try again.
-
Turned off the behavior shield, try to print.
If that works, turn the behaviour shield back on and try again.
Thanks, but already tried with no luck. Behavior Shield back on, printing eventually dies in Office, either later that day if the next day or two.... It is that way with the whole behavior shield or just the one item in the expert settings mentioned above.....
-
is your behavior shield set to auto decide? Mine is and all boxes checked.
-
is your behavior shield set to auto decide? Mine is and all boxes checked.
I have tried it with both Auto decide and ask. It does not seem to make a difference.
I do have the one box unchecked ('Monitor the system for unauthorized modifications') as that is the only way I can get consistant printing. Once I check that, my printing dies either later that day or the following day.
-
Sorry to reply to myself, but just an update....
I have left avast! with that one box of the Behavior shield unchecked and that has clearly solved the issue. As it had recurred sometimes after a few days, I had this fear, early on, that the problem would show back up, but it hasn't.
Today, avast! support replied to the ticket I put in earlier. Basically, they said there will be changes to the Behavior Shield in avast! 7 and that I should wait and see if that resolves the issue. I understand that.... With a new release coming out, no need to try to fix a problem in the soon to be old version....
That does bring up a question. Things I have seen in these forums and even the tone of the support reply indicate that there have been some problems with the Behavior Shield being imperfect. So, has the Behavior Shield had issues? I am not asking to complain, but rather trying to find solace that other had issues with that shield as well...
-
That does bring up a question. Things I have seen in these forums and even the tone of the support reply indicate that there have been some problems with the Behavior Shield being imperfect. So, has the Behavior Shield had issues? I am not asking to complain, but rather trying to find solace that other had issues with that shield as well...
Its not that it causes regular conflict problems. It has just so far been more or less useless in the eyes of us users. There are apparently things that it does "under the hood", so to speak, involving auto-subission of suspicious files for further analysis. But it is utterly passive in its default auto-decide mode, it detects/blocks nothing that I have ever seen or heard of. So its hard to have faith in a feature you are not seeing direct results with.
-
I do have the one box unchecked ('Monitor the system for unauthorized modifications') as that is the only way I can get consistant printing. Once I check that, my printing dies either later that day or the following day.
Well all good things come to an end...My system is now doing the same thing..not sure what changed but I'm glad I was in this thread so the solution was easy... :)