avast 6 - Office Click to Run

[bob3160]

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

[ady4um]

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).

[hrova]

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.

[ady4um]

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.

[hrova]

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.

[bob3160]

@ady4um,
Let someone from Avast deal with it. 

[Dch48]

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.

[hrova]

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.

[Dch48]

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.

[hrova]

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....

[Dch48]

And I agree that it needs to be resolved. It may take a cooperative effort but it should be fixed.

[bob3160]

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

[claprood]

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

[claprood]

I should also  mention I have the 64 bit version of win 7 if that is relevant.

[hrova]

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...