Error: "PlatformLib::TargetRegEdit": Invalid key path

H

Hawk Gauss

When I built my image, I got many errors after "R:Building ..." such as:

Error 1010 (0x3F2) in "PlatformLib::TargetRegEdit": Invalid key path:
"HKEY_LOCAL_MACHINE\HKEY_LOCAL_MACHINE\Software\Microsoft\Windows
NT\CurrentVersion\Terminal
Server\Compatibility\{182C40F0-32E4-11D0-818B-00A0C9231C29}"

I have checked my components including name of "Terminal Server".
No component contain those registry values. so does "Volume Shadow Copy
Service" component.

How can the double key "HKEY_LOCAL_MACHINE\HKEY_LOCAL_MACHINE\" occur? Where
is it reside? How can I modify?

I am so confused. thanks for any help.

------------------------------------------------------
The follow is my xpe image build log:
....
....
R: Building: "SMTP Server [Version 5.1.2600.1106, R1507]"...
R: Building: "Volume Shadow Copy Service [Version 5.1.2600.1106, R1507]"...
Error 1010 (0x3F2) in "PlatformLib::TargetRegEdit": Invalid key path:
"HKEY_LOCAL_MACHINE\HKEY_LOCAL_MACHINE\Software\Microsoft\Windows
NT\CurrentVersion\Terminal
Server\Compatibility\{182C40F0-32E4-11D0-818B-00A0C9231C29}"
R: Error 1004: Invalid resource:
"HKEY_LOCAL_MACHINE\HKEY_LOCAL_MACHINE\Software\Microsoft\Windows
NT\CurrentVersion\Terminal
Server\Compatibility\{182C40F0-32E4-11D0-818B-00A0C9231C29}\fSystemGlobalClass":
(Error 1010 (0x3F2) in "PlatformLib::TargetRegEdit": Invalid key path:
"HKEY_LOCAL_MACHINE\HKEY_LOCAL_MACHINE\Software\Microsoft\Windows
NT\CurrentVersion\Terminal
Server\Compatibility\{182C40F0-32E4-11D0-818B-00A0C9231C29}")
Error 1010 (0x3F2) in "PlatformLib::TargetRegEdit": Invalid key path:
"HKEY_LOCAL_MACHINE\HKEY_LOCAL_MACHINE\Software\Microsoft\Windows
NT\CurrentVersion\Terminal
Server\Compatibility\CLSID\{182C40F0-32E4-11D0-818B-00A0C9231C29}"
....
....
R: Estimated component sizes:
R: Accessibility Control Panel ................................
140KB
R: Accessibility Core .........................................
284KB
....
....
 
K

KM

Hawk,

When you added those reg keys to your components did you set "HKEY_LOCAL_MACHINE\Software\Microsoft\Windows
NT\CurrentVersion\Terminal Server\Compatibility\..." string under Key Name field?
It should be just "Software\Microsoft\Windows NT\CurrentVersion\Terminal Server\Compatibility\..." as you specify the root key in a
field above.
 
H

Hawk Gauss

Oh, It is very possible. Thank KM.

But I have checked my custom components.
They don't add those keys at all.

*** How can I find where those key may reside? ***


KM said:
Hawk,

When you added those reg keys to your components did you set
"HKEY_LOCAL_MACHINE\Software\Microsoft\Windows
NT\CurrentVersion\Terminal Server\Compatibility\..." string under Key Name
field?
It should be just "Software\Microsoft\Windows NT\CurrentVersion\Terminal
Server\Compatibility\..." as you specify the root key in a
field above.

--
Regards,
KM, BSquare Corp.

When I built my image, I got many errors after "R:Building ..." such as:

Error 1010 (0x3F2) in "PlatformLib::TargetRegEdit": Invalid key path:
"HKEY_LOCAL_MACHINE\HKEY_LOCAL_MACHINE\Software\Microsoft\Windows
NT\CurrentVersion\Terminal
Server\Compatibility\{182C40F0-32E4-11D0-818B-00A0C9231C29}"

I have checked my components including name of "Terminal Server".
No component contain those registry values. so does "Volume Shadow Copy
Service" component.

How can the double key "HKEY_LOCAL_MACHINE\HKEY_LOCAL_MACHINE\" occur?
Where
is it reside? How can I modify?

I am so confused. thanks for any help.

------------------------------------------------------
The follow is my xpe image build log:
...
...
R: Building: "SMTP Server [Version 5.1.2600.1106, R1507]"...
R: Building: "Volume Shadow Copy Service [Version 5.1.2600.1106,
R1507]"...
Error 1010 (0x3F2) in "PlatformLib::TargetRegEdit": Invalid key path:
"HKEY_LOCAL_MACHINE\HKEY_LOCAL_MACHINE\Software\Microsoft\Windows
NT\CurrentVersion\Terminal
Server\Compatibility\{182C40F0-32E4-11D0-818B-00A0C9231C29}"
R: Error 1004: Invalid resource:
"HKEY_LOCAL_MACHINE\HKEY_LOCAL_MACHINE\Software\Microsoft\Windows
NT\CurrentVersion\Terminal
Server\Compatibility\{182C40F0-32E4-11D0-818B-00A0C9231C29}\fSystemGlobalClass":
(Error 1010 (0x3F2) in "PlatformLib::TargetRegEdit": Invalid key path:
"HKEY_LOCAL_MACHINE\HKEY_LOCAL_MACHINE\Software\Microsoft\Windows
NT\CurrentVersion\Terminal
Server\Compatibility\{182C40F0-32E4-11D0-818B-00A0C9231C29}")
Error 1010 (0x3F2) in "PlatformLib::TargetRegEdit": Invalid key path:
"HKEY_LOCAL_MACHINE\HKEY_LOCAL_MACHINE\Software\Microsoft\Windows
NT\CurrentVersion\Terminal
Server\Compatibility\CLSID\{182C40F0-32E4-11D0-818B-00A0C9231C29}"
...
...
R: Estimated component sizes:
R: Accessibility Control Panel ................................
140KB
R: Accessibility Core .........................................
284KB
...
...
Click to expand...
Click to expand...
 
K

KM

Hawk,

There are no components in the XPe Repository that held the registry entries you mentioned.
It must be your custom component or any 3rd party component you used (I doubt, though, these may have such obvious bugs).

Can you check you custom components one more time? And please also check TD Extra Registry section.

--
Regards,
KM, BSquare Corp.

Oh, It is very possible. Thank KM.

But I have checked my custom components.
They don't add those keys at all.

*** How can I find where those key may reside? ***


KM said:
Hawk,

When you added those reg keys to your components did you set
"HKEY_LOCAL_MACHINE\Software\Microsoft\Windows
NT\CurrentVersion\Terminal Server\Compatibility\..." string under Key Name
field?
It should be just "Software\Microsoft\Windows NT\CurrentVersion\Terminal
Server\Compatibility\..." as you specify the root key in a
field above.

--
Regards,
KM, BSquare Corp.

When I built my image, I got many errors after "R:Building ..." such as:

Error 1010 (0x3F2) in "PlatformLib::TargetRegEdit": Invalid key path:
"HKEY_LOCAL_MACHINE\HKEY_LOCAL_MACHINE\Software\Microsoft\Windows
NT\CurrentVersion\Terminal
Server\Compatibility\{182C40F0-32E4-11D0-818B-00A0C9231C29}"

I have checked my components including name of "Terminal Server".
No component contain those registry values. so does "Volume Shadow Copy
Service" component.

How can the double key "HKEY_LOCAL_MACHINE\HKEY_LOCAL_MACHINE\" occur?
Where
is it reside? How can I modify?

I am so confused. thanks for any help.

------------------------------------------------------
The follow is my xpe image build log:
...
...
R: Building: "SMTP Server [Version 5.1.2600.1106, R1507]"...
R: Building: "Volume Shadow Copy Service [Version 5.1.2600.1106,
R1507]"...
Error 1010 (0x3F2) in "PlatformLib::TargetRegEdit": Invalid key path:
"HKEY_LOCAL_MACHINE\HKEY_LOCAL_MACHINE\Software\Microsoft\Windows
NT\CurrentVersion\Terminal
Server\Compatibility\{182C40F0-32E4-11D0-818B-00A0C9231C29}"
R: Error 1004: Invalid resource:
"HKEY_LOCAL_MACHINE\HKEY_LOCAL_MACHINE\Software\Microsoft\Windows
NT\CurrentVersion\Terminal
Server\Compatibility\{182C40F0-32E4-11D0-818B-00A0C9231C29}\fSystemGlobalClass":
(Error 1010 (0x3F2) in "PlatformLib::TargetRegEdit": Invalid key path:
"HKEY_LOCAL_MACHINE\HKEY_LOCAL_MACHINE\Software\Microsoft\Windows
NT\CurrentVersion\Terminal
Server\Compatibility\{182C40F0-32E4-11D0-818B-00A0C9231C29}")
Error 1010 (0x3F2) in "PlatformLib::TargetRegEdit": Invalid key path:
"HKEY_LOCAL_MACHINE\HKEY_LOCAL_MACHINE\Software\Microsoft\Windows
NT\CurrentVersion\Terminal
Server\Compatibility\CLSID\{182C40F0-32E4-11D0-818B-00A0C9231C29}"
...
...
R: Estimated component sizes:
R: Accessibility Control Panel ................................
140KB
R: Accessibility Core .........................................
284KB
...
...
Click to expand...
Click to expand...
Click to expand...
 
H

Hawk Gauss

Thank KM very much.

I have found the exception in Extra Registry section. Just as you described.


KM said:
Hawk,

There are no components in the XPe Repository that held the registry
entries you mentioned.
It must be your custom component or any 3rd party component you used (I
doubt, though, these may have such obvious bugs).

Can you check you custom components one more time? And please also check
TD Extra Registry section.

--
Regards,
KM, BSquare Corp.

Oh, It is very possible. Thank KM.

But I have checked my custom components.
They don't add those keys at all.

*** How can I find where those key may reside? ***


KM said:
Hawk,

When you added those reg keys to your components did you set
"HKEY_LOCAL_MACHINE\Software\Microsoft\Windows
NT\CurrentVersion\Terminal Server\Compatibility\..." string under Key
Name
field?
It should be just "Software\Microsoft\Windows
NT\CurrentVersion\Terminal
Server\Compatibility\..." as you specify the root key in a
field above.

--
Regards,
KM, BSquare Corp.


When I built my image, I got many errors after "R:Building ..." such
as:

Error 1010 (0x3F2) in "PlatformLib::TargetRegEdit": Invalid key path:
"HKEY_LOCAL_MACHINE\HKEY_LOCAL_MACHINE\Software\Microsoft\Windows
NT\CurrentVersion\Terminal
Server\Compatibility\{182C40F0-32E4-11D0-818B-00A0C9231C29}"

I have checked my components including name of "Terminal Server".
No component contain those registry values. so does "Volume Shadow
Copy
Service" component.

How can the double key "HKEY_LOCAL_MACHINE\HKEY_LOCAL_MACHINE\" occur?
Where
is it reside? How can I modify?

I am so confused. thanks for any help.

------------------------------------------------------
The follow is my xpe image build log:
...
...
R: Building: "SMTP Server [Version 5.1.2600.1106, R1507]"...
R: Building: "Volume Shadow Copy Service [Version 5.1.2600.1106,
R1507]"...
Error 1010 (0x3F2) in "PlatformLib::TargetRegEdit": Invalid key path:
"HKEY_LOCAL_MACHINE\HKEY_LOCAL_MACHINE\Software\Microsoft\Windows
NT\CurrentVersion\Terminal
Server\Compatibility\{182C40F0-32E4-11D0-818B-00A0C9231C29}"
R: Error 1004: Invalid resource:
"HKEY_LOCAL_MACHINE\HKEY_LOCAL_MACHINE\Software\Microsoft\Windows
NT\CurrentVersion\Terminal
Server\Compatibility\{182C40F0-32E4-11D0-818B-00A0C9231C29}\fSystemGlobalClass":
(Error 1010 (0x3F2) in "PlatformLib::TargetRegEdit": Invalid key path:
"HKEY_LOCAL_MACHINE\HKEY_LOCAL_MACHINE\Software\Microsoft\Windows
NT\CurrentVersion\Terminal
Server\Compatibility\{182C40F0-32E4-11D0-818B-00A0C9231C29}")
Error 1010 (0x3F2) in "PlatformLib::TargetRegEdit": Invalid key path:
"HKEY_LOCAL_MACHINE\HKEY_LOCAL_MACHINE\Software\Microsoft\Windows
NT\CurrentVersion\Terminal
Server\Compatibility\CLSID\{182C40F0-32E4-11D0-818B-00A0C9231C29}"
...
...
R: Estimated component sizes:
R: Accessibility Control Panel ................................
140KB
R: Accessibility Core .........................................
284KB
...
...
Click to expand...
Click to expand...
Click to expand...
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

error information 1
Run Key 9
meet a error about Speech API Core 3
Importing INF file - Error Log 2
D945GTP Components trouble 3
Cannot fix corrupted registry value: The handle is invalid error. 2
Cannot edit corrupted registry value: The handle is invalid. 0
Updating INI Files 1

Top