x/build/cmd/release: Windows installer fails to open device or file when installer file is located on ram disk #35251
Comments
Thanks for the report. @tamayika Out of curiosity: is the inability to run the installer from a ramdisk a showstopper for you (and if yes, can you explain why, and what your use-case is)? Or does the obvious workaround - not running the installer from a ramdisk - work well for you, and this is more of an "exotic" defect report? I'm asking because the answer may help assessing the seriousness of this issue. |
I usually use Firefox for browsing, and its download destination is ram disk. This is useful to cleanup unnecessary downloaded files when rebooting os. |
@tamayika I know very little about how Go installer works. I cannot help you. Alex |
What version of Go are you using (
go version
)?go1.13.3.windows-amd64.msi
Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
What did you expect to see?
Installer installed files successfully.
What did you see instead?
Error dialog shows like attached images which means "cannot open the device or file specified" in japanese. Retry does not have any effect.

If I moved installer to physical disk, installer works fine.
I've never experienced this problems in other installers.
The text was updated successfully, but these errors were encountered: