I wanted to disable the prompt and button for new Outlook. I found this guide and wrote a few lines of PowerShell to automate it and wanted to share.
# Source https://edi.wang/post/2025/1/20/how-to-stop-automatically-switching-to-new-outlook
$path='HKCU:\Software\Microsoft\Office\16.0\Outlook'
# Remove and create to ensure correct data type
Remove-ItemProperty -Path "$path\Options\General" -Name 'NewOutlookAutoMigrationStage' -ErrorAction SilentlyContinue
New-ItemProperty -Path "$path\Options\General" -Name 'NewOutlookAutoMigrationStage' -Type DWord -Value 1
Remove-ItemProperty -Path "$path\Options\General" -Name 'NewOutlookAutoMigrationStage'
Remove-ItemProperty -Path "$path\Options\General" -Name 'NewOutlookAutoMigrationType'
Remove-Item -Path "$path\NewOutlook"
# Remove and create to ensure correct data type
Remove-ItemProperty -Path "$path\Preferences" -Name 'UseNewOutlook' -ErrorAction SilentlyContinue
New-ItemProperty -Path "$path\Preferences" -Name 'UseNewOutlook' -Type DWord -Value 0
Remove-ItemProperty -Path "$path\Preferences" -Name 'NewOutlookRenudgeStartDate'
Remove-ItemProperty -Path "$path\Preferences" -Name 'NewOutlookRenudgeStartDate'
You must log in or # to comment.
Good stuff!
Nice. So this is all user-based though?
You could do a machine deployment with something like PSADT but it’s probably overcooking it (I don’t really understand when/how it switches from old to new)
So this is all user-based though?
I would assume so since it is
HKEY_CURRENT_USER. I took a glance atHKEY_LOCAL_MACHINEand the same keys were not there. Perhaps this would had to be run for each user at first login.I am the only user of my work computer and it is not even managed, so PSADT would indeed be overkill. :-)
Does this work different than the policy key? As far as I know the keys under software\policies are used by both group policy and intune, and honored by windows home editions so I’d expect they’d work more reliably than an outlook config setting.
