Announcement

Collapse
No announcement yet.

OSF v10 to v11 upgrade error - Failed to load OSFConfig file

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • OSF v10 to v11 upgrade error - Failed to load OSFConfig file

    I upgraded this morning from v10 to v11 and this error keeps popping up.

    Click image for larger version  Name:	image.png Views:	75 Size:	6.1 KB ID:	57475

    In the event it is an unexpected issue. I have now completely deleted all the files.
    I have reinstalled it with the same result.

    Message: "Failed to load OSFConfig file, reverting back to defaults"

  • #2
    Can you send us a copy of your current OSF config file for us to test/reproduce error with?
    OSF config file is typically saved at:
    C:\Users\<User>\Documents\PassMark\OSForensics\con fig.OSFCfg

    Can you also run OSF is debug mode (using option 2):
    https://www.osforensics.com/faqs-and...ebug-mode.html
    And send us the generated file

    You can email the files to: info@passmark.com

    Comment


    • #3
      Hi Simon, these files have been emailed to you.

      Comment


      • #4
        By chance, I discovered what caused the issue as I was getting similiar errors from other applications (r-studio).
        Message: "Allow an app through controlled folder access"

        Ransomware protection was turned on for my OneDrive folders. Now considering Windows wants everything to be on Onedrive, like my profile, it threw a hissy fit when an app wanted to change/access it. The solution to my problem was to allow OSF to have access to the controlled folders. After I had done this, no more issues. The irony of all this it was during a forensic course where I was demonstrating OSF and the features and I misclicked the notification and found the issue. Grr.

        Thanks for everyone that helped.

        Click image for larger version  Name:	image.png Views:	0 Size:	16.8 KB ID:	58036

        Comment


        • #5
          This seems like expected behavior once you have turned on this security feature. So I don't think it is anything we can "fix".

          Thanks for the update however. It will surely help some other users.

          Comment

          Working...
          X