www.sarducd.it

[sweepy]

I've just paid for the full pro tech version, installed (updated) it, checked that it had updated the licence, then tried to add a single iso - Windows 10 iso - and got the message 'iso limit reached for this SARDU version' and telling me I need to buy the pro version...

Am I doing something wrong?

many thanks

[davidecosta]

Good morning,
The best and fastest solution to receive assistance for pro users is to open a ticket or send an email

You have updated SARDU manually.
Can you rebuild your update ?

software manually, these are the step:

1 -Open software SARDU
2 -Go to "?"
3 -Create update file (.upd) and save it in the desktop (need your mail and serial code)
4 -Go to https://www.sardu.pro/account.php
5 -Press the button "Manual update" and choice the saved update file .upd from desktop
6 -The server return you one file, save it in the desktop
7 -Return in the software SARDU
8 -Go to "?"
9 -Import Update file

Let me know



Davide

[sweepy]

hi
Many thanks for your reply.

I have imported the update file and it is still saying my iso limit is reached and I need to upgrade. The program says at the top 'Multiboot Creator 3.4.2 Pro Tech Lifetime' (it already said this) so I appear to have the correct version.

But when I right click on e.g. 'Installer 10 - only pro licences' and then select 'Search ISO' I get the error 'Iso managed by Sardu multiboot creator limit reached by this version....'

Any ideas why it is doing this? Do I need to deregister my original free registered version first?

thanks

[davidecosta]

NO.
Now your account is enabled for 3 PC PRO.


Do you have one antivirus, firewall or Proxy which forces you to use manual updating ?

[sweepy]

Now resolved following excellent support from Davide.

It seems my Firewall/AV were the the culprits - I'm not sure exactly which one yet - but I resolved it by turning them both off completely. I've now run another update and have got full functionality.

It looks like AV/Firewall was preventing the Sardu update process from running fully, so although update appeared to have run (my version was showing as having updated to 'Pro'), in fact not ALL the old files were actually updating, with one or more of the old 'non Pro version' files not being over-written as they should.

[davidecosta]

Thanks