Thank you for the suggestion. I have considered linking the entire user folder; however, my testing indicates that the root of the problem involves how the game now parses directory depth and handles OneDrive-managed paths since the update.
Even when the link is active, the game appears to 'bypass' it and generate a fresh, physical directory on the C: drive. Furthermore, I've noticed that the update has significantly tightened the allowed 'levels' for mod loading. Because a junction or symlink technically adds a layer to the file path, my script mods (which must be at Level 1) are being pushed to Level 2 in the eyes of the game engine, causing them to fail even if the link technically 'points' to the right place.
With 105GB of content, moving the entire user folder via a symlink often triggers 'Access Denied' or 'LiveKernelEvent' errors in my DxDiag, especially with OneDrive active. At this stage, only a physical folder directly on the C: drive seems to be recognized by the game’s startup crawler. Is there any known change to the game's file-system permissions in this patch that would explain why it is now prioritizing local physical directories over established Windows junctions?
