Defense+ Conflict with Microsoft Office Starter

[Guest]

[Valentin N]

Could you make bug report in the bug report? Thanks

Regards,
            Valentin N

[BenBrereton]

Hi Valentin N. I originally opened this task in the bug reports area but it was quickly moved out of there by the moderator, Dennis2. Perhaps my opening entry wasn't clear enough?

I'll open another task in the bug reports area referencing this one to see if I can get it moved back.

[BenBrereton]

For info, I have reported it as a bug. It turns out the problem with my first attempt was probably that I didn't use the right format. This has now been moved to the verified section. The topic is here:

https://forums.comodo.com/format-verified-issue-reports-cis/defense-conflict-with-microsoft-office-starter-nbz-t70696.0.html

[Digitaluke33]

Hi BenBrereton,

Could you try to put the whole Q drive in a new group of Protected Files and Folders. To do that : Defense+ > Computer Security Policy > Potected Files and Flders > Goup > give it  a name  > apply

You'll find your new group at the bottom of the list. Then right click on add files here > add > existing items > choose Q > drag to selected items > apply.

In Protected files and Folders : add > group > choose your new group > ok

In Computer Security Policy > Defense + rules > add > select > files group > choose your new group and give it the predefined policy installer/updater

Normally, Def+ will now let everything on drive Q run without problem.

NB: you'll maybe will have also to click in Def+ Settings > sandbox settings :
automatically detect installers/updaters and run them outside the sandbox
automatically trust files from trusted installers


Tell me please if this works.


Boris

Just for the record - this solution worked perfectly for me.

My issue was Word Starter 2010 would not recognize any printers as being installed when Defense+ was in Safe mode, but in Clean PC mode everything worked fine. In Safe mode D+ would flag certain Word files as Unrecognized Files no matter how many times I would "Move to > Trusted Files" that file.

Thank you Boris, D+ is now running in Safe mode and my printers are working perfectly!

[mouse1]

Just for the record - this solution worked perfectly for me.

My issue was Word Starter 2010 would not recognize any printers as being installed when Defense+ was in Safe mode, but in Clean PC mode everything worked fine. In Safe mode D+ would flag certain Word files as Unrecognized Files no matter how many times I would "Move to > Trusted Files" that file.

Thank you Boris, D+ is now running in Safe mode and my printers are working perfectly!

Does this fix survive a reboot? If so you are lucky!

[mouse1]

On reflection think this fix a significant security risk. You are defining the whole drive as an installer updater...

If instead you just define the problematic files as installer updaters, that would be a bit more fiddly, but fine. Assuming the definition survives reboot (watch out for purge too)

This needs a proper resolution I think....

Best wishes

Mouse

[sleepydog]

I have been trying to help a friend with a very similar problem.  CIS and Microsoft Office 2010 running together results in MS Word not being able to print.  Winword.exe is continually sandboxed and partially disabled by Comodo no matter what I do.  If I disable Defense+ everything works fine.    I do not mean to hijack this thread - I just want you to know that in some circumstances CIS and MS Office do not get along well.

[michalko58]

I have the same problem with latest version of CIS (5.8.213334.2131). If Defense+ is set to Clean PC Mode everything works fine, but in Safe Mode no printer is visible in Word (and Excel) Starter 2010. 

[Valentin N]

I have the same problem with latest version of CIS (5.8.213334.2131). If Defense+ is set to Clean PC Mode everything works fine, but in Safe Mode no printer is visible in Word (and Excel) Starter 2010. 

could you provide us your d+ events?

[michalko58]

Unfortunately not, because that computer was controlled remotely via Logmein (Windows 7 Professional 64bit, Comodo 64bit) . But I have found later solution for this problem here: https://forums.comodo.com/format-verified-issue-reports-cis/defense-conflict-with-microsoft-office-starter-nbz-t70696.30.html

mouse1, thank You! The problem is SOLVED!

1. Run Word
2. Allow global hook MSCTF.dll
3. Close Word
4. Go to Defense+ ~ Computer Security Policy ~ Defense+ Rules ~ Double-click on "Q:\....\WINWORD.EXE" ~ Use a Predefined Policy [Installer or Updater] ~ Apply ~ OK
5. Run Word
6. Allow CVH.EXE

Repeat these operations for Excel / PowerPoint / OneNote.

[Valentin N]

Unfortunately not, because that computer was controlled remotely via Logmein (Windows 7 Professional 64bit, Comodo 64bit) . But I have found later solution for this problem here: https://forums.comodo.com/format-verified-issue-reports-cis/defense-conflict-with-microsoft-office-starter-nbz-t70696.30.html

You have given word,exe god right, so look at the ending. if it has exe than is a malware , such as avi.exe, jpg.exe and so on.

Regards,
            Valentin N

[michalko58]

It is pre-installed Office 2010 Starter (which is creating secured partition Q:\, where CIS cannot access), by HP, so it isn´t malware. This was the only solution to make the printer visible for Word and Excel.

And the god right is only for word.exe and excel.exe from Q drive.

[TORL]

I had the printing problem with Word Starter and solved it including CVH.exe (located in C:\Program Files (x86)\Common Files\microsoft shared\Virtualization Handler) in Defence+ Settings - Execution Control Settings - Exclusions.

[ildome]

I have printing network problems too.

For me this doesn't work:

... including CVH.exe ... in Defence+ Settings - Execution Control Settings - Exclusions.

But word can see the printer adding

Code:

Q:\*.*

in Defence+ Settings -> Execution Control Settings -> Exclusions

But I can't print, if sandbox is enabled.
Works if defence+ level is on "clean pc"

[cruelsister]

Same thing is happening to a friend with Office Starter. No amount of playing around prevents files from being sandboxed which results in the inability to print.

As Office Starter is preloaded on many computers currently, this issue may bar many from sticking with CIS. which would be a shame.

[Tags:]