P: Saving in 25.6.2 You do not have write access to the directory And Save As Crashes Premiere Pro

[bobb35642846]

After updating to Premiere Pro 25.6.2 if I open and edit any project, when I attemt to save, I receive the error "You do not have write access to the directory where the project is located". If I choose to "save as" the project appears to save but my premere desktop then turns black with no visable panels.

I have confirmed that I do not have an access issue. As the only user/administrator on this PC I have FULL CONTROL of all drives. All other Adobe products I use (After Effects, Photoshop, Audition, Media Encoder, LRC) can, Open, edit, save, & write to the same directory. 

If I uninstall Premiere and install version 25.5, Premiere works as expected and I do not receive any write access error messages.

I also attempted to uninstall and then install 25.6.1 and again received the "You do not have write access to the directory where the project is located" if I attempt to edit and then save a project. I again uninstalled and re-installed 25.5 and the issue goes away.

This issue is clearly introduced in version 25.6.1 and is also present in 25.6.2

I am running the latest version of Windows 11 Pro (Version 25H2 - OS build 26200.7171)

I am running on the following hardware:

MSI Z390 GAMING PRO CARBON AC Motherboard
Processor Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz (3.60 GHz)
Installed RAM 64.0 GB
System type 64-bit operating system, x64-based processor
Display Adapter: NVIDIA Quadro RTX 4000 (8GB)

[bobb35642846]

Upon further investigation this seems to be an issue when placing the project file on the ROOT of ANY drive. If I create a directory and move the project file to the directory of any drive, save works as expected and I do not get the error message.

If I move the file back to the root of the drive the error returns. I also noticed an anomoly that I cannot explain. If the project file is on the root of ANY drive and I look at Project Settings | Scratch Disks the path is incorrectly displayed. You can see by the screenshot below that the path is displayed as Path: \\?\E: This happens on ALL drives on my system. If I move the file inside of a directory on the same drive and then open the project, it saves without error and the path on the scratch disks settings screen are also displayed properly.

If I close Premiere after initially opening a project file on the root of any drive and close Premiere and once again open Premiere and try to create a new project, it defaults to the root of my disk with this incorrect path displayed:

This happens with all disks on my systems and ONLY appears to be happening with Premiere.

FWIW this odd behavor happens in BOTH 25.5 and 25.6.2 but 25.5 does NOT throw the error abount not having write access when the project file is on the root of a drive and 25.6.2 always throws the error.

I do have a work around and can use 25.6.2 now. I just need to ensure each project has it's own directory and avoid using the root of any drive, but I cannot explain this issue.

[Dani_V.]

Hi @bobb35642846, 

Thank you for reporting a problem and for the information provided. 

Is this happening only when creating new projects, or with existing projects as well? Could you provide any additional details about your drives (are they local/internal/external SSD or HDD, network, how are they formatted, etc)?

Sorry for the frustration, 
Dani

[bobb35642846]

Hi Dani,

This happens with BOTH new and exsisting projects. If I create a New project on the root of ANY drive Premeiere throws the error message, but actually creates the project file. If I open the file, it's an empty project that I can add media to and use normally but if I try to save, I get the same error and my changes are never saved. If I move that same file to any directory in that same drive, everything works as normally. I can edit save etc. I have take that same edited file from the directory and move it back to the root of the drive, the project opens up as I lasted edited it, but I can no longer save (I get the "you don't have wrote access"... error)

If I roll back to version 25.5 I am able to create/edit/save on the root of any drive.

I have tried this on ALL of my drives and it happens on every one. I have the following drive types on my system:

1. C-Drive SSD 2 TB - NTFS
2. D-Drive HDD 4 TB - NTFS
3. E-Drive SSD 2 TB - NTFS (Primary drive used for video editing)
4. F-Drive SSD 1 TB - NTFS (Primary Scratch drive)
5. G-Drive External USB HDD 18 TB - (Primary storage drive)
6. H-Drive External USB HDD 18 TB - (mirred with G Drive)

The highlighted drives are the F-drive & E-Drive respectively. These are my primary drives used for editing/scratch.

[LuMags]

I'm trying to save a project on my laptop when working remotely and getting the attached error.

It doesnt explain as to what the actual error is and how to fix it other than to use a different file name.

Which I do. However, I cant overwrite the newly created Project filename and have to do Save As which is getting silly as I Ctrl+S automatically because I'm paranoid / do a lot of changes per minute!

 Totally fine on my rig in the office. Have tried turning Dropbox off in case thats clashing/tmp raging but no difference. Any ideas please how to fix?

Cheers

[Ann Bens]

Try and change all the - (dash) characters for _ (underscore)

And save to a local drive instead of Dropbox.

[TPFenyx]

Premiere has been giving me the same exact error as well, I cant save ANY projects to my main drive. Same issue with me

[LuMags]

Hi,
What's your filename /. Address like? Is it full of dashes as mine was?
The problem seems intermittent. On my laptop again today, different project
working fine. Need to test later if it's that particular project the other
day that's the problem.

[bobb35642846]

@Dani_V. I provided the requested feedback promptly (on Nov 24), but have not heard back from you. Are you still looking into this?

I look forward to your replay.

Bob

[Dani_V.]

Hi @bobb35642846, 

The team is aware of this issue now and will update the thread as we learn more. 

Thank you for all of the information provided, 

Dani

[Yani Torres]

Primier Pro

Version 25.6.3 Build 2

During the processes of Save AS if you the same file name in in Use, afte the warning messeges file already exist. Do yo wanto to replece it?. if yes is select project is lost and the original project get blank

 

 

[IanB_360]

Hi @Yani Torres 

This is a known issue, and the team is currently working on a fix. For now, the workaround is to avoid replacing the existing project file with the same name by using the Save As option. You will not crash if you choose the options to Quick Save, Save, or Save a Copy. 
Here to help
Ian

[IanB_360]

This is a known issue, and the team is currently working on a fix. This post has highlighted two separate issues we are aware of. The save permissions error and the crash that occurs when using 'Save As'. For now, the workaround to avoid crashing when using 'Save As' is to avoid replacing the existing project file with the same name. You will not crash if you choose the options to Quick Save, Save, or Save a Copy. 
Here to help