Closed lowercase-donkey closed 1 year ago
I've been experiencing the same problem for a couple of weeks now
Same here too, seems to be caused by the new "explorer" version
Hi,
I could not reproduce this error, it seems to work. Did you do something special before or its always happenning if you click on Add/Change Folder?
My windows version is:
Hello, Since reporting this issue back in December, I discovered the problem was caused by a Microsoft OneDrive update. I also found a temporary solution on a Microsoft forum: https://answers.microsoft.com/en-us/windows/forum/all/windows-11-browse-for-folder-dialog-issue-only/0a0ce0a5-0a72-4483-a51e-1b3ee9dffcdb?page=1
I hope I am not violating any rules by copying and pasting from the forum the solution that worked for me. Here it is:
**"OneDrive seems to be the culprit. The workaround is to stop syncing your Desktop folder with OneDrive.
Important: Before proceeding, copy the files in those special folders to another folder or external drive. Please don’t copy them anywhere under Desktop/Documents/Pictures. This is because disabling OneDrive backup for a folder erases the local copies of the files. Copying them to a different location beforehand will ensure that you don’t need to download them again from the OneDrive cloud.
Right-click the OneDrive icon in the Notification area and click Settings. Select the Backup tab, and click Manage Backup In the Manage folder backup dialog, click on the Stop backup link for "Desktop" Click Stop backup in the confirmation dialog that appears.
Ramesh Srinivasan Microsoft MVP (2003 to 2012), Windows Shell."**
Oh god windows onedrive is so stupid... Thx for the solution !
Solved and not a bug -> Closed
When I try to select or change a folder, all I get is this:
Desktop
cannot be expanded in any way.My current windows version:![image](https://user-images.githubusercontent.com/28416282/203610484-d681c14c-8fa3-4f94-ab77-ff0ffb0aecba.png)
For those that need a workaround, you can edit the default starting location in the XML:
This obviously is still very limiting.
I do note #143; hopefully this is already fixed internally and we get a release soon. Thanks!