Jump to content

slabbi

Members
  • Content Count

    5
  • Joined

  • Last visited

About slabbi

  • Rank
    Newbie

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Well, it is not always the same process, that's why the problem is so hard to identify. After windows has been restarted you can usually update Affinity Photo without any problems. After some time some processes seem to "hijack" the folder (or maybe all folders containing "Photo" or something similar in the name). On my system it is BrCtrlCntr.exe (Brother ControlCenter 4) in 90% of all cases but not always. On other systems I found other processes in the past. The problem with the setup program is, that is removes in a first pass all files (which succeeds), then remov
  2. For everybody who has this Problem: Use the Process Explorer (procexp64.exe) from the Sysinternals Suite to find out which process blocks the "Photo" folder: https://docs.microsoft.com/de-de/sysinternals/downloads/process-explorer 1. Start the Process Explorer and search (Ctrl+F) for "photo". 2. Check the list which process still accesses "C:\Program Files\Affinity\Photo" folder. 3. Terminate the program or use Process Explorer to kill the process. Restart the setup program, enjoy.
  3. For everybody who has this Problem: Use the ProcessExplorer (procexp64.exe) from the SysinternalsSuite to find out which process blocks the "Photo" folder. 1. Start the ProcessExplorer and search (Cntrl+F) for "photo". 2. Check in the list which process blocks "C:\Program Files\Affinity\Photo" folder. 3. Exit the program or use ProcessExplorer to kill the process. Restart setup program, enjoy.
×
×
  • Create New...

Important Information

Please note there is currently a delay in replying to some post. See pinned thread in the Questions forum. These are the Terms of Use you will be asked to agree to if you join the forum. | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.