Premiere Pro 24.4.1 creates the "AppData" folder at a wrong position

[KlausKi]

The latest Windows version of Premiere Pro creates the "AppData" folder at a wrong position:

"AppData" is a user folder, supposed to be stored at "%USERPROFILE%".

Whenever I start Premiere Pro on Windows, this folder is re-created by Premiere Pro at the wrong location.

Where can I report this bug?

[Stan Jones]

Win10. PR 24.4.1 installs in AppData in usual location.

Stan

[KlausKi]

What does PowerShell return if you enter:

[System.Environment]::GetFolderPath('MyDocuments')

It returns D:\Documents on my machine. If you don't have this setting, you cannot reproduce.

[R Neil Haugen]

That folder is at the location it's supposed to be on my Win10 system also. And no, it's not on my D drive, period. Yes, I do know how to verify folder/file location and other data.

So ... is there a permissions problem for that drive or folder for Premiere on your machine?

[Ann Bens]

I would deinstall Premiere

Use cleaner tool and reinstall.

I too have Documents on 😄 but AppData is on C where is should be.

[Kevin-Monahan]

Hi @KlausKi,

I'm Kevin, one of the moderators here. Thanks for the bug report. The team may need more information. See: How do I write a bug report?

I hope the team can help you shortly.

Thanks,
Kevin

[KlausKi]

Hi @Kevin-Monahan,

thank you for your reply. Sorry for getting back on this issue so late. I'm back at my home machine now.

I tried to investigate further on the issue using Microsoft ProcMon. I guess, the LUTManager.dll or the LUTEngine.dll are resolving the path wrong. See this ProcMon log excerpt:

 Im currently using Premiere Pro 2024, v24.4.1(2):

[Kevin-Monahan]

Hi @KlausKi,

Are you still seeing this issue? Did you try Ann's potential solution? Please report back so we can help you further.

Thanks,
Kevin

[KlausKi · Accepted solution]

Hi Kevin,

actually I did a number of re-installs in a blank virtual machine, but the issue re-appeared all the time.

However, I now updated to the latest version an the issue doesn't seem to occur anymore.

Thank you for all your efforts.