Registries in Windows 10 Pro
-
I have a basic WindowsForm C# application that loops thru a key (Dependencies) and list all values of all subkeys found. It is compiled to use Any CPU (unselecting "Prefer 32-bit" option as well ) registry hive looks like this: Dependencies -{{050d4fc8-5d48-4b8f-8972-47c82c46020f} ..... ..... -{030d4fc8-5d48-4b8f-8342-47c82c46020f} ... ... -Microsoft.VS.VC_RuntimeAdditionalVSU_x86,v11 -Microsoft.VS.VC_RuntimeMinimumVSU_amd64,v12 .... .... When I run the application in server 2012 or higher, the application reads all values found in each subkey (works great) but when I ran it in Windows 10 Pro, only the subkeys that start with Microsoft.VS.VC_..etc are read. Any ideas how to fix it?
-
I have a basic WindowsForm C# application that loops thru a key (Dependencies) and list all values of all subkeys found. It is compiled to use Any CPU (unselecting "Prefer 32-bit" option as well ) registry hive looks like this: Dependencies -{{050d4fc8-5d48-4b8f-8972-47c82c46020f} ..... ..... -{030d4fc8-5d48-4b8f-8342-47c82c46020f} ... ... -Microsoft.VS.VC_RuntimeAdditionalVSU_x86,v11 -Microsoft.VS.VC_RuntimeMinimumVSU_amd64,v12 .... .... When I run the application in server 2012 or higher, the application reads all values found in each subkey (works great) but when I ran it in Windows 10 Pro, only the subkeys that start with Microsoft.VS.VC_..etc are read. Any ideas how to fix it?
picasso2 wrote:
Any ideas how to fix it?
Without seeing some code it is impossible. You need to use regedit to look at the entries and see if there are any differences between the two systems. Then use your debugger to track the code and see exactly where the problem occurs. See also 32-bit and 64-bit Application Data in the Registry (Windows)[^].