Skip to main content
Inspiring
September 24, 2018
Answered

AEP created in Win7 won't open on Win10.

  • September 24, 2018
  • 2 replies
  • 982 views

I'm trying to open an AE 2017 file created in Win7 on a laptop with Win10. I get numberous 1114 plugin errors and a corrupted file message. Same file opens fine on another Win 7 machine. The Win10 laptop is new. SSD's 64GB ram Quadro 4000. Not sure what the deal is. Thought my beefy laptop could help me render. But what's up? Everything has been updated to latests versions.

I'm not using AE2018 because its performance blows. But it won't open in 2018 either.

I just wanted to render some scenes on the laptop for a project that has some big scenes to render. But no deal.

Any idea what could be causing the problems? Plugins cited are stardust and tao. But the project doesn't even have all the layers in a main comp once opened. This project does have some pretty intense comps. But like I said, my older computer with Win7 had no problem with it.

Any help is appreciated. Thanks.

    This topic has been closed for replies.
    Correct answer little fat girl

    Things are working!!! And I *think* I know what it is. Thanks OussK for taking time to try to help me troubleshoot.

    I changed a lot of stuff around uninstalled everything (except the OS) and reinstalled. But in the end, I think it was that I have Quicktime Pro on my desktop and use it regularly as an output module. My new laptop didn't have it. I put Quicktime Pro on there today (because I like it) and around that time stuff starts working. It could have been one of the other things I did. But this seems the most likely. The ugly thing is that the error messages made things look like this was an issue with plugins.

    Here were the errors I got:

    After Effects error: plug-in "Stardust_controls_airforce.aex" could not be loaded (1114).

    (48 :: 46)

    After Effects error: plug-in "Stardust_controls_airforce.aex" could not be loaded (1114).

    (48 :: 46)

    After Effects error: plug-in "Stardust_controls_splitter.aex" could not be loaded (1114).

    (48 :: 46)

    After Effects error: plug-in "Stardust_controls_splitter.aex" could not be loaded (1114).

    (48 :: 46)

    After Effects error: plug-in "Stardust_controls_splitter.aex" could not be loaded (1114).

    (48 :: 46)

    After Effects error: plug-in "Stardust_controls_splitter.aex" could not be loaded (1114).

    (48 :: 46)

    After Effects error: plug-in "Stardust_controls_airforce.aex" could not be loaded (1114).

    (48 :: 46)

    After Effects error: plug-in "Stardust_controls_airforce.aex" could not be loaded (1114).

    (48 :: 46)

    After Effects error: plug-in "Mir_64.aex" could not be loaded (1114).

    (48 :: 46)

    After Effects error: plug-in "Mir_64.aex" could not be loaded (1114).

    (48 :: 46)

    After Effects error: plug-in "Stardust_controls_splitter.aex" could not be loaded (1114).

    (48 :: 46)

    After Effects error: plug-in "Stardust_controls_splitter.aex" could not be loaded (1114).

    (48 :: 46)

    After Effects error: Can't find layer ID=68962646 in composition "NCS Track Scene Particular Test".

    (26 :: 93)

    After Effects error: Can't find layer ID=68964114 in composition "NCS Track Scene Particular Test".

    (26 :: 93)

    After Effects error: Can't find layer ID=68962646 in composition "NCS Track Scene Particular Test".

    (26 :: 93)

    After Effects warning: your project file is apparently damaged (skipped sections: 6). Please save using a different name.

    (26 :: 0)

    2 replies

    little fat girlAuthorCorrect answer
    Inspiring
    September 26, 2018

    Things are working!!! And I *think* I know what it is. Thanks OussK for taking time to try to help me troubleshoot.

    I changed a lot of stuff around uninstalled everything (except the OS) and reinstalled. But in the end, I think it was that I have Quicktime Pro on my desktop and use it regularly as an output module. My new laptop didn't have it. I put Quicktime Pro on there today (because I like it) and around that time stuff starts working. It could have been one of the other things I did. But this seems the most likely. The ugly thing is that the error messages made things look like this was an issue with plugins.

    Here were the errors I got:

    After Effects error: plug-in "Stardust_controls_airforce.aex" could not be loaded (1114).

    (48 :: 46)

    After Effects error: plug-in "Stardust_controls_airforce.aex" could not be loaded (1114).

    (48 :: 46)

    After Effects error: plug-in "Stardust_controls_splitter.aex" could not be loaded (1114).

    (48 :: 46)

    After Effects error: plug-in "Stardust_controls_splitter.aex" could not be loaded (1114).

    (48 :: 46)

    After Effects error: plug-in "Stardust_controls_splitter.aex" could not be loaded (1114).

    (48 :: 46)

    After Effects error: plug-in "Stardust_controls_splitter.aex" could not be loaded (1114).

    (48 :: 46)

    After Effects error: plug-in "Stardust_controls_airforce.aex" could not be loaded (1114).

    (48 :: 46)

    After Effects error: plug-in "Stardust_controls_airforce.aex" could not be loaded (1114).

    (48 :: 46)

    After Effects error: plug-in "Mir_64.aex" could not be loaded (1114).

    (48 :: 46)

    After Effects error: plug-in "Mir_64.aex" could not be loaded (1114).

    (48 :: 46)

    After Effects error: plug-in "Stardust_controls_splitter.aex" could not be loaded (1114).

    (48 :: 46)

    After Effects error: plug-in "Stardust_controls_splitter.aex" could not be loaded (1114).

    (48 :: 46)

    After Effects error: Can't find layer ID=68962646 in composition "NCS Track Scene Particular Test".

    (26 :: 93)

    After Effects error: Can't find layer ID=68964114 in composition "NCS Track Scene Particular Test".

    (26 :: 93)

    After Effects error: Can't find layer ID=68962646 in composition "NCS Track Scene Particular Test".

    (26 :: 93)

    After Effects warning: your project file is apparently damaged (skipped sections: 6). Please save using a different name.

    (26 :: 0)

    OussK
    Community Expert
    Community Expert
    September 24, 2018

    I don't think it's a OS issue, it look like you have problem with your AE on windows 10, so try to remove and reinstalled again

    Inspiring
    September 24, 2018

    I tried reinstalling AE. No change. Is there some trick to it? I just uninstalled and reinstalled.

    I also tried running as administrator. I also tried importing my project into an open (empty) project. No change.