How do you remove OneDrive Photos

Before removing anything, confirm whether this is a separate Windows package or a feature delivered inside the OneDrive sync client. A name containing “Photos” does not by itself prove that it is an independently installed OneDrive application, and removing the wrong package could remove the built-in Windows Photos app instead.

Run the following on one affected VDI image first:

Get-AppxPackage -AllUsers | Where-Object { $_.Name -match 'OneDrive|Photos' } | Select-Object Name, PackageFullName, InstallLocation

If the item does not appear as a separate AppX package and has no entry under Settings > Apps > Installed apps, it is probably part of the OneDrive client. In that case, there is no supported way to remove only that feature; removing OneDrive folders or using DISM blindly is likely to damage the sync client.

For a non-persistent VDI deployment, the immediate control should be the golden image and the OneDrive update policy. Check the OneDrive sync app update ring in Intune or the OneDrive administrative templates, and make sure it is set to the organization’s approved production or enterprise ring, not an Insider or preview ring. Test future OneDrive updates on a separate image before releasing them to the production pool.

If the command identifies a distinct package, record its exact PackageFullName, publisher, version, and install location before creating a removal or AppLocker/WDAC rule. Test removal and blocking on a disposable VDI image first, then apply the approved change to the golden image. Do not use a broad rule that blocks every Microsoft Photos or OneDrive package, because that can also break OneDrive sign-in or normal Windows Photos functionality.

The package name, version, deployment time, and OneDrive client version are also the information Microsoft support will need to determine whether this was a OneDrive feature rollout, a Store package, or an unintended preview deployment.