Forum Discussion
App installs with no errors, but does not fully install
I have verified that all pieces are in the package. The part that is not coming through are the registry entries. The entries are in the Virtual Registry in the package. I have set the package to run with elevated privileges.
Where in the registry are the entries that are not coming through? Only keys under HKLM\Software are read from the package; keys under HKCU or other parts of the registry are not.
- David HedApr 22, 2020Copper Contributor
One set is under HKLM\Software. The other is under HKCU\Software. Neither are coming through. They are ODBC definitions.
- David HedApr 23, 2020Copper Contributor
Here are screen captures of the Virtual Registry in the package and what the registry on the machine I install the package on after installation.
- ChaconApr 23, 2020
Microsoft
To reiterate what Dan Gough already said, it is expected that you do not see the registry keys from your package when you run Regedit normally. Packaged apps run inside a container and you will only be able to see the keys from inside the app's container.
To see what the registry looks like for your app, you would need to launch Regedit inside the container. You can do "Invoke-CommandInDesktopPackage -PackageFamilyName <your package's family name> -Command regedit.exe", or use one of the tools Dan suggested. You should see the expected keys under HKLM\Software\ODBC.
I'm not familiar with ODBC, but if what reads the registry keys is outside of your package, it will not be able to see the keys in it. To see them it would have to be inside the container.