S
S
sitev_ru2016-10-14 16:46:01
C++ / C#
sitev_ru, 2016-10-14 16:46:01

What about the registry (writes in WOW64)?

I am writing a program that works with the registry.
I write down the data here: "Software\\my-firm". It used to be written like that. Now writes to "SOFTWARE\Wow6432Node\my-firm". This is a WOW64 redirect.
I don’t even understand what happened ... I didn’t do anything like that. How to turn it off?

Answer the question

In order to leave comments, you need to log in

4 answer(s)
M
MiiNiPaa, 2016-10-14
@MiiNiPaa

Build 64bit application not 32. Wow6432Node is a virtual registry for 32bit applications.

M
Mercury13, 2016-10-14
@Mercury13

So it is necessary, W32 and W64 have different places in the registry. And in 90% of cases, nothing needs to be done.
But sometimes you still have to, for example:
• There are programs for W32 and W64, and I would like to have general settings.
• Program for W32 reads other people's settings from the program for W64, and vice versa.
• You have a program that operates on the registry: editor, cleaner, archiver...
Then here's the M$ doc explaining it all.
https://msdn.microsoft.com/en-us/library/windows/d...
PS "Works with the registry" - does it write its settings to the registry or does it really operate on the registry, like an editor or registry cleaner?

S
Stanislav Makarov, 2016-10-14
@Nipheris

MiiNiPaa is right, you don't have to do anything special. Meet this Windows subsystem for 32-bit applications. By the way, system32 in 32 bits is also not system32, but SysWow64. You don't need to disable it, everything should be visible from a 32-bit application as before. If you want without virtualization, build a 64-bit application.
And in general, describe the real problem better, because now you are talking about the aesthetic side of the issue.

A
Alexander Ananiev, 2016-10-14
@SaNNy32

https://msdn.microsoft.com/en-us/library/windows/d...

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question