Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Collection of scripts to install various tools on Windows

License

NotificationsYou must be signed in to change notification settings

lelegard/win-install-scripts

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

50 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Each PowerShell script downloads and installs some software for Windows.Each downloaded software is either open source or free to use or is abuiltin feature of Windows.

These scripts are useful to automate the setup of a software environment,typically in a CI/CD pipeline.

Eachinstall-*.ps1 script only depends oninstall-common.ps1.Both files can be individually extracted for reuse in another project(liberal BSD-2-Clause license).

By default, when a script is run from the Windows explorer, it pops upa PowerShell window, performs the download and installation and finallywaits for the user to press before closing the window. Whenused in an automated scripted environment, use option-NoPause toavoid the final interaction.

Each installation script accepts the following options.

OptionDescription
-DestinationpathSpecify a local directory where the package will be downloaded. By default, use the downloads folder for the current user.
-ForceDownloadForce a download even if the package is already downloaded.
-GitHubActionsWhen used in a GitHub Action workflow, make sure that the required environment variables are propagated to subsequent jobs.
-NoInstallDo not install the package. Only download it. By default, the package is installed.
-NoPauseDo not wait for the user to press at end of execution. By default, execute apause instruction at the end of execution, which is useful when the script was run from Windows Explorer.

Note on executing PowerShell scripts from the Windows Explorer:The default action for double-click on a.ps1 file in Windows Explorer is toedit the script file using notepad. This is not very convenient. The registryfileWindowsPowerShell.reg changes this to execute the PowerShell scripton double-click. This is more consistent with.exe files which are executed.

Additionally, a fewset-*.ps1 scripts are provided to setup typicalconfigurations such as autologin or wallpaper. These scripts require optionsand, unlike theinstall-*.ps1 scripts, they must be run from a PowerShellwindow or script, not from the Windows Explorer.

About

Collection of scripts to install various tools on Windows

Topics

Resources

License

Stars

Watchers

Forks

Releases

No releases published

[8]ページ先頭

©2009-2025 Movatter.jp