Importerquicktime prm premiere pro ошибка

I do understand what you’re saying and that Adobe has created an area for Users to request features.

I understand that Adobe has a call/chat 1 on 1 service as well. However, others spent 5 hours with Adobe support 1 on 1 and Adobe blamed Microsoft at the end and couldn’t solve the problem. This forum proved to be the best place to find a solution when Adobe Support could not.

I’ve used the feature request area, not sure if that’s what User Voice is, but I’ve voted and gave my thoughts on multiple posts, but as others have pointed out there, even high voted feature requests don’t seem to be implemented on new releases. More importantly, a high  voted post there is about the need to have Premiere much more stable, but Premiere hasn’t become more stable. Each release is about as buggy as the last, so it’s my opinion that Adobe doesn’t really seem to implement things into Premiere that Users request.

The video link I shared earlier proves that when Adobe sent 2 people to a pro Editor’s place and still hasn’t implemented many of the requests he had: https://www.youtube.com/watch?v=O6ERELse_QY&feature=youtu.be&t=12103/external-link.jspa?url=https%3A%2F%2Fyoutu.be%2FO6ERELse_QY%3Ft%3D12103

This forum would be a good place for Adobe to equally consider getting feedback from, is all I’m saying. User’s thoughts are expressed better and issues can be explained deeper here because of the nature of it being a forum. Without Adobe’s input within this forum (Your help), we wouldn’t have been able to find a solution. Unfortunately, it took a while to get to though because Adobe has established this forum to be user to user.

I do understand what you’re saying and that Adobe has created an area for Users to request features.

I understand that Adobe has a call/chat 1 on 1 service as well. However, others spent 5 hours with Adobe support 1 on 1 and Adobe blamed Microsoft at the end and couldn’t solve the problem. This forum proved to be the best place to find a solution when Adobe Support could not.

I’ve used the feature request area, not sure if that’s what User Voice is, but I’ve voted and gave my thoughts on multiple posts, but as others have pointed out there, even high voted feature requests don’t seem to be implemented on new releases. More importantly, a high  voted post there is about the need to have Premiere much more stable, but Premiere hasn’t become more stable. Each release is about as buggy as the last, so it’s my opinion that Adobe doesn’t really seem to implement things into Premiere that Users request.

The video link I shared earlier proves that when Adobe sent 2 people to a pro Editor’s place and still hasn’t implemented many of the requests he had: https://www.youtube.com/watch?v=O6ERELse_QY&feature=youtu.be&t=12103/external-link.jspa?url=https%3A%2F%2Fyoutu.be%2FO6ERELse_QY%3Ft%3D12103

This forum would be a good place for Adobe to equally consider getting feedback from, is all I’m saying. User’s thoughts are expressed better and issues can be explained deeper here because of the nature of it being a forum. Without Adobe’s input within this forum (Your help), we wouldn’t have been able to find a solution. Unfortunately, it took a while to get to though because Adobe has established this forum to be user to user.

вы можете попробовать следующее:
При открытии Premiere и когда он зависает на сервере QT32, попробуйте убить процесс в диспетчере задач и убить процесс premiere, затем проверьте, не работает ли процесс QT, а также проверьте, не работает ли процесс динамической компоновки. Если они просто перезапустить премьеру.

Если процесс QT не может быть остановлен, то у вас есть проблема с вашим программным обеспечением брандмауэра. Есть некоторые сторонние приложения брандмауэра, которые могут вызвать сбой создания экземпляра QT server, например Comodo брандмауэр у меня был плохой опыт с ним.

также есть еще одна возможность, что вы добавили некоторые новые кодеки, которые конфликтуют со старыми, особенно в отношении быстрого времени, как, например, DNxHD QT кодеков или аналогичных от Avid.

эти данные не могут быть найдены на Adobe или, по крайней мере, я не нашел его там.

надеюсь, что это будет работать для вас, или по крайней мере дать вам идею, как найти решение.

наилучшие пожелания

Hi everyone,

I have been having this problem since morning (12/11/2020). In fact, it has robbed me of 80% of my active time today.

So, I went on a hunt for a viable solution.

After many trials, uninstalling Premiere, searching for an elusive %Appdata% folder, and almost giving a thought of starting afresh my computer, I found one solution that led me to the finding I will share in this thread. The solution has to do with the idea of creating another user account.

After my analysis, it seems like this is a Windows 10 sort of a problem.

Another similarity is that the culprit is Adobe Premiere or Adobe Media Encoder or both hugging or cruising at the final stage of the loading AEXD.aex or importerquicktime.prm plugins. 

This is the same problem I encountered with my Camtasia. However, Camtasia resolved it by suggesting a new location. That went on smoothly. I didn’t even think there is a huge problem lying beneath.

So, to fix this, once I was in the second user account, I noticed when load Premiere Pro, I got this notification from my Windows 10 defender to allow Premiere Pro to have access to My Document.

It is obvious by default, this folder is accessible to these apps, right?

However, with the revamped Windows Security, the Ransomware protection is super active to watch which apps access certain paths in your computer.

So, with these two plugins in need to access the Adobe folder in my Documents (I hope that’s the case here), the windows defender sees it as a threat. As a result, it prevents them from accessing the folder.

This is the reason Adobe Premiere Pro and Adobe Media Encoder are the two most affected apps from the creative suite. That is, for Windows 10 users who are using Windows security as their default antivirus.

So, the fix…

You have 2 options here:

Option 1:

1. Open your Windows 10 Security App (Windows Defender for win 10)

2. Click Virus & threat protection

3. Click on Protection history (Wait a little bit to load the history)

4.  Toggle the histories from «Protected folder access blocked» — you will require administration rights here.

5. Click on Actions Button and select Allow on device.

Option 2:

1. Open your Windows 10 Security App (Windows Defender for win 10)

2. Click Virus & threat protection

3. Click on Ransomware Protection

4. Then, on Manage ransomware protection.

5. Next, on Block History

6. Toggle the histories from «Protected folder access blocked» — you will require administration rights here.

7. Click on Actions Button and select Allow on device.

One thing to note, you cannot remove the Documents path from the list of protected folders.

I hope you find this useful. 

joaocverde  wrote

Thanks Jeff.

In my case I discovered short before your answer that somehow, the folders where Premiere keeps some files (on my Libraries) required administrator privileges to be accessed. I had to access those in Windows Explorer with elevated permissions beforehand, and after that Premiere (and Media Encoder too, curiously AE did not have any errors) would run OK, and since then I have rebooted and Premiere continues to launch successfully.

This did NOT work for me, but after a very long and annoying back and forth in another thread, the problem was isolated to a file in User App Data that needed to be force deleted. Here’s what I did to fix it for me:

I can confirm that deleting this file on the user account that’s preventing Adobe Premiere Pro will work to fix the problem:

C:UsersYOUR USER FOLDERAppDataRoamingAdobeCommonEssential Sound/SharedTags

If you can’t get there, go to any open folder and at the top under View;check show hidden files.

This file will NOT delete just by right clicking and deleting it. It will say it cannot be deleted because it’s in use. Even with closing all Adobe related files in task manager, it still was unable to be deleted because ‘System’ is using it.

1. You have to force delete it either through your command prompt, or by installing a program that does it for you.
2. I used a free program called lock hunter: https://lockhunter.com/download.htm
3. https://lockhunter.com/download.htmAfter you install lockhunter, you can right click the SharedTags file and go to ‘What is locking this file?’.
4. Then lock hunter will open and if you open the ‘system’ dropdown, it will reveal the SharedTags file.
5. Select the SharedTags file (Not system)
6. Hit the delete button below.
7. It will tell you that you STILL can’t delete it because it’s in use, so it will ask if you want to delete it when you restart the computer, say yes.
8. After the restart, it will say successfully deleted.
9. You’ll now be able to start Premiere pro.
10. Premiere Pro CC will automatically put back in a new SharedTags file into the Essential Sound folder, but this time since the computer didn’t crash while in Premiere (yet), that file didn’t get corrupted, meaning all is good, until the next crash, which you’ll then need to redo this process.

This is a perfect example of how Adobe loves to introduce new features (Essential Sound) that causes conflicts with other parts of Premiere that used to work perfect. In this case, the new feature wouldn’t even let Premiere start up.

Adobe, can we please all agree that you seriously need to do FULL testing before new features are introduced?

joaocverde  wrote

Thanks Jeff.

In my case I discovered short before your answer that somehow, the folders where Premiere keeps some files (on my Libraries) required administrator privileges to be accessed. I had to access those in Windows Explorer with elevated permissions beforehand, and after that Premiere (and Media Encoder too, curiously AE did not have any errors) would run OK, and since then I have rebooted and Premiere continues to launch successfully.

This did NOT work for me, but after a very long and annoying back and forth in another thread, the problem was isolated to a file in User App Data that needed to be force deleted. Here’s what I did to fix it for me:

I can confirm that deleting this file on the user account that’s preventing Adobe Premiere Pro will work to fix the problem:

C:UsersYOUR USER FOLDERAppDataRoamingAdobeCommonEssential Sound/SharedTags

If you can’t get there, go to any open folder and at the top under View;check show hidden files.

This file will NOT delete just by right clicking and deleting it. It will say it cannot be deleted because it’s in use. Even with closing all Adobe related files in task manager, it still was unable to be deleted because ‘System’ is using it.

1. You have to force delete it either through your command prompt, or by installing a program that does it for you.
2. I used a free program called lock hunter: https://lockhunter.com/download.htm
3. https://lockhunter.com/download.htmAfter you install lockhunter, you can right click the SharedTags file and go to ‘What is locking this file?’.
4. Then lock hunter will open and if you open the ‘system’ dropdown, it will reveal the SharedTags file.
5. Select the SharedTags file (Not system)
6. Hit the delete button below.
7. It will tell you that you STILL can’t delete it because it’s in use, so it will ask if you want to delete it when you restart the computer, say yes.
8. After the restart, it will say successfully deleted.
9. You’ll now be able to start Premiere pro.
10. Premiere Pro CC will automatically put back in a new SharedTags file into the Essential Sound folder, but this time since the computer didn’t crash while in Premiere (yet), that file didn’t get corrupted, meaning all is good, until the next crash, which you’ll then need to redo this process.

This is a perfect example of how Adobe loves to introduce new features (Essential Sound) that causes conflicts with other parts of Premiere that used to work perfect. In this case, the new feature wouldn’t even let Premiere start up.

Adobe, can we please all agree that you seriously need to do FULL testing before new features are introduced?