Skip to content
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

Rufus detects wrong size for Windows 8.1 Pro VL with Update (x64) ISO #554

Closed
pbatard opened this issue Jul 28, 2015 · 2 comments
Closed
Assignees
Milestone

Comments

@pbatard
Copy link
Owner

pbatard commented Jul 28, 2015

As per this reddit thread, Rufus reports that a 4.4 GB ISO (en_windows_8.1_pro_vl_with_update_x64_dvd_6050880.iso) is more than 17 exabytes in size!

Will try to get my hand on that ISO to see if I can replicate the same result and fix it.

@pbatard pbatard added the Major label Jul 28, 2015
@pbatard pbatard self-assigned this Jul 28, 2015
@pbatard pbatard added this to the 2.3 milestone Jul 28, 2015
@pbatard pbatard changed the title Rufus detects wrong size for IR5_CPRA_X64FREV_EN-US_DV9 ISO Rufus detects wrong size for Windows 8.1 Pro VL with Update (x64) ISO Jul 28, 2015
@pbatard pbatard removed the Major label Aug 4, 2015
@pbatard
Copy link
Owner Author

pbatard commented Aug 4, 2015

Considering that I haven't been able to replicate the issue, and OP was unable/unwilling to provide additional details with regards to the non-official ISO they were using, as well as the fact that nobody else has been reporting a similar problem, I have no choice but to assume that this is an environmental issue on OP's computer.

The check for size is a fairly straightforward one, using a single call to Microsoft's APIs, and I don't see anything surrounding that code that could explain how the size could be populated so wrong. Short of having a memory leak that would overwrite the size value (but then I would expect many people to report weird issues with Rufus), I don't see how what OP experienced could have anything to do with the code.

I will close this issue, and wait for somebody else more willing to collaborate with the troubleshooting process to report a similar problem, if any.

@pbatard pbatard closed this as completed Aug 4, 2015
@lock
Copy link

lock bot commented Apr 7, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue if you think you have a related problem or query.

@lock lock bot locked and limited conversation to collaborators Apr 7, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant