files-community / files-community/Files

Bug: After changing the folder name, renaming a subfolder will cause an error.

Open
#18,698 2 comments 0 reactions 0 assignees View on GitHub
area - columns view
Dominant language
C#
Stars
45.4k
Forks
2.9k
Avg merge
19h 7m
Merged PRs (30d)
62

Description

### Description

https://github.com/user-attachments/assets/76478f65-397a-44de-b401-93462f47daa9

1. This file is being used by another program.
2. Item not found
3. Has this folder been deleted?

### Steps To Reproduce

1. In the "Test" folder, select the "CCC" folder and rename it to "Test_C".
2. After typing "Test_C", directly click on the "123" folder inside the "CCC" subfolder. This triggers **BUG-1**:
3. You must now click on a blank area of the window, or any folder outside the "CCC" folder, to clear this bug state.
4. Now rename the "CCC" folder again, and it can be successfully renamed to "Test_C".
5. Now you can directly select the "123" folder without triggering **BUG-1**.
6. After selecting the "123" folder, click the rename button and change the name to "ABC". This triggers **BUG-2**.
7. Click on a blank area, then select the "123" folder again. This triggers **BUG-3**.
8. Select a different folder at a higher level to clear the bug state. Then go back to the "123" folder, and you can rename it freely.

### Files Version

4.2.0.0

### Windows Version

10.0.26200.8737

### User ID

5be1ab97-a6f8-4ceb-8e51-64d2d86df27a

### Log File

[debug.log](https://github.com/user-attachments/files/29804596/debug.log)

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the rename sequence in the Files app on Windows 10/11, following the listed steps for the Test, CCC, and 123 folders. Review the attached debug.log alongside each reported error; done means renaming the parent and nested folders no longer produces BUG-1, BUG-2, or BUG-3.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.