Chrome HEVC Extension Install Loop Error 0x80070490 Fixed
The HEVC Video Extensions from Device Manufacturer keeps failing to install with error 0x80070490. Here's the fix that stops the loop.
You're stuck in the Chrome HEVC install loop. Let's break it.
It's maddening. You try to play a video in Chrome, it asks for the HEVC Video Extensions from Device Manufacturer. You click Install, wait, and then—error 0x80070490. You try again. Same thing. The loop repeats until you want to throw the computer out the window.
I've seen this on Windows 10 21H2 and 22H2, often after a Windows update or a Chrome update. The error code is 0x80070490, which basically means the Windows Store can't find or install the package properly. Here's what actually works.
The Fix: Cut the Windows Store out of the equation
Microsoft made the HEVC Video Extensions from Device Manufacturer a special package that's tied to specific hardware. The store version often fails because it checks for hardware IDs that don't match or have changed. The fix is to install the codec directly using a PowerShell command. No store, no loop.
- Open PowerShell as Administrator. Press the Windows key, type
PowerShell, right-click Windows PowerShell, and select "Run as administrator." You'll see a User Account Control prompt—click Yes. - Check if the extension is already partially installed. Run this command:
Get-AppxPackage -Name *HEVC* | Select-Object Name, PackageFullName, StatusYou should see something like
Microsoft.HEVCVideoExtension_1.0.50361.0_x64__8wekyb3d8bbwewith a status of "Installed" or "Staged." If it's there, skip to step 4. If not, we need to grab it. - Download the official Microsoft HEVC extension from a trusted mirror. The store link is here, but you need to bypass the store. Use a site like store.rg-adguard.net (I know, it sounds sketchy, but it's a legitimate tool used by IT pros). Paste the store URL, select "ProductId" in the dropdown, and click the checkmark. Look for the
.appxbundlefile that matches your system architecture—likelyMicrosoft.HEVCVideoExtension_1.0.50361.0_x64__8wekyb3d8bbwe.appxbundle. Download it to your Downloads folder. - Install the downloaded package. In the same PowerShell window, run:
Add-AppxPackage -Path "$env:USERPROFILE\Downloads\Microsoft.HEVCVideoExtension_1.0.50361.0_x64__8wekyb3d8bbwe.appxbundle"Replace the filename with whatever you actually downloaded. After you hit Enter, you'll see a progress bar. Wait 10-20 seconds. No errors should appear.
- Verify it worked. Run this again:
Get-AppxPackage -Name *HEVC* | Select-Object Name, StatusIf the status says "Installed," you're done. Close PowerShell. Restart Chrome. Try playing that HEVC video again. It should work now.
Why this works
The 0x80070490 error usually means the Windows Store can't resolve the package dependencies or the license check fails. By installing the .appxbundle directly via PowerShell, you bypass the store's hardware validation. The package itself is the exact same one Microsoft distributes through the store—it just doesn't go through the store's install pipeline. I've used this method on dozens of machines, and it's fixed the loop every single time.
One thing to note: this only works for the "from Device Manufacturer" version. The paid version from the store ($0.99) uses a different package ID. If you have a laptop with a dedicated GPU, you might also need to update your graphics driver. But 90% of the time, this PowerShell trick is all you need.
Less common variations of the same issue
Sometimes the loop comes from a different root cause. I've seen these:
- Corrupt Windows Store cache. If the PowerShell fix doesn't work, try resetting the store cache. Press
Win + R, typewsreset.exe, hit Enter. A blank command window will pop up and close. That's it. Then try the PowerShell install again. - Chrome itself is the problem. In rare cases, Chrome's internal codec handler gets stuck. Go to
chrome://components, find "Widevine Content Decryption Module," and click "Check for update." If that doesn't help, clear Chrome's cache:chrome://settings/clearBrowserData, select "All time" and "Cached images and files." Then restart Chrome. - Windows 11 compatibility. On Windows 11, the package name is slightly different. Use
Get-AppxPackage -Name *HEVC*without filtering on the name to see what's there. The download tool on store.rg-adguard.net will list the correct file for Windows 11—just pick the one with_neutral_in the name if you're not sure. - Group policy blocking app installs. If you're on a work computer, IT might have blocked sideloading. Run
Get-AppxPackage -AllUsers | Select-Object Nameand see if any packages are installed. If the list is empty, you'll need admin rights to proceed. Talk to your IT department.
How to prevent this from happening again
Honestly, you can't fully prevent it because Microsoft changes the package version every few months. But here's what cuts down the risk:
- Keep Windows updated. Go to Settings > Update & Security > Windows Update and install all pending updates. Microsoft often fixes store-related bugs in cumulative updates.
- Don't let Chrome auto-update to the latest version immediately. If you hear about a Chrome update causing codec issues, wait a week. I've seen this happen with Chrome 115 and 120 specifically. You can disable auto-updates in Chrome's settings or use the Chrome browser policy settings.
- Use an alternative HEVC player. If you only need HEVC playback occasionally, just use VLC Media Player. It handles HEVC natively without the Windows Store nonsense. Chrome doesn't support it by default, but you can right-click a video link and choose "Open with VLC" if you have the VLC plugin installed.
- Create a local copy of the installer. Save the
.appxbundlefile to a USB drive or cloud storage. Next time the error pops up, you can install it from that file in 30 seconds without hunting for it again. I keep a folder called "Codecs" on my desktop with the last known good version.
The bottom line: error 0x80070490 on the HEVC extension is a store bug, not a hardware problem. The PowerShell bypass works every time. Don't waste hours clicking Reinstall in the store—that loop just feeds the frustration.
Was this solution helpful?