This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(262.40000000000003, 87%, 35%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ER%3C/text%3E%3C/svg%3E)
Recently we've noticed that the Photos app no longer works.
It is being blocked by our AppLocker policy, which shows a block for MicrosoftCorporationII.WinAppRuntime.Main.1.5 every time anyone tries to open Photos, including double-clicking on a .jpg .png etc. but also when trying to open Photos from the Start Menu.
I don't know what has changed - either Photos never used to need the WinAppRuntime, or AppLocker used to just allow it silently, and now doesn't.
I tried to add a rule to our AppLocker policy, but MicrosoftCorporationII.WinAppRuntime.Main.1.5 doesn't show as an installed app. I found a download for Microsoft.WindowsAppRuntime 1.5 MSIX (note slightly different name) but AppLocker won't let me add it saying:
Unable to Create Publisher Rule: A publisher rule cannot be created for this app package because it is a framework package.
Does anyone have any suggestions, or can please escalate to somebody inside Microsoft who can think about how to un-break Photos (and who knows what else) for anyone using AppLocker.
I managed to work around this by using a machine with an AppLocker policy that allowed all signed packaged apps. I was able to run Photos, and on first launch it installed both these apps:
MicrosoftCorporationII.WinAppRuntime.Main.1.5
MicrosoftCorporationII.WinAppRuntime.Singleton
From that machine I was then able to add them to the AppLocker policy that applies to the other machines.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(166.4, 97%, 26%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAD%3C/text%3E%3C/svg%3E)
Can you share your progress on this? I mean: did it work? Photos app is working? Having the same issue. Added the following for now:
<FilePublisherRule Id="7e0f481e-83d2-46b6-8f32-864db75db7f1" Name="MicrosoftCorporationII.WinAppRuntime.Main.1.5, from Microsoft Corp." Description="" UserOrGroupSid="S-1-1-0" Action="Allow"> <Conditions> <FilePublisherCondition PublisherName="CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US" ProductName="MicrosoftCorporationII.WinAppRuntime.Main.1.5" BinaryName="*"> <BinaryVersionRange LowSection="*" HighSection="*" /> </FilePublisherCondition> </Conditions> </FilePublisherRule>
Unfortunaltely it did not help: note that I am not getting any errors inside Applocke. I will be looking into Singleton thing today...
If it's the same thing I had, you'll see an event ID 8025 (error) in the Microsoft-Windows-AppLocker/Packaged app-Deployment log telling you that MicrosoftCorporationII.WinAppRuntime.Main.1.5 was prevented from running.
To fix that you need to create rule(s) in the Packaged app Rules section of AppLocker to allow those two packaged apps I mentioned.
After allowing both those two packaged apps, Photos is now working again.
Well, those two actually only seem to install - event 8023, I've yet to see a log event saying they've executed, which would be event 8020 in the Microsoft-Windows-AppLocker/Packaged app-Execution log - not seen that, just an 8020 for MICROSOFT.WINDOWS.PHOTOS.