Azurestorageexplorer: Cannot directly open blobs with no file extension on Windows 10 1903

[neilrees]

Storage Explorer Version: 1.9.0
Build Number: 20190701.8
Platform/OS: Windows 10 1903
Architecture: x64
Regression From: Regression from behavior on Windows 10 1809

Bug Description

When double clicking a blob to open it and the blob does not have a file extension (e.g. configuration), rather than showing the "Open file with" windows dialog, you instead receive an error dialog: e.g.:

Steps to Reproduce

1. Navigate to a Storage Account -> Container that contains a blob without a file extension
2. Double click the blob

Expected Experience

Expect to receive the standard Windows "How do you want to open this file" picker:

After picking an application from the list the file would be opened in the selected app.

Actual Experience

An error is received:

The file cannot be opened in an editor without downloading it explicitly.

Additional Context

The behavior is as expected on Windows 10 1803 and 1809, but shows the error on 1903.

[OzBob]

I have the same issue on 1903

Work around:
Right click on the blob | Download
Save.
Open Windows Explorer
Double click file
Choose a program to open file, e.g. notepad
or Optionally rename file to have .txt(?) extension

[MRayermannMSFT]

@JasonYeMSFT , let's look into this while doing AzCopy open.

[MRayermannMSFT]

Ok, I'm on 1809 and things are working as expected....I'm going to update to 1903 and see what happens...

[MRayermannMSFT]

Yep, it regresses on upgrade. Unfortunately there doesn't seem to be anything we can do on our side for this. I'll need to file an electron bug tomorrow. Sorry y'all. 😰

[MRayermannMSFT]

Filed Electron issue: https://github.com/electron/electron/issues/20543

We'll continue monitoring that.

[neilrees]

@MRayermannMSFT Electron have closed the bug - where does this go next?

[MRayermannMSFT]

They believe it is an issue in Windows. So we need to do some more investigation.

[neilrees]

I've now seen this issue in a number of electron based applications. Is there an upstream bug we can be tracking?

[OzBob]

@MRayermannMSFT : do you have a windows issue for us to monitor?

[OzBob]

@jinglouMSFT I've tried double clicking on a file and the same error is reported.
Storage Explorer Version: 1.13.1
Build Number: 18362.836
Platform/OS: Windows 10 1903
Architecture: x64

[jinglouMSFT]

This is still repro with Storage Explorer 1.13.1 and Windows 10.1909. Will enter a bug on Windows.

[jinglouMSFT]

Reported the issue to Windows. It is Bug 26623267 in Windows 10 Feedback hub.

[jinglouMSFT]

Reporting back on the Windows bug - There was a regression in the ShellExecute API in Windows 10 builds 190x. This issue has been fixed in Windows 10 build 2004. Build 2004 is currently being rolled out gradually. In terms of a workaround if you are on Windows 10 build 190x and if you are comfortable modifying your Windows registries, you can associate the file extension (no-extension) there. We don't recommend this if you don't normally modify the registries as the impact is system wide. Another workaround is to down load the file/blob to a local temp folder, and open it from Windows File Explorer. This is the default download experience in Storage Explorer. The association in the File Explorer works just fine.

[neilrees]

Thanks @jinglouMSFT can confirm that upgrading to Windows 2004 has solved this 👍

[jinglouMSFT]

That's great. Thanks much for letting us know.