To Mike Gilbert,
The file:// URL is not incorrect. Your given URL link answers and explain everything.
But for the sake of other readers I will include a part of it here.
A file URL takes the form of "file://host/path".
where host is the fully qualified domain name of the system on which the path is accessible, and path is a hierarchical directory path of the form directory/directory/.../name. If host is omitted, it is taken to be "localhost", the machine from which the URL is being interpreted. Note that when omitting host you do not omit the slash ("file:///foo.txt" is okay, while "file://foo.txt" is not, although some interpreters manage to handle the latter).
On my report this one works for me.
Meaning of slash character
The slash character (/), depending on its position, is used in different meanings in a file URL.
The // after the file: is part of the general syntax of URLs. (The double slash // should always appear in a file URL according to the specification, but in practice many Web browsers allow you to omit it, in some cases at least.)
The single slash between host and path is part of the syntax of file URLs.
And the slashes in path separate directory names in a hierarchical system of directories and subdirectories. In this usage, the slash is a general, system-independent way of separating the parts, and in a particular host system it might be used as such in a pathname (as in Unix systems).
This is one is also correct because this is the correct URI as understood by the Windows Shell API.
To all the readers thank you very much for appreciating this article.