xstefen/winutil
1
0
Fork 0
mirror of https://github.com/ChrisTitusTech/winutil.git synced 2025-01-15 17:30:37 -06:00
Code Issues Packages Projects Releases Wiki Activity

updated irm to iwr for the progress and

Browse Source 
updated one-liner with scoped execution
This commit is contained in:
psyirius 2024-08-21 02:14:40 -07:00
parent 51dd5ee125
commit d73b237550
3 changed files with 7 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
README.md
View File

@ -23,15 +23,15 @@ Winutil must be run in Admin mode because it performs system-wide tweaks. To ach
### Launch Command
#### Stable Branch (Recommended)
#### Stable Release (Recommended)
```ps1
irm "https://christitus.com/win" | iex
iex "& { $(iwr 'https://christitus.com/win') }"
```
#### Dev Branch
```ps1
irm "https://christitus.com/windev" | iex
iex "& { $(iwr 'https://christitus.com/win') } -preview"
```
If you have Issues, refer to [Known Issues](https://christitustech.github.io/winutil/KnownIssues/)

2
scripts/launcher.ps1
View File

@ -20,12 +20,14 @@
.EXAMPLE
Launch the latest release of winutil. (one-liner)
Invoke-Expression "& { $(Invoke-RestMethod 'https://christitus.com/win') }"
iex "& { $(iwr 'https://christitus.com/win') }"
.EXAMPLE
Launch the latest preview release of winutil.
.\launcher.ps1 -preview
.EXAMPLE
Launch the latest preview release of winutil. (one-liner)
Invoke-Expression "& { $(Invoke-RestMethod 'https://christitus.com/win') } -preview"
iex "& { $(iwr 'https://christitus.com/win') } -preview"
#>
[CmdletBinding()]
param(

4
windev.ps1
View File

@ -1,13 +1,13 @@
<#
.SYNOPSIS
This Script is used as a target for the https://christitus.com/win/dev alias.
This Script is used as a target for the https://christitus.com/win/preview alias.
It queries the latest winget release (no matter if Pre-Release, Draft or Full Release) and invokes It
.DESCRIPTION
This Script provides a simple way to always start the bleeding edge release even if it's not yet a full release.
This function should be run with administrative privileges.
Because this way of recursively invoking scripts via Invoke-Expression it might very well happen that AV Programs flag this because it's a common way of mulitstage exploits to run
.EXAMPLE
irm https://christitus.com/win/dev | iex
iex "& { $(iwr 'https://christitus.com/win/preview') }"
OR
Run in Admin Powershell > ./windev.ps1
#>