How to get a clean uninstall of 2016 R3 from PC running Windows 7 SP1 32 Bit with fully update security patches
I haven't used the software since mid 2016 i was running R2 when I came to set up a new template and save it, the software crashes. Thought it might be a version issue so deleted R2 and loaded R3 but same problem. Now can get a clean uninstall, when i go to activate a fresh installation its telling me there its already been activated.... despite Support team advice.
Help!
-
Sorry should read "Now can't get a clean uninstall"
P
0 -
I've also had issues not resolved by uninstalls. When you uninstall, a lot of registry keys remain. Look in your system registry for: "hkey_current_user\software\Seagull Scientific" and delete the keys. There are some other location in the registry that aren't deleted that might have some impact, though the majority of document level things seem to be there.
Aside from that, depending on the edition of bartender you have ( e.g. automation) it may be automatically connecting to the seagull license server and activating. I imagine you would have to disable SLS to fix that.
0 -
With problem like these it tends to be better to reach out to us here in tech support directly through phone or email.
We can do some troubleshooting with you and tailor a solution to the specific problem. Also, it give us a chance to see what happened and report this back to our developers in case its an issue where we need to improve some aspect of BarTender to avoid similar issues in the future.
It sounds as if you may have reached out to us on this already, please follow up with us if this hasn't been resolved yet!
0 -
James
I'm Running Profesional version
It is already in the your System and is being addressed Roman has been supporting me, I'm now at the stage where a new installation of R3 to load without recognising a previous installation,
However i get a message the "BarTender has stopped working" message every time I try to save a template file and the program then restarts.
Was doing the same with the R2 version which was working perfectly 6 months or so ago. Thought it might have been a Revision issue hence the move to R3
0
Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.
Kommentare
4 Kommentare