Martin Wiethan

Update: There actually are leftovers now. The theme and chocolatey settings are "saved" as a file under %localappdata%/winutil It's still to be evaluated where and how we want to store...

/close

nothing to do here anymore /close

I've taken a look at this and this is quite difficult to implement. Seeing that @MyDrift-user is working on a *huge* redesign of the install tab at the moment that...

Seems to be a bit more complicated than anticipated. https://github.com/PowerShell/PowerShell/issues/12872 An idea to try to find out how the implementation differs from win10 to win11 would probably be a quite...

The chocolatey method is already included in install-winutilchoco.ps1 and _should_ run automatically of the direct approach fails. The chocolatey way in the past also produced some errors for me.

@og-mrk please keep in mind, that the pre-release script also used different tags (with the prefix pre-) this had a simple reason. If Chris would create a full release in...

> I like having these job separated. I don't want to have anything with the Compile and most time I will use the pre-release and change it to a full...

Could you rename the function and the file Do-preprossing to something following the function naming convention from Microsoft like Start-Preprocessing or Invoke-Preprocessing https://learn.microsoft.com/en-us/powershell/scripting/learn/ps101/09-functions?view=powershell-7.4 Seeing as there are not really any...

@Ed-Bryce nice workaround. @ChrisTitusTech @MyDrift-user How do we want to handle this kind of "Cross Repository Issue" in the future? This seems to be an issue with the setup script...