Only administrator account permits this program.

I have pretty much moved my computer from x86 to x64. I get the above
message on a couple of programs. I am the administrator and have used Net
User to make sure it is active. My internet search has not turned up and
useful information. I have also used compatibility to set it to run as
administrator. Anybody have a source of information?
--
Bill

Brought to you from Anchorage, Alaska

On 5/21/20 2:05 PM, this is what KenW wrote:
On Thu, 21 May 2020 09:17:29 -0800, "Bill Bradshaw"
wrote:

I have pretty much moved my computer from x86 to x64. I get the above
message on a couple of programs. I am the administrator and have used Net
User to make sure it is active. My internet search has not turned up and
useful information. I have also used compatibility to set it to run as
administrator. Anybody have a source of information?

Every shortcut has a "run as administrator". If I have a program that
needs to be run as admin, I modify the program exe


KenW

I agree with Ken, make a shortcut to the program and then in the shortcut set the run as administrator.

On 21/05/2020 18:17, Bill Bradshaw wrote:
I have pretty much moved my computer from x86 to x64. I get the above
message on a couple of programs. I am the administrator and have used Net
User to make sure it is active. My internet search has not turned up and
useful information. I have also used compatibility to set it to run as
administrator. Anybody have a source of information?

If a program requires Admin privileges then the bells should start
ringing.Â* WHY?Â*Â* What do they want to write in protected folders?

Only the upgrades to programs/Apps require Admin rights; anything else
is scam and likely to be a malware.

It looks like you have downloaded something from a dodgy site or
installed some free tools recommended by idiots on these newsgroups.Â*
These free tools comes with a huge price tag which users like yourself
can't understand or grasp this because of low intelligence.


--
With over 1.2 billion devices now running Windows 10, customer
satisfaction is higher than any previous version of windows.

On 21/05/2020 21:42, KenW wrote:
I don't have any additional info.



"No worries; Nobody expected you to have any "additional info". "

--
With over 1.2 billion devices now running Windows 10, customer
satisfaction is higher than any previous version of windows.

Bill Bradshaw wrote:

I have pretty much moved my computer from x86 to x64. I get the above
message on a couple of programs. I am the administrator and have
used Net User to make sure it is active. My internet search has not
turned up and useful information. I have also used compatibility to
set it to run as administrator. Anybody have a source of
information?

Did leave UAC enabled (enabled by default on install)? I keep it, but
lots of users disable it because they don't like the nuisance of a
prompt checking if you want to allow the program to have admin
privileges. Way too many users log into a Windows account that had
admin rights when they aren't doing anything that requires that level of
rights. They're just using web browsers, editors, e-mail clients, and
other non-admin software. However, because they log into an admin
Windows account, anything they run normally gets that same level of
permissions, including ransomware, rogueware, and other malware. UAC is
a safety measure, like wearing a condom. Alas, most users don't have
the expertise to make correct decisions, so they okay the UAC prompt for
any process that wants elevated rights. It is a nuisance to them
because they have no clue if the process should be granted elevated
rights.

https://en.wikipedia.org/wiki/User_Account_Control

https://docs.microsoft.com/en-us/win...-control-works

VanguardLH wrote:
Bill Bradshaw wrote:

I have pretty much moved my computer from x86 to x64. I get the
above message on a couple of programs. I am the administrator and
have used Net User to make sure it is active. My internet search
has not turned up and useful information. I have also used
compatibility to set it to run as administrator. Anybody have a
source of information?

Did leave UAC enabled (enabled by default on install)? I keep it, but
lots of users disable it because they don't like the nuisance of a
prompt checking if you want to allow the program to have admin
privileges. Way too many users log into a Windows account that had
admin rights when they aren't doing anything that requires that level
of rights. They're just using web browsers, editors, e-mail clients,
and other non-admin software. However, because they log into an admin
Windows account, anything they run normally gets that same level of
permissions, including ransomware, rogueware, and other malware. UAC
is a safety measure, like wearing a condom. Alas, most users don't
have the expertise to make correct decisions, so they okay the UAC
prompt for any process that wants elevated rights. It is a nuisance
to them because they have no clue if the process should be granted
elevated rights.

https://en.wikipedia.org/wiki/User_Account_Control

https://docs.microsoft.com/en-us/win...-control-works

I am the only one in this house so the first thing I turn off is UAC.
Besides I do not do anything illegal and password protect personal info. Is
there anything that would bring this up because I am trying to install x86
on x64?

Bill

Bill Bradshaw wrote:

I am the only one in this house so the first thing I turn off is UAC.
Besides I do not do anything illegal and password protect personal
info. Is there anything that would bring this up because I am trying
to install x86 on x64?

Don't know if you upgraded from x32 to x64 (didn't think you could do
that, but I've not tried), or if you did a fresh install of x64 (I
always do fresh installs, never upgrades). Also, no idea what are "some
programs" or under what folder they are installed (some old programs
expect allowances under C:\Program Files [x86]" that haven't been
allowed since Windows Vista).

Is the exact message you get "Only administrator account permits this
program"? UAC gives a prompt "Do you want to allow this app to make
changes". What you describe sounds like a policy setting.

VanguardLH wrote:

Don't know if you upgraded from x32 to x64 (didn't think you could do
that, but I've not tried), ...

I say that because the bitwidt of drivers *MUST* match the OS bitwidth.
You would have 32-bit drivers under an x86 version of Windows, and those
are not usable under an x64 version of Windows. You must use 64-bit
drivers with 64-bit Windows.

On 5/22/2020 11:10 AM, VanguardLH wrote:
Bill Bradshaw wrote:

I am the only one in this house so the first thing I turn off is UAC.
Besides I do not do anything illegal and password protect personal
info. Is there anything that would bring this up because I am trying
to install x86 on x64?

Don't know if you upgraded from x32 to x64 (didn't think you could do
that, but I've not tried),


It is not possible to change the "bitness"
of Windows. You have to do a clean installation.



or if you did a fresh install of x64 (I
always do fresh installs, never upgrades). Also, no idea what are "some
programs" or under what folder they are installed (some old programs
expect allowances under C:\Program Files [x86]" that haven't been
allowed since Windows Vista).

Is the exact message you get "Only administrator account permits this
program"? UAC gives a prompt "Do you want to allow this app to make
changes". What you describe sounds like a policy setting.



--
Ken

On 22/05/2020 17:45, Bill Bradshaw wrote:
Is
there anything that would bring this up because I am trying to install x86
on x64?


You could hire a competent technician (avoid hiring rogue traders) who
can resolve this for you in 10 minutes.

They are charging a premium rate these days because of lockdown and
special precautions they need to take!.


--
With over 1.2 billion devices now running Windows 10, customer
satisfaction is higher than any previous version of windows.

Ken Blake wrote:

VanguardLH wrote:

Bill Bradshaw wrote:

I am the only one in this house so the first thing I turn off is
UAC. Besides I do not do anything illegal and password protect
personal info. Is there anything that would bring this up because
I am trying to install x86 on x64?

Don't know if you upgraded from x32 to x64 (didn't think you could
do that, but I've not tried),

It is not possible to change the "bitness" of Windows. You have to do
a clean installation.

Addressed in a reply to myself (about having to match bitwidth of
drivers to bitwidth of OS) issued 1 minute after my prior post and over
2 hours before your reply.

The OP said, "install x86 on x64". Unless x86 refers to the OS (32-bit)
and X64 refers to the hardware (install 32-bit OS on 64-bit hardware),
the indication is OP intends to upgrade an x86 OS to an x64 OS, but
there's the bitwidth driver issue.

We also don't know if the OP went to a Home or Pro edition of Win 10.
The Pro version includes the policy editor, and the message noted in the
Subject hints that a policy is causing interference. All policies are
registry entries, so it is possible a tweaker or installed program can
tweak the registry to add policies, or even the user without the policy
editor can edit the registry to add policies (except those where the OS
generates and later tests a hash to prevent malicious modification).

" get the above message on a couple of programs" tell us nothing about
what are those programs. Since the actual version of original Windows
was never specified, the OP might be moving from Windows 9x/ME or XP to
Windows 10, so those could be really old programs ran under a version of
Windows that has protected the C:\Program Files [x86] folder since
Vista: programs are NOT to store their user data under there, and
instead use the %appdata% or %allusersprofile% folders. For example, my
ancient NNTP client (40tude Dialog) will have problems accessing its
message store if the program is installed under C:\Profile Files x86.
It much be installed elsewhere, because the program is abandoned, so it
will never get fixed. I created a C:\Programs folder for such programs
that expect their data to get stored under their install folder, so
Dialog is installed under C:\Programs\40tude. Program folder protection
was added back in Windows Vista. Again, we don't know what x86 means
for the prior version of Windows for the OP.

Just way too much was left vague by the OP. With the number of guesses
regarding which is the old version of Windows, which bitwidth of the old
OS, the bitwidth supported by the hardware, which edition of Windows,
and what are the old programs (in case they aren't vertical market
software, so someone else might also use them), the guess matrix just
gets too big.

VanguardLH wrote:
Bill Bradshaw wrote:

I am the only one in this house so the first thing I turn off is UAC.
Besides I do not do anything illegal and password protect personal
info. Is there anything that would bring this up because I am trying
to install x86 on x64?

Don't know if you upgraded from x32 to x64 (didn't think you could do
that, but I've not tried), or if you did a fresh install of x64 (I
always do fresh installs, never upgrades). Also, no idea what are
"some programs" or under what folder they are installed (some old
programs expect allowances under C:\Program Files [x86]" that haven't
been allowed since Windows Vista).

Is the exact message you get "Only administrator account permits this
program"? UAC gives a prompt "Do you want to allow this app to make
changes". What you describe sounds like a policy setting.

It was a fresh install of x64 Windows Pro. I thought maybe x64 did not like
some x86 programs which would make sense. The exact message is how you
typed it. It is surprising that I could not find this wording on a search
of the internet.

Bill

VanguardLH wrote:
Ken Blake wrote:

VanguardLH wrote:

Bill Bradshaw wrote:

I am the only one in this house so the first thing I turn off is
UAC. Besides I do not do anything illegal and password protect
personal info. Is there anything that would bring this up because
I am trying to install x86 on x64?

Don't know if you upgraded from x32 to x64 (didn't think you could
do that, but I've not tried),

It is not possible to change the "bitness" of Windows. You have to do
a clean installation.

Addressed in a reply to myself (about having to match bitwidth of
drivers to bitwidth of OS) issued 1 minute after my prior post and
over 2 hours before your reply.

The OP said, "install x86 on x64". Unless x86 refers to the OS
(32-bit) and X64 refers to the hardware (install 32-bit OS on 64-bit
hardware), the indication is OP intends to upgrade an x86 OS to an
x64 OS, but there's the bitwidth driver issue.

We also don't know if the OP went to a Home or Pro edition of Win 10.
The Pro version includes the policy editor, and the message noted in
the Subject hints that a policy is causing interference. All
policies are registry entries, so it is possible a tweaker or
installed program can tweak the registry to add policies, or even the
user without the policy editor can edit the registry to add policies
(except those where the OS generates and later tests a hash to
prevent malicious modification).

" get the above message on a couple of programs" tell us nothing about
what are those programs. Since the actual version of original Windows
was never specified, the OP might be moving from Windows 9x/ME or XP
to Windows 10, so those could be really old programs ran under a
version of Windows that has protected the C:\Program Files [x86]
folder since Vista: programs are NOT to store their user data under
there, and instead use the %appdata% or %allusersprofile% folders.
For example, my ancient NNTP client (40tude Dialog) will have
problems accessing its message store if the program is installed
under C:\Profile Files x86. It much be installed elsewhere, because
the program is abandoned, so it will never get fixed. I created a
C:\Programs folder for such programs that expect their data to get
stored under their install folder, so Dialog is installed under
C:\Programs\40tude. Program folder protection was added back in
Windows Vista. Again, we don't know what x86 means for the prior
version of Windows for the OP.

Just way too much was left vague by the OP. With the number of
guesses regarding which is the old version of Windows, which bitwidth
of the old OS, the bitwidth supported by the hardware, which edition
of Windows, and what are the old programs (in case they aren't
vertical market software, so someone else might also use them), the
guess matrix just gets too big.

These are progams that ran fine under x86 Windows 10 Pro. So the drivers
would have been written for x86. One of these manages the function keys on
the computer and would have been written for x86 Vista. Is there anyway
around this? I did make a full backup and saved it so I can use that to
restore the computer back to x86 Windows 10 Pro. Maybe it is time to
replace this 10 year old laptop with a new one. One of the things I like is
it has a modem built into it. There are remote villages in the Alaska that
do not have Broadband. Everybody should experience calling through a modem
over a satellite connection.

Bill

On Sat, 23 May 2020 10:18:39 -0800, "Bill Bradshaw"
wrote:

VanguardLH wrote:
Bill Bradshaw wrote:

I am the only one in this house so the first thing I turn off is UAC.
Besides I do not do anything illegal and password protect personal
info. Is there anything that would bring this up because I am trying
to install x86 on x64?

Don't know if you upgraded from x32 to x64 (didn't think you could do
that, but I've not tried), or if you did a fresh install of x64 (I
always do fresh installs, never upgrades). Also, no idea what are
"some programs" or under what folder they are installed (some old
programs expect allowances under C:\Program Files [x86]" that haven't
been allowed since Windows Vista).

Is the exact message you get "Only administrator account permits this
program"? UAC gives a prompt "Do you want to allow this app to make
changes". What you describe sounds like a policy setting.

It was a fresh install of x64 Windows Pro. I thought maybe x64 did not like
some x86 programs

"...some x86 programs" that you installed. We can't see what they are. Can
you give an example or two? Maybe someone else ran into the same situation
and worked out a solution.

which would make sense. The exact message is how you
typed it. It is surprising that I could not find this wording on a search
of the internet.

On Sat, 23 May 2020 10:28:32 -0800, "Bill Bradshaw"
wrote:

VanguardLH wrote:
Ken Blake wrote:

VanguardLH wrote:

Bill Bradshaw wrote:

I am the only one in this house so the first thing I turn off is
UAC. Besides I do not do anything illegal and password protect
personal info. Is there anything that would bring this up because
I am trying to install x86 on x64?

Don't know if you upgraded from x32 to x64 (didn't think you could
do that, but I've not tried),

It is not possible to change the "bitness" of Windows. You have to do
a clean installation.

Addressed in a reply to myself (about having to match bitwidth of
drivers to bitwidth of OS) issued 1 minute after my prior post and
over 2 hours before your reply.

The OP said, "install x86 on x64". Unless x86 refers to the OS
(32-bit) and X64 refers to the hardware (install 32-bit OS on 64-bit
hardware), the indication is OP intends to upgrade an x86 OS to an
x64 OS, but there's the bitwidth driver issue.

We also don't know if the OP went to a Home or Pro edition of Win 10.
The Pro version includes the policy editor, and the message noted in
the Subject hints that a policy is causing interference. All
policies are registry entries, so it is possible a tweaker or
installed program can tweak the registry to add policies, or even the
user without the policy editor can edit the registry to add policies
(except those where the OS generates and later tests a hash to
prevent malicious modification).

" get the above message on a couple of programs" tell us nothing about
what are those programs. Since the actual version of original Windows
was never specified, the OP might be moving from Windows 9x/ME or XP
to Windows 10, so those could be really old programs ran under a
version of Windows that has protected the C:\Program Files [x86]
folder since Vista: programs are NOT to store their user data under
there, and instead use the %appdata% or %allusersprofile% folders.
For example, my ancient NNTP client (40tude Dialog) will have
problems accessing its message store if the program is installed
under C:\Profile Files x86. It much be installed elsewhere, because
the program is abandoned, so it will never get fixed. I created a
C:\Programs folder for such programs that expect their data to get
stored under their install folder, so Dialog is installed under
C:\Programs\40tude. Program folder protection was added back in
Windows Vista. Again, we don't know what x86 means for the prior
version of Windows for the OP.

Just way too much was left vague by the OP. With the number of
guesses regarding which is the old version of Windows, which bitwidth
of the old OS, the bitwidth supported by the hardware, which edition
of Windows, and what are the old programs (in case they aren't
vertical market software, so someone else might also use them), the
guess matrix just gets too big.

These are progams that ran fine under x86 Windows 10 Pro. So the drivers
would have been written for x86. One of these manages the function keys on
the computer and would have been written for x86 Vista. Is there anyway
around this?

Possibly. Go back to where you got the program and look for a compatible
version, or look for a forum where folks talk about Win 10x64
compatibility.

I did make a full backup and saved it so I can use that to
restore the computer back to x86 Windows 10 Pro. Maybe it is time to
replace this 10 year old laptop with a new one.

How would a new laptop help?

One of the things I like is
it has a modem built into it. There are remote villages in the Alaska that
do not have Broadband. Everybody should experience calling through a modem
over a satellite connection.