Having trouble while installing Creative Cloud app extensions or plugins? Quickly find solutions to some common errors that you might encounter during installation.
Marketplace tab doesn’t show in Creative Cloud desktop app
If you don’t see the Stock & Marketplace tab in the Creative Cloud desktop app, it’s likely that you are using Windows on ARM. We are working to ensure plug-in support for Windows computers that use ARM processors. In the meantime, we recommend that you install and run your plug-ins on Windows computers that use Intel processors.
Cannot install Adobe XD plugins from Marketplace
Your Adobe XD plugins can only be installed from the Stock & Marketplace tab in the Creative Cloud desktop app. If you don’t have the latest version of Adobe XD and try to install an XD plugin, you get the following error message:
Fix error «Something went wrong. You might not see all of your plugins.»
It might happen that the Adobe Exchange website shows your acquired plugins, but they don’t show in the Creative Cloud desktop app. In this case, you get the following error message: «Something went wrong. You might not see all of your plugins.»
You can fix this issue with the following steps:
Once the Creative Cloud desktop app finishes loading, your acquired plugins or extensions show up in the Stock & Marketplace tab.
Prompted to open app in Intel emulation mode after installing plugin
When you install a plugin or extension on Mac computers with Apple Silicon, you are prompted to open the app in Intel emulation mode.
To open the app in Intel emulation mode, do the following:
Not seeing your plugins when signing in from your Business ID?
Sometimes, plugins aren’t migrated after your business account is upgraded.
Sign in to the Creative Cloud desktop app with the appropriate Profile and re-install the plugins. If you require a plug-in for multiple profiles, repeat the process for each profile.
Find solution for your error code
Find your error code in the following table and follow the given solutions.
How to fix errors when installing plugins from the Creative Cloud desktop app
| Error code | Error message or description | How to fix the error |
|
-1 |
Unknown Error |
Quit the Creative Cloud desktop app and the installed app. Then, relaunch the Creative Cloud desktop app and try installing the extension or plugin again. |
| -2 | File System Error |
The file system errors are usually permission errors or are related to disk space. Free some space on the disk. Then, relaunch the Creative Cloud desktop app and try installing the extension or plugin again. If this doesn’t work, quit the Creative Cloud desktop app and the installed app. Then try installing the extension or plugin again. |
|
-3 |
Extraction failure |
Error -3 indicates that the compressed plugin file is corrupt, is missing one of the plugin files, or has run out of disk space. Free some space on the disk. Quit the Creative Cloud desktop app and the installed app. Relaunch the Creative Cloud desktop app and try installing the extension or plugin again. |
|
-4 |
Manifest Parse failure |
Quit the Creative Cloud desktop app and the installed app. Then, relaunch the Creative Cloud desktop app and try installing the extension or plugin again. |
|
-5 |
Internal parsing failure |
Quit the Creative Cloud desktop app and the installed app. Then, relaunch the Creative Cloud desktop app and try installing the extension or plugin again. |
|
-6 |
Plugin not compatible |
Error code -6 indicates that the downloaded plugin is not compatible with any of the installed apps. An extension or plugin installed on Adobe Exchange does not get added to your Creative Cloud app if the app version is not compatible with the extension. Similarly, if you update your app and it is no longer compatible with the extension or plugin, it won’t appear in the app. Install a compatible app, and quit the Creative Cloud desktop app and the installed app. Then, relaunch the Creative Cloud desktop app and try installing the extension or plugin again. If the above solution doesn’t work, try the solutions on this page in the given order. |
|
-7 |
Download failure |
First, make sure that you are connected to the Internet. Then, check to see that you are signed in to the Adobe Exchange website and the Creative Cloud desktop app with the same account. |
|
-8 |
No Internet connection |
Check the Internet connection, and quit the Creative Cloud desktop app and the installed app. Then, relaunch the Creative Cloud desktop app and try installing the extension or plugin again. |
| -9 | Connection timeout | Check the Internet connection, and quit the Creative Cloud desktop app and the installed app. Then, relaunch the Creative Cloud desktop app and try installing the extension or plugin again. |
|
-10 |
Invalid extension |
Quit the Creative Cloud desktop app and the installed app. Then, relaunch the Creative Cloud desktop app and try installing the extension or plugin again. |
|
-11 |
Database update failure |
Quit the Creative Cloud desktop app and the installed app. Then, relaunch the Creative Cloud desktop app and try installing the extension or plugin again. |
| -12 |
Task canceled |
Quit the Creative Cloud desktop app and the installed app. Then, relaunch the Creative Cloud desktop app and try installing the extension or plugin again. |
| -13 | User canceled the operation | Quit the Creative Cloud desktop app and the installed app. Then, relaunch the Creative Cloud desktop app and try installing the extension or plugin again. |
| -14 |
The application is running but not responsive |
Quit the Creative Cloud desktop app and the installed app. Then, relaunch the Creative Cloud desktop app and try installing the extension or plugin again. |
| -15 | Application not reachable | Quit the Creative Cloud desktop app and the installed app. Then, relaunch the Creative Cloud desktop app and try installing the extension or plugin again. |
| -16 | Incorrect package returned | Quit the Creative Cloud desktop app and the installed app. Then, relaunch the Creative Cloud desktop app and try installing the extension or plugin again. |
| -17 | Timeout Error | This error occurs when you haven’t entered your account credentials on being prompted, leading to a timeout. To fix this issue, retry the operation and enter the credentials when prompted. |
| -18 | User is not signed in | This error occurs when you aren’t signed in. To fix this issue, ensure that you are signed in to the Creative Cloud desktop app. |
| -19 | Operation failed | Quit the Creative Cloud desktop app. Then, relaunch the Creative Cloud desktop app and try the operation again. If the issue still occurs, reinstall the Creative Cloud desktop app. |
| -20 | Operation failed | Quit the Creative Cloud desktop app. Then, relaunch the Creative Cloud desktop app and try the operation again. If the issue still occurs, reinstall the Creative Cloud desktop app. |
| -21 | Adobe application compatible with the extension is currently running. Please quit the application and retry. | Quit the app compatible with the plugin and then try to install the extension or plugin again. |
| -22 |
Plugin installer is not ready |
Quit the Creative Cloud desktop app. Then, relaunch the Creative Cloud desktop app and try installing the extension or plugin again. |
| -23 | Failed signature verification |
This error occurs for UXP hybrid plugins when they are not signed. Request the developer to sign the executables in the plugin. |
| -24 | Extension is not entitled |
Acquire the entitlement for the plugin and try installing the plugin again. |
| -152 | Couldn’t install plugin | This error only occurs on macOS Catalina and later versions. To fix this error, go to System Settings > Privacy & Security > Full Disk Access. Select Add an application and then add the Creative Cloud desktop app, if not already present. Turn on the settings for the Creative Cloud desktop app. Then, relaunch the Creative Cloud desktop app and try installing the extension or plugin again. |
| 1001 | Entitlement not found |
|
| 1002 | Permission issue |
This error occurs when you haven’t entered your account credentials on being prompted. Try to install the plugin or extension again and enter your credentials when prompted. |
| 1003 | Plugin operation timeout | Check the Internet connection, and quit the Creative Cloud desktop app and the installed app. Then, relaunch the Creative Cloud desktop app and try installing the extension or plugin again. |
How to fix errors when installing plugins from ExManCmd tool or Unified Plugin Installer Agent (UPIA)
| Error code | Error message or description | How to fix the error |
| -175 | The Add-on failed to install: It requires escalated privileges. |
This error occurs if you do not have administrator access to install applications on your computer, or if you select No or Cancel when prompted to enter an administrator password. To fix this error, you need to enter the administrator password if it is requested during installation. Try to install the extension or plugin again. Go to Stock & Marketplace in the Creative Cloud desktop app. Find the extension, and if it is installed, select Uninstall. Wait for two minutes for the removal to complete, then select Install. Select the notification message when it appears. Enter your administrator password if prompted, and select Yes in the notification dialog. (Windows only) If the issue persists, open the Task Manager and go to the Details tab. Select the process AdobeExtensionsService.exe, and then select End task. Once the background process closes, try to install the plugin again. |
| -192 | Extension Manager init failed, status = -192!
Your version of the Creative Cloud desktop app is incompatible with the ExMan Command Tool. Please update your Creative Cloud app and try again.
|
Update to the latest version of the Creative Cloud desktop app and then try to install your extension or plugin. |
| -201, 204 | Couldn’t install plugin | This error only occurs on macOS Catalina and later versions. To fix this error, go to System Settings > Privacy & Security > Full Disk Access. Select Add an application and then add the Creative Cloud desktop app, if not already present. Turn on the settings for the Creative Cloud desktop app. Then, relaunch the Creative Cloud desktop app and try installing the extension or plugin again. |
| -402 | Failed signature verification | This error occurs when the plugin is not signed. Request the developer to sign the plugin. |
| -403, -411 | Compatible Creative Cloud app not found. | Install a compatible version of the Creative Cloud application before installing the extension. Once the application is installed, try installing the extension again |
| -407, -408 | Another Add-on required by this one is not installed or enabled. | Check which extensions or plugins must be installed first by reading the description of the extension or plugin you are trying to install. Install the required extension or plugin first, and then reinstall the one you were trying to install. |
| -412 | An Add-on with the same name is already installed. | Check that the extension or plugin you have already installed is the one you want. If it is a different product with the same name and you want the one available through Creative Cloud Marketplace, you must uninstall the one that is currently installed. Then reinstall the extension or plugin through Creative Cloud Marketplace. |
| -418 | A newer version of this Add-on is already installed. | If you want the specific version being offered through Creative Cloud Marketplace, you must remove the newer version that you have previously installed. Then reinstall the older version through Creative Cloud Marketplace. Go to Plugins in Creative Cloud Marketplace, find the extension or plugin, and if it is already installed, select Uninstall. Wait two minutes for the removal to complete, then select Install. |
| -456 |
Case 1: The Add-on requires the relevant Creative Cloud apps to be closed to complete the installation/update. Case 2: The Add-on requires its compatible Adobe application to be closed to complete the installation/update. |
Quit the compatible Creative Cloud applications that are running. Then, try installing/updating the extension or plugin again. |
| -458 | None of the required Adobe applications have been installed. |
An extension or plugin installed on Adobe Exchange does not get added to your Creative Cloud app if the app version is not compatible with the extension or plugin. Similarly, if you update your app and it is no longer compatible with the extension or plugin, they won’t appear in the app. Install at least one compatible Creative Cloud application that supports this extension (plugin or add-on), and then try installing the extension or plugin again. |
| -459 | Installation failed because it is incompatible with installed Adobe applications. |
An extension or plugin installed on Adobe Exchange does not get added to your Creative Cloud app if the app version is not compatible with the extension or plugin. Similarly, if you update your app and it is no longer compatible with the extension or plugin, they won’t appear in the app. Install at least one compatible Creative Cloud application that supports this extension (plugin or add-on), and then try installing the extension or plugin again. |
| -1xx (-151 to -191) | There was a file operation error when installing this Add-on. | The extension or plugin is corrupted. Try installing it again. |
| -2xx (-251 to -278) | There was a file operation error when installing this Add-on. | The extension or plugin is corrupted. Try installing it again. |
| -5xx (-500 to -513) | Failed to update the database | The extension or plugin is corrupted. Try installing it again. |
| -506 | You are trying to install a plugin using the UPIA tool when it is already installed through the Creative Cloud desktop app. | Uninstall your plugin or extension from the Creative Cloud desktop app and then install it using the UPIA tool. |
| -602 | License check failed, or you are using an encrypted plugin without signing into the Creative Cloud desktop app. |
This error may occur when either the plugin installation is tied with administrator privileges, or when you are signed out of the Creative Cloud desktop app. To fix this error:
|
| -6xx (-601, -602, -603, -604, -651, -652, -653) | Your license failed to validate, or you are using an encrypted plugin when the Creative Cloud desktop app is not installed. |
This error may occur when either the plugin is corrupted, or when you don’t have the Creative Cloud desktop app installed on your device. To fix this error:
|
| -629 | Admin privileges not provided | This error occurs when you deny the admin credentials when prompted. To fix this issue, retry the operation and provide the admin credentials when prompted. |
| -630 | Timeout Error |
This error occurs when you haven’t entered your account credentials upon being prompted, leading to a timeout. To fix this issue, retry the operation and enter the credentials when prompted. |
| -631 | Request failed | This issue occurs when you are trying to install extensions or plugins using the Universal Plugin Installer Agent (UPIA) while being signed out of the Creative Cloud desktop app. To fix this issue, sign in to the Creative Cloud desktop app. Then try installing your extension or plugin. |
| -641, -642 | Couldn’t install plugins | This error occurs when you are trying to install extensions or plugins using commands with sudo on the Universal Plugin Installer Agent (UPIA) command-line tool. To fix this issue, open the Creative Cloud desktop app. Then try installing your extension or plugin. |
| -643, -644 | Internal communication failure | Relaunch the Creative Cloud desktop app and try performing the plugin operation again. |
| -645 |
Failed to launch CCD | Relaunch the Creative Cloud desktop app and try performing the plugin operation again |
| -646 |
Plugin Installer init failed | Reinstall the Creative Cloud desktop app and retry the plugin operation. |
Share log files of the installation with Adobe Customer Care so we can help diagnose the issue.
С недавних пор для After Effects стали появляться скрипты (правильнее их называть «расширениями») в формате ZXP. Они обладают более широкими возможностями, например OVERLORD позволяет запускать себя и в After Effects и в Illustrator и при этом обмениваться данными между этими программами на лету. Для установки такого формата на сайте aescripts.com создали специальную программу ZXP Installer — бесплатный установщик CEP расширений для Adobe After Effects и Premiere Pro:
https://aescripts.com/learn/zxp-installer/
ZXP — это новый формат пакета расширений на основе ZIP. Расширения ZXP имеют ту же функциональность, что и традиционные расширения MXP. Помимо этого, расширения ZXP могут включать цифровую подпись издателя расширения.
Мы же поговорим о ручной установке необходимых файлов в операционную систему. Так как ZXP — это простой архив ZIP архив, их нужно вначале разархивировать в отдельную папку. В ее корне должен находится файл mimetype и папка CSXS, ну и другие возможно тоже.
Эту папку надо переместить в один из каталогов:
- Для всех пользователей
c:Program Files (x86)Common FilesAdobeCEPextensions - Для конкретного пользователя
c:Users***AppDataRoamingAdobeCEPextensions
Теперь при запуске программы After Effects вы сможете обнаружить свои установленные расширения в разделе меню Window — Extensions.
Однако некоторым расширениями может понадобится еще кое-что. В реестре Windows надо добавить ключ «PlayerDebugMode» со значением 1 по адресу HKEY_CURRENT_USER/Software/Adobe/CSXS.5 А возможно и с другими номерами для более поздних версий. На момент написания статьи мне было известно CSXS.5, CSXS.6, CSXS.7 и CSXS.8. На всякий случай прилагаю файлик реестра с нужными данными, который достаточно запустить и переменный сами импортируются.
Код: Выделить всё
Windows Registry Editor Version 5.00
[HKEY_CURRENT_USERSoftware]
[HKEY_CURRENT_USERSoftwareAdobe]
[HKEY_CURRENT_USERSoftwareAdobeCSXS.6]
"PlayerDebugMode"="1"
[HKEY_CURRENT_USERSoftwareAdobeCSXS.7]
"PlayerDebugMode"="1"
[HKEY_CURRENT_USERSoftwareAdobeCSXS.8]
"PlayerDebugMode"="1"
[HKEY_CURRENT_USERSoftwareAdobeCSXS.5]
"PlayerDebugMode"="1"
Для новых версий еще нужно и
Код: Выделить всё
[HKEY_CURRENT_USERSoftwareAdobeCSXS.9]
"PlayerDebugMode"="1"
И на будущее смотрите в ветке HKEY_CURRENT_USERSoftwareAdobe новые CSXS.*
Полезные ссылки:
- ZXP Installer — aescripts.com
https://aescripts.com/learn/zxp-installer/ - ZXP Installer FAQ — aescripts.com
https://aescripts.com/knowledgebase/ind … aller-faq/ - Adobe Extension Manager — Создание пакетов и передача расширений
https://help.adobe.com/ru_RU/extensionm … 7fe9a.html
Причин появления несколько: неполная установка, повреждение реестра из-за изменения (установки или удаления), вредоносное ПО и т.д.
Как исправить?
Просканируйте ПК на вирусы вредоносное ПО.
Есть вероятность, что проблема связана с заражением компьютера. Вирусы повреждают или удаляют файлы. Поэтому очистка, вероятно, решит возникшую проблему.
Очистите систему от временных документов и папок.
Как запустить очистку диска в Виндовс XP, Vista, 7, 8 и 10?
- Нажимаем Winkey + R.
- Печатаем «cleanmgr» -> Enter.
- Откроется диалоговое окно «очистка диска», содержащее флажки. В большинстве, категория «временные файлы» занимает большую часть.
- Установите флажки напротив не использующихся категорий и примените.
- Поставьте автоматическое обновление драйверов устройств.
Ошибки 193 иногда связаны с повреждением или устареванием драйверов
- Запустите sysdm.cpl. Для этого используйте кнопки «Winkey + R», вбейте «sysdm.cpl» в командной строке и тапните Enter.
- В окне «свойства системы» кликните вкладку «оборудование».
- В «параметрах установки устройств» проверьте настройку автоматического обновления.
- На той же вкладке найдите диспетчер устройств.
- Не установленные или поврежденные драйверы обозначаются желтым знаком восклицания.
- Обновите автоматически или вручную.
Используйте «восстановление системы Виндовс» для отмены последних изменений.
Это вернет файлы и программы на вашем ПК к тому времени, когда все работало нормально. Произведите следующие шаги:
- Нажмите «пуск».
- В поисковой строке введите «Восстановление системы» и нажмите «ок».
- В окне результатов выберите «Восстановление».
- По инструкциям уже «мастера настроек» завершите работу.
- Запустите проверку системных файлов Windows («sfc /scannow»).
Весьма удобный инструмент, позволяющий просканировать и исправить поврежденные файлы (включая те, что имеют отношение к ошибка 193).
- Выберите «пуск».
- Введите «cmd».
- Запустите от имени администратора.
- Наберите «sfc /scannow» и Enter.
- Проверка начнет сканирование на наличие проблем.
- Завершите процедуру по инструкциям на экране.
How to fix the Runtime Code 193 Adobe After Effects Error 193
This article features error number Code 193, commonly known as Adobe After Effects Error 193 described as Error 193: Adobe After Effects has encountered a problem and needs to close. We are sorry for the inconvenience.
About Runtime Code 193
Runtime Code 193 happens when Adobe After Effects fails or crashes whilst it’s running, hence its name. It doesn’t necessarily mean that the code was corrupt in some way, but just that it did not work during its run-time. This kind of error will appear as an annoying notification on your screen unless handled and corrected. Here are symptoms, causes and ways to troubleshoot the problem.
Definitions (Beta)
Here we list some definitions for the words contained in your error, in an attempt to help you understand your problem. This is a work in progress, so sometimes we might define the word incorrectly, so feel free to skip this section!
- Adobe — Adobe Systems is a software company headquartered in San Jose, California, USA
- Effects — Non functional enhancements of user interaction with a product most commonly visual and sound
Symptoms of Code 193 — Adobe After Effects Error 193
Runtime errors happen without warning. The error message can come up the screen anytime Adobe After Effects is run. In fact, the error message or some other dialogue box can come up again and again if not addressed early on.
There may be instances of files deletion or new files appearing. Though this symptom is largely due to virus infection, it can be attributed as a symptom for runtime error, as virus infection is one of the causes for runtime error. User may also experience a sudden drop in internet connection speed, yet again, this is not always the case.
(For illustrative purposes only)
Causes of Adobe After Effects Error 193 — Code 193
During software design, programmers code anticipating the occurrence of errors. However, there are no perfect designs, as errors can be expected even with the best program design. Glitches can happen during runtime if a certain error is not experienced and addressed during design and testing.
Runtime errors are generally caused by incompatible programs running at the same time. It may also occur because of memory problem, a bad graphics driver or virus infection. Whatever the case may be, the problem must be resolved immediately to avoid further problems. Here are ways to remedy the error.
Repair Methods
Runtime errors may be annoying and persistent, but it is not totally hopeless, repairs are available. Here are ways to do it.
If a repair method works for you, please click the upvote button to the left of the answer, this will let other users know which repair method is currently working the best.
Please note: Neither ErrorVault.com nor it’s writers claim responsibility for the results of the actions taken from employing any of the repair methods listed on this page — you complete these steps at your own risk.
Method 7 — IE related Runtime Error
If the error you are getting is related to the Internet Explorer, you may do the following:
- Reset your browser.
- For Windows 7, you may click Start, go to Control Panel, then click Internet Options on the left side. Then you can click Advanced tab then click the Reset button.
- For Windows 8 and 10, you may click search and type Internet Options, then go to Advanced tab and click Reset.
- Disable script debugging and error notifications.
- On the same Internet Options window, you may go to Advanced tab and look for Disable script debugging
- Put a check mark on the radio button
- At the same time, uncheck the «Display a Notification about every Script Error» item and then click Apply and OK, then reboot your computer.
If these quick fixes do not work, you can always backup files and run repair reinstall on your computer. However, you can do that later when the solutions listed here did not do the job.
Method 1 — Close Conflicting Programs
When you get a runtime error, keep in mind that it is happening due to programs that are conflicting with each other. The first thing you can do to resolve the problem is to stop these conflicting programs.
- Open Task Manager by clicking Ctrl-Alt-Del at the same time. This will let you see the list of programs currently running.
- Go to the Processes tab and stop the programs one by one by highlighting each program and clicking the End Process buttom.
- You will need to observe if the error message will reoccur each time you stop a process.
- Once you get to identify which program is causing the error, you may go ahead with the next troubleshooting step, reinstalling the application.
Method 2 — Update / Reinstall Conflicting Programs
Using Control Panel
- For Windows 7, click the Start Button, then click Control panel, then Uninstall a program
- For Windows 8, click the Start Button, then scroll down and click More Settings, then click Control panel > Uninstall a program.
- For Windows 10, just type Control Panel on the search box and click the result, then click Uninstall a program
- Once inside Programs and Features, click the problem program and click Update or Uninstall.
- If you chose to update, then you will just need to follow the prompt to complete the process, however if you chose to Uninstall, you will follow the prompt to uninstall and then re-download or use the application’s installation disk to reinstall the program.
Using Other Methods
- For Windows 7, you may find the list of all installed programs when you click Start and scroll your mouse over the list that appear on the tab. You may see on that list utility for uninstalling the program. You may go ahead and uninstall using utilities available in this tab.
- For Windows 10, you may click Start, then Settings, then choose Apps.
- Scroll down to see the list of Apps and features installed in your computer.
- Click the Program which is causing the runtime error, then you may choose to uninstall or click Advanced options to reset the application.
Method 3 — Update your Virus protection program or download and install the latest Windows Update
Virus infection causing runtime error on your computer must immediately be prevented, quarantined or deleted. Make sure you update your virus program and run a thorough scan of the computer or, run Windows update so you can get the latest virus definition and fix.
Method 4 — Re-install Runtime Libraries
You might be getting the error because of an update, like the MS Visual C++ package which might not be installed properly or completely. What you can do then is to uninstall the current package and install a fresh copy.
- Uninstall the package by going to Programs and Features, find and highlight the Microsoft Visual C++ Redistributable Package.
- Click Uninstall on top of the list, and when it is done, reboot your computer.
- Download the latest redistributable package from Microsoft then install it.
Method 5 — Run Disk Cleanup
You might also be experiencing runtime error because of a very low free space on your computer.
- You should consider backing up your files and freeing up space on your hard drive
- You can also clear your cache and reboot your computer
- You can also run Disk Cleanup, open your explorer window and right click your main directory (this is usually C: )
- Click Properties and then click Disk Cleanup
Method 6 — Reinstall Your Graphics Driver
If the error is related to a bad graphics driver, then you may do the following:
- Open your Device Manager, locate the graphics driver
- Right click the video card driver then click uninstall, then restart your computer
Other languages:
Wie beheben Fehler 193 (Adobe After Effects-Fehler 193) — Fehler 193: Adobe After Effects hat ein Problem festgestellt und muss geschlossen werden. Wir entschuldigen uns für die Unannehmlichkeiten.
Come fissare Errore 193 (Errore di Adobe After Effects 193) — Errore 193: Adobe After Effects ha riscontrato un problema e deve essere chiuso. Ci scusiamo per l’inconveniente.
Hoe maak je Fout 193 (Adobe After Effects-fout 193) — Fout 193: Adobe After Effects heeft een probleem ondervonden en moet worden afgesloten. Excuses voor het ongemak.
Comment réparer Erreur 193 (Erreur 193 d’Adobe After Effects) — Erreur 193 : Adobe After Effects a rencontré un problème et doit se fermer. Nous sommes désolés du dérangement.
어떻게 고치는 지 오류 193 (Adobe After Effects 오류 193) — 오류 193: Adobe After Effects에 문제가 발생해 닫아야 합니다. 불편을 끼쳐드려 죄송합니다.
Como corrigir o Erro 193 (Erro 193 do Adobe After Effects) — Erro 193: O Adobe After Effects encontrou um problema e precisa fechar. Lamentamos o inconveniente.
Hur man åtgärdar Fel 193 (Adobe After Effects Error 193) — Fel 193: Adobe After Effects har stött på ett problem och måste avslutas. Vi är ledsna för besväret.
Как исправить Ошибка 193 (Ошибка Adobe After Effects 193) — Ошибка 193: Возникла ошибка в приложении Adobe After Effects. Приложение будет закрыто. Приносим свои извинения за неудобства.
Jak naprawić Błąd 193 (Błąd Adobe After Effects 193) — Błąd 193: Adobe After Effects napotkał problem i musi zostać zamknięty. Przepraszamy za niedogodności.
Cómo arreglar Error 193 (Error 193 de Adobe After Effects) — Error 193: Adobe After Effects ha detectado un problema y debe cerrarse. Lamentamos las molestias.
About The Author: Phil Hart has been a Microsoft Community Contributor since 2010. With a current point score over 100,000, they’ve contributed more than 3000 answers in the Microsoft Support forums and have created almost 200 new help articles in the Technet Wiki.
Follow Us: 
Last Updated:
11/07/22 03:39 : A Android user voted that repair method 7 worked for them.
This repair tool can fix common computer problems such as blue screens, crashes and freezes, missing DLL files, as well as repair malware/virus damage and more by replacing damaged and missing system files.
STEP 1:
Click Here to Download and install the Windows repair tool.
STEP 2:
Click on Start Scan and let it analyze your device.
STEP 3:
Click on Repair All to fix all of the issues it detected.
DOWNLOAD NOW
Compatibility
Requirements
1 Ghz CPU, 512 MB RAM, 40 GB HDD
This download offers unlimited scans of your Windows PC for free. Full system repairs start at $19.95.
Article ID: ACX02062EN
Applies To: Windows 10, Windows 8.1, Windows 7, Windows Vista, Windows XP, Windows 2000
Speed Up Tip #72
Disabling Under Utilized Hardware:
Hardware devices on your computer such as DVD Drive, USB ports, IR ports and Firewire port can be easily disabled in the BIOS if not used. These devices can use up power resources and slow down boot up time.
Click Here for another way to speed up your Windows PC
Microsoft & Windows® logos are registered trademarks of Microsoft. Disclaimer: ErrorVault.com is not affiliated with Microsoft, nor does it claim such affiliation. This page may contain definitions from https://stackoverflow.com/tags under the CC-BY-SA license. The information on this page is provided for informational purposes only. © Copyright 2018
Некоторые пользователи сталкиваются с кодом ошибки Skyrim SE Error 193 при попытке модифицировать свою установку Skyrim SE. Подтверждено, что эта проблема возникает в Windows 7, Windows 8.1 и Windows 10.
Skyrim SE Ошибка 193
После тщательного изучения этой проблемы выясняется, что есть несколько разных виновников, которые могут вызвать этот конкретный код ошибки. Вот краткий список потенциальных виновников:
- Устаревшее программное обеспечение для извлечения. Некоторые затронутые пользователи смогли решить эту проблему после того, как поняли, что их стандартная утилита извлечения в конечном итоге повредила определенные файлы мода. Большинству из них удалось решить эту проблему, переключившись на 7Zip (вместо использования WinZip или WinRar).
- Отсутствует доступ администратора. Как оказалось, этот код ошибки также может появиться, если основная программа, которую вы используете для установки модов, не имеет доступа администратора для внесения необходимых изменений в основную игру или связанные с ней зависимости. В этом случае вы сможете решить проблему, заставив утилиту Mod Organizer открыться с правами администратора.
Метод 1: использование 7 Zip для распаковки модов
По словам некоторых затронутых пользователей, эта проблема может возникать из-за несоответствия с программным обеспечением для распаковки, которое вы используете при извлечении содержимого режима, который вы пытаетесь установить, или Skyrim SE.
В большинстве случаев проблема будет вызвана более старой установкой WinRar или WinZip, которая приводит к повреждению некоторых файлов внутри папки mob.
Если вы оказались в подобной ситуации, вам следует начать с использования 7Zip для извлечения содержимого архива вместо инструмента, который вы использовали раньше. Несколько затронутых пользователей сообщили, что им удалось решить проблему, установив 7 Zip и используя его для извлечения мода, который собирается установить в Skyrim SE.
Вот краткое руководство по всему процессу:
- Откройте браузер по умолчанию и откройте официальная страница загрузки 7Zip и нажмите кнопку загрузки, связанную с версией Windows, совместимой с вашим компьютером.
Скачивание последней версии 7Zip
- После завершения загрузки дважды щелкните программу установки и следуйте инструкциям на экране, чтобы завершить установку 7-Zip.
- После завершения установки перезагрузите компьютер, затем щелкните правой кнопкой мыши архив мода и выберите 7 Zip> Извлечь файлы (или Извлечь сюда).
Извлечение мода Skyrim с помощью 7Zip
- Следуйте инструкциям на экране, чтобы завершить извлечение, затем установите мод в обычном режиме и посмотрите, удалось ли вам избежать кода ошибки Skyrim SE Error 193.
Если та же проблема все еще возникает, перейдите к следующему потенциальному исправлению ниже.
Метод 2: открытие модуля запуска MO2 с доступом администратора
По словам некоторых затронутых пользователей, эта проблема также может возникнуть, если средство запуска модов, которое вы используете для установки и применения модов (скорее всего, Mod Organizer 2) не имеет доступа администратора.
Если этот сценарий применим, вы сможете решить проблему, принудительно запустив приложение Mod Launcher с правами администратора. Для этого щелкните его правой кнопкой мыши и выберите в контекстном меню «Запуск от имени администратора».
Запуск от имени администратора
Убедившись, что приложение Mod установлено правильно, примените моды в соответствии с инструкциями в специальном руководстве и посмотрите, решена ли проблема теперь, когда у приложения мода есть доступ администратора.