After the upgrade of 70 computers from Windows 10 1607 to Windows 10 1709 discussed in the previous post people started complaining about a lack of toast notifications coming from Outlook 2016.
And indeed. When checking the Settings app under "System -> Notifications & Actions" there were entries for all kinds of applications but no trace of Outlook 2016 anywhere. And checking a Windows 10 1607 machine showed that it had been there before the upgrade. So something broke with the upgrade to 1709, again ...
Searching for the issue on the internet quickly brought me across this article. The issue described in the article sounded exactly like what we were seeing. Even though I knew that we did not use the GPO mentioned in the article I still made sure that the registry key was indeed not set.
The Office 2016 installation we use is modified to create the various shortcuts in a subfolder of the start menu called "Microsoft Office 2016" rather than placing all shortcuts in the root of the start menu. The article mentioned that the cause of the missing toast notifications could also be that the shortcut for Outlook 2016 is missing from "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\" so I went ahead and copied the shortcut from "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Microsoft Office 2016" to the aforementioned directory. But no luck. Toast notifications were still not working.
So with the shortcut in the supposedly correct place I went ahead and did a full office repair. But even after that toast notifications were still not working.
So I went ahead and modified the Office installation to create the Outlook shortcut in the correct folder (in addition to in the "Microsoft Office 2016" subfolder) and reinstalled Office 2016 after first purging it from a test machine. But yet again no luck. No toast notifications.
Then I went ahead and wiped the whole "updates" folder of the Office 2016 installation source folder including the .msp-file containing all the modifications and installed a completely unmodified Office 2016 on a test machine and ... toast notifications are working. I did not even have to restart Outlook. Or do a repair installation. It just started working instantly. Outlook 2016 even shows up in the settings app under "System -> Notifications & Actions" again.
I double checked the paths of the Outlook 2016 shortcuts but they were the same as previously tested with the modified Office installation.
I then created a GPO that will push the Outlook 2016 shortcut from the non-modified installation to all Windows 10 clients with Office 2016 installed. That should take care of the missing toast notifications.
But this still does not explain why the shortcut from a non-modified installation works while the shortcut from a modified installation does not.
So I copied both shortcuts to a directory and looked at them with the following script:
function
Get-ShortcutsInfo {
$Shortcuts
= Get-ChildItem
-Recurse "C:\test"
-Include *.lnk
$Shell
= New-Object
-ComObject WScript.Shell
foreach
($Shortcut in
$Shortcuts) {
$Properties
= @{
ShortcutName = $Shortcut.Name;
ShortcutSize = $Shortcut.Length;
ShortcutFull = $Shortcut.FullName;
ShortcutDate = $Shortcut.LastWriteTime;
ShortcutPath = $shortcut.DirectoryName
Target =
$Shell.CreateShortcut($Shortcut).targetpath
}
New-Object
PSObject -Property
$Properties
}
[Runtime.InteropServices.Marshal]::ReleaseComObject($Shell)
| Out-Null
}
Get-ShortcutsInfo | Out-GridView
The output did not disappoint. There was a difference in the shortcuts' target, as expected:
Both files exist in the paths shown. But apparently a shortcut to "C:\WINDOWS\Installer\{90160000-0011-0000-0000-0000000FF1CE}\Icon.A6B0014D.69D6.46E4.B6EE.BD4A5C12E26F.exe" will not work while a shortcut to "C:\WINDOWS\Installer\{90160000-0011-0000-0000-0000000FF1CE}\outicon.exe" will make toast notifications for Outlook 2016 under Windows 10 1709 work again.
The wrong shortcut was created by creating a modified Office 2016 installation using "setup.exe /admin" to create a .msp-file that was placed in the "updates" folder of the installation source. And "Outlook 2016" was selected from the dropdown in the modification tool. The target path was not entered manually. So the fault clearly lies with Microsoft messing something up, again.
Why exactly this is breaking or why exactly the default shortcut of an unmodified Office 2016 installation works, I have no idea.
If you know why, please leave a comment.
[1] https://www.reddit.com/r/sysadmin/comments/7smk7g/office_2016_toast_notifications_after_upgrading/
[2] https://twitter.com/BeingSysAdmin/status/956153637096579072
[3] https://outlook.uservoice.com/forums/322590-outlook-2016-for-windows/suggestions/32794093-desktop-notifications-banner-or-toast-notificatio
Hello,
ReplyDeleteFascinating work with that outlook. I wanted to ask if you could send me your working outlook.exe file? I have tried replicating but no dice and no toast notifications are driving me insane. I'd be really grateful.
Sending you my outlook.exe would not help you. Even sending you my shortcut file would only help you if you had the same exact version of Office 2016 as me. Already tested that with someone else.
DeleteStill can't get this fixed. Does the above suggest that you need to install a 'vanilla' Office install (albeit from the 'admin' install on-premise), and then copy the Start Menu shortcuts back over the top of the problematic machine?
ReplyDeleteYes, you basically need a vanilla installation of Office. Basically don't have anything in the "updates" folder, install it on some machine, copy the shortcut file from the startmenu folder to a safe location and then remove the Office installation again.
DeleteAfter that you can deploy your Office installation like you usually do it and then overwrite the startmenu shortcut with the one you created earlier.
That should do the trick.
Hi, i cannot seem to get this to work :( need help here. Tryed a vanilla installation but still got the same shortcut and no notifications.
ReplyDeleteThe other big question is: Why the fuck hasnt microsoft done anything about this? Its nearly half a year since the bug introduced! and its on an UI Level which users will recognize!
Hi, Nice post and solution but it's not working for me.
ReplyDeleteI have 2 questions:
1. What if we have "C:\WINDOWS\Installer\{90160000-0011-0000-0000-0000000FF1CE}\outicon.exe" and still no joy;
2. Does it matter if we use Ivanti Workspace Manager? Don't think so since the shortcuts are the same;
Thanks Timotatty
Did you figure this out?
DeleteI have the same problem running Ivanti Workspace Manager v.10.2.500.1
C:\WINDOWS\Installer\{90160000-0011-0000-0000-0000000FF1CE}\outicon.exe is there but no toast notification.
Tried a clean install of Office and still the same issue
This is not really a solution, but as a temporary workaround while I'm figuring out how to get my toaster notifications back I did the following:
ReplyDelete- Open the Windows 10 "Mail" app (Hit Windows button and type "Mail")
- Enter login details for an Outlook or Exchange/Office 365 account
- Click the cog icon to access the settings menu, and make sure notifications for incoming mail is turned on.
Now, I at least get notified in a noticeable manner when I receive emails. I can't click the notification itself, unless I want the "Mail" app to open up.
I know this isn't a solution, but at least I have some kind of toaster notification for the time being.
Hello.
ReplyDeleteThanks for your contribution on this. This has been driving me crazy for weeks!
I have Windows 10 ver 1803 and Office 2013
Please, I have some doubts about the explanation.
1)... wipe out the updates from Office's source installation folder. In Program Files, which folders do I have to delete?
2) I need to install a new Microsoft Office in a different computer and then copy these folders into the PC with faulty toast notifications?
Waiting for your reply.
Thanks
No. You don't have to delete anything in "Program Files". If you want to obtain a functional Outlook shortcut you have to remove all files from the "updates" folder located in your source folder. After installing Office with no included update and especially no MSP file (admin installation) you can then copy the shortcut to Outlook from the allusers startmenu and deploy it to all clients with broken toast notifications using a group policy.
DeleteAgain: All you have to do is install Office without any modifications on one machine and then copy the Outlook shortcut from that machine to all other machines.
Though, make sure all machines are running the exact same version of Office (language and edition) otherwise this will not work.
Ok. I get it now.
DeleteAfter install this "Vanilla" Office, what options in the Group Policy should I have to set to put the new shortcut in every workstation with this issue?
Thanks in advance.
Just copy the correct shortcut file onto your NETLOGON (or any other) server share and then configure a GPP to copy the file from there to the correct startmenu location.
DeleteI was able to get mine to work by the following steps.
ReplyDeleteOpen my already customized .msp file (setup.exe /admin) and added another entry for Outlook 2016.
Target: [Outlook 2016]
Location: [ProgramMenuFolder]
Name: Outlook 2016.
I uninstalled office and reinstalled using the new MSP file. After a restart I ensured the outlook shortcut icon now shows up under C:\ProgramData\Microsoft\Windows\Start Menu\Programs. Once this was confirmed i verified outlook now shows under Notifications and Actions, opened outlook and verified i get the notification banner when a new email comes in.