missing- api-ms-win-crt-runtime-|1-1-0.dll

[eryk sun]

On Tue, Sep 18, 2018 at 1:43 PM, Gene Heskett <gheskett at shentel.net> wrote:
>
> <https://www.techadvisor.co.uk/how-to/windows/how-fix-api-ms-win-crt-runtime-l1-1-0dll-error-3676874/>
>
> So apparently the | is a legal filename component, to a windows box.

"l1-1-0" starts with "l" (ordinal 0x6c, i.e. lower-case "L"), not "|"
(pipe, 0x7c).

Other than the OS path separator, \ (backslash, 0x5c), the set of
reserved characters is up to the file system. It's recommended to
reserve NUL (0x00), / (slash, 0x2f) and the 5 wildcard characters:
*?"<> (0x2a, 0x3f, 0x22, 0x3c, 0x3e). NTFS additionally reserves :
(colon, 0x3a) as the delimeter for stream names and types, | (pipe,
0x7c) for no good reason, and control characters (0x01 - 0x1F). In
contrast, if you're running Windows as a guest OS in a VirtualBox VM,
its VboxSF file system (for sharing folders with the host OS) actually
allows colon, pipe, and control characters in filenames.