Thank you Jamie for letting us know. There were 4 different possible solutions shared on this thread. It's possible that different solutions might work for different PC's. Or a combination of solutions might work. (1- deleting .json files and denying user write permissions, 2- deleting olk.exe, 3- Python script for auto uninstall, 4- Installing dummy new outlook)
I realised that in my case, the "olk.exe" file also reappeared but the new outlook would still not launch.
But previously I had gone to username]\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\Migration\settings.json
and deleted all the .json files. Then I changed the security settings of the "Migration" folder and denied the current user (me) from write privileges. (Credit Jimmy W. post)
This did not work for me but deleting .olk.exe worked.
So possibly you need to do BOTH things. ie. delete .json files, deny write privileges of the Migration folder,
Then go to "C:\Program Files\WindowsApps\Microsoft.OutlookForWindows" and delete "olk.exe" and afterwards restore the owner to "Trusted Installer"
_________________________
If that doesn't work, I also have another suggestion you might try.
1- Close the new outlook.
2- Go to "C:\Program Files\WindowsApps\Microsoft.OutlookForWindows" and rename "olk.exe" to "old_olk.exe".
3 Create a new text document on your desktop and rename it to olk.exe
4- Copy the dummy olk.exe file into "C:\Program Files\WindowsApps\Microsoft.OutlookForWindows"
It might help.
Please let us know how you get on.
Kind regards
Chris