Запуск скрипта при загрузке windows

On previous versions of Windows I have used the below technique to run a batch file on Windows startup.

1. Create a shortcut to the batch file.
2. Once the shortcut is created, right-click the shortcut file and select Cut.
3. Click Start, then Programs or All Programs. Find the Startup folder and right-click that folder, then select Open.
4. Once the Startup folder is opened, click Edit in the menu bar, then Paste to paste the shortcut file into the Startup folder. If you do not see the menu bar, press the Alt key to make the menu bar visible.
   Any shortcuts in the Startup folder will automatically run each time the user logs in to Windows.

I have been unsuccessful in finding how to do something similar on Windows 10.

Any ideas?

asked Aug 10, 2015 at 20:20

To add to user314352’s answer:

The startup folder is still there and functions as normal.

To access it, press Windows+R, then type shell:startup.

You should be able to do what you were previously doing in Windows 7 from there.

You can also type shell:common startup to access the startup folder for all users.

Alternative through Group Policy

gpedit: Local Computer Policy > Computer Configuration > Windows Settings > Script (Startup/Shutdown)

answered Jun 2, 2021 at 9:04

On previous versions of Windows I have used the below technique to run a batch file on Windows startup.

1. Create a shortcut to the batch file.
2. Once the shortcut is created, right-click the shortcut file and select Cut.
3. Click Start, then Programs or All Programs. Find the Startup folder and right-click that folder, then select Open.
4. Once the Startup folder is opened, click Edit in the menu bar, then Paste to paste the shortcut file into the Startup folder. If you do not see the menu bar, press the Alt key to make the menu bar visible.
   Any shortcuts in the Startup folder will automatically run each time the user logs in to Windows.

I have been unsuccessful in finding how to do something similar on Windows 10.

Any ideas?

asked Aug 10, 2015 at 20:20

To add to user314352’s answer:

The startup folder is still there and functions as normal.

To access it, press Windows+R, then type shell:startup.

You should be able to do what you were previously doing in Windows 7 from there.

You can also type shell:common startup to access the startup folder for all users.

Alternative through Group Policy

gpedit: Local Computer Policy > Computer Configuration > Windows Settings > Script (Startup/Shutdown)

answered Jun 2, 2021 at 9:04

I have a PowerShell script that monitors an image folder. I need to find a way to automatically run this script after the computer starts.

I already tried the following methods, but I couldn’t get it working.

1. Use msconfig and add the PowerShell script to startup, but I cannot find the PowerShell script on that list.

2. Create a shortcut and drop it to startup folder. No luck.

   %SystemRoot%\SysWOW64\WindowsPowerShell\v1.0\powershell.exe -File "C:\Doc\Files\FileMonitor.ps1"
   

   or

   %SystemRoot%\system32\WindowsPowerShell\v1.0\powershell.exe -File "C:\Doc\Files\FileMonitor.ps1"
   

   Here’s my PowerShell script:

   $folder = "C:\\Doc\\Files"
   $dest = "C:\\Doc\\Files\\images"
   $filter = "*.jpg"
   
   $fsw = new-object System.IO.FileSystemWatcher $folder, $filter -Property @{
       IncludeSubDirectories=$false
       NotifyFilter = [System.IO.NotifyFilters]'FileName, LastWrite'
   }
   
   $onCreated = Register-ObjectEvent $fsw Created -SourceIdentifier FileCreated -Action {
   
       Start-Sleep -s 10
       Move-Item -Path C:\Doc\Files\*.jpg C:\Doc\Files\images
   }
   

3. I also tried to add a basic task using taskschd.msc. It is still not working.

   Here’s what I found, and maybe that will help to debug it.

   If I open up a PowerShell window and run the script there, it works. But if I run it in a command prompt,

   powershell.exe -File "C:\Doc\Files\FileMonitor.ps1"
   

   It will not work. I am not sure it’s a permission problem or something else.

   BTW, I have PowerShell 3.0 installed, and if I type $host.version, it will show 3 there. But my powershell.exe seems like it is still v1.0.

   %SystemRoot%\system32\WindowsPowerShell\v1.0\powershell.exe
   

You could set it up as a Scheduled Task, and set the Task Trigger for «At Startup»

This is really just an expansion on @mjolinor simple answer [Use Task Scheduler].

I knew «Task Scheduler» was the correct way, but it took a bit of effort to get it running the way I wanted and thought I’d post my finding for others.

Issues including:

• Redirecting output to logs
• Hiding the PowerShell window

Note: You must have permission to run script see ExecutionPolicy

Then in Task Scheduler, the most important/tricky part is the Action

It should be Start a Program

Program/Script:

powershell

Add arguments (optional) :

-windowstyle hidden -command full\path\script.ps1 >> "%TEMP%\StartupLog.txt" 2>&1

Note:

If you see -File on the internet, it will work, but understand nothing can be after -File except the File Path, IE: The redirect is taken to be part of the file path and it fails, you must use -command in conjunction with redirect, but you can prepend additional commands/arguments such as -windowstyle hidden to not show PowerShell window.

I had to adjust all Write-Host to Write-Output in my script as well.

answered Sep 28, 2020 at 5:11

Be sure, whenever you want PowerShell to run automatically / in the background / non-interactive, it’s a good idea to specify the parameters
-ExecutionPolicy Bypass to PowerShell.exe

PowerShell.exe -ExecutionPolicy Bypass

answered Jun 16, 2019 at 1:33

One thing I found. if you are using Write-Host within your PowerShell scripts, and are also using Task Scheduler (as shown in the posts above), you don’t get all the output from the command line.

powershell.exe -command C:\scripts\script.ps1 >> "C:\scripts\logfile.log"

In my case, I was only seeing output from commands that ran successfully from the PowerShell script.

My conclusion so far is PowerShell uses Out-File to output to another command or in this case a log file.

So if you use *> instead of >> you get all the output from the CLI for your PowerShell script, and you can keep using Write-Host within your script.

powershell.exe -command C:\scripts\script.ps1 *> "C:\scripts\logfile.log"

How to Output to File with PowerShell Out-File Cmdlet

You can also run the script in the background, regardless of user login.

Within your task in Task Scheduler set «Run whether user is logged on or not», and then in the password prompt type your hostname\username then your password (In my case an account with Admin permissions).

I used Set-ExecutionPolicy RemoteSigned -Scope CurrentUser to get around the script execution problem. I still would have preferred to run it on a per-process basis though. A problem for another time.

A relatively short path to specifying a Powershell script to execute at startup in Windows could be:

1. Click the Windows-button (Windows-button + r)
2. Enter this:

shell:startup

1. Create a new shortcut by rightclick and in context menu choose menu item: New=>Shortcut

2. Create a shortcut to your script, e.g:

C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -NoProfile -Command «C:\Users\someuser\Documents\WindowsPowerShell\Scripts\somesscript.ps1»

Note the use of -NoProfile
In case you put a lot of initializing in your $profile file, it is inefficient to load this up to just run a Powershell script. The -NoProfile will skip loading your profile file and is smart to specify, if it is not necessary to run it before the Powershell script is to be executed.

Here you see such a shortcut created (.lnk file with a Powershell icon with shortcut glyph):

answered Sep 24, 2018 at 8:04

This worked for me. Created a Scheduled task with below details:
Trigger : At startup

Actions:
Program/script : powershell.exe
Arguments : -file

answered Nov 2, 2018 at 8:47

You can see scripts and more scheduled for startup inside Task Manager in the Startup tab. Here is how to add a new item to the scheduled startup items.

First, open up explorer to shell:startup location via start-button => run:

explorer shell:startup

Right click in that folder and in the context menu select a new shortcut. Enter the following:

C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -NoProfile
-Command «C:\myfolder\somescript.ps1»

This will startup a Powershell script without starting up your $profile scripts for faster execution. This will make sure that the powershell script is started up.

The shell:startup folder is in:

$env:APPDATA\Microsoft\Windows

And then into the folder:

Start Menu\Programs\Startup

As usual, Microsoft makes things a bit cumbersome for us when a path contains spaces, so you have to put quotes around the full path or just hit tab inside Powershell to autocomplete in this case.

answered Dec 27, 2018 at 20:05

If you do not want to worry about execution policy, you can use the following and put into a batch script. I use this a lot when having techs at sites run my scripts since half the time they say script didnt work but really it’s cause execution policy was undefined our restricted. This will run script even if execution policy would normally block a script to run.
If you want it to run at startup. Then you can place in either shell:startup for a single user or shell:common startup for all users who log into the PC.

cmd.exe /c Powershell.exe -ExecutionPolicy ByPass -File "c:\path\to\script.ps1"

Obviously, making a GPO is your best method if you have a domain and place in Scripts (Startup/Shutdown); under either Computer or User Configurations\Windows Settings\Scripts (Startup/Shutdown).
If you go that way make a directory called Startup or something under **

\\yourdomain.com\netlogon\

and put it there to reference in the GPO. This way you know the DC has rights to execute it. When you browse for the script on the DC you will find it under

C:\Windows\SYSVOL\domain\scripts\Startup\

since this is the local path of netlogon.

answered Feb 11, 2020 at 9:59

Execute PowerShell command below to run the PowerShell script .ps1 through the task scheduler at user login.

Register-ScheduledTask -TaskName "SOME TASKNAME" -Trigger (New-ScheduledTaskTrigger -AtLogon) -Action (New-ScheduledTaskAction -Execute "${Env:WinDir}\System32\WindowsPowerShell\v1.0\powershell.exe" -Argument "-WindowStyle Hidden -Command `"& 'C:\PATH\TO\FILE.ps1'`"") -RunLevel Highest -Force;

-AtLogOn — indicates that a trigger starts a task when a user logs on.

-AtStartup — indicates that a trigger starts a task when the system is started.

-WindowStyle Hidden — don’t show PowerShell window at startup. Remove if not required.

-RunLevel Highest — run PowerShell as administrator. Remove if not required.

P.S.

If necessary execute PowerShell command below to enable PowerShell scripts execution.

Set-ExecutionPolicy -Scope LocalMachine -ExecutionPolicy Unrestricted -Force;

Bypass — nothing is blocked and there are no warnings or prompts.

Unrestricted — loads all configuration files and runs all scripts. If you run an unsigned script that was downloaded from the internet, you’re prompted for permission before it runs.

answered Feb 23, 2020 at 12:02

I’m aware that people around here don’t need a tool like this, but I think it will be useful especially for novice users. Auto Start Tool is a portable freeware designed to simplify the process of automatically launching an app or script when you log in to Windows. It offers three different options for autostart:

1. Task Scheduler
2. Startup Folder
3. Registry Run Key

The best part of the tool is that it supports PowerShell scripts (.ps1), which means you can run a PowerShell script automatically at system startup using any of the three available methods.

Download:
https://disk.yandex.com.tr/d/dFzyB2Fu4lC-Ww

Source:
https://www.portablefreeware.com/forums/viewtopic.php?f=4&t=25761