-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug: Force Close when Rearranging Pin items in side bar #16808
Comments
Thanks for the report, the log doesn't show any errors, can you type Event Viewer into the Windows start menu search > Click Windows logs > Click Application > Screenshot the first error that have Files.exe shown on the first line > Send this on GitHub (Email attachments don't work) |
I had this as well this evening on the 1st usage. Once reopened, the app seemed ok and didn't do it again on reordering them. |
@Rockisaway Can you provide the asked information above |
@Rockisaway Can you see if this is still an issue in the preview version https://files.community/download If so, can you type Event Viewer into the Windows start menu search > Click Windows logs > Click Application > Screenshot the first error that have Files.exe shown on the first line > Send this on GitHub (Email attachments don't work) |
This comment has been minimized.
This comment has been minimized.
Please screenshot the error. GitHub will format the text wrong otherwise. Can you also try the preview version |
Unfortunately it only says that Windows force closed Files with no reason as far as I can see. |
I found this from at WinRT.ExceptionHelpers.g__Throw|39_0(Int32 hr) 無法指出的錯誤 |
I found that even unpinning folder crashes as well. |
Description
I just downloaded the application for files and it keeps force closing whenever I am trying to rearrange the pinned items in the sidebar. So far it won't let me actually save a new order.
Steps To Reproduce
Files Version
3.9.1.0
Windows Version
10.0.26100.3194
User ID
2cbaca5a-a95b-4527-a525-e44b93be7a88
Log File
debug.log
The text was updated successfully, but these errors were encountered: