Premiere Pro 22.3 Error Directory object cannot construct with this path.

[MWongSound]

Fresh install of Premiere Pro 22.3 today and when I lauch the Premiere Pro it comes up with the error "Directory object cannot construct with this path."  

Im on Big Sur 11.6.5, File & Folder permissions all checked, tried with full disk access as well with the same errror on launch.

Tried uninstalling and reinstalling, same error.

No idea what directory its trying to create.

[Jeff Bugbee]

Just FYI, generally, the plugin developer needs to adapt their plugin to work with the base software, not the other away around. 

According to this there are some legacy plugins that are not compatible with Big Sur: https://support.izotope.com/hc/en-us/articles/360052231634-Compatibility-with-macOS-11-Big-Sur

You may want to discuss with Izotope why their plugins are stopping your Adobe Apps from launching.

[MWongSound · Accepted solution]

Ok, so I hate having to answer myself since I seemed to have figured out the solution.   It has absolutely nothing to do with the iZotope plugins, it just happened to be the last thing on the splash to load.  

I was sucessfully able to get 22.3 to launch using the following:

I unintalled 22.3 (full removal since it never fully installed), reinstalled from CC.

When it initially started to launch 22.3, I went to inspect the premiere settings folder permissions in /Documents/Adobe/Premiere Pro/22.0 (im on a mac) and the 22.0 folder permissions were installed incorrectly.  It had the user as Read & Write and Staff set to Read Only and Everyone set to Read Only.

I changed the permission of staff to Read & Write while the plugins were loading the first time and that allowed the initial files Premiere needed to install correctly and fully launch.

I suspected it needed to write something from inspecting logs from earlier last week but just came about to actually thinking about it.  

Hopefully this helps the rest of you having issues!

[Jeff Bugbee]

My 22.0 folder is set to Read and Write, Staff set to Read only, and Everyone set to Read Only (just like yours was before) and my Premiere loads (and has always loaded) just fine. I do not have Izotope plugins installed. Other people in this thread with this exact issue also have Izotope plugins intalled.

I'm glad you were able to get it working but I'm not sure if that permission change resolved it. You may have applied the changes recursively, which changed something deeper in the folder hierarchy which allowed Izotope to successfully access the folder, but simply changing staff/wheel is unlikely to resolve your issue.

[Miles Emerson]

I am getting the same error message. No plug-ins installed. Just did a clean install of Premiere Pro and it failed to launch. I had the previous version installed but removed it as I was trying out other software. The previous version worked just fine, but this new version gives me the error message and will not launch. 

Has there been any progress on a solution to this?

Thanks,

Miles

[Kevin-Monahan]

Hi Miles, 

Sorry about that. Is it hanging on launch? Which plug-in or extension is it freezing on the splash screen? Can we have a screen shot of the issue?

Thanks,
Kevin

[Miles Emerson]

Kevin,

Yes, it is hanging up on launch. I’ve never actually had the program open before getting the error message. I uninstalled and installed a previous version (which worked for months on my system from January to March), but it froze on opening and gave the same error message.

I have no idea which plug-in or extension it is freezing on. My eyes are not that quick, but attached is a screenshot of the progress it reached before crashing. It actually lasted a second or so after the screenshot. Also attached is the error the message, which appears after the launchscreen closes.

Fingers crossed you can help.

Thanks,

Miles

[Jeff Bugbee]

QuickTime Player.app - New Screen Recording, record the whole screen, launch Premiere. Then you can pinpoint the exact moment it crashes and see if there is a specific plugin causing it.

[Miles Emerson]

Sorry for the delay, Jeff. I've been ill for a week. I've also had to learn how to work around a glitch in Quicktime on my system that causes the controls to disappear once I start recording!  Anyway, here's teh video I took of Premiere's launch failure. 

Thank you again for any advice or direction.

Miles

[Miles Emerson]

Hello again, Kevin.

It’s been some time since my last email to Adobe Support and I have yet to receive a response. I use Premiere Pro from time to time for work, so there are periods of time when I delete the program before needing it again.

I worked on a project back in March. Deleted the program in April. Tried to use it again in May, but suddenly found that Premiere would no longer run. I have sent you screenshots of of the error messages as well as a video of when the program freezes and gives the message, “Error. Directory object cannot construct with this path.”

I had a similar issue months earlier while working on a Windows machine. I literally had to copy a file from one directory and place it in another. Unfortunately, I am no so familiar with Apple computers (this is a new purchase as of March) and do not know how to manipulate files within program folders … if that solution would even still work on a macbook.

I made do in May with another program, but I am not in a position of needing Premiere to work as I am needing to edit old files; however, the launch issues remain and the program will not run.

Do you have an update for me or a workaround? I am desperate for help.

Best regards,

Miles

[Kevin-Monahan]

Hi Miles,

Others solved their issues by changing the permissions of the Adobe, Premiere Pro permissions, and v.22 folders to Read/Write. Can you try that? Let us know if you need help with that.

Thanks,
Kevin

[Miles Emerson]

Kevin,

I have tried that strategy but to no avail. Today, after I posted, I completely unistalled all Adobe apps on my computer using Adobe's specialized tool for this. I then shut down and reinstalled. Two issues remain, and they may be related.

Creative cloud has a file syncing error. "Could not enable sync". I've tried to change the sync folder location but it never works. I also cannot delete the file Adobe suggests in it's solution because the sync folder/file does not exist. Perhaps this is also why Premiere won't load; it cannot find the folder to sync ... ?

What do we do if our Creative Sync folder doesn't exist? 

The desktop program also says that there is "no storage information available". 

I had hoped that a complete wipe and reinstallation would solve this issue, but it hasn't. Premiere Pro worked in March. Once I uninstalled that version I have been unable to reinstall and successfully launch the program. I really need to move past this--especially since I am paying for a program that isn't working.

Thanks for any further advice you can offer.

Miles

[Miles Emerson]

Kevin,

My apologies, but I read over the portion of changing the properties of folders as well. I have now done so and it appears to be working.
Thank you!

Best,
Miles

[Kevin-Monahan]

Glad to hear it, Miles!

Kevin

[Tuğcihan24786233kt0z]

I did what you did but still have the same problem does anyone have another solution?

[blacksheepdigital]

Just came across this thread after having the same issue on a fresh install of PrPro 23.1 on Monterey 12.6.2.

For me the folder User/Documents/Adobe had been created with Read & Write permissions for "System", Read Only for "staff" & "everyone", but had no User or Administrator permissions set.

Solution was to Get Info on the Documents/Adobe folder, and add my User account with Read & Write permissions, then click the drop down below the user list and "Apply to enclosed items..."

Then I manually created folders inside it to make the path

Documents/Adobe/Premiere Pro/23.0

The app then launched without error.

[Tlgnmtl]

This worked for me. Monterey 12.6.2.

[Lourdes Cathe24433277g0l7]

I have the same problem and the only way that I can open the program is since the adobe creative cloud 😞 (tengo el mismo problema y solo puedo abrirlo desde el Creative cloud). 

[Jon24514022y5ok]

resolved it by disabling CONTROLLED FOLDER ACCESS under RANSOMWARE PROTECTION. 

Check your AV settings.

[Sami24670277mc77]

Issue resolved in my case by disabling offline files in Windows 10. 

[Kira5C55]

how do i do this on a mac?

[dawson_accidently]

Hi, still having this issue and have tried everything. Adobe for the love of God please fix old bugs. This program is unusable at the moment.

[Kira5C55]

I have this problem, I have no plug ins and I've never used Premiere pro before on my Mac, I just updated it to Monterrey 12.5 and my Premiere pro is up to date as well. I have tried uninstalling and re-installing several times, and the same error message "Directory object cannot onstruct with this path" is appearing when I try to use Premiere rush. I tried changing the file Sharing settings, and I don't have any firewall turned on. Can anyone help?

[Kevin-Monahan]

Hi Kira,

Check out System Preferences > Security and the Privacy Tab. Check if Full Desk Access has been granted to Premiere Pro. You also might try a reinstallation and allow permissions when those dialog boxes appear. I hope the advice helps you work around this problem. I am sorry for the frustration. 

Thanks,
Kevin

[Francoces]

Hi Kevin, I am having the same issue. I've gone down this whole thread and am running out of ideas. I get the same error every time I try to load it ever since I updated Premiere. It does not ask me for permissions.  Thank you

[Kevin-Monahan]

Hi Francoces,

Have you inspected your System Preferences yet? Is Full Disk Access enabled for Premiere Pro? Let me know.

Thanks,
Kevin