Operating System
Finding the Microsoft System CLR Types for SQL Server 2012 WSUS download can feel like chasing a ghost update—it’s often missing from the catalog.
But without it, your CLR integration in SQL Server 2012 won’t work, leaving stored procedures and functions broken. Here’s where to find the official KB2679828 download, how to verify its legitimacy, and the exact steps to install it without WSUS errors.
Where to download Microsoft System CLR Types for SQL Server 2012 via WSUS
Deploying Microsoft System CLR Types for SQL Server 2012 through WSUS can be tricky if you don’t know where to find the exact update package. This critical component (KB2679828) enables CLR integration in SQL Server 2012, but it often gets overlooked in standard update catalogs.
Without it, your database applications may fail to execute CLR stored procedures or functions. Let’s walk through the official download process and verify compatibility before pushing it to your WSUS server.
The KB2679828 update is a standalone package that must be manually added to WSUS if it’s not already in your Microsoft Update Catalog. Many admins miss this because it’s not part of the default SQL Server 2012 service pack updates.
Below, I’ll show you how to locate it, check its SHA-256 hash for authenticity, and troubleshoot common issues like proxy restrictions or missing catalog entries.
⚠️ Critical Note: Always verify the update’s compatibility** with your SQL Server 2012 version (SP1 or later) and ensure your WSUS server is synced with the latest Microsoft catalog before proceeding.
Step-by-Step: Locate and Download KB2679828 via WSUS
- Step 1: Navigate to Microsoft Update Catalog
Open your browser and go to the official Microsoft Update Catalog at https://www.catalog.update.microsoft.com. This is the only trusted source for standalone updates like KB2679828.
- Step 2: Search for KB2679828
In the search bar, enter "KB2679828" and filter for SQL Server 2012. The correct package should appear as "System CLR Types for Microsoft SQL Server 2012".
- Step 3: Verify the Package Details
Check the package version (should be 11.0.2100.60) and language (e.g., English). Download the MSU file (Microsoft Update package) for your architecture (x64 or x86).
- Step 4: Add to WSUS Console
Log in to your WSUS server and navigate to Updates > All Updates. Click "Add" and manually import the MSU file you downloaded. This bypasses the automatic sync and ensures the update is available for deployment.
- Step 5: Approve for Deployment
In the WSUS console, locate KB2679828 under Updates. Right-click and select "Approve". Choose the target computer groups (e.g., SQL Servers) and set the installation deadline.
- Step 6: Verify Installation via PowerShell
On a test machine, run Get-HotFix | Where-Object {$.HotFixID -like "_KB2679828_"} in an elevated PowerShell session to confirm the update installed correctly.
💾 Pro Tip: Bookmark the Microsoft Update Catalog link—you’ll need it for future standalone SQL Server updates!
If KB2679828 isn’t appearing in your WSUS console after syncing, it’s likely because Microsoft no longer automatically pushes standalone CLR updates to WSUS. In this case, you’ll need to manually add the MSU file as shown in Step 4.
This is a common pain point, but the workaround ensures your SQL Server 2012 environments stay compliant with CLR requirements.
For environments with proxy restrictions, download the MSU file directly to a local machine and transfer it to your WSUS server via SMB share or USB drive. Avoid using untrusted sources—always verify the SHA-256 hash of the downloaded file against Microsoft’s official checksums to prevent malware risks.
Once deployed, test CLR functionality by creating a simple CLR stored procedure in SQL Server 2012. Open SQL Server Management Studio (SSMS), connect to your instance, and run:
CREATE ASSEMBLY TestCLR FROM 'C:\Path\To\Your\CLR\Assembly.dll' WITH PERMISSIONSET = SAFE;
If this succeeds, your System CLR Types are properly installed.
🔧 Troubleshooting Tip: If you encounter "0x80131500" errors during installation, ensure .NET Framework 3.5 SP1 is installed on target machines. This is a prerequisite for KB2679828 and often overlooked in WSUS deployments.
How to install System CLR Types for SQL Server 2012 without breaking WSUS
Installing Microsoft System CLR Types for SQL Server 2012 requires careful handling to avoid disrupting your WSUS infrastructure. This update (KB2679828) enables CLR integration in SQL Server, but improper deployment can cause update conflicts or approval issues.
I’ll walk you through the silent installation method and prerequisites to ensure a smooth rollout.
Before proceeding, verify your SQL Server 2012 edition supports CLR integration (Enterprise/Developer editions only). Also, ensure .NET Framework 3.5 SP1 is installed, as it’s a mandatory dependency. If missing, WSUS may reject the update or trigger dependency errors during deployment.
If you skip WSUS approval, this update may appear as "unapproved" in your update approval workflow. Always approve it in the WSUS console before pushing to clients. Use the Update Services Manager to verify approval status under Updates > All Updates.
Start by downloading the CLR Types package from the Microsoft Update Catalog (direct link: KB2679828). Save it to a network share accessible by all target machines. For silent installation, use the following command in an elevated Command Prompt:
/quiet /norestart with the full path to the SQLServer2012SP1-KB2679828-x64-ENU.exe file. Example: "C:\Temp\SQLServer2012SP1-KB2679828-x64-ENU.exe" /quiet /norestart. This suppresses UI prompts and prevents reboots, which is critical for WSUS-managed environments.
After installation, validate CLR registration by running sqlcmd and executing SELECT * FROM sys.clrtypes. If no results appear, manually register CLR in SQL Server using sp_configure 'clr enabled', 1 and restart the SQL Server service. Log errors in SQL Server Error Log for troubleshooting.
To maintain WSUS compliance, sync your WSUS server with Microsoft’s update catalog immediately after installation. Use Update Services Manager to refresh metadata and approve the update for your target groups. Always test on a non-production machine first to catch potential conflicts.