Word Problem Gets Black Screen

[lluner]

Dear , I am having problem when I run word 2013 , for now , on antivirus version 88.x .

No antivirus

With Endpoint version 87.52 

[the_rock]

I believe you can make an exception based on the file extension. Have you tried that?

Andy

[lluner]

Interesting before I had version 86.60 and didn't have this problem .when I updated to version 88.10 and 88.30 I started to have this kind of problem . I've created the exclusions and I'm going to check if it happens. I'm exclusions  excel.exe and word.exe

[the_rock]

Let us know if that works.

Andy

[PhoneBoy]

That would probably require a TAC case: https://help.checkpoint.com 

[JoseAquije]

Have you had any response or solution to this problem? I am going through the same scenario with all versions 88.1X onwards and with all of them the same fault occurs.

Jose

[the_rock]

I would definitely open TAC case for that.

[lluner · Accepted solution]

hi @JoseAquije 

I already opened a TAC  and so far nothing

WORDAROUND

Turn Off Hardware Acceleration in Office 2010 / 2013 Application

After a series of troubleshooting, I traced the problem to the accelerated graphics. Just disable the it. Here’s how:

1.   File menu,

2.   Options command

3.   Advanced option

4.   Scroll down to the Display section of the dialog,

5.   toggle the check the box for “Disable hardware graphics acceleration

Registry “Hack” to Disable Hardware Acceleration

1. Run regedit (Win + R ; “regedit”)

2. Browse to HKEY_CURRENT_USER\Software\Microsoft\Office\15.0\Common

3. Create a New Key and name it “Graphics”

4. Select Graphics, right-click on the right panel and create a New DWORD (32-bit) Value and name it DisableHardwareAcceleration.

5. Enter Value data as 1

It worked with the current user, when the user logs in the key is not in the registry. I'm trying to put it in the GPO. When it works I will inform you here

[JoseAquije]

Thank you very much,

The incident with the equipment has been solved. Indeed we would have to find how to launch it in a GPO, but this step by step helped me to solve the problem.

Best regards