Acrobat Reader, Chrome, or Firefox do not work properly
技術的な記事 ID:
KB77179
最終更新: 11/13/2020
環境
McAfee Application and Change Control (MACC) 6.1
Adobe Acrobat Reader
Chrome
Firefox
問題
Adobe Acrobat Reader, Chrome, or Firefox do not work as expected when MACC 6.1 is enabled. A conflict exists between MACC 6.1 Memory Protection and the sandboxing technology used by the products. You see the following:
Acrobat Reader - Displays an error pop-up window while opening a PDF file.
Chrome - Browser opens a blank page with Memory Protection (MP) enabled.
Firefox - Hangs when a flash-intensive site is browsed.
解決策
This issue is resolved in MACC 6.2.0 and later. Technical Support recommends that you upgrade to one of these versions to resolve the issue.
McAfee product software, upgrades, maintenance releases, and documentation are available from the Product Downloads site.
Do the following to work around this issue for the respective browser:
For Chrome:
Create a shortcut for Chrome.
Right-click the new shortcut and click Properties.
Add the following to the target entry: -no-sandbox
Use this shortcut to start Chrome.
Or:
Click Start, Run, type cmd, and click OK.
Run the following command: chrome.exe –no-sandbox
For Adobe: CAUTION: This article contains information about opening or modifying the registry.
The following information is intended for System Administrators. Registry modifications are irreversible and could cause system failure if done incorrectly.
Do not run a REG file that is not confirmed to be a genuine registry import file.
Click Start, Run, type regedit,and click OK.
Navigate to: [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Adobe\Adobe Reader\11.0\FeatureLockDown\bProtectedMode]
Change the registry value to 0.
For Firefox: Disable Protected Mode:
Click Start, Run, type explorer,and click OK.
Navigate to the mms.cfg file in:
Windows (32-bit): C:\windows\system32\macromed\flash
Windows (64-bit): C:\windows\syswow64\macromed\flash
Add the following line to the mms.cfg file:
ProtectedMode=0
Save the changes.
回避策
If the first workaround does not help, bypass the process for Adobe and Chrome from MP-CASP and MP-VASR. Open a service request with Technical Support for assistance with setting up a bypass of the processes from MP.
