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

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

C1 20 installation issue on Win10 Pro

コメント

6件のコメント

  • Paul Steunebrink
    Are you logged in as an Administrator on your machine(s)?

    Did you had Capture One installed earlier, which was not uninstalled with the installer, but just had its files removed (no meaning to offend you)?
    0
  • NNN637030423507154273
    Paul_Steunebrink wrote:
    Are you logged in as an Administrator on your machine(s)?

    Did you had Capture One installed earlier, which was not uninstalled with the installer, but just had its files removed (no meaning to offend you)?


    Thanks for the reply. Yes I'm the local admin on these machines; sorry forgot to mention that part earlier.

    As for the second question ... this is a brand new installation; and a fresh install of Win10 Pro as well.
    The other Win10 Pro machines I tested against (and failed) were also fresh install of Win10 Pro.
    0
  • NNN637030423507154273
    Here is the actual error message screenshot ...

    http://www.sleepyhead.duckdns.org/nextcloud/index.php/apps/gallery/#Photos/Capture_Screen.JPG
    0
  • NNN637030423507154273
    Ok ... found a workaround for the issue.

    I booted Win10 in Safe mode and ran the installation from there; it worked. I still don't understand why it doesn't work in Normal mode; but for the time being I'm able to move on 😄
    1
  • Paul Steunebrink
    NNN637030423507154273 wrote:
    Ok ... found a workaround for the issue.

    I booted Win10 in Safe mode and ran the installation from there; it worked. I still don't understand why it doesn't work in Normal mode; but for the time being I'm able to move on 😄

    It is a common error message in Windows 10 (just google for it). Smart move to try save mode. In that mode all kind of configurations are not loaded. It might be one of those that made it happen.

    You're fine now, and that's what counts.
    1
  • Vincent Englebert

    Same problem with a new PC (win10 prof). The safe mode solved that issue (so far) also. It would be nice to fix this issue for the next times... ;-) 

     

    1

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