メインコンテンツへスキップ

⚠️ Please note that this topic or post has been archived. The information contained here may no longer be accurate or up-to-date. ⚠️

Why was a service release update so time consuming and tedious?

DanM

Why can't the program just update itself? I followed the update instructions (only jumped up one service release) and uninstalled the program, then ran the installer and had to retrieve my registration key and then the password for my account. It's not the time wasted (about 15 or 20 minutes), but the energy I brought to what I was going to do. Could this be a little more painless, please?

 

0

コメント

9件のコメント

日付 投票
  • Permanently deleted user
    Top Commenter

    It is painless - which instructions told you to uninstall?

    0
  • SFA

    I'm sure Capture One has its reasons (as do many other suppliers) for instructing us to uninstall the previous program and in general, especially in Mac world, that is probably the best approach is people have been having strange problems.

    You could simply ignore the Uninstall options and reinstall in the same place and see what happens. I have done that once or twice without any problems.

    However I normally just run the update creating a new folder and then take a few seconds to sort out the activation. That way it is easy to revert should anything go wildly wrong during the installation.

    0
  • DanM

    I thought I had done it once already and that it had presented me with a simple update option. The only option I saw this time was to download the update and then install it, so just to not mess anything up, I checked the C1P site and it said to first uninstall, then run the update, which is what I did, but I had to retrieve my key and then my site password to proceed. It's not the end of the world, but it was a speed bump on my way to getting something done.

    0
  • Permanently deleted user

    SFA,

    i suppose that you do not use a Mac. Otherwise you should know that

    1. Applications are usually distributed in such a way that they contain all necessary data without requiring to change the content of OS directories (vs. Windows applications storing files in the Windows system directory structure)
    2. The (macOS) "Uninstall" for CO would be just performed by deleting the application.
    3. The (macOS) Capture One installer asks if the earlier version (if existing) should be kept as well

     

    In my experience from using both worlds, Windows is more critical concerning Updates.

    • Under Windows, I do have applications, which need to uninstall the earlier version before the new version may be installed. (These applications even start the uninstaller before installing the new version => no possibility for two different versions installed at the same time)
    • For being able to keep the earlier version of CO under Windows, a custom installation would be required. Under macOS, I'm offered to keep both versions when updating CO.
    • Still the effects on the registry entries would be uncertain, when installing two (minor) versions of an application, e.g. 13.1.2 and 13.1.3. This might even harm the installation of the earlier version, when you decide to uninstall the newer version.

    Anyhow, I haven't encountered any problems when installing a new release of CO over the earlier version under Windows. 

    But I would agree that under Windows the safest way to update any application would be to uninstall the earlier version, reboot the computer and then install the new version... But that has been a OS design decision by Microsoft long ago...

    0
  • SFA

    I am aware that Mac policy is to protect the user from any involvement and decision making wherever it is possible to do so.

    I am aware that some Windows applications will delete all that has gone before even for a point update. That's fine if they feel a need to do so, especially if they are overwriting a previous installation for specific reasons. They may also need to do so, especially in a corporate environment, as part of license management controls and avoid the possibility of backwards compatibility support issues.

    C1 seems to be increasingly adopting unique version (and release in some case) management assists and that fits well with the option to use a current licence for earlier version of the software (should someone wish to do so) and, of course, the ability to continue to process legacy image in the current version using older processing engines.

    I carry the overhead of disk usage but by installing releases (more often then not) in new dedicated folders I have the options to revert to an previous release or a previous version quite quickly if required. Coincidentally it was a requirement tonight for the first time I can remember outside of testing requirements.

    Having installed 20.1.3 I seem to be having some issues connecting to the server to activate it but I could simply fire up 20.1.2 instead.

    I do appreciate that doing things this way runs the risk of something getting screwed up. If it was my fault I would not expect Support to be either pleased or indeed helpful. But this is the way I have been doing things for quite a while now without any problems I could associate with having multiple versions installed. It worked well even before the recent work to enhance the way that version and release related variables are handled.

    So I'm happy with it for now.

     

    Whether Windows 10, when I am forced to move to it, will throw in some special curve balls I'll have to wait to see.

    0
  • DanM

    It is usually seamless with the installer first uninstalling the old and then installing the new version. Just didn't work that way this time. The only annoying part was to have to find and enter my key # and also find my pw for the site, which is normally saved, but didn't come up for the update screen. Not a huge deal, but I was in a hurry to get started this morning and get as much done as possible. I'm still happy w/ the program.

     

    0
  • Permanently deleted user
    • 編集済み

    SFA, you wrote

    "I am aware that Mac policy is to protect the user from any involvement and decision making wherever it is possible to do so."

    Actually that is not correct. Opposite to macOS, Windows is making the decisions on behalf of the user by allowing every single application to use whatever resource is requested without asking for permission.

    When I look at C1 under the (latest) macOS, there is no decision made by macOS what resources could be used. In contrary, macOS demands that the user makes the decision(s), what resources an application is allowed to use. This is intended to protect users from malicious SW stealing (private) data or make it harder for malicious devices to take over control of the computer.

    For C1, this is done once per major release. Unfortunately, some users just deny everything (without considering if the would be legitimate reason for the usage). This is then usually causing lots of the problems seen here in the forums.

     

    Anyhow, I guess that it could be endlessly discussed what is the more user friendly way, the protection of the system and user data. I'm just saying that from my own experience installing C1 under macOS is no problem at all.

     

    Edit:

    "Windows 10, when I am forced to move to it"

    Win7 is EoL since Apr. 20 (and Win 8.x was much less usable than Win7). I would recommend you to switch to Win10 already now (You might even still get a free upgrade...). Test it at least on a virtual machine. You might even still get a free upgrade...

    0
  • Michael Pegg

    I'm a Windows 10 user. Just downloaded the new update and it installed over the existing file with not problem.  

    0
  • Jim Hughes

    I've been hit with this too, and now I skip the updates because of it.  I'm afraid something will go wrong, "invalid key" yada yada, and I'll have to waste time straightening it out.

    0

投稿コメントは受け付けていません。