A family of Microsoft relational database management and analysis systems for e-commerce, line-of-business, and data warehousing solutions.
The error indicates that the SQL Server 2025 Express setup media being invoked by WinGet does not match the OS language, and the media does not contain the English-language setup files required for installation on the current Windows installation.
To resolve the problem, use these supported approaches from the SQL Server setup guidance:
- Reacquire the installation media
- Download the SQL Server 2025 Express image again from the original Microsoft location instead of relying only on the WinGet invocation.
- After downloading, run the setup program directly from the local image (ISO/EXE) rather than from a possibly corrupted or mismatched package.
- Install from local media instead of network/indirect source
- If the current installation is effectively being run over the network (or via a package manager that pulls from the network), copy or download the full SQL Server Express media to a local drive and run
setup.exefrom there.
- If the current installation is effectively being run over the network (or via a package manager that pulls from the network), copy or download the full SQL Server Express media to a local drive and run
- Ensure correct language support
- If using a localized version of Windows and the SQL Server media does not match that language, use media that matches the OS language, or use media that explicitly contains the English-language installation files and specify English where supported.
- For localized SQL Server versions, adjust OS regional settings to support the localized SQL Server language as documented in the SQL Server language support guidance. Installations of different language versions of SQL Server instances on the same computer are not supported.
- If the issue persists
- Check the SQL Server setup logs already indicated in the message:
C:\Program Files\Microsoft SQL Server\170\Setup Bootstrap\Log\20260226_155233 - If re-downloading and running from local, language-appropriate media does not resolve the issue, treat it as a different installation problem and follow the general SQL Server installation and repair guidance.
- Check the SQL Server setup logs already indicated in the message:
For more advanced scenarios (unattended or scripted installs), use the documented command-line parameters such as /ACTION, /ENU, and /IACCEPTSQLSERVERLICENSETERMS when invoking setup.exe directly, ensuring that the media and OS language combination is supported.
References: