Scanning Audio Plug-Ins Immediate Crash

[Boris0608]

Hi all, 

Premiere Pro was working just fine and Creative Cloud updated and now I cannot start Premire Pro.
When I open it it shows little box saying ''Scanning Audio Plug-Ins'' and just crashes and ''Send report'' windows pops-up. Until yesterday it was working normally. 

I don't have any plugins installed, cannot figure out what happened,nothing on the web about that. 
It happened once before and I had to reinstall whole Windows and all the programmes and it went away,
but I really don't want to do that every couple of weeks.

Does anyone have a solution, I am desperate and of course in the middle of blood thirsty clients waiting their projects to be delivered!

Thanks!

[Boris0608]

After almost five hours with guys from Adobe remote customer support, no solution...Premiere is not working still.
Multiple CC installations and re-installations of Premiere - nothing.
Even plugging out the Graphic Card and replacing it with another one - nothing.

If someone has any idea...Thanks.

[Tom22003089q132]

Same issue here! No soluion yet 😞

[Jeff Bellune]

The first thing I would try is launching Pr from a shortcut (Desktop, Dock, LaunchPad, Taskbar, Start Menu) while holding down the Shift+Alt or Shift+Opt keys. Keep them pressed until you see the main program window.

Shift resets the plugin cache and Alt/Opt resets the Preferences.

[Boris0608]

I tried that...No result unfortunately.

[Boris0608]

Just an update. Tonight it happened again. I cannot beleive that I have nobody to adress this issue and it is happening for the third time in 5 months. The guys who made this programme should know why the hell this is happening.

Paying 500$ per year for this kind of business-ruining software is outrageous.

I beleive that this time I will solve the issue with a hammer.

[Boris0608]

After almost two days with customer support, no solution. I had to reinstall Windows (and we all know how much we love that) and after that the problem was gone...And now I live in fear and anxiety every time when I launch Premiere 🙂

[Louis Julien22602511are6]

Hi, have the same issue here. I spent 2.5 hours with an agent and still no answers. Any solution?

[Boris0608]

Never solved the problem, tried everything 😞 
Complete re-install of the system and that is it, haven't had the problem since.

Just out of the curiosity...Have u used some external devices or controllers?
I am suspecting that my Loupedeck+  controller made some bugs in the system.
It happened to me twice, and both of the times I had the Loupedeck+  installed , now I don't use it and everything works without problems. It doesn't have anything with the sound plug-ins, but who knows...

[Jeff Bellune]

Apparently the Loupedeck has problems across all Adobe apps. 

Thank you for posting your solution and I'm sorry you had to go through the pain of a system re-install. 

[Louis Julien22602511are6]

Hi, I don't use any external device like Loupedeck+.  Could a wireless mouse or keyboard cause a problem?

[Boris0608]

I don't think mouse or keyboard made the problem...Some crucial drivers were messed up by something and nobody could figure out what... My suggestion is save your time, take a deep breath and refresh your computer with a nice clean Windows installation 🙂

[Louis Julien22602511are6]

Thanks for the advice! 🙂

[Boris0608]

I was thinking...

Can you tell me your computer specs? 
What graphic card and motherboard do you have?
Now I am suspecting that my NVIDIA 1660 GPU made the problem after some driver update or something...

[Louis Julien22602511are6]

Hi, 
I'm sorry to read that you still experience problems. I gave on the program since I am not using it a lot and I went for DaVinci Resolve.
But for the info you're asking, I am using a Intel Core i7-8700K 3.70GHz with a NVIDIA GeForce GTX 1080 graphic card.

[Boris0608]

Yeah...No wonder people are making transition to DaVinci...Thanks...

[Boris0608]

Another UPDATE for anyone who has this issue, since there is nothing on the internet about solving this problem. 

I realized that before all three times that my Premiere started crashing I installed some government certificates and softwares that are needed so you can activate Identity card reader (You put your ID in the device and it reads your data, so you can access your taxes, medical card, etc. ) and I remembered that I installed all those certificates, third party Middleware software, some Visual+ C stuff and something else, before every time my Premiere started crashing. 

Since it is government developed software I am somehow quite sure that they messed up 🙂
So if you have some government card readers in your countries, maybe that was making the problem.

[neil wilkes]

I know this is no help at all, but my money here is on Windows 10 causing all the trouble.

I refuse point blank to put that dog of an OS on my working DAW system and this is why:

Recently I had to buy a new NLE editing setup as the old system had a motherboard fail after almost 10 years, and getting a new W7 system proved to be impossible because it is allegedly 'EOL & Unsupported' (despite the fact you can purchse extended support direct from Microsoft) and I reluctantly went for W10 Professional because it was supposedly capable of allowing you to NOT install 'updates' - that turned out to be an Urban Myth however, as after only 2 weeks I was forced to do a full OS update because it would not defer any longer.

On restarting I found my £2500 machine was effectively now a Boat Anchor. I called the system builders (this was not an off-the-shelf setup from a box shifter) who told me that this is common, and when MS do an OS update approximately 20% of the time it will fail and turn your PC into a boat anchor, and for that reason there was a little thumb drive in the case with the OS installation files. I had to open it up, take out the little drive & completely wipe my HDD and reinstall everything - including all the motherboard drivers and hope like crazy I did not forget anything.

It took HOURS.

Other people I know have had their PC go into Mac Mode, as I call it - the OS 'update' breaks a load of 3rd party applications, or severely reduces their functionality & time is then wasted on the phone to various support people trying to find out how to get software I have paid for working again after MS broke it in the update.

So I am really sorry but my guess is the OS update killed you - but just in case, can you please let me know just what audio plugins are causing the crash?

What type - VST2 or VST3? AAX32-bit or AAX64-bit?

Have you tried deleting the unnecessary AAX plugins (assuming you do not use ProTools)?

Where are the install paths for your audio plugins?

The more info you can give me the more chance I havce of finding a possible answer for you

[Boris0608]

I guess it goes both ways, Adobe is unprotected from Windows flaws and Windows is so easily broken (often it breaks itself and everything connected to it) ...When I think of changing the system, selling all the kidneys I have to buy a decent Apple device I remember that on that side is whole differend kind of hell,So, I guess the best thing is to leave all the editing business and turn myself to agriculture and plant tomatoes.

I am mainly focused on video editing, never had any additional audio plug-ins, never did any sound jobs, nothing in the sound area, just video stuff.

Last time when it happened, I was in the middle of project, making a simple scroll through timeline. In one moment, HDD just started working hard, frame froze, Premiere crashed and that was it. Next time I started Premiere, it shows that Scanning audio plug-in screen and crash. 

I am wondering, If an Adobe software engineer made a little window that says Scanning audio plug-in, why there is no answer what is that and why it crashed in that position.And nobody knows why it happened...I guess this question goes into ''What is the meaning of life? Is there life in space? '' basket.

And for your Boat anchor... At least you have a boat 😛
Thanks for your reply!

[mjdvc]

Just update, having the same trouble with Premier and trying to uninstall some software for reading ID and etcd. After that all back to normal. It's probably some conflict, so when this happened you can try uninstalling previous updates on windows or software.