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(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
I have a vast number of Word documents that include links to jpg images in nearby folders.
When you click on it, normally (until today) the image opens up in Photoshop Elements 14, and I can edit and save it etc.
Today however when I click on any of these links I get a box asking me to look for an app in the Microsoft Store: "you'll need a new app to open this about link". I don’t want to go there as I already own Photoshop and if I click on Store it doesn’t seem to have a route back to my own programme files.
In Windows Explorer I can see that jpg files default open with Photoshop, as they always have done. This only seems to apply to hyperlinks. It continues to work for .tiff files, but not for .jpg or .jpeg files.
On Settings/App/Default apps, Photoshop is correctly set as the default software for images
Photoshop Elements Update says it is fully up to date. In settings/App etc. there is no Modify button, just uninstall which I don’t want to risk. I’ve tried to Repair Office which made no difference.
Allori.jpg
AlloriT.tif
[Moderator note: thread updated with operating system (Windows 10)]
A family of Microsoft word processing software products for creating web, email, and print documents.
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
I can now confirm that the fix has been done, and having reenabled auto updates on Office the hylerlinks are now working correctly.
Hi Neil, Luke here. I tested several recent Office update releases and I think I isolated the culprit that broke your Word doc links.
For the April 20 Version 2203 (Build 15028.20228), the test docs with JPG and PNG links work as expected when I click on the hyperlink. Note the first time I tried the JPG link, there appeared a security warning about dangerous file formats which you can ignore. Standard Microsoft procedure for JPGs.
For the subsequent release of April 26 Version 2204 (Build 15128.20178), the test docs with JPG and PNG links did not work and produced this error message when I click on the hyperlink: "No Program is registered to open this file." I checked my file associations in Windows settings and confirmed this is incorrect; my JPG and PNG file associations are still the same as ever.
To rollback to the last working version, I modified LiranLustig's suggestion with the version number. You can use this command line (following LiranLustig's instructions):
"C:\Program Files\Common Files\microsoft shared\ClickToRun\officec2rclient.exe" /update user updatetoversion=16.0.15028.20228
After a successful install is achieved, open Word again, go to File\Account, and make sure to Disable Updates so you don't receive the rogue update. No telling how long the wait for an update with the bug fix but there's little downside to sticking with the April 20 Version for a while.
Note that I have tested this only on Windows 11 and Office 365. It is expected to work on Windows 10 and Office 2016 but no guarantees. As LiranLustig notes, this is not a system restore so it is relatively low impact and should not affect other operations or programs.
So to recap, it appears the April 26 Version 2204 (Build 15128.20178) update introduced this bug.
Cheers,
Luke
This is not a system restore.
It will only take 10 minutes to try...
Fantastic: I'm most grateful. Presumably my starting point is first to go to Office 2016 Deployment tool etc....
I hope to have time to try this tomorrow - if Microsoft haven't already fixed it...
I'm happy to report that a rollback to updatetoversion=16.0.15028.20228 fixed this for me (that's version 2203, as at 20 April. (But of course we can't accept updates until Microsoft fix this properly.)