Cant Download Serum Demo

Started by djbj112de

Hey There,
I cant download the Demo for Serum completely.
it gets stuck at 132mb of 151mb
I tried several times but nothing changed, everytime the same problem
can anyone help?
Thanks a lot

Sorry to hear it - you can write me on the contact form and let me know the OS you use, and I can send a mirror link via email.

Hi Steve, It's the same for me. Been trying to download this a few times and it just stops there here and there. Can't use a program that allows resuming either.

Thanks

Everything I buy can't be downloaded, it's stuck. My computer is the windows10 operating system。thank you。

I would suggest to try another computer or physical location if possible. We use Amazon S3 which tends to be very reliable and everything is working well here. Write me via [email protected] or contact form if you are unable to solve that.

SteveBurley2000

Hi I have a similar problem, that may give a clue to the above issues, I am running a PC, Windows 10 with Norton 360 Premier installed.

When I download and try and run the Serum demo exe, Norton throws up a WS.Reputation.1 security warning and deletes the file. This warning is for the detection of files that have a low reputation score based on analyzing data from Symantec’s community of users. Yet Cubase 9.5, released today is fine.

So maybe the other users antivirus software is causing their issues too.

Normally you can tell Norton that you will accept the risk of the file you have downloaded and restore it and install it, but in this case I cannot.

I guess I'll just have to wait a few more months until enough Norton users say the file is safe. Although I'm not sure how that works, if you can't override Norton.

SteveBurley2000

Thanks steve_xfer, got there in the end, shouldn't you guys upload the exe to the Norton 'false positives' process mentioned on your link to get the file excluded from Nortons overly keen anti virus porcess?

I've done that at least 5 times, but every time I update they reset the reputation. I'm going to codesign the executables which should mitigate it, I hope (or I just wasted a bunch of time and money!)