Windows 10: How to allow Standard User local account to Install Programs

I have Win 11 set up with a Standard User Account local without admin privileges for day to day operations. I don't want anyone with admin privileges doing day to day work for safety reasons. What is the best way to give the Standard User temporary access to an admin password for doing tasks like installing programs and other tasks requiring admin?

:)

 

Local account installation question

I'm fairly certain that Skip this step was available in 10.0.130 - the workaround in Step 20 (back button) is no longer required.

The currently known, as of 10.0.130, ways to create a Local account sign-in are

• Skip this step at the MS account creation phase
• No Internet connection during the install
• static IP (post# 2 by Fragment) - New (to me anyway)

 

Is there still reason to use standard user account in Windows OS?

Thanks to all for taking the trouble to share your opinion. I personally have always had two accounts on my computer – administrator for administrator actions and standard for everyday use. The reason I'm asking is that some legitimate modern programs still require administrative permissions to run them in standard user. I suspect that some legitimate modern programs are unable to install updates in standard user even with administrative permissions. And some programs have limited functionality in standard user account. Last but not least, it's an extra work to set up and administer two accounts for one user of the computer and it takes up more space (relevant for SSD). This is all quite annoying.

As I’m the only user of my computer my only concern is adequate virus protection. I'm well aware of all the everyday hazard associated with using the computer in this day and age. I know how to use and properly configure antivirus software and firewall. So what I’m trying to find an answer to is whether or not UAC turns an administrator account into what is known as a protected administrator account, basically, an administrator account that runs with standard user account privileges. And if not, how much of a benefit for me to use standard user account for everyday work considering that I frequently have to deal with some of my programs constantly requiring administrative permissions to run and some are unable to install updates even with elevated permissions [in standard account].

 

Allowing Local Standard Account Log On As Batch Job Rights

Hi,

At the risk of sounding naive, I hope someone can help with the following situation.

I created a task in Task Scheduler for the standard user account to have Windows Defender check for and update signatures every 3 hours rather than the once per day default setting.

However, when running the task the command prompt window remained open, which I did not want.

I logged in as administrator and as the title says allowed the standard user log on as a batch job rights which then allowed me to set the task to not have the window open.

So far so good, but the question is whether or not I have now lowered the security of both the standard and admin accounts by changing the setting in secpol.msc to allow the rights.

Any input appreciated, even if the suggestion is to undo what I set up.

Thanks!