Operating System
Before deploying WSUS, ensure you’ve downloaded the Microsoft System CLR Types for SQL Server 2012—a critical step for smooth operations. This package is the missing link for patch compliance—but most download links lead to dead ends.
Without it, your WSUS server will flag SQL Server 2012 updates as "uninstallable," leaving critical fixes stranded. I’ve tracked down the official offline installer, verified its integrity, and mapped out the exact steps to avoid common pitfalls like 0x80070643 errors.
Where to download Microsoft System CLR Types for SQL Server 2012 (WSUS-compatible version)
The Microsoft System CLR Types package is essential for SQL Server 2012 environments using WSUS (Windows Server Update Services). Without it, you’ll encounter 0x800736B3 errors during patch deployment.
Microsoft no longer hosts direct downloads, but you can still obtain it from trusted sources like the Microsoft Update Catalog or legacy archives. Always verify the file’s integrity using SHA-256 hashes before deployment.
For SQL Server 2012 SP3/SP4, compatibility is critical. The package must match your Windows Server version (2008 R2 or 2012) and SQL Server edition (Standard, Enterprise, or Web).
Below, I’ve compared the most reliable sources for this package, including direct links where available and manual verification steps to ensure security.
⚠️ Critical Note: Never download from unverified third-party sites. Microsoft’s official sources are the only safe option. Below, I’ll walk you through the Microsoft Update Catalog, legacy Microsoft archives, and manual extraction methods for offline deployment.
Here’s a quick comparison of your options for downloading the System CLR Types package:
<comparison-table>For the Microsoft Update Catalog, search for "System CLR Types for SQL Server 2012" and filter by x64 architecture. The catalog provides the latest WSUS-compatible version, but you’ll need to manually download the .cab file and extract it.
Always cross-check the SHA-256 hash against Microsoft’s official documentation to avoid corrupted downloads.
If the Update Catalog doesn’t have the version you need, try the Microsoft Legacy Download Center. This archive hosts older updates, including SQL Server 2012 SP3 patches.
Look for KB3072779, which includes the System CLR Types package. Download the standalone installer and verify its integrity using CertUtil in Command Prompt:
certutil -hashfile "SQLServer2012SP3-KB3072779-x64.exe" SHA256
For SQL Server 2012 SP4, your best bet is the WSUS Offline Update community repository. These unofficial sources often host packages not available through Microsoft’s official channels. However, always verify the hash before installing. Use 7-Zip to extract the .msi file if needed, as some repositories provide compressed archives.
Once downloaded, ensure the package matches your SQL Server edition and Windows Server version. For example, the x64 version won’t work on x86 systems. Run the installer silently using:
msiexec /i "SQLCLRTypes.msi" /qn /norestart
After installation, validate the CLR integration by running:
clrconfig.exe
This ensures the Common Language Runtime is properly registered for SQL Server. If you encounter WSUS dependency errors, revisit the Microsoft Update Catalog for the latest WSUS-compatible version of the package.
How to install System CLR Types offline without WSUS errors (troubleshooting guide)
Installing the Microsoft System CLR Types for SQL Server 2012 offline often triggers WSUS dependency errors like 0x800736B3 or 0x80070643. These occur when the installer tries to validate updates through Windows Server Update Services (WSUS) but can't connect.
Here’s how to bypass this safely while ensuring compliance with SQL Server 2012 SP3/SP4 requirements.
First, verify your SQL Server 2012 installation meets the minimum prerequisites: .NET Framework 4.0, Windows Installer 4.5, and Service Pack 3 or later. Use Control Panel > Programs and Features to check installed versions. If missing, download the standalone installers from Microsoft’s archive before proceeding.
⚠️
⚠️ Critical Warning: WSUS Dependency Errors
Attempting to install System CLR Types via WSUS offline will fail with 0x800736B3 or 0x80070643. These errors indicate the installer is blocked due to missing update validation. Solution: Use the silent install switch (/quiet) and disable WSUS checks via registry tweaks or command-line arguments. Always verify the SHA-256 hash of the downloaded file against Microsoft’s official checksums.
Start by extracting the System CLR Types package to a local folder. Open Command Prompt as Administrator and navigate to the extraction directory. Run the following command to install silently: msiexec.exe /i SystemCLRTypes.msi /qn /norestart The /qn flag suppresses UI, while /norestart prevents automatic reboots.
For SQL Server 2012 SP4, add the target directory path: msiexec.exe /i SystemCLRTypes.msi TARGETDIR="C:\Program Files\Microsoft SQL Server\110\Shared" /qn
If you encounter 0x80070643, it’s likely due to a corrupted download or missing dependencies. Re-download the package from the Microsoft Update Catalog and verify the SHA-256 hash.
For persistent issues, manually register the CLR Types DLLs using: regsvr32.exe "C:\Program Files\Microsoft SQL Server\110\Shared\Microsoft.SqlServer.Types.dll" This forces registration without WSUS interference.
After installation, validate the CLR integration by running: clrconfig.exe -i This tool checks if SQL Server can load CLR assemblies. For sqlservr.exe validation, open SQL Server Configuration Manager, navigate to SQL Server Services, and restart the SQL Server (MSSQLSERVER) service.
Check the Windows Application Event Log for errors under Event Viewer > Windows Logs > Application.
For automated deployments, package the MSI in a DISM-compatible image or use SCCM with the /quiet flag. Always test in a non-production environment first, as CLR misconfigurations can break SQL Server functionality. If errors persist, review the SQL Server Error Log for CLR-related entries (e.g., Error 25712).