wmv files are not "session" friendly i.e. you can't deliver them when the "Files Provider" searches for an authorization token before delivering them to the end user.
If you look behind the scenes of your browser (<F12> o Fiddler) you'll see a first successful download of the first e.g. 768KB than a subsequent request carrying out no cookies i.e. no auth token i.e. no content to the end user.
It's a known issue of that file format, even in Moodle: MDL-15642. Since Moodle will always check if you're authorized to access those files before sending them to you, wmv files will never work unless you'll change the strategy to serve those files e.g. outside Moodle.
That being said, if the files not served are just the wmv files, you could create a folder exposed via HTTP and within the same domain of your Moodle instance (e.g. just add a folder named /extpackages/ under the Moodle wwwroot), drop the unzipped package there and publish the SCORM package into Moodle by referencing that external package via the imsmanifest.xml file. Everything will work since the "external repository" (a plain HTTP-exposed folder) will not perform any auth check on any served file. Refs.: http://danmarsden.com/blog/2012/11/01/managing-scorm-content-in-moodle-2/.
Up to you to define if such kind of deployment could be a security issue for your SCORM content. There is also the possibility to customize the security checks in Moodle by accepting that wmv files will be always served regardless being logged in but this means that you need to remember that customization whenever you'll upgrade your Moodle instance (which should be done on a regular basis).