[SIZE=9pt]Everybody has probably come across the metro app crashing issues immediately after execution. I have solved a couple of these issues so far. One
issue I solved by adding "ALL APPLICATION PACKAGES" permissions to a registry key ("HKCLwow6432nodeinterface", group policy applying and excluding read access for this user), one by adding permissions to "C
rogram FilesWindowsApps"
directory (same user), another by adding permissions to "%localappdata%Packages" (same user again).[/SIZE]
[SIZE=9pt]The most annoying thing about troubleshooting these issues is that I don't understand the detailed behaviours and workings of how these apps work,
and I can't find any documentation on it either. I'm working on using WADK and procmon to gain some knowledge at the moment, but want to get the information faster.[/SIZE]
[SIZE=9pt]Is there anybody who can step through the registry keys, executables, directories, network addresses metro apps generally use and require for successful
execution and the permissions required to access them for troubleshooting purposes?[/SIZE]
View the full article
issue I solved by adding "ALL APPLICATION PACKAGES" permissions to a registry key ("HKCLwow6432nodeinterface", group policy applying and excluding read access for this user), one by adding permissions to "C
rogram FilesWindowsApps"directory (same user), another by adding permissions to "%localappdata%Packages" (same user again).[/SIZE]
[SIZE=9pt]The most annoying thing about troubleshooting these issues is that I don't understand the detailed behaviours and workings of how these apps work,
and I can't find any documentation on it either. I'm working on using WADK and procmon to gain some knowledge at the moment, but want to get the information faster.[/SIZE]
[SIZE=9pt]Is there anybody who can step through the registry keys, executables, directories, network addresses metro apps generally use and require for successful
execution and the permissions required to access them for troubleshooting purposes?[/SIZE]
View the full article