Search Issue Tracker

Fixed

Fixed in 6000.4.11f1, 6000.5.0b12, 6000.6.0a7

Fix In Review for 6000.3.18f1

Votes

3

Found in

6000.3.16f1

6000.4.8f1

6000.5.0b9

6000.6.0a5

Issue ID

UUM-142421

Regression

Yes

[Windows] Package installation fails non-deterministically with Errors "EPERM: operation not permitted" when installing Packages

Packman

-

Steps to reproduce:

  1. Create 2 new URP 3D Projects
  2. In both Select all Feature Sets at the top of the Packages List when the Unity Registry List of the Package Manager is selected
  3. Install all selected Feature Sets

Actual results: Error is logged and Package installation stalls: " Error adding/removing packages", "One or more dependencies could not be added to the local file system:
      com.unity.2d.psdimporter: EPERM: operation not permitted, rename 'D:\Projects\My project (2244)\Library\PackageCache\.tmp-71444-JYuoN5aQyGlt\package' -> 'D:\Projects\My project (2244)\Library\PackageCache\com.unity.2d.psdimporter@bbb90878229a'
      com.unity.2d.spriteshape: EPERM: operation not permitted", ..."

Expected results: Installation of Packages does not fail, no errors are logged

Reproducible with versions: 6000.3.15f1, 6000.3.16f1, 6000.4.8f1, 6000.5.0b8, 6000.5.0b9, 6000.6.0a5

Not reproducible with versions: 6000.0.75f1, 6000.3.14f1

Tested on (OS): Windows 11
Notes:

  • Issue does not reproduce all of the time, around 2/5 times
  • I've had more success in reproduction when installing the Feature Sets with 2 Editors open
  • This can also reproduce when creating Templates, indicating this might also affect single Package installations non-deterministically
  • Issue might be reproducible on 6.0 as well, not determined
  1. Resolution Note:

    Fixed in 6000.6.0a7

  2. Resolution Note (fix version 6000.6.0a7):

    Fixed in 6000.6.0a7

  3. Resolution Note (fix version 6000.3.18f1):

    Fixed in 6000.3.18f1

Comments (2)

  1. manuelgoellnitz

    May 27, 2026 14:56

    Sometimes this happens when VSCode is open. But not consitanty.
    I have this on one PC regardless.

  2. astamarr

    May 26, 2026 08:42

    This issue is a huge deal for us : it completely breaks our CI pipelines. It appeared with 6000.3.15f1 , 3.13 was fine.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.