I'm having a problem capturing the following registry value in an MSI. This is copied from a file exported from regedit.exe

REGEDIT4

[HKEY_CLASSES_ROOT\CLSID\{E69C0280-ABC4-11D3-B3EA-00500411DC99}]
"Reg6.00"=hex(2ce):40,b3,4d,7e,49,00,00,c0,40,


For some reason this will not get captured or deployed correctly. I'm not sure how this would be represented in the registry table of the msi. Here is the entry in the table that was captured:

Registry_0 0 CLSID\{E69C0280-ABC4-11D3-B3EA-00500411DC99} Ver6.00 #x413132464B510043553743414C4500 RegistryData_HKCR


Is this some sort of msi limitation for this particular type of registry entry? In regedit the type is shown as a 0x2ce which I'm not really familiar with. I have to have this particular registry entry because it suppresses registration dialog of the application. Options?
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
No one has any idea on this? Maybe this registry entry should not go in the Registry table? Is there another recommended method to add a registry entry to the registry without using the Registry table?
Answered 02/10/2009 by: joedown
Second Degree Brown Belt

Please log in to comment
0
i didn't know so i didn't answer :-)
looks like your #x is correct for interpreting a binary value.

maybe check and make sure you export/import with the same format, regedit not regedt4 and make sure it's unicode if exporting/importing.
Answered 02/10/2009 by: aogilmor
Ninth Degree Black Belt

Please log in to comment
0
Are you using Wise or IS?

If it's IS, I'm willing to test this in my lab for you.

If you really get in a jam, you could always call a VBS CA that writes the key.
Answered 02/10/2009 by: turbokitty
Sixth Degree Black Belt

Please log in to comment
0
I created a .REG from your post and imported it. RegEdit shows it as type '0x2ce', a custom type.

If you went the VBS route, I'm wondering how, being a custom type, you'd use the standard methods e.g.Shell.RegWrite or WMI, as they take only the standard types. Me, I'd install a .REG containing the data and have a two-step VBS which first merges the .REg with RegEdit and then deletes the .REG (having checked that the import worked, of course!)
Answered 02/11/2009 by: VBScab
Red Belt

Please log in to comment
0
ORIGINAL: VBScab

I created a .REG from your post and imported it. RegEdit shows it as type '0x2ce', a custom type.

If you went the VBS route, I'm wondering how, being a custom type, you'd use the standard methods e.g.Shell.RegWrite or WMI, as they take only the standard types. Me, I'd install a .REG containing the data and have a two-step VBS which first merges the .REg with RegEdit and then deletes the .REG (having checked that the import worked, of course!)



Unfortunately I do not know VBS. Would I be able to run a custom action that imports the registry file?
Answered 02/11/2009 by: joedown
Second Degree Brown Belt

Please log in to comment
0
I have had this happen. Build your MSI (without the key) then take the .reg key that you have exported from the registry and using your .msi editor Import the key into the .msi and recompile. That is how I have handled those in the past.
Answered 02/11/2009 by: Foleymon
Orange Senior Belt

Please log in to comment
0
ORIGINAL: Foleymon

I have had this happen.  Build your MSI (without the key) then take the .reg key that you have exported from the registry and using your .msi editor Import the key into the .msi and recompile.  That is how I have handled those in the past.


I imported the reg file into the MSI using Install Editor. It's closer, the value is correct but the type comes up as REG_BINARY instead of 0x2ce. I guess this company does not want people to be able to preregister the install.
Answered 02/11/2009 by: joedown
Second Degree Brown Belt

Please log in to comment
0
Unfortunately I do not know VBS. !! If you can get your head round packaging, VBS is a breeze. There are tons of examples, plus AppDeploy's 'Scripts' forum.
I imported the reg file into the MSI using Install Editor. It's closer, the value is correct but the type comes up as REG_BINARY instead of 0x2ce. That's probably because IS's developers don't handle that data type, either.

Notwithstanding the above, create a CA to silently import the .REG using RegEdit. That'll get you going for now. You can build a more elegant method once you're comfortable with VBS.
Answered 02/12/2009 by: VBScab
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity