You followed the install, setup said it finished - and now Picture Manager either is not there, opens and vanishes, or your photos keep opening in the Photos app anyway. These are three different problems wearing the same coat. This page separates the symptoms first, then gives each one its real fix, in the order worth trying.
A failed first launch after installing a 2010 tool on Windows 11 is common enough that it deserves its own checklist instead of panic. The good news: the causes are boring - a component that was never selected, a first-run setup that got interrupted, a stale shortcut, or simply Windows still preferring its own Photos app. None of them means your PC or your photos are damaged. Find your exact symptom below and take only its fix.
Four different symptoms, four different causes. Match your symptom to its row before changing anything - the fixes are not interchangeable.
If Start search finds nothing, the component was probably never installed - the most common reason is picking the wrong branch in the setup tree, or setting Picture Manager itself to Not Available by accident. Do not reinstall blindly. First check whether the program file exists: open C:\Program Files (x86)\Microsoft Office\Office14 in File Explorer and look for OIS.exe. If the folder or file is missing, run the SharePoint Designer 2010 setup again, choose Customize, and this time confirm Microsoft Office Picture Manager under Office Tools says Run from My Computer before installing.
The file is there, the icon does nothing. Work through these in order:
OIS.exe itself, not a shortcut - a dead shortcut is common after the setup moves things around. If it opens, right-click it and create a fresh shortcut.OIS.exe, Properties, Compatibility tab, tick Run this program in compatibility mode for Windows 7, Apply, and launch again. On most Windows 11 PCs this is not needed, but on some it settles the old program.This one is not a fault at all. Picture Manager is installed and healthy - Windows 11 simply still uses its own Photos app as the default for image files. Double-clicking any JPG will keep opening Photos until you change the default, which is a separate setting with its own guide on this site. Quick test that proves the tool works: open Picture Manager from Start first, then use its folder browser to open the same photo inside the program.
Messages claiming the program is not a valid application, or that setup cannot continue, usually mean the wrong installer file - a corrupted download, or media meant for a different setup. The honest fix is sourcing, not tweaking: delete the suspect installer, and get SharePoint Designer 2010 again only from Microsoft, or use an Office 2010 disc or ISO you already own. Installers of this age circulating on random sites are a known malware route, and no compatibility setting will make a tampered file safe.
If you have run the setup twice and Picture Manager still will not open, remove the half-state completely: uninstall SharePoint Designer 2010 from Settings, Apps, Installed apps, restart the PC, then install again with Customize and only Picture Manager selected. A clean second install fixes almost every leftover-registry case. And one thing you never need to worry about: none of this touches your photos. Picture Manager only reads image files - broken installs cannot damage the pictures themselves.
The video shows a clean install from download to first open - the fastest way to spot which step went differently on your PC.
▶️ Watch Full VideoProbably nothing is broken. Picture Manager only lists folders you add or browse to. Use File, Add Picture Shortcut, or browse through the folder pane to the folder holding your photos, and the thumbnails will appear.
That means the first-run setup never completed. Launch Picture Manager, let the configuration finish without closing it, then close and reopen. If it still repeats, repair the installation from the setup or reinstall cleanly with only Picture Manager selected.
It is an old Intel-era program. On regular x86 and x64 Windows 11 PCs it runs normally. On ARM-based Windows devices it would run only through emulation, which is not officially supported and may be slow or unstable.