Error Reparse 741 (0x2E5): Fix it With 4 Steps

If you’re a system administrator, sometimes you may encounter an ERROR_REPARSE message. This error code appears when working with files, so in today’s guide, we’re going to show you how to fix it.

How can I fix ERROR_REPARSE?

1. Verify the rephrase point

1. Open the command line.
2. Next, run the following command, but replace the <path> with the destination directory: dir /al <path>
    
3. Look for <SYMLINK> or <JUNCTION> in the output.

2. Resolve or update the symbolic link

1. Open the command line.
2. Next, run the following commands:
   del /aL <path>
mklink <path> <new_target>
   
3. Remember to replace the values with the correct paths.

This will delete the previous link and create a new one.

3. Give full control to the specific user

1. Once again, open the command line.
2. Run the following: icacls <path> /grant <user_or_group>:F
   
3. Remember to replace the path and user with the correct values.

After that, the selected group or users will have full control and the ERROR_REPARSE should be gone.

4. Other solutions to try

1. Ensure that the application or script supports symbolic links.
2. If working with rsync or scp, ensure they are configured to follow or ignore symbolic links.
3. Use correct paths. Symbolic links might work better for absolute paths.
4. Use Sysinternals Process Monitor to trace file operations and determine where the symbolic link is pointing.
5. Ensure that your file system supports reparse points. For example, FAT32 doesn’t support this feature.
6. If you’re writing a script, use the GetFinalPathNameByHandle function to resolve reparse points.

The ERROR_REPARSE often is represented by the following message: 741 (0x2E5) A reparse should be performed by the Object Manager since the name of the file resulted in a symbolic link.

This isn’t the only issue, and we wrote about DRIVER_RETURNED_STATUS_REPARSE_FOR_VOLUME_OPEN and ERROR_DYNLINK_FROM_INVALID_RING in our previous guides, so don’t miss them for more information.