I had this problem. So, having updated the firmware, I then updated the plugin, or restarted it or somethiing…and rebooted the PC, and then the ‘link to minifreak’ reappeared.
2 Likes
I finally took the plunge and successfully updated the FW to 2.0 and so far so good.
Favorites was a little weird for a minute but I got it and it makes life a lot faster. I’ll dive into wavetables and unisons over the next hour and see what happens.
1 Like
So I also took the plunge this morning and started the update. As happened previously with the 1.0.0 to 1.1.0 update, the Minifreak didn’t reboot itself, so I was getting a sinking feeling.
However this time the Minifreak V software showed a link to open in case of this happening.
So I clicked on that link and was instructed to keep Minifreak V open, while restarting the Minifreak with the Shift + Octave Down buttons being pressed.
So I did this and the Minifreak started up with the V2.0.0 welcome message. Minifreak V also informed me that the firmware was successfully updated to V2.0.0.
So far so good I guess. I hope this update will stick. Maybe during the time at Arturia to get fixed after the failed V1.0.0 to V1.1.0 update they also fixed the root cause for the updater completely failing. Who knows?
But I still find it extremely disturbing that the automatic reboot that should take place just doesn’t seem to happen, not even after waiting for more that 1 minute (as instructed by Minifreak V) and that Minifreak V seems to think that it did successfully reboot the Minifreak when it clearly hasn’t done so.
2 Likes
It’s good that someone thought to patch that Shift + Octave down path into the update process. More people should know about this. It might cut down on some of the rough experiences and bad press. Wavetable produces some good sounds and I really like super unison.
Favorites is extremely helpful but produces some wonky behaviors that make me have to switch back & forth between it & panel mode (a lot). I wish the Shift button was an octave from the Save button so I could keep my right hand going on the 
. Overall this is a great sounding board with lots of flexibility.
You’re not the only one! 
1 Like
After about 12 tries to update I had success. This is my story:
They did say when the V1.0 to V1.1 patch came out that you should use a direct USB port on your system, not one connected to a hub or something like that. I assume that VirtualBox’s USB passthrough didn’t meet that criterium. But I do agree with you that their update protocol is way too fragile as it is now. Not sure if they can do anything about that though through patches.