Sign In:     


Forum: VirtualDJ Technical Support

Topic: Updated and now VirtualDJ won't open on my MacBook Pro Ventura 13.4
MacBook Pro running Ventura 13.4. I opened up the application to do some music filing, window popped up said VDJPro had been updated and do I want to use it. I clicked "yes" and now it won't open. Says "the application virtualDJ can't be opened", what happened? What is the resolve? TIA
 

Posted Sun 11 Jun 23 @ 9:59 pm

[ selected best answer by Adion on Wed 12 Jul 23 @ 2:16 am ]
Same here. I've just opened a ticket with VDJ for the same reason.
 

 

 

well I made a backup copy, uninstalled, reinstalled and went to "restore" my backup file but it's not wanting to pull it... when I click on the actual file it opens to all the folders inside it and wants me to choose one of those...what am I doing wrong so that it brings in the entire "VirtualDJ" folder in the restore?
 

What version of vdj are you all using?
 

Got this issue too. Running on a Macbook Pro M1 8Gb on OS Ventura 13.4.1. Just had to turn off updates for now. For the past 2/3 weeks getting this problem. Just have to use version : virtualdj_2023_b7555_mac. Hope This helps.
 

Just FYI working fine here;

My System Specs;
M1 MacBook Pro (14-inch, 2022), Apple Silicon M1 Pro, 16gb, 500 gb SSD, macOS Ventura 13.4.1, VirtualDJ Early Access v2023-m b7600.
 

 

 Selected as best answer
I just update VDJ and it won't open up. Using MacBook Pro Ventura 13.4.1
 

This is very terrible. Same just happed to me. Im preparing for a gig tomorrow and the update came up. As soon as i updated i get "The application “VirtualDJ” can’t be opened." doesn't feel like this was tested through & though before rolling out
 

@adion from your answer I assume you were able to reproduce this bug.
When will it be fixed?
I didn‘ t have this bug at the beginning and suddenly (after over a year on the same machine) it appeared out of nowhere …
 

Unfortunately it seems to be something Apple changed that prevents the update from being applied correctly.
It is fixed in build 7600 but we can't fix the updater in older versions unfortunately.