>>>App MUST use WScript, Fox Code isn't a solution - I know, it's weird but it's mandatory :)
>>
>>I don't have the answer, but the registry class in the FFC failed as well. I tried a search on MSDN without success either.
>>
>>If you do find out the answer, please let us know.
>
>I've looked high and low as well and I'm now starting to be discouraged, but rest assured that if I ever find a solution I'll post it here...
>
>I'm not even sure if it's feasable

It looks like it's no go with the WSH. After doing it properly with the Windows Registry functions I was able to open such a key and read the value.

As Sergey pointed out to me, the problem is in the way the WSH tries to retrieve the value. Here's the difference in the two methods.

With the API calls you first open the key with
HKEY_CURRENT_USER and Software\Microsoft\Windows NT\CurrentVersion\Devices as separate parameters. You then query the key with the double backslash (\\) name to retrieve its value.

With the WSH you simply pass the entire key and name as a single string. The wrapper then has to determine two things. First, which root is being open (HKEY_CURRENT_USER also known as HKCU), then which name.

Now the first part works fine. However, the WSH apparently works backwards from the end of the string and stops parsing when it finds the first backslash, rather than the last backslash.

Hope this makes sense.