Skip to main content
Participant
May 16, 2023
Answered

dvacore::config::Localizer not initialized crash error

  • May 16, 2023
  • 8 replies
  • 6690 views

My Premiere Pro is up to date, and the Creative Cloud says nothing is wrong with it. Recently, I've tried loading it up and it says "dvacore::config::Localizer not initialized. Check dvacore/config/Localizer.h" and I'm not sure what that even means. I need help because I can't edit any videos at all and its kinda my job.

Correct answer mrmvillela

Six hours with Adobe remote help desk technician accessing my laptop for nothing. At the end he did logout without give any response. BUT I found a solution. Uninstalled last version and installed the previous one. Worked for me. 

8 replies

Participant
January 31, 2025

open your CMD with Admin and type this comand 

 

sfc /scannow

 

Wait and enjoy 😉

Participant
August 2, 2023

I looked through this thread, and nothing helped, but I did install a previous version. I had to go back to 23.3.0 to get it to work. I am running Windows 11 v22H2 (OS Build 22621.1992)

 

Participant
August 2, 2023

I have Windows 11  v22H2, OS Build 22.621.1992, fully updated. I had to go back to PPro version 23.3.0 to get it to work on my workstation.

 

Participant
May 31, 2023

Adobe what is going on with Premier.

Will not run.

Dvacore::Localizer not initialized. Check dvacore/config/Localizer.h.

Fix this, or do you not know how?

 

 

mrmvillelaCorrect answer
Participant
May 27, 2023

Six hours with Adobe remote help desk technician accessing my laptop for nothing. At the end he did logout without give any response. BUT I found a solution. Uninstalled last version and installed the previous one. Worked for me. 

Peru Bob
Community Expert
Community Expert
May 19, 2023
Participant
May 19, 2023

i have the same problem, have updated windows didnt help. Did u figure it out?

 

RealMotchAuthor
Participant
May 19, 2023
No, I have not solved the problem. That’s why I asked.
Peru Bob
Community Expert
Community Expert
May 17, 2023

Just a guess:

Try updating Windows.