BackUp Before Updating to UC v3.0 -
Posted: Wed Apr 03, 2019 11:46 am
Good morning from SoCal -
Word of Warning - Backup Up your 192 Scene Setting Prior to installing new version -
It just may reset back to factory -
Earlier this week 04/01/2019 - Ironically -
I launched UC and it had an update waiting - 3.0
I did as always, ran the update -
For some reason the update did an uninstall and did not install -
My 192 No Longer recognized I resolved the issue by running the new version package and the 192 is working -
HOWEVER, all my 192 Scenes and Customizations that I had are gone. It completely wiped everything.
Yes, we all know to make backups. -
I am working with a PreSonus tech to see if there is a recovery, but I know when a file is gone it is gone. I am also letting them know that the package installer does have an option to copy/move any modified "scene" files rather then just delete them. I have developed install packages. I know because I've been there and done that.
In any case, if you find this is happened - report it to PreSonus in a ticket - I hope that it was just a quirk in my install -
Be Blessed!!!
Word of Warning - Backup Up your 192 Scene Setting Prior to installing new version -
It just may reset back to factory -
Earlier this week 04/01/2019 - Ironically -
I launched UC and it had an update waiting - 3.0
I did as always, ran the update -
For some reason the update did an uninstall and did not install -
My 192 No Longer recognized I resolved the issue by running the new version package and the 192 is working -
HOWEVER, all my 192 Scenes and Customizations that I had are gone. It completely wiped everything.
Yes, we all know to make backups. -
I am working with a PreSonus tech to see if there is a recovery, but I know when a file is gone it is gone. I am also letting them know that the package installer does have an option to copy/move any modified "scene" files rather then just delete them. I have developed install packages. I know because I've been there and done that.
In any case, if you find this is happened - report it to PreSonus in a ticket - I hope that it was just a quirk in my install -
Be Blessed!!!