microsoft / microsoft/PowerToys
Image Resizer does not immediately modify file size when "Overwrite Files" is checked
- Dominant language
- C
- Stars
- 139k
- Forks
- 8.6k
- PR merge metrics
- PR metrics pending
Description
### Microsoft PowerToys version
0.95.0
### Installation method
PowerToys auto-update
### Area(s) with issue?
Image Resizer
### Steps to reproduce
1. Select an image with an easily identifiable "large" file size - for my example, the image is about 20 MB
2. Resize the image with Image Resizer, I resized to "Large". Make sure that "Overwrite Files" is checked.
3. Check the file size of the "new" overwritten file.
### ✔️ Expected Behavior
Within a couple of seconds of the file being resized and overwritten, the file size should update to the new file size.
### ❌ Actual Behavior
The file size does not immediately update. In my experimentation, it takes 1-2 minutes for the file size to actually update. During that time, the file size stays the original file size, not the "new" overwritten file size.
Note that if you don't "Overwrite" the original file, the actually "new" file will be appropriately sized.
### Upload Bug Report ZIP-file
[PowerToysReport_2026-05-23-19-09-23.zip](https://github.com/user-attachments/files/28185079/PowerToysReport_2026-05-23-19-09-23.zip)
### Additional Information
These operations were done on Windows 11, and the files resided on an M.2 NVME SSD
Perhaps the file size is cached by windows or something, I'm not sure how file sizes work. I'd imagine there's some form of cacheing of file sizes.
### Other Software
Not a VM or anything, I'm running baremetal Windows on an M.2 NVME SSD
I do have a 4 TB hard drive connected as well, but the file operations were not done on that.
Contributor guide
Research direction
Start by reproducing the Image Resizer overwrite flow on Windows 11 with a large image, comparing the delayed size update with the non-overwrite case. Trace the overwrite operation and verify that the replaced file reports its new size within a couple of seconds; no source file or test is identified in the issue.
Written by the indexing model from the issue text.
Assessment
- Domain
- desktop, operating-systems
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100