{"id":1641,"date":"2009-08-18T02:43:47","date_gmt":"2009-08-18T10:43:47","guid":{"rendered":"http:\/\/www.sapien.com\/blog\/?p=1641"},"modified":"2009-08-18T09:38:48","modified_gmt":"2009-08-18T17:38:48","slug":"registry-access-from-32-to-64-bit-and-back","status":"publish","type":"post","link":"https:\/\/dev.sapien.com\/blog\/2009\/08\/18\/registry-access-from-32-to-64-bit-and-back\/","title":{"rendered":"Registry access from 32 to 64 bit and back"},"content":{"rendered":"

Just recently, I received an email asking how you can access the 64 bit registry from a 32 bit script, or vice versa. The task the individual was facing was to come up with a way to verify installed applications via checking the corresponding Windows Installer registry entries.<\/p>\n

For a C++ programmer with access to the API, that really is not a big issue. From VBScript, using only WshShell.RegRead that is a completely different story. A quick consult with some fellow script experts revealed that the only real way was using WMI and the StdRegProvider. The main complaint I heard though was that this was a rather slow and sluggish way of doing it.<\/p>\n

So I decided to pick up the slack and create a new COM component that makes accessing the registry a bit simpler than using WMI, all the while maintaining some of the native API’s speed.<\/p>\n

 <\/span><\/pre>\n
<\/a> \"image\"<\/a><\/p>\n
The new component is available with PrimalScript builds 5.0.615 and higher. It is automatically installed and registered. Please check out the sample file RegistryAccess.vbs in the PrimalScript samples folder.<\/p>\n
Additionally, VBScript expert and all-around scripting guru Alex Angelopoulos was nice enough to help me design the interface and test it by providing two more sample scripts that use this control:<\/p>\n
EnumerateControlsWithKillBits.vbs:<\/strong><\/p>\n
Enumerates GUIDs for controls that have been kill-bitted to not run in IE. (Note that these controls CAN still run in HTAs and other local applications). Shows the flags set for the control as a simple number, and – if the control is installed and it has a common name listed – shows the control name and the path to the control.
Elements are separated by commas. This will give odd-looking output in a console window, but is useful for redirection to a file and later opening in Excel.<\/em><\/p>\n
AutoAddScriptRunAs.vbs:<\/strong><\/p>\n
Simplifies running scripts as privileged processes or with alternate
credentials.  For our purposes, a “script” is any file type whose extension is in the environment’s %pathext% variable (except .com\/.exe\/.msc files since they are handled by Windows already), and ALSO files with the .hta extension.
This script has the following effects when run:
(1) On pre-Vista systems, the only apparent change will be a “Run As” entry on the context menu allowing you to specify alternate credentials for running a script.
(2) On Vista and newer, the context menu choice will be a localized variant of “Run as administrator” and will show an LUA shield icon next to the choice. Selecting this will cause the script host to request elevation at launch.
(3) On Windows 7 and newer systems, scripts containing the word
“admin” in their names will automatically attempt to run elevated if you double-click them or run them using the Run dialog. Note that the word admin must be a distinct word separated from other alphanumeric characters in the script name. The following are examples of names that will cause automatic elevation requests in HTA files:
admin.hta, “admin file.hta”, admin-test.hta
the following will NOT cause automatic elevation requests:
admintools.hta makemeadmin.hta
Also note that you can choose to right-click and Open the script without elevation explicitly.<\/em><\/p>\n
Click here to download the sample files.<\/a><\/p>\n
Below is a brief overview of the methods and properties in this new component:<\/p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
Property<\/strong><\/td>\nDescription<\/strong><\/td>\n<\/tr>\n
RegistryView<\/td>\nSet or returns the current registry view,
(1 = 32 bit (default), 2 = 64 bit)<\/td>\n<\/tr>\n
ErrorCode<\/td>\nReturns the error code of the last operation. 0 = no error, positive numbers are Windows error codes, negative numbers are internal error codes.<\/td>\n<\/tr>\n
ErrorDescription<\/td>\nReturns the description of the last error indicated in the ErrorCode property<\/td>\n<\/tr>\n
Handle<\/td>\nReturns the actual HKEY handle value of the currently opened key.<\/td>\n<\/tr>\n
FullKeyPath<\/td>\nReturns the full key path of the currently opened key. Does not operate on remote keys.<\/td>\n<\/tr>\n
RootKey<\/td>\nReturns the root key (HKLM, HKCR, HKEY_CURRENT_USER etc.) of the currently opened key. Does not operate on remote keys.<\/td>\n<\/tr>\n
SubKeyPath<\/td>\nReturns the key path of the currently opened key without the root node specifier. Does not operate on remote keys.<\/td>\n<\/tr>\n
ReadOnly<\/td>\nSets or returns the content of the read-only flag (default: FALSE), which determines if registry keys are opened with KEY_READ or KEY_ALL_ACCESS<\/td>\n<\/tr>\n
Methods<\/strong><\/td>\nDescription<\/strong><\/td>\n<\/tr>\n
OpenKey(BaseKey,SubKey,bCreate)<\/td>\nOpens a registry key or optionally creates it if it does not exist<\/td>\n<\/tr>\n
CloseKey()<\/td>\nCloses the handle of the currently opened registry key<\/td>\n<\/tr>\n
DeleteKey(BaseKey,SubKey)<\/td>\nDeletes an existing registry key. No key must be opened at the time<\/td>\n<\/tr>\n
DeleteValue(ValueName)<\/td>\nDeletes the specified value in the opened key, use “” to delete the default value<\/td>\n<\/tr>\n
GetValue(ValueName)<\/td>\nReturns the content of the specified value, use “” to retrieve a key’s default value<\/td>\n<\/tr>\n
GetValueType(ValueName)<\/td>\nReturns the type of specified value, use “” to retrieve a key’s default value’s type<\/td>\n<\/tr>\n
GetValueList()<\/td>\nReturns an array with the names of the values under the currently opened key. The default value (empty name) is not included in this list<\/td>\n<\/tr>\n
GetKeyList()<\/td>\nReturns an array with names of the immediate child keys of the currently opened key<\/td>\n<\/tr>\n
GetSubKey(Key,bCreate)<\/td>\nReturns a new object representing the opened handle of the specified subkey.<\/td>\n<\/tr>\n
SetValue(Name,Value,ValueType)<\/td>\nSets the content of the specified value. Use “” to set the content of the default value. Non-existent values will be created automatically.
Supported value types are: REG_SZ, REG_EXPAND_SZ, REG_MULTI_SZ and REG_DWORD<\/td>\n<\/tr>\n
SaveKey(FileName)<\/td>\nSaves the currently open key as binary data to the specified file. Existing files are overwritten<\/td>\n<\/tr>\n
RestoreKey(FileName,bForce)<\/td>\nRestores the content of the currently opened key from a binary file previously created with “SaveKey”<\/td>\n<\/tr>\n
ConnectRegistry(MachineName, BaseKey [,  UserID][, Password]<\/td>\nOpens a root registry handle of a remote machine. You must have administrative rights on the remote computer.<\/td>\n<\/tr>\n
OpenFromHandle(Handle)<\/td>\nOpens the registry key as specified by the handle<\/td>\n<\/tr>\n
HasSubKey(key)<\/td>\nIndicates if the currently opened key has a child key with the specified name<\/td>\n<\/tr>\n
HasValue(Name)<\/td>\nIndicates if the currently opened key has the specified value<\/td>\n<\/tr>\n
IsKey(BaseKey,SubKey)<\/td>\nReturns if the provided key exists. This does not depend on the currently opened key. Does not operate on remote keys<\/td>\n<\/tr>\n
IsValue(Basekey,SubKey, ValueName)<\/td>\nReturns if the specified value exists. This does not depend on the currently opened key. Does not operate on remote keys<\/td>\n<\/tr>\n
GotoSubKey(SubKey)<\/td>\nNavigates the current key to a child key. Multiple levels can be specified separated by a ‘\\’ character. The specified key must exist.<\/td>\n<\/tr>\n
GotoParentKey()<\/td>\nNavigates to the immediate parent key of the currently opened key<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
Unless otherwise noted, functions return vbTrue or vbFalse to indicate success or an error.<\/p>\n
For feedback, feature requests or error reports please use our free tools support forum<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"
Just recently, I received an email asking how you can access the 64 bit registry from a 32 bit script, or vice versa. The task the individual was facing was to come up with a way to verify installed applications via checking the corresponding Windows Installer registry entries. For a C++ programmer with access to […]<\/p>\n","protected":false},"author":5,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[283,410,21,24,389,26],"tags":[526,525,61,37,31,36,996],"class_list":["post-1641","post","type-post","status-publish","format-standard","hentry","category-howto","category-primalscript-software-news","category-software-news","category-vbscript","category-vbscript-scripts","category-windows-scripting-news","tag-32-bit","tag-64-bit","tag-com","tag-primalscript","tag-registry","tag-remote","tag-vbscript"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t