- Jan 9, 2016
- 3
- 0
- 4,510
Hi all,
I recently moved ~100 miles from my place of employment, and began working remote. I connect to the workplace resources using a VPN. I'm connected to my home network via Ethernet.
As a software developer, one thing that I have to do frequently is acquire somewhat large installation files (typically ~200MB). These installation files are placed on a Share Drive that I access from Windows 10. When I move the installation files from the Share Drive to my local machine and attempt to run it, 90% of the time, the installation fails due to it being corrupt.
I don't think it matters, but the file in question is an NSIS-compiled installation executable. The installation fails to run due to a failed validity check. If I attempt to bypass this check, the installer just fails differently.
What's particularly puzzling is that if I get lucky and the installer works, if I go back in an hour and attempt to run the installation again, it is corrupted. This made me think it was something to do with my hard drive, so I tried a different hard drive, and got the same results...
Let me know if any more info is needed. Perhaps there is a more reliable way of getting files from share drives? Thank you.
I recently moved ~100 miles from my place of employment, and began working remote. I connect to the workplace resources using a VPN. I'm connected to my home network via Ethernet.
As a software developer, one thing that I have to do frequently is acquire somewhat large installation files (typically ~200MB). These installation files are placed on a Share Drive that I access from Windows 10. When I move the installation files from the Share Drive to my local machine and attempt to run it, 90% of the time, the installation fails due to it being corrupt.
I don't think it matters, but the file in question is an NSIS-compiled installation executable. The installation fails to run due to a failed validity check. If I attempt to bypass this check, the installer just fails differently.
What's particularly puzzling is that if I get lucky and the installer works, if I go back in an hour and attempt to run the installation again, it is corrupted. This made me think it was something to do with my hard drive, so I tried a different hard drive, and got the same results...
Let me know if any more info is needed. Perhaps there is a more reliable way of getting files from share drives? Thank you.
Facebook
Twitter
Instagram