topic Re: Errors went after the new 2024.2 update in Maya Creative Forum

Errors went after the new 2024.2 update

thenewkgb82 — Tue, 21 Nov 2023 18:23:42 GMT

I did want an answer for why errors and warnings filled my MEL prompt. These are only the errors, ignoring warnings...

// Error: file: C:/Program Files/Autodesk/MayaCreative2024/scripts/others/typeInitPlugin.mel line 37: File C:/Program Files/Autodesk/MayaCreative2024/bin/plug-ins/svgFileTranslator.py does not have a valid digital signature and is not authorized for use with this application // Error: file: C:/Program Files/Autodesk/MayaCreative2024/scripts/others/typeInitPlugin.mel line 37: (svgFileTranslator) evalDeferred "shaderBallRendererMenuUpdate"; import arnold import mtoa import mtoa.cmds.registerArnoldRenderer;mtoa.cmds.registerArnoldRenderer.registerArnoldRenderer() # Error: file: C:/Program Files/Autodesk/MayaCreative2024/scripts/startup/autoLoadPlugin.mel line 40: File C:/Program Files/Autodesk/MayaCreative2024/bin/plug-ins/renderSetup.py does not have a valid digital signature and is not authorized for use with this application # Error: file: C:/Program Files/Autodesk/MayaCreative2024/scripts/startup/autoLoadPlugin.mel line 40: (renderSetup) # Error: Register failed for arnoldAOVChildSelector

I tried resetting preferences by following this link:

Support - reset prefs

I don't have a new pref folder, but I did update to the latest version and now all the errors and warnings have gone. Either in a new scene or an old project I started.

The topic is quite unnecessary now, except when I started learning Maya and didn't know if errors would disrupt my experience. Especially the plugins. Errors have gone now.

Just as a note: Windows -> General -> Script Editor

Re: Errors went after the new 2024.2 update

richard_anywhere — Sat, 01 Mar 2025 01:02:21 GMT

If the error affects loading your scene, you can disable secure plugins/Python/MEL in Preferences under Security.

You will receive a warning if you do this, so only do this if you trust the plugins you are trying to use.

Maya Security Preferences

Re: Errors went after the new 2024.2 update

Mario-Cada — Fri, 04 Apr 2025 19:31:24 GMT

not working (Maya 2025.3), even after adding the plugins-folder to the list of trusted plugin locations and restarting the program.

"Error: file: C:/Program Files/Autodesk/MayaCreative2025/scripts/others/pluginWin.mel line 316: File C:/Program Files/Autodesk/MayaCreative2025/bin/plug-ins/svgFileTranslator.py does not have a valid digital signature and is not authorized for use with this application"

Re: Errors went after the new 2024.2 update

animatewithabhay — Sun, 25 Jan 2026 19:35:36 GMT

These errors appear because Maya Creative is a restricted version of Maya and does not allow certain plugins or Python modules to load, even though they still exist in the installation folder.

Why these errors appear in the MEL prompt:
Maya Creative scans the standard Maya plugin directories during startup. Some scripts and plugins (such as SVG import, Render Setup, and Arnold components) are present on disk but are not digitally signed or authorized for use in Maya Creative. When Maya attempts to initialize them, it blocks them and reports the error in the Script Editor.

Explanation of the main errors:

svgFileTranslator.py
This plugin is used for importing SVG files. Maya Creative does not support it, so the file is blocked due to missing authorization.
renderSetup.py
Render Setup is part of the full Maya rendering pipeline. Maya Creative does not support advanced rendering features, so this module is intentionally disabled.
Arnold-related errors (arnold, mtoa, arnoldAOVChildSelector)
Arnold is not supported in Maya Creative. Even though the Arnold files exist, they cannot register correctly, which causes startup errors.

Why this is not a crash or corruption:

Maya Creative is working as intended
These are startup initialization failures, not runtime errors
Autodesk leaves shared scripts in place for code compatibility, but blocks execution based on license type

Why warnings and errors still appear:
The Script Editor reports all failed plugin loads, even when the failure is expected. Maya does not silently hide these messages.

What you should do:

Nothing, if you are using Maya Creative intentionally
Do not try to manually enable these plugins
Do not disable plugin signature checking
Ignore these messages unless Maya features are actually broken

When this becomes a real problem:

If Arnold menus appear but do not work
If Maya fails to launch
If core modeling or animation tools stop functioning

In those cases, reinstalling or switching to Maya (full) instead of Maya Creative is the correct solution.