Confirm the file uses HEVC
Open the Video Codec Identifier. Check the container and video codec before purchasing, installing, or resetting anything. An iPhone .mov or camera .mp4 may contain HEVC, but the extension alone does not prove it.
For a full report, check profile and bit depth in MediaInfo. Also note the audio stream. A successful HEVC install will not repair a damaged container or unsupported audio codec.
Use official HEVC Video Extensions sources
Microsoft documents HEVC and HEIF support for its Photos workflows and publishes the extension through Microsoft Store. Availability and price can vary by Windows edition, region, device manufacturer, and licensing arrangements.
Use one of these paths:
- The Microsoft Store listing opened from the error or from Microsoft Support.
- Windows Update and the optional features supplied for your edition.
- Your PC manufacturer’s support application when the device includes licensed HEVC support.
Avoid unofficial “free codec” executables. Some search results bundle installers, adware, or obsolete components, and they can alter system-wide media behavior.
If the HEVC extension is already installed
Restart the application first. If it still fails, reboot Windows once, then test a small trusted HEVC sample and the original file separately.
Check Microsoft Store for an extension update. Update the affected app too. A Windows Photos problem and a browser playback problem use different stacks, so reproduce inside the exact program that raised the message.
Browser versus Windows application errors
| Situation | Most relevant path |
|---|---|
| Photos or another local Windows app requests the extension | System/application HEVC support |
| Chrome rejects a confirmed H.265 file | Chrome H265 diagnosis |
| VLC opens the same file | VLC's decoder path works; Windows support remains separate |
| A site reports a MIME-type error | Server response and browser support |
Check for a damaged or unusual file
If the official extension is present and a trusted sample works, compare the failed file. Look for zero-byte or suspiciously small files, interrupted cloud downloads, uncommon profiles, 10-bit video, multiple streams, and extension/container mismatches.
Try the official current version of VLC. A VLC success suggests that the file is decodable somewhere, though it cannot guarantee the Windows app will support the same profile.
When conversion makes more sense
Conversion is reasonable when you cannot install Store components, the receiving computer is locked down, or the file must work on older devices. Create an H.264 compatibility copy in MP4 with a supported audio track.
Transcoding can reduce quality and takes time. Preserve the source, compare a difficult frame, and verify audio before sharing or removing anything.
Retest the original application
Return to the exact app and file that failed. A different player succeeding is useful evidence, but it is not the finish line when Photos, Clipchamp, or another workflow is the actual requirement.
If the original issue was a browser, run the HEVC browser test instead. Record Windows version, application version, extension version where visible, file metadata, and the new result.