Reply to thread

Message

<blockquote data-quote="RandyDSok" data-source="post: 167289" data-attributes="member: 201">This has nothing to do with you using a MS Account or a local account... it has everything to do with how users ( even ones created having admin permissions ) by default single program install as a standard user and not an administrator user unless run the install file as an administrator ( right click option )... but things get more complicated when the install process is actually calling other install routines ( like installing the C++ runtimes ) because of how UAC ( user access control ) works.So newer installation packages are programmed to request and raise the permissions from the standard user profile up to an admin profile for each installation process... Older ones didn't do that. Why... this was done for security reasons so, if an install package got infected with a second package ( virus etc ) ... the second installation process doesn't get the same rights as the initial one does. So each install process is now suppose to request a UAC rights permission increase from a standard user to an admin user. Older installation packages this wasn't an issue in earlier versions of Windows as long as the initial install package was given admin rights, then the following installation packages that may be called also had admin rights... that is now not a loophole that is available to the following installation processes... now each one must make that UAC request.Tony mentions one solution... enable the Adminstrator's account and install while logged into that account. The other solution which isn't as easy, is to manually install the other required packages first which of course requires that you find and download those packages separately.</blockquote>

[QUOTE="RandyDSok, post: 167289, member: 201"] This has nothing to do with you using a MS Account or a local account... it has everything to do with how users ( even ones created having admin permissions ) by default single program install as a standard user and not an administrator user unless run the install file as an administrator ( right click option )... but things get more complicated when the install process is actually calling other install routines ( like installing the C++ runtimes ) because of how UAC ( user access control ) works. So newer installation packages are programmed to request and raise the permissions from the standard user profile up to an admin profile for each installation process... Older ones didn't do that. Why... this was done for security reasons so, if an install package got infected with a second package ( virus etc ) ... the second installation process doesn't get the same rights as the initial one does. So each install process is now suppose to request a UAC rights permission increase from a standard user to an admin user. Older installation packages this wasn't an issue in earlier versions of Windows as long as the initial install package was given admin rights, then the following installation packages that may be called also had admin rights... that is now not a loophole that is available to the following installation processes... now each one must make that UAC request. Tony mentions one solution... enable the Adminstrator's account and install while logged into that account. The other solution which isn't as easy, is to manually install the other required packages first which of course requires that you find and download those packages separately. [/QUOTE]

Verification