Is there any reason for an application to be installed in AppData on Win7?
I installed the Zoom Client for Meetings on a Win7 box.
This software is a popular application used by many people (in other words, it's not just some shady random piece of software).
What surprised me is that the application installed itself in C:Users[username]AppDataRoamingZoom.
I've never seen an application install itself in AppData before. (They always use Program Files or Program Files (x86).)
Is this an error by the development team, or does it sometimes make sense to install an application into AppData?
(As a side-question, Windows' application compatibility assistant popped up and asked if the application was installed correctly. Since the application appeared to work, I did not try an immediate reinstall via the compatibility assistant. What would have happened if I did?)
windows-7 windows installation compatibility appdata
add a comment |
I installed the Zoom Client for Meetings on a Win7 box.
This software is a popular application used by many people (in other words, it's not just some shady random piece of software).
What surprised me is that the application installed itself in C:Users[username]AppDataRoamingZoom.
I've never seen an application install itself in AppData before. (They always use Program Files or Program Files (x86).)
Is this an error by the development team, or does it sometimes make sense to install an application into AppData?
(As a side-question, Windows' application compatibility assistant popped up and asked if the application was installed correctly. Since the application appeared to work, I did not try an immediate reinstall via the compatibility assistant. What would have happened if I did?)
windows-7 windows installation compatibility appdata
1
It's not uncommon. When you have software that is just being installed for a specific user instead of system-wide, it will usually go in that folder. Even Chrome installs itself there when you choose "just for this user."
– n8te
Jan 25 at 4:51
Chrome for the longest time installed to AppData.
– Ramhound
Jan 25 at 4:51
1
Each AppData folder is allocated only for that current user. So installing in that folder will not affect other users in that machine.
– Biswapriyo
Jan 25 at 4:52
add a comment |
I installed the Zoom Client for Meetings on a Win7 box.
This software is a popular application used by many people (in other words, it's not just some shady random piece of software).
What surprised me is that the application installed itself in C:Users[username]AppDataRoamingZoom.
I've never seen an application install itself in AppData before. (They always use Program Files or Program Files (x86).)
Is this an error by the development team, or does it sometimes make sense to install an application into AppData?
(As a side-question, Windows' application compatibility assistant popped up and asked if the application was installed correctly. Since the application appeared to work, I did not try an immediate reinstall via the compatibility assistant. What would have happened if I did?)
windows-7 windows installation compatibility appdata
I installed the Zoom Client for Meetings on a Win7 box.
This software is a popular application used by many people (in other words, it's not just some shady random piece of software).
What surprised me is that the application installed itself in C:Users[username]AppDataRoamingZoom.
I've never seen an application install itself in AppData before. (They always use Program Files or Program Files (x86).)
Is this an error by the development team, or does it sometimes make sense to install an application into AppData?
(As a side-question, Windows' application compatibility assistant popped up and asked if the application was installed correctly. Since the application appeared to work, I did not try an immediate reinstall via the compatibility assistant. What would have happened if I did?)
windows-7 windows installation compatibility appdata
windows-7 windows installation compatibility appdata
asked Jan 25 at 4:49
RockPaperLizardRockPaperLizard
3,126133571
3,126133571
1
It's not uncommon. When you have software that is just being installed for a specific user instead of system-wide, it will usually go in that folder. Even Chrome installs itself there when you choose "just for this user."
– n8te
Jan 25 at 4:51
Chrome for the longest time installed to AppData.
– Ramhound
Jan 25 at 4:51
1
Each AppData folder is allocated only for that current user. So installing in that folder will not affect other users in that machine.
– Biswapriyo
Jan 25 at 4:52
add a comment |
1
It's not uncommon. When you have software that is just being installed for a specific user instead of system-wide, it will usually go in that folder. Even Chrome installs itself there when you choose "just for this user."
– n8te
Jan 25 at 4:51
Chrome for the longest time installed to AppData.
– Ramhound
Jan 25 at 4:51
1
Each AppData folder is allocated only for that current user. So installing in that folder will not affect other users in that machine.
– Biswapriyo
Jan 25 at 4:52
1
1
It's not uncommon. When you have software that is just being installed for a specific user instead of system-wide, it will usually go in that folder. Even Chrome installs itself there when you choose "just for this user."
– n8te
Jan 25 at 4:51
It's not uncommon. When you have software that is just being installed for a specific user instead of system-wide, it will usually go in that folder. Even Chrome installs itself there when you choose "just for this user."
– n8te
Jan 25 at 4:51
Chrome for the longest time installed to AppData.
– Ramhound
Jan 25 at 4:51
Chrome for the longest time installed to AppData.
– Ramhound
Jan 25 at 4:51
1
1
Each AppData folder is allocated only for that current user. So installing in that folder will not affect other users in that machine.
– Biswapriyo
Jan 25 at 4:52
Each AppData folder is allocated only for that current user. So installing in that folder will not affect other users in that machine.
– Biswapriyo
Jan 25 at 4:52
add a comment |
2 Answers
2
active
oldest
votes
Actually this is perfectly normal and expected behavior.
Applications that install for only one user do this. This usually includes programs that give you an option to install for “this user only” or “all users” of this computer. The former is installed under AppData - for one specific user.
This is also a good indication that the application does NOT require elevated permissions to run. Applications do not have write permissions in the Program Files folders unless you click to Allow the program to “make changes to your computer,” during installation.
For these reasons, it is perfectly normal for an application like this to install under AppData. It is designed for one specific user, and does not require elevated permissions to function.
Another interesting fact is that the application will only show up under your user account when viewing the “Programs & Features” listing. As a systems admin, you may notice that “non-admin” users have certain applications installed and showing up in the “Programs & Features” list. You may immediately question how that user was able to install software on the computer. But, the reasons above are why. It did not require admin permissions. If the admin then logs in, they will NOT see the application in their programs listing. The application has to also be uninstalled by the same user who installed it. This can be a source of confusion as some applications can be installed simultaneously for one user account and system-wide for all user accounts.
Thank you for the details. You wrote: Applications that install for only one user do this. This usually includes programs that give you an option to install for “this user only” or “all users” of this computer. I guess it would have been nice if the installer presented such an option, but it didn't. At least I now know why it got installed there.
– RockPaperLizard
Jan 25 at 6:55
add a comment |
Yes it is a normal practice.
This is mostly for administrative reasons and is known as Install Context
Install context allows admins to specify if the application is to be installed in user context or system context. Installing application in system context allows an administrator to make the application available for all the users in a computer. Similarly, installing application in user context allows an application to be made available for only one user.
Re-installing the application wouldn't have changed this behavior.
Another good read
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1398194%2fis-there-any-reason-for-an-application-to-be-installed-in-appdata-on-win7%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
Actually this is perfectly normal and expected behavior.
Applications that install for only one user do this. This usually includes programs that give you an option to install for “this user only” or “all users” of this computer. The former is installed under AppData - for one specific user.
This is also a good indication that the application does NOT require elevated permissions to run. Applications do not have write permissions in the Program Files folders unless you click to Allow the program to “make changes to your computer,” during installation.
For these reasons, it is perfectly normal for an application like this to install under AppData. It is designed for one specific user, and does not require elevated permissions to function.
Another interesting fact is that the application will only show up under your user account when viewing the “Programs & Features” listing. As a systems admin, you may notice that “non-admin” users have certain applications installed and showing up in the “Programs & Features” list. You may immediately question how that user was able to install software on the computer. But, the reasons above are why. It did not require admin permissions. If the admin then logs in, they will NOT see the application in their programs listing. The application has to also be uninstalled by the same user who installed it. This can be a source of confusion as some applications can be installed simultaneously for one user account and system-wide for all user accounts.
Thank you for the details. You wrote: Applications that install for only one user do this. This usually includes programs that give you an option to install for “this user only” or “all users” of this computer. I guess it would have been nice if the installer presented such an option, but it didn't. At least I now know why it got installed there.
– RockPaperLizard
Jan 25 at 6:55
add a comment |
Actually this is perfectly normal and expected behavior.
Applications that install for only one user do this. This usually includes programs that give you an option to install for “this user only” or “all users” of this computer. The former is installed under AppData - for one specific user.
This is also a good indication that the application does NOT require elevated permissions to run. Applications do not have write permissions in the Program Files folders unless you click to Allow the program to “make changes to your computer,” during installation.
For these reasons, it is perfectly normal for an application like this to install under AppData. It is designed for one specific user, and does not require elevated permissions to function.
Another interesting fact is that the application will only show up under your user account when viewing the “Programs & Features” listing. As a systems admin, you may notice that “non-admin” users have certain applications installed and showing up in the “Programs & Features” list. You may immediately question how that user was able to install software on the computer. But, the reasons above are why. It did not require admin permissions. If the admin then logs in, they will NOT see the application in their programs listing. The application has to also be uninstalled by the same user who installed it. This can be a source of confusion as some applications can be installed simultaneously for one user account and system-wide for all user accounts.
Thank you for the details. You wrote: Applications that install for only one user do this. This usually includes programs that give you an option to install for “this user only” or “all users” of this computer. I guess it would have been nice if the installer presented such an option, but it didn't. At least I now know why it got installed there.
– RockPaperLizard
Jan 25 at 6:55
add a comment |
Actually this is perfectly normal and expected behavior.
Applications that install for only one user do this. This usually includes programs that give you an option to install for “this user only” or “all users” of this computer. The former is installed under AppData - for one specific user.
This is also a good indication that the application does NOT require elevated permissions to run. Applications do not have write permissions in the Program Files folders unless you click to Allow the program to “make changes to your computer,” during installation.
For these reasons, it is perfectly normal for an application like this to install under AppData. It is designed for one specific user, and does not require elevated permissions to function.
Another interesting fact is that the application will only show up under your user account when viewing the “Programs & Features” listing. As a systems admin, you may notice that “non-admin” users have certain applications installed and showing up in the “Programs & Features” list. You may immediately question how that user was able to install software on the computer. But, the reasons above are why. It did not require admin permissions. If the admin then logs in, they will NOT see the application in their programs listing. The application has to also be uninstalled by the same user who installed it. This can be a source of confusion as some applications can be installed simultaneously for one user account and system-wide for all user accounts.
Actually this is perfectly normal and expected behavior.
Applications that install for only one user do this. This usually includes programs that give you an option to install for “this user only” or “all users” of this computer. The former is installed under AppData - for one specific user.
This is also a good indication that the application does NOT require elevated permissions to run. Applications do not have write permissions in the Program Files folders unless you click to Allow the program to “make changes to your computer,” during installation.
For these reasons, it is perfectly normal for an application like this to install under AppData. It is designed for one specific user, and does not require elevated permissions to function.
Another interesting fact is that the application will only show up under your user account when viewing the “Programs & Features” listing. As a systems admin, you may notice that “non-admin” users have certain applications installed and showing up in the “Programs & Features” list. You may immediately question how that user was able to install software on the computer. But, the reasons above are why. It did not require admin permissions. If the admin then logs in, they will NOT see the application in their programs listing. The application has to also be uninstalled by the same user who installed it. This can be a source of confusion as some applications can be installed simultaneously for one user account and system-wide for all user accounts.
answered Jan 25 at 5:04
AppleoddityAppleoddity
7,77021225
7,77021225
Thank you for the details. You wrote: Applications that install for only one user do this. This usually includes programs that give you an option to install for “this user only” or “all users” of this computer. I guess it would have been nice if the installer presented such an option, but it didn't. At least I now know why it got installed there.
– RockPaperLizard
Jan 25 at 6:55
add a comment |
Thank you for the details. You wrote: Applications that install for only one user do this. This usually includes programs that give you an option to install for “this user only” or “all users” of this computer. I guess it would have been nice if the installer presented such an option, but it didn't. At least I now know why it got installed there.
– RockPaperLizard
Jan 25 at 6:55
Thank you for the details. You wrote: Applications that install for only one user do this. This usually includes programs that give you an option to install for “this user only” or “all users” of this computer. I guess it would have been nice if the installer presented such an option, but it didn't. At least I now know why it got installed there.
– RockPaperLizard
Jan 25 at 6:55
Thank you for the details. You wrote: Applications that install for only one user do this. This usually includes programs that give you an option to install for “this user only” or “all users” of this computer. I guess it would have been nice if the installer presented such an option, but it didn't. At least I now know why it got installed there.
– RockPaperLizard
Jan 25 at 6:55
add a comment |
Yes it is a normal practice.
This is mostly for administrative reasons and is known as Install Context
Install context allows admins to specify if the application is to be installed in user context or system context. Installing application in system context allows an administrator to make the application available for all the users in a computer. Similarly, installing application in user context allows an application to be made available for only one user.
Re-installing the application wouldn't have changed this behavior.
Another good read
add a comment |
Yes it is a normal practice.
This is mostly for administrative reasons and is known as Install Context
Install context allows admins to specify if the application is to be installed in user context or system context. Installing application in system context allows an administrator to make the application available for all the users in a computer. Similarly, installing application in user context allows an application to be made available for only one user.
Re-installing the application wouldn't have changed this behavior.
Another good read
add a comment |
Yes it is a normal practice.
This is mostly for administrative reasons and is known as Install Context
Install context allows admins to specify if the application is to be installed in user context or system context. Installing application in system context allows an administrator to make the application available for all the users in a computer. Similarly, installing application in user context allows an application to be made available for only one user.
Re-installing the application wouldn't have changed this behavior.
Another good read
Yes it is a normal practice.
This is mostly for administrative reasons and is known as Install Context
Install context allows admins to specify if the application is to be installed in user context or system context. Installing application in system context allows an administrator to make the application available for all the users in a computer. Similarly, installing application in user context allows an application to be made available for only one user.
Re-installing the application wouldn't have changed this behavior.
Another good read
answered Jan 25 at 5:06
punpun
4,88581853
4,88581853
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1398194%2fis-there-any-reason-for-an-application-to-be-installed-in-appdata-on-win7%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
It's not uncommon. When you have software that is just being installed for a specific user instead of system-wide, it will usually go in that folder. Even Chrome installs itself there when you choose "just for this user."
– n8te
Jan 25 at 4:51
Chrome for the longest time installed to AppData.
– Ramhound
Jan 25 at 4:51
1
Each AppData folder is allocated only for that current user. So installing in that folder will not affect other users in that machine.
– Biswapriyo
Jan 25 at 4:52