The successful reading of an URL containing blank spaces is a browser behavior and we cannot control it. This is why when a browser is not able to handle such URL, FileExplorer receives the part of the name, which is readable for the specific browser.
The only workaround I could suggest you is to implement a custom logic, which is encrypting the file's name by replacing the white spaces and then decrypting it when the file is being downloaded.
the Telerik team
If you want to get updates on new releases, tips and tricks and sneak peeks at our product labs directly from the developers working on the RadControls for ASP.NET AJAX, subscribe to their blog feed