To post new answers or open threads, you need to log in. The registration is closed now, sorry. If you are not a member, you are welcome to read the posted content without any limitations. If you have any DAEMON Tools related question, contact our support team.
I had 3.47 on my system for a long time... no problems. I upgrade to 4 it removes the old on, all its assoicated drives go away and from device manager but when it gets to installing the SPTD install I get the System File Error.
Yes, it's a registry issue: HKLM\system\currentcontrolset\services\stpd\cfg is write protected. I could however not change the permission (being the administrator). Does anybody has an idea?
Did you have this error from the very first setup attempt?
It seems SPTD is already running on you system as it protects this key, but setup does not detect it somehow.
Any errors in system event log?
Try to delete sptd.sys and reboot (so it releases this key) then run setup again. What happens?
If you still get same error immediately then some other application blocks access to registry in general.
Where can I find this System event log? (I had the same problem, posted a thread about it, you asked me if there were any errors in my system event log)
This log just shows SPTD could not start after reboot but it WAS successfilly installed. I cannot understand then - when you got this System file error, at which point in installation?
Ive been having this same error each time I try to install DT v4. I deleted the sptd.sys file and rebooted. On restart I was able to modify the permission settings for the cfg folder in the registry (I hadnt been able to earlier) however the problem persists.
I checked the event manager. There are a good number of errors, but none seem to be of any relation to DT as they dont chronologically align with my installation attempts.
Ive been putting off a good 'ol reformat for a while now (never done it in 3 years), so maybe Ill do that and see if it does anything.
No event at all shown! This issue came after the reboot during th e install. Is this a new key generated? So it would be okay to delete it overall (no idea if deleting would work)?
I could only see during the install that while install writing into the cfg folder of the registry "ACCESS DENIED" popped up (in regmon) and then the install program aborts.
So must be an installation script issue.
The issue could come having two administrators defined on a machine (one local one defined via a domain) as I'm login via the domain one (on XP). If the install does NOT use the current logged on this could be maybe the issue?
I had the same problem and did what VeNoM386 suggested in his last post. It fixed the system file error, but now I get this error during the D-tools install, and I'm posting it here since it might be related :
Failed calling CreateFile; GetLastError = 32
I already installed V4 once without problems, but I had some other problems with my PC and had to do a system repair (yes, just after I installed V4; it wasn't related to it though) and I may need to delete some other files before being able to install it again.
This log just shows SPTD could not start after reboot but it WAS successfilly installed. I cannot understand then - when you got this System file error, at which point in installation?
Well, the error occurs when right after rebooting due to installation of the SPTD, it automatically launches the installation upon entry of Windows again. It then tells me to install SPTD, if I'm ok with that (so, basically, just like a fresh installation without SPTD already on my system), only then, when I click OK, it gives me this System File error.
Any idea if Norton AntiVirus 2005 might be the culprit here?
BTW: I have multiple sptd.sys 's. They're named sptd****.sys (where **** is a four character number). Maybe this helps in understanding my problem.
We process personal data about users of our site, through the use of cookies and other technologies, to deliver our services, personalize advertising, and to analyze site activity. We may share certain information about our users with our advertising and analytics partners. For additional details, refer to our Privacy Policy.
By clicking "I AGREE" below, you agree to our Privacy Policy and our personal data processing and cookie practices as described therein. You also acknowledge that this forum may be hosted outside your country and you consent to the collection, storage, and processing of your data in the country where this forum is hosted.
Tweet
Comment