Forum Discussion
Downloads in Edge Dev are incorrect
- Jun 12, 2019
I went and did this myself ismailhassani to see what results I would get. I am using Edge Dev (was updated today) and do not see the different file size like you have. Edge Can showed same file size and no issue in either executing the file(s).
Couple of thoughts
- It's possible the file size difference is due to a bad download/corruption, bad timing on a bad MSI that was changed at the time you downloaded after the first one - a long shot I'm sure, but possible,. or a Dev update fix.
- Make sure Edge is up to date as Dev was updated today -
Version 76.0.182.6 (Official build) dev (64-bit)
- How are you executing the file(s) via Explorer or letting Edge open?
- Is it possible you have a 3rd party app locking the installer file(s)?
- Are you doing this within Sandbox by chance?
Just trying to figure out what we have different between us to dig a bit further.
I went and did this myself ismailhassani to see what results I would get. I am using Edge Dev (was updated today) and do not see the different file size like you have. Edge Can showed same file size and no issue in either executing the file(s).
Couple of thoughts
- It's possible the file size difference is due to a bad download/corruption, bad timing on a bad MSI that was changed at the time you downloaded after the first one - a long shot I'm sure, but possible,. or a Dev update fix.
- Make sure Edge is up to date as Dev was updated today -
Version 76.0.182.6 (Official build) dev (64-bit)
- How are you executing the file(s) via Explorer or letting Edge open?
- Is it possible you have a 3rd party app locking the installer file(s)?
- Are you doing this within Sandbox by chance?
Just trying to figure out what we have different between us to dig a bit further.
- ismailhassaniJun 13, 2019Copper Contributor
DarrenMH Ok i tried it again today, and everything seems fine after i updated Edge.
Thank you.
ps.
The other possibilities (bad connection) didn't apply because downloading the file under MS Edge worked just fine. It was something inside de previous version of Edge dev.