How to control display of Version History on Myriad startup using the Windows Registry (v6.8.1 and later)

⚠️ Important Notes Before Proceeding

Editing the Windows Registry can have serious consequences if done incorrectly. Always:

• Back up your registry before making any changes.

• Ensure changes are performed by a qualified IT administrator or support professional.

• Use appropriate tools such as Group Policy if deploying settings across multiple machines.

Registry Key Overview

The setting is controlled via a registry value located at:

HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\BroadcastRadio\Profiles\(Shared)\Myriad v6

Value Name:

ShowVersionHistoryOnStartup

Value Type:

DWORD (32-bit)

Behaviour by Value:

Example Registry File

You can create a .reg file using the following text to disable the version history popup (i.e. set to 0):

Windows Registry Editor Version 5.00 
[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\BroadcastRadio\Profiles\(Shared)\Myriad v6] "ShowVersionHistoryOnStartup"=dword:00000000

To apply:

1. Save the text above as a .reg file (e.g., DisableMyriadVersionHistory.reg) or you can download it from the attached file.

2. Double-click the file on the target machine, or

3. Use a deployment method such as Group Policy, PowerShell, or System Center Configuration Manager (SCCM).

Group Policy Deployment (Advanced)

For domain-joined environments, this registry setting can be deployed via Group Policy Preferences:

1. Open the Group Policy Management Editor.

2. Navigate to:

   Computer Configuration → Preferences → Windows Settings → Registry
   

3. Right-click and select New → Registry Item.

4. Configure the following:

   • Action: Update

   • Hive: HKEY_LOCAL_MACHINE

   • Key Path: SOFTWARE\WOW6432Node\BroadcastRadio\Profiles\(Shared)\Myriad v6

   • Value name: ShowVersionHistoryOnStartup

   • Value type: REG_DWORD

   • Value data: 0 (or as required)

This approach ensures consistent application across multiple endpoints.

Summary

This registry setting gives administrators fine control over the visibility of the Myriad version history on startup. It is especially useful in managed environments where a consistent user experience is important or when avoiding unnecessary user prompts after application updates.

As always, we recommend testing in a controlled environment before applying changes widely.