My suggestions may or may not provide an answer for @Ahmed, but they seem to work in solving the SecureDownloadManager download problems for me.
SecureDownloadManager needs administrator privileges
I found that when my boot kiosk, even after many restarts, it was caused by the fact that SecureDownloadManager does not have administrator privileges (which I often forgot at the time). When I restarted SecureDownloadManager with the option "Run as administrator", he managed to find the place where it was stopped, and completed the boot process.
The following information applies to Windows 8.1:
The problem is finding SecureDownloadManager.exe. If you have a link in the Start menu, right-click on the tile and select "Open File Location." Then right-click on the link and select "Properties." You will find the location of SecureDownloadManager in the Start menu: if you do not have a link, you can find SecureDownloadManager in the registry by searching for keys for SecureDownloadManager and getting the execution path for it. In my case it was,
C:\Users\raymond\AppData\Local\e-academy Inc\SecureDownloadManager
Of course, you need to enable hidden folders in order to get into the AppData folder. When you find SecureDownloadManager.exe, right-click it, select "Properties", go to the "Compatibility" tab, check the box "Run this program as administrator", click "Apply", then "OK".
This is a programming problem.
Due to the fact that the problem with SecureDownloadManager lasts so long, no one guesses. But I know that I spent a lot of time on this problem, and I know that I am not alone. This, however, serves as a good example of how not to program, but ??
I have to disagree with @Dukeling. This question is a topic in the programming forum, because many, many computer programming students spend their time on unsuccessful downloads when they can be busy programming. If you cannot get tools that you cannot program.
My last case was downloading a copy of Windows Server 2008 R2 for installation in a virtual instance to isolate software testing in a specific environment. Therefore, loading the OS, at least in my case, qualifies as a programming task.