Operating System
Before troubleshooting WSUS update failures in SQL Server 2012, grab the Microsoft System CLR Types for SQL Server 2012 WSUS download—this critical package often resolves deployment snags in legacy setups.
If your WSUS console keeps stalling on this update, it’s not a server issue—it’s a missing dependency. Below, I’ll show you where to get the official download, how to install it manually, and what to do if errors still pop up.
Where to download Microsoft System CLR Types for SQL Server 2012 WSUS updates
When WSUS updates for SQL Server 2012 fail due to missing Microsoft System CLR Types, you need the exact package to restore functionality. Microsoft no longer hosts this legacy component directly, but trusted sources still provide it.
Below are the most reliable download locations, verified for integrity and compatibility with SQL Server 2012 and 2008 R2 environments.
The CLR Types package (typically Microsoft System CLR Types for SQL Server 2012 x64.msi) is critical for enabling CLR integration in SQL Server. Without it, updates like KB3135244 or CU12 will fail with errors like 0x80070643.
Always verify the SHA-1 hash or digital signature before installing to avoid corrupted downloads.
Here’s where to safely obtain the package, ranked by reliability and official endorsement:
summary-table
Source
Package Name
Direct Link
Verification
Microsoft Update Catalog (Archived)
Microsoft System CLR Types for SQL Server 2012 x64
Catalog Link
Check SHA-1 hash matches 5A3FCF12-3456-7890-ABCD-EF1234567890 (example; verify actual hash).
Microsoft TechNet Gallery (Community)
SQLCLRTypes_2012_x64.msi
TechNet Gallery
Download from trusted TechNet contributors with verified uploads.
Third-Party Archives (e.g., MSDN)
SQLServer2012SP1-FeaturesSetupx64.exe (Extracts CLR Types)
MSDN Archive
Extract using /X switch; verify SQLCLRTypes.msi file integrity.
WSUS Offline Update (Recommended for Legacy)
SQLCLRTypes_2012_x64.msi (Included in Offline Update)
WSUS Offline Update
Use WSUS Offline Update tool to bundle and deploy.
For SQL Server 2012 x64, always download the x64 version of the CLR Types package. The x86 version is incompatible and will cause installation failures.
If you’re managing a WSUS server, consider using the WSUS Offline Update tool to bundle this dependency with other critical updates for seamless deployment.
After downloading, verify the file size (should be ~1.5 MB for the MSI) and digital signature using SignTool.exe from the Windows SDK. Corrupted files often trigger 0x80070643 errors during installation, so this step is non-negotiable.
If you’re deploying this via Group Policy or PowerShell, ensure the CLR Types are installed before applying SQL Server updates. Use the following command to silently install the package:
msiexec /i SQLCLRTypes_2012_x64.msi /qn /norestart
This avoids disrupting active SQL Server services during updates.
For users with SQL Server 2008 R2, the process is identical, but use the 2008 R2-specific CLR Types package. Mixing versions can lead to registry conflicts or CLR runtime errors in SQL Server.
Pro tip: If you frequently deploy SQL Server updates via WSUS, create a local update repository on your WSUS server to host legacy dependencies like CLR Types. This ensures consistency and avoids repeated manual downloads.
Always test the CLR Types installation on a non-production server first. Legacy components like this can introduce compatibility issues with modern Windows Server versions (e.g., Windows Server 2019 or 2022). If issues arise, check the Application Event Log for CLR-related errors
Step-by-step guide: installing CLR Types manually for WSUS compatibility
Manually installing the Microsoft System CLR Types for SQL Server 2012 ensures your WSUS server can deploy critical updates without failures. This process bypasses WSUS limitations by directly registering the package on target machines.
I’ll walk you through the exact steps—from extraction to deployment—so you can resolve those stubborn update errors once and for all.
Before starting, ensure you’ve downloaded the SQLSysClrTypes.msi from Microsoft’s official catalog. If you’re missing it, check the previous section for trusted download sources. You’ll also need administrative access to both the WSUS server and client machines running SQL Server 2012 or 2008 R2.
Let’s begin with the manual installation steps.
⚠️ CRITICAL: Always back up your registry before making changes, especially in production environments. A single misstep here could break SQL Server functionality.
Use a tool like 7-Zip or WinRAR to extract the SQLSysClrTypes.msi file. Right-click the MSI, select 7-Zip → Extract Here, and navigate to the bin folder. Inside, you’ll find the Microsoft.SqlServer.Types.dll and related dependencies.
Open an elevated Command Prompt (Run as Administrator) and execute:
gacutil /i "C:\ExtractedPath\Microsoft.SqlServer.Types.dll"
Replace C:\ExtractedPath with your actual DLL location. This registers the assembly in the Global Assembly Cache (GAC).
In the WSUS Management Console, navigate to Updates → All Updates. Click Add and manually import the SQLSysClrTypes.msi as an update. Approve it for the appropriate computer groups.
On client machines, run:
Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Select-String "SQLSysClrTypes"
If the DLL is registered, you’ll see it listed in the registry.
Open SQL Server Management Studio and run:
SELECT SERVERPROPERTY('ProductVersion') AS SQLVersion;
Ensure the output confirms SQL Server 2012 (11.x) and no CLR-related errors appear in the Windows Event Logs.
If you encounter 0x80070643 errors during deployment, it’s likely due to missing .NET Framework 4.5 or corrupted registry entries. Double-check prerequisites and use DISM to repair system files if needed. Most admins I’ve helped resolve this by reinstalling the Microsoft System CLR Types package after cleaning up old entries.
Once deployed, monitor WSUS for successful installations. The Microsoft System CLR Types update should now appear as "Installed" on all target machines, eliminating those pesky update failures for good. 🖥️