The fastest path

from script to deployed app.

Windows PowerShell IDE that compiles your whole deployment folder into one EXE, or a ready Intune app, with a right-click. No installer builder, no self-extracting archive, and no manual IntuneWinAppUtil run: PSConsole downloads it and builds the .intunewin for you.

Runs on any Windows with .NET Framework 4.8, nothing extra to install. One EXE, and it updates itself from GitHub.

The PSConsole window PSConsole with Install-DotNet.ps1 open in the editor, the workspace explorer on the left and a terminal tab connected to LAB-PC-0421 at the bottom, where the same script has just installed the .NET runtime. File Run Zoom Project Help PSConsole - Install-DotNet.ps1 Open New File Save Format Run (F5) Stop Theme: PowerShell Auto Session: ON EXPLORER v Deploy Install-DotNet.ps1 Uninstall.ps1 Detection.ps1 v Intune DotNet10.intunewin logo.png > Modules > Reports Files Notes Vault Graph Git Cloud Database Install-DotNet.ps1 Detection.ps1 1 function Install-DotNet { 2 [CmdletBinding()] 3 param( 4 [ValidateSet('8', '9', '10')] 5 [string] $Version = '10', 6 [switch] $Force 7 ) 8 # Resolve the newest patch for the requested channel 9 $index = Invoke-RestMethod -Uri $ReleaseIndex 10 $release = $index.'releases-index' | 11 Where-Object 'channel-version' -eq "$Version.0" 12 Write-Log "Resolved release : $($release.'latest-release')" 13 } PSConsole LAB-PC-0421 + Split Terminal [Connected LAB-PC-0421] PS> .\Install-DotNet.ps1 -Version 10 -Force [INFO] Resolved release : 10.0.14 (lts, active) [INFO] Downloading x64 installer : 54 MB [INFO] Installer exit code : 0 [INFO] All required components installed and verified [Connected LAB-PC-0421] PS> Ready D:\Deploy\Install-DotNet.ps1

More than an editor. Everything around the script.

Packaging, remote sessions, secrets, notes and test VMs, each one tab away from your code.

  • Edit-Script

    Write PowerShell, C# and Razor with highlighting driven by the real parsers.

    PSScriptAnalyzer marks problems while you type and formats on save. Tab completion comes from a live runspace, and every extra terminal tab gets its own, so a long job never blocks the next one.

    Editor and terminals ->
  • New-Package

    Right-click a folder. Get one EXE.

    Create EXE embeds every file in the folder, runs the entry script on the target and cleans up after itself. Create IntuneApp uploads straight to your tenant, and EXEs can be Authenticode-signed with a timestamp so endpoints that trust your certificate run them without a SmartScreen warning. Open any .intunewin to read its metadata or extract the original files.

    Intune packaging ->
  • Enter-Remote

    Open a terminal on the computer you are supporting.

    Connect directly on your network, or through the cloud relay where both sides connect outbound, so NAT, home networks and closed inbound ports stop mattering.

    Remote support ->
  • PS-Vault

    Credentials your scripts can read without hardcoding them.

    Logins, app registration secrets, API keys and certificates, encrypted with an optional master password. Scripts read them with Get-PSCSecret, any session with Get-Secret -Vault PSConsole. Imports from Edge, Chrome, 1Password and Bitwarden.

    Vault ->
  • PS-Notes

    Notes, tasks and reminders that live beside your code.

    Always saved and encrypted, with unlimited nesting, tags, ticket numbers, links and reminders. Keep the change log, the to-do list and the gotchas next to the script they belong to, and sync them through your own database when you want them on another PC.

    Notes ->
  • Start-OracleVM

    Test the package on a VM without leaving the editor.

    When Oracle VirtualBox is installed, PSConsole finds it and adds a VMs panel: start and stop machines, take and restore snapshots, forward ports, and create VMs with an unattended Windows install. Without VirtualBox the panel stays out of the way.

    VirtualBox ->

Inside PSConsole.

Pick an area. Optional parts appear in the explorer only once they are installed or configured.

All features in detail

Terminals that work like VS Code's.

Open up to eight extra terminals, each with its own PowerShell session, and split any two side by side.

  • A long build in one terminal never blocks the next command in another.
  • Type straight into the terminal, or use the docked command box.
  • Tagged output from Blob, Graph, EXE and other tools collects in channels with unread badges.
Read the details on editor and terminals
Split terminals and output channels Two terminals side by side. The left one restarted the Print Spooler service; the right one, marked as running, builds and signs a package. The Output menu is open and shows unread messages in the Blob and EXE channels. PSConsole PS 2 PS 3 + Unsplit Terminal 3 PS> Get-Service Spooler | Restart-Service -PassThru Status Name DisplayName ------ ---- ----------- Running Spooler Print Spooler PS> Get-PSCSecret 'Intune App' | Connect-MgGraph -NoWelcome PS> PS 2> .\Build-Package.ps1 -Sign [EXE] Compiling DotNet10.exe [EXE] Signing, timestamp: DigiCert [EXE] Creating DotNet10.intunewin WARNING: logo.png is larger than 1 MB [EXE] Packaged 14 files (54.2 MB) Running... Terminal All Channels Blob 2 EXE 1 Graph Mark All as Read Clear

The rest of the admin day, in tabs.

Tools that usually live in five other windows. More detail

Microsoft Graph
Intune reports for detected apps, Autopilot group tags, stale devices and Windows builds, plus ad-hoc queries. Export to CSV.
Azure Files and Blob
Browse a share or container through a SAS link, upload whole folders and download with progress.
Import Module
Right-click a folder to save a module from the PowerShell Gallery into it, with its required modules. How it works
Git
Status, diffs and commit and push for the folder you have open.
Compare and spreadsheets
Two files side by side, and .xlsx or CSV results opened in a sortable grid.
Local AI assistant
Chat and script analysis through Ollama on your own machine. Nothing leaves it.
Run as and elevation
Restart the window as administrator, or run a command under another account.

Watch it work.

All videos

PSConsole in ten minutes

A tour of the editor, terminals, packaging and the remote terminal, from first launch to a script running on another PC.

Getting started

Run PowerShell on a remote PC through the relay

Enroll an agent, connect from PSConsole, answer prompts, stop a running script and upload files with Remote Files.

Remote support

From script to Intune app

Build a signed EXE, create the .intunewin and upload it to Intune with Create IntuneApp.

Packaging

Get PSConsole.

Download the EXE and run it. Optional parts install from inside the app when you first need them.

Windows
Any Windows with .NET Framework 4.8
Runtime
.NET Framework 4.8, already part of Windows
Install
None. Run PSConsole.exe; updates arrive from GitHub releases.
Installed on demand
PSScriptAnalyzer, the Roslyn C# engine and the MySQL connector
Remote support
RemoteService on each target computer, set up with its Install.ps1
Something went wrong on this page. Reload

Rejoining the server...

Rejoin failed... trying again in seconds.

Failed to rejoin.
Please retry or reload the page.

The session has been paused by the server.

Failed to resume the session.
Please retry or reload the page.