98
edits
Platform/Integration/InjectEject/Launcher Process/: Difference between revisions
Platform/Integration/InjectEject/Launcher Process/ (view source)
Revision as of 21:41, 24 July 2019
, 24 July 2019no edit summary
(Clarifications) |
No edit summary |
||
| Line 23: | Line 23: | ||
** Firefox will be affected by User Interface Privilege Isolation (UIPI); the Firefox UI is not allowed to communicate with other UI running at higher integrity levels. Since the user's desktop and other applications are most likely still running at high integrity level, the Firefox UI will not be able to communicate with them. This means that certain GUI features such as drag-and-drop will not work. | ** Firefox will be affected by User Interface Privilege Isolation (UIPI); the Firefox UI is not allowed to communicate with other UI running at higher integrity levels. Since the user's desktop and other applications are most likely still running at high integrity level, the Firefox UI will not be able to communicate with them. This means that certain GUI features such as drag-and-drop will not work. | ||
** We have an [https://support.mozilla.org/en-US/kb/windows-administrator-launcher-process-error-fix article in the SUMO Knowledge Base] instructing users on how to mitigate these issues. | ** We have an [https://support.mozilla.org/en-US/kb/windows-administrator-launcher-process-error-fix article in the SUMO Knowledge Base] instructing users on how to mitigate these issues. | ||
*** Note: '''Do not''' advise users to attempt these suggestions unless it is known for a fact that they are running as Administrator with UAC disabled. | *** Note: '''Do not''' advise users to attempt these suggestions unless it is known for a fact that they are running as Administrator with UAC disabled! It is not a "catch-all" solution for launcher process problems. | ||
=== Starting Firefox via Automation / Scripting === | === Starting Firefox via Automation / Scripting === | ||