AccountRight PC Edition 2026.6 MSI

Thank you for the additional info jbiskit​ , and sorry for the delayed response.
For the logs, can you please check: %localappdata%\SquirrelTemp

I have enabled private messaging for you if you want to share the logs to me via direct message.

Hi Mike,

I've checked the %localappdata% path for the SYSTEM account after a failed install attempt and there was no output of a SquirrelTemp folder.

For reference, this is the script I've used previously. When running as SYSTEM it fails, when running as a local administrator, it works fine. 

TLDR: Save the below as a .ps1 file, call it using `ScriptName.ps1 -version 2026.6`
It will download the latest version, and attempt to install it.

[CmdletBinding()]
param(
    # Version to install; this is passed through to URL and installer args.
    [Parameter(Mandatory = $true)]
    [string]$Version,

    # URL template must contain "{version}" placeholder.
    [string]$DownloadUrlTemplate = "https://download.myob.com/arl/MYOB_AccountRight_Setup_{version}.exe",

    # Extra installer arguments passed through as-is.
    [string[]]$InstallerArguments = @("-allusers")
)

$ErrorActionPreference = "Stop"

function Get-InstalledMyobVersion {
    param(
        [Parameter(Mandatory = $true)]
        [string]$TargetVersion
    )

    $uninstallPaths = @(
        "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*",
        "HKLM:\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\*"
    )

    $entries = foreach ($path in $uninstallPaths) {
        Get-ItemProperty -Path $path -ErrorAction SilentlyContinue
    }

    $expectedDisplayName = "MYOB AccountRight $TargetVersion"

    $myobEntry = $entries |
        Where-Object { $_.DisplayName -eq $expectedDisplayName } |
        Select-Object -First 1

    return $myobEntry.DisplayName
}


$installedVersion = Get-InstalledMyobVersion -TargetVersion $Version

if ($installedVersion) {
    Write-Output "MYOB version $Version is already installed. Nothing to do."
    exit 0
}

$downloadUrl = $DownloadUrlTemplate.Replace("{version}", $Version)
$tempInstaller = Join-Path 'c:\temp' ("MYOB_AccountRight_Setup_{0}.exe" -f $Version)

Write-Output "Download URL: $downloadUrl"
Write-Output "Temporary installer path: $tempInstaller"

if (-Not (Test-Path -Path $tempInstaller)) {
    Write-Output "Temporary installer not found at $tempInstaller. Will download."
    Write-Output "Downloading from $downloadUrl"
    try {
        Invoke-WebRequest -Uri $downloadUrl -OutFile $tempInstaller
    } catch {
        throw "Failed to download MYOB installer from $downloadUrl. $_"
    }
    if (-not (Test-Path -Path $tempInstaller)) {
        throw "Downloaded installer not found at $tempInstaller."
    }
} else {
    Write-Output "Temporary installer already exists at $tempInstaller. Will re-download."
}

Write-Output 'Swapping Install Mode...'
change user /install ##Tested to see if this would fix the SYSTEM issue on Terminal / Multi-user hosts. It doesn't

Write-Output "Running installer..."
$process = Start-Process -FilePath $tempInstaller -ArgumentList $InstallerArguments -Wait

if ($process.ExitCode -ne 0) {
    throw "MYOB installer failed with exit code $($process.ExitCode)."
}

$postInstallVersion = Get-InstalledMyobVersion -TargetVersion $Version
if ($postInstallVersion) {
    Write-Output "MYOB $Version installed successfully."
    Remove-Item -Path $tempInstaller -Force
} else {
    throw "Install completed but expected app name 'MYOB AccountRight $Version' was not detected."
}

Hi Mike_MYOB​ 

This is now working for me but not on an elevated CMD prompt - this install method failed on my in-house staff server as it has for my client servers.

However, what worked perfectly was an elevated Powershell process.

Download the MYOB_AccountRight_Setup_2026.6.exe to a directory on your desktop eg. MYOB_Installers

Open an elevated Powershell window.

Cd to the desktop directory holding the installer exe.

Then in Powershell type     .\MYOB_AccountRight_Setup_2026.6.exe -ALLUSERS  and it silently installs PC Edition into 

C:\Program Files (x86)\MYOB\MYOB AccountRight 2026.6 and deposits in public desktop a shortcut for 2026.6.

This process does not appear to work under an elevated Cmd.

The Doc

Why is no one asking why the heck myob just decided to end MSI support ? 

are they really trying to tell Australia we don't want enterprise customers anymore ?

I sit on a board as a CTO of company that runs myob though its companies - with AI now, migration is painless.. perhaps its time to look at a company that understands why we need MSI deployment 

Hi lwilden​ , the change to MSI was related to the underlying offline functionality which is no longer supported.
But we have updated AccountRight PC edition to support terminal server installation. 

The Doc and others have been sharing their experiences using the -allusers install in PC edition, it is working for some but not all and we are supporting customers where possible.
Other members like The_Doc​ are very experienced as well and are likely able to offer advice if you are encountering any errors 

Thanks for the reply, but I’m still not clear on the technical reasoning.

You said the change to drop MSI was related to offline functionality no longer being supported. That doesn’t really make sense from a technical standpoint.

Offline functionality is a product feature. MSI is just the installer packaging format. Removing a feature has no technical requirement to abandon the Windows Installer (MSI) format. Plenty of software drops features all the time and continues shipping as MSI.

MSI has clear advantages for multi-user and terminal server environments (standardised silent install, repair, proper uninstall, Group Policy/Intune deployment, etc.). Switching to EXE (even with -allusers) removes those advantages and forces a less reliable deployment method.

Can you explain the actual technical reason why supporting offline functionality required dropping MSI? Or is it simply that the new installer was built as EXE and MSI support was not prioritised?

Hi lwilden​ , thanks for waiting for my reply, I have been making sure I get the correct information here, please see below.

To clarify the reasoning behind the AccountRight installer changes:

MYOB needed to retire AccountRight’s offline mode because it relied on older technology that no longer met our standards for ongoing development, security and support.

We recognised that some customers, including customers using perpetual licences, might not be ready to move their company files online immediately. To make that transition easier, AccountRight’s installation options were separated to support the two different use cases:

• PC Edition for customers working with online company files.
• Server Edition and MSI as transitional options for customers who still needed to work with offline company files.

This distinction is particularly important for partners who support customers in both situations and need to deploy AccountRight in bulk/IT controlled enviroments.

• For customers working with offline files, the existing MSI installation process remained available as a temporary offline access path. This was a natural choice as most MSI installs used offline files already
• For customers working with online files, PC Edition was updated to support deployment in an IT-managed environment, including machine-level installation across multiple user profiles.

This gives partners a way to support both online and offline customer scenarios during the transition, while the recommended long-term path remains moving offline company files online and using PC Edition.

For the detailed installation guidance, see Deploying AccountRight in an IT-managed environment.