Skip to content

About

No description, website, or topics provided.

Resources

Stars

0 stars

Watchers

0 watching

Forks

Latest commit

 

History

5 Commits

Folders and files

NameName
Last commit message
Last commit date
 
 
 
 

Repository files navigation

WinTuner GUI

A graphical interface for WinTuner — package Winget apps as Win32 apps and deploy them to Microsoft Intune, without writing a single command.

Features

  • WinTuner detection — detects whether the WinTuner module is installed at startup and offers to install it automatically
  • Winget search — search the Winget catalog directly from the GUI
  • Package creation — build Intune or Winget packages with one click
  • Deploy to Intune — deploy built packages to your tenant
  • Auto update — optionally enable AutoUpdate on a deployed app after deployment
  • Connection status — clear visual indicator (green/red) showing tenant connection state
  • Activity log — timestamped log of all actions and output

Requirements

Requirement Version
PowerShell 7.4 or higher
WinTuner module latest (Install-Module WinTuner)
Microsoft Intune Admin account with DeviceManagementApps permissions
OS Windows 10 / 11

Getting started

1. Install PowerShell 7.4+

Download from aka.ms/powershell if not already installed.

2. Download the script

git clone https://github.com/nickhoog/wintunergui.git

Or download wintuner_gui.ps1 directly.

3. Run the GUI

Right-click wintuner_gui.ps1 and choose Run with PowerShell, or:

pwsh -File wintuner_gui.ps1

4. Install WinTuner (first run)

On first launch the GUI checks whether the WinTuner module is present. If not, it will ask whether to install it automatically via Install-Module.

You can also install it manually:

Install-Module WinTuner -Scope CurrentUser

Workflow

1. Enter admin UPN  →  Import module  →  Connect tenant
2. Search for a Winget package  →  select it  →  Create package
3. Select the built package from the deploy list  →  Deploy

Security notes

  • No credentials are stored. Authentication is handled entirely by the WinTuner module and Azure/Intune device flows.
  • Admin access required. A valid Intune admin account (UPN) is needed to connect. The account must have DeviceManagementApps.ReadWrite.All permissions.
  • Local execution only. This script runs locally on your machine and communicates with the Intune Graph API through the WinTuner module. No data is sent to any third party.
  • Execution policy. You may need to allow script execution:
    Set-ExecutionPolicy -Scope CurrentUser -ExecutionPolicy RemoteSigned

Contributing

Pull requests are welcome. Please open an issue first for larger changes.

License

MIT

About

No description, website, or topics provided.

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages