You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Azure Storage Explorer not showing correct number of files, if there are more than 7K file then it show up to 6809 or 6978 but file stored in container is more than that. I've downloaded the files and it show more that 20K but explorer show 6811. I've attached photo as well.
Steps to Reproduce
After upload file into container it is not showing right number of file.
Actual Experience
Not giving the right number
Expected Experience
No response
Additional Context
No response
The text was updated successfully, but these errors were encountered:
craxal
changed the title
Azure Storage Explorer not showing wrong number of files in container.
Azure Storage Explorer showing wrong number of files in container
Jan 23, 2025
@sachinmalla Can you double-check your architecture, please? We do not support 32-bit machines.
Can you also provide more information on the state of your blob container (I assume this is a blob container)? Specifically, how many blobs are in the container before uploading and after uploading (you can also verify using the Azure Portal)? If there are existing blobs, do you need to resolve conflicts? Does the container get a log of activity from other users? Can you identify any blobs that appear to be missing or shouldn't have been downloaded?
Preflight Checklist
Storage Explorer Version
1.37.0
Regression From
No response
Architecture
i86
Storage Explorer Build Number
No response
Platform
All
OS Version
No response
Bug Description
Azure Storage Explorer not showing correct number of files, if there are more than 7K file then it show up to 6809 or 6978 but file stored in container is more than that. I've downloaded the files and it show more that 20K but explorer show 6811. I've attached photo as well.
Steps to Reproduce
After upload file into container it is not showing right number of file.
Actual Experience
Not giving the right number
Expected Experience
No response
Additional Context
No response
The text was updated successfully, but these errors were encountered: