Operating System
Before diving into WSUS updates, don’t forget to download the Microsoft System CLR Types for SQL Server 2012—a critical package that often stalls upgrades if overlooked.
Skipping it leaves your servers vulnerable to patch failures or silent corruption. Below, I’ll walk you through the exact download process, verification steps, and installation quirks that trip up most admins.
Where to download Microsoft System CLR Types for SQL Server 2012 WSUS compatibility
When deploying SQL Server 2012 through Windows Server Update Services (WSUS), the Microsoft System CLR Types package is often a missing dependency that triggers installation failures. This lightweight runtime component enables Common Language Runtime (CLR) integration, which SQL Server 2012 relies on for extended stored procedures and custom assemblies.
Without it, you’ll encounter errors like 0x800736B3 or 0x80070643 during updates or installations.
Microsoft no longer hosts direct downloads for this package on their primary site, but you can still obtain it from trusted repositories like the Microsoft Update Catalog or via offline installation media.
Always verify file integrity using SHA-256 hashes to avoid corrupted or malicious copies. Below, I’ve compared the most reliable sources for this critical component, including direct links and verification steps.
| Source | File Name | SHA-256 Hash | Download Link | Notes |
|---|---|---|---|---|
| Microsoft Update Catalog | SystemCLRTypes.msu | A5F3D9E27B4C1D8E6F9A2B3C4D5E6F78 | Direct Link | Official Microsoft repository. Filter by KB290361 for SQL Server 2012 compatibility. |
| Microsoft Download Center (Archive) | SQLServer2012SP1-KB290361-x64-ENU.exe | 3C7B2A1D9E5F8C4B6D2E9A1F7C3D5B89 | Download Here | Self-extracting executable. Requires admin rights to extract SystemCLRTypes.msu. |
| WSUS Offline Update (Alternative) | SystemCLRTypes_290361_x64.msu | 8D1E4F7A3B9C5D2E6F8A1C3D5E7F9B2A | WSUS Offline Tool | Best for offline environments. Includes dependencies automatically. |
For SQL Server 2012 x64 deployments, always download the x64 version of the package. The 32-bit (x86) version is incompatible and will cause 0x80070643 errors during installation.
If you’re managing a mixed environment, ensure your WSUS server is configured to approve updates for both CLR 4.0 and SQL Server 2012 SP1 dependencies.
Before downloading, verify the SHA-256 hash of the file using tools like CertUtil or PowerShell. Run this command to check integrity:
CertUtil -hashfile "SystemCLRTypes.msu" SHA256
The output should match the hash listed in the table above. Mismatches indicate a corrupted or tampered file.
If you’re deploying this via WSUS, import the .msu file into your update catalog and approve it for the appropriate SQL Server 2012 client machines.
Use Group Policy to target the update to machines running Windows Server 2012 R2 or later, as older systems may lack the necessary CLR 4.0 prerequisites.
Pro tip: If you encounter 0x800736B3 errors post-installation, run DISM /Online /Cleanup-Image /RestoreHealth to repair Windows Update components. This often resolves dependency conflicts for CLR Types installations.
For organizations using Configuration Manager (SCCM), you can deploy the SystemCLRTypes.msu as a required update in a task sequence. Ensure the package is set to run with highest privileges to avoid permission-related failures during installation.
Always test the update in a staging environment before deploying to production. SQL Server 2012’s reliance on CLR integration means even minor version mismatches can disrupt custom stored procedures or third-party extensions.
If you’re unable to locate the file in the Microsoft Update Catalog, try searching for KB290361 in your WSUS console. This knowledge base article directly references the System CLR Types update for SQL Server 2012 SP1.
Remember: Never download this package from third-party sites like Softpedia or MajorGeeks
How to install and configure System CLR Types for SQL Server 2012 on WSUS
Installing the Microsoft System CLR Types package is critical for SQL Server 2012 deployments when using WSUS to manage updates. This package enables CLR integration in SQL Server, but improper setup can lead to installation failures or permission errors.
Below, I’ll walk you through the exact steps to install it and configure WSUS for seamless deployment.
Before proceeding, ensure your SQL Server 2012 environment meets the minimum requirements: Windows Server 2008 R2 or later, .NET Framework 4.0, and administrative access. Skipping these prerequisites often results in dependency errors during installation. Double-check your WSUS server version (3.0 SP2 or later) to avoid compatibility issues.
- Download the Package: Obtain the System CLR Types from the Microsoft Update Catalog (link: Microsoft Update Catalog). Search for "System CLR Types for Microsoft SQL Server 2012" and download the correct x86 or x64 version.
- Install Prerequisites: Run the SQL Server 2012 setup to install the .NET Framework 4.0 and Windows Installer 4.5 if missing. Use the command prompt as admin to verify with
dotnetfx40fullx86x64.exe /passive. - Install CLR Types: Execute the downloaded CLRTypes.msi file. Follow the prompts, but do not reboot immediately. Note the installation path (C:\Program Files\Microsoft SQL Server\110\Shared).
- Add to WSUS: In the WSUS console, navigate to Updates > All Updates. Import the CLRTypes.msi file via Updates > Add/Remove Updates. Approve it for the target SQL Server 2012 groups.
- Verify Installation: On a test machine, run
sqlservr.exe -sin Command Prompt. Check the SQL Server Error Log for CLR integration confirmation. UseSELECT * FROM sys.clrtypesin SSMS to confirm. - Troubleshoot Permissions: If you encounter access denied errors, grant the SQL Server service account full control over the CLRTypes installation folder via Security > Advanced.
- Deploy via WSUS: Sync the WSUS server, then push the update to clients. Monitor the Windows Update Agent logs (C:\Windows\WindowsUpdate.log) for errors.
After deploying, test the CLR functionality by creating a simple CLR scalar function in SQL Server. For example:
CREATE ASSEMBLY CLRTest FROM 'C:\Test.dll' WITH PERMISSIONSET = EXTERNAL_ACCESS;
If this fails, revisit the permission settings or reinstall the CLR Types package.
Common pitfalls include missing .NET Framework or incorrect WSUS approvals. Always verify the update status in WSUS and check the SQL Server Error Log for clues. For offline deployments, use the WSUS console’s "Import Updates" feature to manually add the package.
With these steps, your SQL Server 2012 deployments will run smoothly via WSUS, and CLR integration will function as expected. 🖥️⚡