Skip to main content

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

System Temp folder not found - TEMP environment variable -SOLVED!

Permanently deleted user
  • Edited

Hi,

I've come across an issue I cannot understand,

When trying to start C1-21 I get an error stating:

"System Temp folder not found. The "TEMP environment variable might be set wrong. This program will now exit."

No indication how to fix, and I've tried to re-add the environment variable but to no avail..

Anyone seen anything like this?

0

Comments

10 comments

Date Votes
  • BeO
    Top Commenter

    Never seen this.

    In the Windows search box, if you type %temp%, do you get a folder which you can open?

    0
  • Permanently deleted user

    Yeah, I get the correct one for my current user:

    "C:\Users\mansp\AppData\Local\Temp"

    And it opens and I've got recent stuff from other SW

    Tried re-installing(not a full uninstall just yet) Capture one as well but didnt change anything.

    I did a clone of the C-drive (swapped an old SSD for an M.2 SSD) about 1 month and a half ago, but I checked everything right after and C1 worked as it should and I used it for about a week, since then I havent really taken any pictures so I have not opened C1.

    0
  • BeO
    Top Commenter

    Hm, and you did not upgrade C1 since the SSD swap?

    You sound as if you were able to read log files. So maybe the C1 application.log can give you a hint:

    C:\Users\mansp\AppData\Local\CaptureOne\Logs

    0
  • BeO
    Top Commenter

    Or the Windows event viewer (eventvwr.exe)

    0
  • Permanently deleted user

    Good ideas!

    Windows event viewer just states on "Information"-level that Capture one has closed with code 0.

    No critical errors as far as I can see.

     

    Shutdown phase of last time I could work in C1 seems ok, cleaned temp files, all good. no crash:

    Application.log 2021-12-16 20:19 - Last working example
    Cleaning up temporary files
    Cleaning up temporary files in C:\Users\mansp\AppData\Local\Temp\CaptureOneTemp1
    Temporary file clean up completed
    Shutdown of managers and cores completed
    Closing app: Closed the IC crash handlers
    Shutdown end

    From the newer logs where I cannot get the program to run, I can see that after "Checking temp path exists" the program goes to "Closing...". But it doesnt really give me much else..

    Application.log - 2022-01-21 12:39
    INFO : Program closed correctly on last run.
    Checking temp path exists
    Closing...
    Saving Documents...
    Saving ApplicationSettings...
    Closing app: Closing the IC crash handlers
    Shutting down processors
    Warning: Detected call to an uninitialized processor
    Cleaning up temporary files
    Shutdown of managers and cores completed
    Closing app: Closed the IC crash handlers
    Shutdown end

    I did upgrade yesterday, from 14.1.0.74.20 to 14.4.1.6.30 to see if it helped. But the between the working run and two days ago I did not upgrade or use C1.

     

    I will try to fully remove C1, all configs etc, later tonight and see if that helps.

    0
  • Permanently deleted user

    OK.. I couldnt wait. (Working from home anyway..)

    I uninstalled, removed all files in user/AppData/Local and C:/program files

    I retained the catalog files though.

     

    Same error.

    0
  • BeO
    Top Commenter

    yep, not very helpful, that log file doesn't even have the message from the message popup box.

    0
  • BeO
    Top Commenter

    Maybe some Windows maintenance, update etc. would help.

    1
  • Permanently deleted user

    Hi,

     

    For anyone having this issue in the future, the following solved it for me:

    Did an upgrade/re-install from a windows .iso file. 
    Not a full reinstall of windows luckily...

     

    Possibly it could have been solved otherwise, but checking for corrupted windows configs etc with powershell yielded nothing and forcing reupdate of windows latest also didnt help. Removing and re-adding the environmental variables also didnt fix it.

     

    Thanks BeO for your help

    1
  • BeO
    Top Commenter

    Glad you figured it out. Hopefully the next Windows updates won't void your efforts.

    0

Post is closed for comments.