Jump to content


Error finding Configuration Key


  • Please log in to reply
18 replies to this topic

#1 Trial User_Blake_*

Trial User_Blake_*
  • Guests

Posted 05 August 2006 - 01:18 PM

When im installing a pop-up says error finding configuration key any suggestions?

#2 zamiel

zamiel

    Forum Support

  • Administration
  • 8,841 posts

Posted 05 August 2006 - 05:26 PM

Please try to download SPTD Installer:

http://forum.alcohol...showtopic=23803

You can also try to disable antivirus real time protection during sptd layer installation.

#3 Trial User_Betan_*

Trial User_Betan_*
  • Guests

Posted 10 August 2006 - 12:02 PM

Same problem here - with Windows XP SP2 (32-bit OS, not the 64-bit version) - go to install Alcohol 120 Trial and you get a warning popup titled:

"SPTD setup V1.25 © 2004 Duplex Secure Ltd."

Which warns you that SPTD is not compatible with kernel mode debuggers. Your options are OK and CANCEL.

You click OK and you get the error: "Failed to open config key" and install aborts.

The SPTD Installer is of no use. In safe mode, safe mode commandline or regular mode you run it with the REMOVE command it says SPTD is not loaded. Then you try to run the ADD command and it gives you the same "Failed to open config key" error.

But this SPTD issue is not just limited to Alcohol .... same thing is happening to Daemon Tools and just about any other application that emulates a Virtual CDROM drive.

huh.gif

#4 Jito463

Jito463

    Forum Support

  • Support Team
  • 5,625 posts

Posted 10 August 2006 - 12:06 PM

Try disabling any firewall or anti-virus software and install again. If it still fails, try booting into Safe Mode and try again.

#5 Trial User_Guest_*

Trial User_Guest_*
  • Guests

Posted 10 August 2006 - 01:12 PM

QUOTE (Jito463 @ Aug 10 2006, 07:03 PM) <{POST_SNAPBACK}>
Try disabling any firewall or anti-virus software and install again. If it still fails, try booting into Safe Mode and try again.


Sorry - that didn't work. Even in SAFE MODE, you still get the "Failed to open config key" ... but I did find something interesting ....

The registry key HKLM\SYSTEM\ControlSet002\Services\sptd\Cfg\ cannot be accessed. It cannot be deleted. It cannot be viewed by even the local administrator account. It cannot have it's privileges changed in regedit. And Cfg cannot be set to inherit privileges from sptd. The SPTD Installer cannot write information to it, and it and Alcohol 120 fail.

#6 Trial User_Betan_*

Trial User_Betan_*
  • Guests

Posted 10 August 2006 - 01:52 PM

I don't know if this will work for everyone - but on another forum, this may be the only way you'll get the software to install from this point on with WinXP SP2 unless Alcohol software finds a better work around ....

One way is this way: www.kkaf.net/sptdfix.htm

Someone else (screen name FLOGGY) recommended this way:

Download SPDTinst(xARCH).exe is either 86 or 64, depends on your OS.

STEP 1. Completely remove sptd associations:

* Reboot into safe mode, press ESC when message sth. like "To interrupt load of SPDT.SYS Press ESC" appears.
* login as a user with root privilege (like a local administrator)
* Say YES to the popup message, to confirm that you want to work in safe mode.
* In Start > Run type cmd and press ok.
* with cd path_where_SPDTinst(xARCH).exe_is_stored change to that directory.
* Type SPDTinst(xARCH).exe remove and follow the instructions
* Reboot into safe mode again and type into start > run regedit. Search for all spdt.sys entries and delete all of them. You may not be able to delete all entries. If that happens delete as much of the affected tree as you can do. This may happen twice to spdt.
* Start (Win+E) Explorer and go to %systemroot%\system32\drivers . Find spdt.sys and rename it to spdt.s_s.

STEP 2.

* Reboot into safe mode commandline mode and install spdt.sys with SPDTinst(xARCH).exe add. Follow the instructions.

STEP 3.

* Reboot into normal mode and install Alcohol 120.

#7 Charalambos

Charalambos

    Support Team Member

  • Support Team
  • 4,880 posts

Posted 11 August 2006 - 02:18 PM

QUOTE
The registry key HKLM\SYSTEM\ControlSet002\Services\sptd\Cfg\ cannot be accessed. It cannot be deleted. It cannot be viewed by even the local administrator account. It cannot have its privileges changed in regedit. And Cfg cannot be set to inherit privileges from sptd. The SPTD Installer cannot write information to it, and it and Alcohol 120 fail.


Usually it is the ControlSet001 that is the active key but it depends on if and how much times you booted with the "Last known good configuration" option. To be sure you must work with the CurrentControlSet, it is always the active one.
In order to delete the sptd\cfg branch from the CurrentControlSet registry root key you must do the following:
1. Change the privilegies for the sptd key to Full Control for Everyone.
2. Reboot your computer.
3. Now you will be able to access the cfg subkey. Change the privilegies for it in the same way as with sptd.
4. Now you can delete the keys. Delete the cfg key and then the sptd key.
After this proccess is completed reboot and install Alcohol.

#8 Trial User_Trial User_Chris_*_*

Trial User_Trial User_Chris_*_*
  • Guests

Posted 25 August 2006 - 12:05 PM

At a command prompt:

INSTSRV sptd REMOVE

#9 Jito463

Jito463

    Forum Support

  • Support Team
  • 5,625 posts

Posted 25 August 2006 - 06:52 PM

On what are you basing that command, Chris? That program is not a native command in Windows XP. Is this something from Win2k perhaps?

#10 Trial User_Trial_User_Jeff_*

Trial User_Trial_User_Jeff_*
  • Guests

Posted 28 October 2006 - 12:46 AM

QUOTE (Jito463 @ Aug 26 2006, 01:49 AM) <{POST_SNAPBACK}>
On what are you basing that command, Chris? That program is not a native command in Windows XP. Is this something from Win2k perhaps?


Chris was giving a command available in the resource kit to remove a service via the command line.

This problem has been dogging me and, for the life of me, I can't get Alcohol (either 52 or 120) to install.

I can remove the service with instserv. I followed the prior post, booted into safe mode, edited the registry to remove all entries relating to spdt.sys (changing ownership as needed to delete the keys). The registry was 100% clean. Then I renamed drivers\sptd.sys to drivers\sptd.s_s. Rebooted, ran "sptdinst_x86.exe add" from safe mode. Rebooted normally. Then Alcohol 120 failed to install with "error finding configuration key".

Can Alcohol install on XP SP2? What magic am I missing?

#11 Charalambos

Charalambos

    Support Team Member

  • Support Team
  • 4,880 posts

Posted 28 October 2006 - 11:07 AM

Wich version of Alcohol are you trying to install? Have you tried the latest one( 1.9.5.4521 with SPTD 1.29)?

#12 Trial User_Trial_User_Jeff_*

Trial User_Trial_User_Jeff_*
  • Guests

Posted 28 October 2006 - 02:32 PM

QUOTE (Charalambos @ Oct 28 2006, 06:04 PM) <{POST_SNAPBACK}>
Wich version of Alcohol are you trying to install? Have you tried the latest one( 1.9.5.4521 with SPTD 1.29)?


I just downloaded from the WWW site, so I imagine it's the latest version. I have:

Alcohol120trial1954521.exe

and have also tried:

Alcohol52trial1954521.exe

The sptdinst_x86.exe image I have isn't versioned, but I just downloaded that as well yesterday, so I would hope it's the latest. Of course, one would hope I wouldn't need that at all, but ...

Any ideas or suggestions?

-- Jeff

#13 Charalambos

Charalambos

    Support Team Member

  • Support Team
  • 4,880 posts

Posted 29 October 2006 - 12:37 PM

Can you give some information about your system( mainly system vendor, cpu, motherboard and OS)? Do you have any other burning or emulation applications installed?

#14 Trial User_Trial_User_Jeff_*

Trial User_Trial_User_Jeff_*
  • Guests

Posted 30 October 2006 - 08:34 PM

QUOTE (Charalambos @ Oct 29 2006, 07:34 PM) <{POST_SNAPBACK}>
Can you give some information about your system( mainly system vendor, cpu, motherboard and OS)? Do you have any other burning or emulation applications installed?


I have an IBM T42 laptop. CPU: Intel Pentium M processor, 1.80GHz, 1.50 GB of RAM. O/S: Windows XP, SP2.

I have Nero OEM installed for burning software. I also have SlySoft AnyDVD installed (but not started). (It's available for a free trial if you want to try that.) That's it for burning or emulation applications.

Suggestions?

-- Jeff

#15 zamiel

zamiel

    Forum Support

  • Administration
  • 8,841 posts

Posted 30 October 2006 - 09:47 PM

Can you uninstall AnyDVD and Nero and try to install Alcohol?

#16 Trial User_Trial_User_Jeff_*

Trial User_Trial_User_Jeff_*
  • Guests

Posted 31 October 2006 - 01:11 PM

QUOTE (zamiel @ Oct 31 2006, 04:44 AM) <{POST_SNAPBACK}>
Can you uninstall AnyDVD and Nero and try to install Alcohol?


Okay, I uninstalled AnyDVD and Nero, it still fails. As soon as sptdinst_x86.exe did it's thing, the "cfg" config key was protected (ownership of that wasn't granted, so I couldn't look at it in the registry), and then the Alcohol installer failed with "Error finding Configuration Key".

Clearly, the Alcohol installer is trying to look at this configuration key and can't, just like I can't, due to the ownership issue of the registry key.

Other people (earlier in this thread) mentioned compatibility issues with sptdinst_x86.exe and XP with SP2. Have those been resolved? Or was that person confused? Is this supposed to install on XP with Service Pack 2?

#17 Charalambos

Charalambos

    Support Team Member

  • Support Team
  • 4,880 posts

Posted 01 November 2006 - 12:38 PM

SPTD 1.35 has been released by Duplex Secure, you can find it at www.duplexsecure.com. Using the the standalone SPTD installer from the above site uninstall the current version of SPTD that you have( run sptdinst_x86 remove from the command prompt) and try to install SPTD in safe mode( run sptdinst_x86 add from the command prompt) and then Alcohol in normal mode after rebooting.

Edited by Charalambos, 01 November 2006 - 12:45 PM.


#18 Trial User_Guest_*

Trial User_Guest_*
  • Guests

Posted 05 November 2006 - 06:24 PM

QUOTE (Charalambos @ Nov 1 2006, 07:35 PM) <{POST_SNAPBACK}>
SPTD 1.35 has been released by Duplex Secure, you can find it at www.duplexsecure.com. Using the the standalone SPTD installer from the above site uninstall the current version of SPTD that you have( run sptdinst_x86 remove from the command prompt) and try to install SPTD in safe mode( run sptdinst_x86 add from the command prompt) and then Alcohol in normal mode after rebooting.


Okay, I went to www.duplexsecure.com and tried 1.35 of their command line utility. My results were 100% identical. That is:

As soon as sptdinst_x86.exe (v1.35) installed and the system rebooted, the "cfg" config key was protected (ownership of that wasn't granted, so I couldn't look at it in the registry), and then the Alcohol installer failed with "Error finding Configuration Key".

Clearly, the Alcohol installer is trying to look at this configuration key and can't, just like I can't, due to the ownership issue of the registry key.

I ask again: Other people (earlier in this thread) mentioned compatibility issues with sptdinst_x86.exe and XP with SP2. Have those been resolved? Or was that person confused? Is this supposed to install on XP with Service Pack 2?

I simply can't get Alcohol to install on XP SP2 due to sptd. If sptd doesn't formally support XP SP2, then I'm clearly wasting my time ... does sptd support XP with Service Pack 2 or not?

There is one minor difference: The remove facility of sptdinst_x86.exe (for v1.35) at least knows to disable the service on removal, so I don't need hand edits of the registry or INSTSERV to get sptd from no longer starting. But that's a minor improvement when the damn thing still won't install properly ...

-- Jeff

#19 zamiel

zamiel

    Forum Support

  • Administration
  • 8,841 posts

Posted 05 November 2006 - 07:02 PM

QUOTE
I simply can't get Alcohol to install on XP SP2 due to sptd. If sptd doesn't formally support XP SP2, then I'm clearly wasting my time ... does sptd support XP with Service Pack 2 or not?


Yes. XP SP2 is mainstream and it seems only a handful of users experience difficulty installing SPTD on it.

Have you tried to install on a fresh installation of Windows?




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users