Announcement

Collapse
No announcement yet.

4.09.1 gives "Internal setup error. Contact support." message

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • LocutusofBorg
    replied
    here is announcement to this issue:



    Sorry for any inconvenience, we had a small issue with older SPTD-driver version caused by latest release

    Leave a comment:


  • tgold
    replied
    Originally Posted by Riftgarde View Post
    I think the current download is corrupted. The one I downloaded from free-codecs.com was slightly larger in size and installed perfectly.
    disc-tools.com: daemon4091-x86.exe 1.71 MB (1,802,208 bytes)
    free-codecs.com: daemon-4091-x86.exe 1.72 MB (1,806,232 bytes)
    Many thanks, that did it.
    Tony

    Leave a comment:


  • ^eRrOR^
    replied
    I got mine from here ^_^

    Leave a comment:


  • ^eRrOR^
    replied
    Thanks

    Originally Posted by Blazkowicz View Post
    Have you tried to install SPTD manually (duplexsecure.com)?
    Thanks very muchly, that sorted that prob for me ^_^

    Leave a comment:


  • Riftgarde
    replied
    I think the current download is corrupted. The one I downloaded from free-codecs.com was slightly larger in size and installed perfectly.
    disc-tools.com: daemon4091-x86.exe 1.71 MB (1,802,208 bytes)
    free-codecs.com: daemon-4091-x86.exe 1.72 MB (1,806,232 bytes)

    Leave a comment:


  • Blazkowicz
    replied
    Have you tried to install SPTD manually (duplexsecure.com)?

    Leave a comment:


  • 4.09.1 gives "Internal setup error. Contact support." message

    I have been trying to update my Windows XP Pro box (Thinkpad A31, 2gb memory, NEC DVD burner) to Daemon Tools 4.09.1, but it always gives the "Internal setup error. Contact support." message.

    I have uninstalled the previous Daemon Tools installation (which was 4.08), rebooted, uninstalled PowerDVD, as someone here suggeted, turned off firewall and virus software, etc. etc. etc. and nothing has worked. I still ALWAYS get that message when I try to install it.

    Is there any developer out there who knows what causes this, or can give me a flag to make the installer spit out some debug log so we can fix this? LOTS of people have had this problem, seemingly.

    - Tim
Working...
X