# Pretend IE is installed for legacy apps New-Item -Path "HKLM:\SOFTWARE\Microsoft\Internet Explorer" -Force Set-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Internet Explorer" -Name "Version" -Value "9.11.10240.0" -Type String Set-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Internet Explorer" -Name "svcVersion" -Value "11.0.1000" -Type String This is a hack. It works for 50% of tools. The other 50% actually try to load ieproxy.dll and will crash anyway. Fix 3: The Official Microsoft Fix (DISM) For Windows Server 2016/2019/2022, you can add the IE feature via DISM:
Unfortunately, "safe" in 2015 became "dangerous" in 2024. The error "uv requires Internet Explorer version 8, 9, 10 or 11 to run" is not a bug; it is a fossil. It is a reminder that Windows is a layered cake of decades of backwards compatibility. uv requires internet explorer version 8 9 10 or 11 to run
Until then, IE may be dead on the desktop, but it lives on forever in your CI/CD pipeline. Have you seen this error in a strange place? Did the registry hack work for you? Let me know in the comments below. # Pretend IE is installed for legacy apps
When Microsoft built many of its system management tools between 2009 and 2015, they didn't build a custom rendering engine. Instead, they used the —a wrapper around the installed version of Internet Explorer. Fix 3: The Official Microsoft Fix (DISM) For
Open PowerShell as Administrator and run:
If you are a developer working with legacy enterprise software, Microsoft tools, or specific CI/CD pipelines, you might have stumbled upon an error message that feels like a slap in the face from the past: "uv requires Internet Explorer version 8, 9, 10 or 11 to run." Your first reaction is likely confusion. You might be running Windows 11, Edge Chromium, or even a headless Linux server. Why on earth does a modern tool require a browser that Microsoft officially retired in June 2022?