[Windows] Archiving Codex tasks fails with ERROR_NOT_SAME_DEVICE (os error 17) #36289

Activity

1. github-actions

   added

   bugSomething isn't workingSomething isn't working

   appIssues related to the Codex desktop appIssues related to the Codex desktop app

   windows-osIssues related to Codex on Windows systemsIssues related to Codex on Windows systems

   sessionIssues involving session (thread) management, resuming, forking, naming, archivingIssues involving session (thread) management, resuming, forking, naming, archiving

   on Jul 31, 2026
2. suizhejiu commented on Sep 13, 2026

   

   suizhejiu

   on Sep 13, 2026

   More actions

   Related observation that may explain a cross-device move error while both session roots are on the same volume.

   On a Windows Desktop machine here, the MSIX package itself was installed to a secondary AppX volume, exposed through a junction:

   Get-AppxPackage OpenAI.Codex -> InstallLocation
     C:\Program Files\WindowsApps\OpenAI.Codex_<version>_x64__2p2nqsd0c76g0
   Get-Item <that path> -Force
     LinkType : Junction
     Target   : D:\WindowsApps\OpenAI.Codex_<version>_x64__2p2nqsd0c76g0
   Get-AppxVolume
     C:\Program Files\WindowsApps   IsSystemVolume = True
     D:\WindowsApps                 IsSystemVolume = False
   

   The app's own user-data path was also a reparse point, and the desktop log contained EXDEV: cross-device link not permitted for renames that appear to be inside a single directory. So the effective filesystem layout is not the plain single-volume layout the visible paths suggest.

   That is consistent with your finding that a move can cross devices even though the standard session root and archive root resolve to C:. It is a hypothesis for the mechanism, not a verified cause of the archive failure: I did not reproduce the archive error on this machine.

   For reference, the same cross-volume layout also broke the app's bundled-runtime relocation (no window, no codex.exe backend) and its bundled-plugin materialization, and moving the package to the system volume resolved those. Full write-up with before/after measurements: #40700 — #40700 (comment)

   If you still have the affected install, these read-only checks would confirm whether your machine shares the layout:

   Get-Item (Get-AppxPackage OpenAI.Codex).InstallLocation -Force |
     Select-Object FullName, LinkType, Target
   Get-AppxVolume | Select-Object PackageStorePath, IsSystemVolume