wow64

I'm trying to add a key to LocalMachine in registry. I'm using this code: System.Diagnostics.Debugger.Launch(); RegistryKey key = Registry.LocalMachine.OpenSubKey("SOFTWARE", true); RegistryKey newkey = key.CreateSubKey("1asdasds", RegistryKeyPermissionCheck.ReadWriteSubTree); newkey.SetValue("ads", "ddsds"); newkey.Close(); I DO run it on Administrator account. I event run it with 'run as administrator", but nothing is added to registry :(. When I change the LocalMachine to CurrentUser , actually it is added to CurrentUser key. But how to force it to be added to LocalMachine? Got it. Actually

I'm trying to run the on screen keyboard from my application. It works correctly under Windows XP 32 bits, but incorrect under Win 7 64 bits. unit Unit5; interface uses Windows, Messages, SysUtils, Variants, Classes, Graphics, Controls, Forms, Dialogs, ShellAPI; type TForm5 = class(TForm) procedure FormCreate(Sender: TObject); private { Private declarations } public class function IsWOW64: Boolean; { Public declarations } end; var Form5: TForm5; implementation {$R *.dfm} procedure TForm5.FormCreate(Sender: TObject); var path:String; res : Integer; function GetSysDir: string; var Buf: array[0.

MSDN tells me that handles to windows (HWND) can be shared between 32- and 64-bit applications, in Interprocess Communication (MSDN). However, in Win32 a HWND is 32 bits, whereas in 64 bit Windows it is 64 bits. So how can the handles be shared? I guess the same question applies to handles to named objects such as mutexes, semaphores and file handles. Doesn't the fact that they can be shared imply that only the lower 32 bits are used in Win64 processes? Windows handles are indexes not pointers, at least as far as I can tell, so unless MS wanted to allow more than 2^32 window/file/mutex/etc.

I am getting a mysterious error from time to time that I just don't get. I can "fix" it by restarting Visual Studio 2008, but that isn't exactly a solution... It states the following: Error while trying to run project: Unable to start debugging. The Microsoft Visual Studio Remote Debugging Monitor has been closed on the remote machine. I am not doing anything remote, as far as I know... Just running regular debug, F5 style. What does it mean? How can I fix it? If you are on a 64bit OS then you are 'silently' remote debugging. Devenv runs in WoW64 (meaning it's a 32bit process) ... when you hit

I'm trying to insert some simple registry keys using Microsoft.Win32.RegistryKey in c# but the path automatically changes from: HKEY_LOCAL_MACHINE\SOFTWARE\Test to HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Test I tried google but I only get some vague and confusing results. Has anyone dealt with this issue before? Some example code would be much appereciated. You can use RegistryKey.OpenBaseKey to solve this problem: var baseReg = RegistryKey.OpenBaseKey(RegistryHive.LocalMachine, RegistryView.Registry64); var reg = baseReg.CreateSubKey("Software\\Test"); Under WOW64, certain registry keys are

My .NET application (any-CPU) needs to read a registry value created by a 32-bit program. On 64-bit Windows this goes under the Wow6432Node key in the registry. I have read that you shouldn't hard-code to the Wow6432Node, so what's the right way to access it with .NET? In the case where you explicitly need to read a value written by a 32 bit program in a 64 bit program, it's OK to hard code it. Simply because there really is no other option. I would of course abstract it out to a helper function. For example public RegistryKey GetSoftwareRoot() { var path = 8 == IntPtr.Size ? @"Software

I have some code that reads the registry and looks for a value in HKEY_LOCAL_MACHINE\Software\App\ but when running on 64-bit versions of Windows the value is under HKEY_LOCAL_MACHINE\Software\Wow6432Node\App\ . How should I best approach this? Do I need a 64-bit installer or should I rewrite my code to detect both places? Arve If you mark you C# program as x86 (and not Any CPU) then it will see HKEY_LOCAL_MACHINE\Software\Wow6432Node\App as HKEY_LOCAL_MACHINE\Software\App\ . A .NET program for Any CPU will run as a 64-bit process if 64-bit .NET is installed. The 32-bit registry is under the