1. Welcome to the Starbound support forums. Please check the support FAQs before posting: http://playstarbound.com/support

Resolved fatal exception caught: (IOException) could not change directory to

Discussion in 'Starbound Support' started by rimir, Mar 2, 2018.

Thread Status:
Not open for further replies.
  1. rimir

    rimir Void-Bound Voyager

    help guys, when you start the game it crawls out this error before played with the mods and without that there was not.
    I'm Russian and translated through an interpreter, sorry for mistakes.
     

    Attached Files:

  2. Iris Blanche

    Iris Blanche Pudding Paradox Forum Moderator

    It seems starbound isnt allowed to access its own folders. You will have to setup correct permissions so that starbound is allowed to access its own folders. Normally this isn't an issue unless you're using a restricted local account. It can also be caused by steam running in admin mode during install but not starbound.
     
  3. rimir

    rimir Void-Bound Voyager

    I'll try
     
  4. rimir

    rimir Void-Bound Voyager

    if permissions are placed in the properties in the security tab, then I have everything right but the error still remains
     
  5. Iris Blanche

    Iris Blanche Pudding Paradox Forum Moderator

    Which OS are you using?
     
  6. rimir

    rimir Void-Bound Voyager

    Windows 10 build 1709
     
  7. Iris Blanche

    Iris Blanche Pudding Paradox Forum Moderator

    Try adding the path to starbound to your exception list of windows defender.
    Normally permissions are set up correct during install.
     
  8. rimir

    rimir Void-Bound Voyager

    did not help :(

    starbound moved to drive C, now the game is running. I do not understand what the problem is.
     
    Last edited by a moderator: Mar 4, 2018
  9. Iris Blanche

    Iris Blanche Pudding Paradox Forum Moderator

    Your OS was restricting starbound to access its own folders causing this error. Since it is working now im closing the topic and mark it as resolved.
     
Thread Status:
Not open for further replies.

Share This Page