4.3.3 Worked fine. Don’t care about security issues. Just want it working again. 2 out of 3 PC’s now useless. i7 with Completely new collection all analised and I can’t write to a new FAT32 formatted SSD. Nearly 6 years Engine experience. WHAT THE HELL IS GOING ON???
1 Like
Sorry to hear you are having problems and we can tell you are frustrated.
If you want help, take the time to share error messages and other relevant details. Your CPU model is one of the least important details.
Thank you. Sadly there are no error messages. Dragging and dropping, editing a playlist, deleting a playlist is all impossible.
Having said that, I had this problem I recall from version 3 to version 4 and I had to completely rebuild my collection and playlists. This time it is an incremental jump though?
Rather than use Engine Sync, I copied the whole Library database from File Explorer to a new SSD and that worked - but I can’t copy my Playlists still?
I think my only option now is to rebuild the whole thing 
All for a security issue.
I decided not to update and keep the vulnerability. It’s probably safer which is quite ironic. I’ve already had engine desktop refusing to load previously so not taking any more chances.
Just counted and I’ve kept 45 database backups too, not bad for just under 12 months 
1 Like
I updated my hardware (prime go) and software to 4.3.4. now engine won’t open on my mac mini (Sequoia 15.7.2).. I can’t update or edit my collection and the go is extremely laggy loading music from my USB. We can download 4.3.3. for our hardware but not for the os..??
So MAC have the same problem as PC with 4.3.4. ??? Solution for me: another T9 SSD (to add to the collection) for a TOTAL rebuild on a quarantined PC ….. (The back ups won’t work as they are 4.3.3)
what’s different about the third PC, which is working fine?
3rd child syndrome perhaps?
1 Like
This is a problem. You can’t just copy a database file from one location to another and expect it to work. The databases have a connection to each other so that they know the source of tracks and the destination. This could definitely be causing the issues you’re seeing.
But just on Engine 4.3.4, it’s very unlikely that the security changes have triggered this, it’s unrelated to the database file. It could just be coincidental that this has occurred at the same time as you have updated. I highly recommend getting in touch with the support team so they can guide you through some steps to resolve the issue.
6 Likes
This does not sound encouraging i’ll hold off updating for now, side point anyone else found red tracks in their library and when relocated it’s still red? Very strange i found a number of tracks that engine can’t find but i havnt moved or changed the file names the relocate all does not seem to work i believe this was raised by others also
This has a Collection that has been built on that PC with 4.3.3 and successfully updated with 4.3.4. It has a library I have been working on for 3 months and have been steadily building playlists. This PC is quarantined from ALL SSD that have been used with the other PC.
Thie other two PC have their own Collections (that worked fine with 4.3.3) Again to clarify, BOTH worked until the 4.3.4 update.
1 Like
Yeah, I think whatever problem it is that you’re having is unrelated to the update. I’d strongly recommend folks do the update to 4.3.4.
1 Like
The solution was to re-partition, re-format and rebuild the Collection on EVERY SSD and Thumbdrive that I use with Prime 4+ & Mixstream Pro Go.
Why did you need to repartition? I’m so confused by this. 
Thank you for sharing your update.
This was the only way I could do it. Starting right back at the beginning near enough - as if I’d bought a new SSD and PC. There is a bug somewhere that is not allowing editing, etc. Maybe a security protocol on USB ports or devices that has been implemented in Windows 11 perhaps?