This message was deleted.
# microsoft-365
s
This message was deleted.
a
There’s a GP policy to disable the “Try new Outlook” button in Outlook. Do you have that enabled as well?
v
GP to hide that button works. [HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Outlook\Options\General] “HideNewOutlookToggle”=dword:00000001 but whether you hide it or not. “Outlook new” is installed on the Windows 11 box a couple of mins after the logon. So you have 2 Outlook apps now.
Microsoft still looking into this one. I tried .bat file below and that worked for “Outlook New” uninstall. == POWERSHELL -ExecutionPolicy Bypass -Command “Get-AppxPackage | Where-Object {$_.Name -Like ‘*OutlookForWindows*‘} | Remove-AppxPackage” == So that will work as plan B. Looks like it is installed from the Windows Store as it is not listed as installed before 1st user logon. So all attempts to remove it fail as it is just not there during the build. It leaves a gap and opportunity for Outlook New to be installed. One of the scenarios – user logs on but there is nothing to remove, then app get installed during user session. See timeline below starting with VM build and finishing with “Outlook new” installed. 10:13 PM 23.01.24 VM built 9:00 AM 24.01.24 running powershell queries on VM remotely “Microsoft.OutlookForWindows” not listed (Get-AppxProvisionedPackage -online) 9:38 AM 24.01.24 User logs on VM, “Outlook new” not installed. (not available in start menu, not listed via get-appxprovisionedpackage – online) 10:19 AM 24.01.24 Outlook new installed
t
We have an automation script which removes the new outlook package using the uninstall string you call out