Search Unity

  1. Unity Asset Manager is now available in public beta. Try it out now and join the conversation here in the forums.
    Dismiss Notice

Failed to resolve packages

Discussion in '2018.1 Beta' started by MonsterYu, Apr 28, 2018.

  1. MonsterYu

    MonsterYu

    Joined:
    Apr 8, 2018
    Posts:
    7
    Failed to resolve packages: EPERM: operation not permitted, mkdir ''. No packages loaded.
    A re-import of the project may be required to fix the issue or a manual modification of H:/Project Test/Unity 2018.1 TestProject/Unity 2018.1 TestProject/Packages/manifest.json file.
     
    MonsterYu, Apr 28, 2018
    #1

  2. MonsterYu

    MonsterYu

    Joined:
    Apr 8, 2018
    Posts:
    7
     
    MonsterYu, Apr 28, 2018
    #2

  3. okcompute_unity

    okcompute_unity

    Unity Technologies

    Joined:
    Jan 16, 2017
    Posts:
    756
    Hi @MonsterYu ,

    Can you give us more details on your project? Which version of Unity 2018.1 are you using? b13, f1?

    It seems that Unity would want to create a folder in `c:\program files\nodejs\node_global npm`, this is not something that the software should do. Do you have this folder already on your system? Do you have *admnistrator* permission on your computer?

    Regards,

    Pascal
     
    okcompute_unity, Apr 30, 2018
    #3
    keth14 likes this.

  4. MonsterYu

    MonsterYu

    Joined:
    Apr 8, 2018
    Posts:
    7
    The error disappeared when I opened the software with administrator privileges.thank you！
    Version is 2018.1.0f1.
    I have deleted this folder.
    This project is newly built without adding anything.
     
    MonsterYu, May 1, 2018
    #4
    maisam_bin_khaqan1996 and Roman_Keivan like this.

  5. okcompute_unity

    okcompute_unity

    Unity Technologies

    Joined:
    Jan 16, 2017
    Posts:
    756
    Hi @MonsterYu,

    Thank you for the feedback! Glad this issue was resolved. We will test your use case, opening a project without administrative permissions, and make sure it doesn't generate errors for you or others.

    Your feedback will help us fix this issue!

    Thanks again,

    Pascal
     
    okcompute_unity, May 1, 2018
    #5
    Gazenvagin likes this.

  6. samuelb_unity

    samuelb_unity

    Unity Technologies

    Joined:
    Nov 13, 2017
    Posts:
    151
    Hi @MonsterYu could you help us in recreating this issue? Couple of questions for you:
    1) How did you install Unity? Using Unity Hub?
    2) Where is Unity 2018.1.0f1 located? (if using the Hub, go to Installs > On My Machine > see path)
    3) When you created your Test Project, were you using the same Windows account that installed Unity?
    4) Have you ever used npm and changed npm's global config?
    5) To fix the issue, did you open Unity.exe as administrator?
     
    samuelb_unity, May 1, 2018
    #6