Install Windows Internal Database Wsus Console Not Working' title='Install Windows Internal Database Wsus Console Not Working' />Install Windows Internal Database Wsus Console AccessHow to Delete Driver Updates from WSUSI ran into the issue where driver updates downloaded into a WSUS infrastructure that had masterreplica servers created a bit of a performance problem. Several weeks into in, my WSUS replica could no longer synchronize successfully with the master. No matter what I tried it just would not synchronize anymore. I wrote about the issue here and referred to Microsoft blog post talking about the issue here. I wasnt able to find a way to drop driver updates from my WSUS WIDS database on the Internet and was left with the only option reinstall both WSUS servers, and then reconfigure and resynchronize everything. That looked unexciting. I thought I could as well try to delete driver updates directly from the database. What can possibly go wrong and even if it does, I have to reinstall anyway. So here it goes. USE AT YOUR OWN RISK. Preparations. If you ran WSUS defrag scripts, you already have SQL Native Client and SQL Command Line tools installed on your WSUS servers. If this is the case,Uninstall SQL Native Client. Install SQL Server Management Studio SSMS for SQL Server 2. Microsoft has released an update for Windows Server Update Services WSUS 3. Service Pack 2 SP2. This article includes information about the contents. A lot of things changed in server 2012 on the PKI model compared to. R2 Express SP2. If you do not have SQL Native Client installed on the WSUS servers, just go ahead and install SSMS. SSMS will fail to install if you already have Native Client. The following steps need to be executed once on each WSUS server in your environment. Connecting to WSUS WIDS Database. Open SSMS and connect to the following SQL instance np. MSSQLMICROSOFTSSEEsqlquery. If you get a securityaccess rights error, close SSMS, restart it using elevated context right click, run as administrator. This will get your SQL Server Management Studio connected to the WIDS database. Install Windows Internal Database Wsus Console 2016' title='Install Windows Internal Database Wsus Console 2016' />If your database is not hosted in WIDS, chances are you are not experiencing the timeout errors anyway and dont need to do this, but if you are doing it anyway then connect to your named or default SQL instance as appropriate. Determine GUID of the Driver Update Type. Open a new query window and run the following two queries USE SUSDB. You can install the WSUS role on a computer that is separate from the database server computer. In this case, the following additional criteria apply. SELECT Update. Type. ID FROM tb. Update. Type WHERE Name Driver. GOThis query gives you the GUID that you will need to substitute in all subsequent queries if the GUID you get is not the same as what I have in subsequent statements. In my case, it is D2. CB5. 99. A FA9. F 4. AE9 B3. 46 9. 4AD5. EE0. 62. 9. I saw this GUID in several WSUS databases so I think it does not change at least not between WSUS 3. SP2 servers. Delete Drivers from Tables with Foreign Key Constraints. The bad news is that WSUS database has over 1. The good news is that SQL allows to enforce referential integrity in data model designs, which in this case can be used to essentially reverse engineer a procedure, that as far as I know isnt documented anywhere. Trick is to delete all driver type records from tb. Update table but FIRST we have to delete all records in all other tables revisions, languages, dependencies, files, reports, which refer to driver rows in tb. Update. Heres how this is done, in 1. I recommend running each query separately. Revision where Local. Update. Id in select Local. Update. Id from tb. Update where Update. Type. ID D2. CB5. A FA9. F 4. AE9 B3. AD5. 4EE0. 62. 9. Property where revisionid in select revisionid from tb. Revision where Local. Update. Id in select Local. Update. Id from tb. Update where Update. Type. ID D2. CB5. A FA9. F 4. AE9 B3. AD5. 4EE0. 62. 9. Localized. Property. For. Revision where revisionid in select revisionid from tb. Revision where Local. Update. Id in select Local. A FA9. F 4. AE9 B3. AD5. 4EE0. 62. 9. File. For. Revision where revisionid in select revisionid from tb. Download Pokemon Diamond No Gba Emulator. Revision where Local. Update. Id in select Local. Update. Id from tb. Update where Update. Type. ID D2. CB5. A FA9. F 4. AE9 B3. AD5. 4EE0. 62. 9. Installed. Update. Sufficient. For. Prerequisite where prerequisiteid in select Prerequisiteid from tb. Pre. Requisite where revisionid in select revisionid from tb. Revision where Local. Update. Id in select Local. Update. Id from tb. Update where Update. Type. ID D2. CB5. A FA9. F 4. AE9 B3. AD5. 4EE0. 62. 9. Pre. Requisite where revisionid in select revisionid from tb. Revision where Local. Update. Id in select Local. Update. Id from tb. Update where Update. Type. ID D2. CB5. A FA9. F 4. AE9 B3. AD5. 4EE0. 62. 9. Deployment where revisionid in select revisionid from tb. Revision where Local. Update. Id in select Local. Update. Id from tb. Update where Update. Type. ID D2. CB5. A FA9. F 4. AE9 B3. AD5. 4EE0. 62. 9. Xml where revisionid in select revisionid from tb. Revision where Local. Update. Id in select Local. Update. Id from tb. Update where Update. Type. ID D2. CB5. A FA9. F 4. AE9 B3. AD5. 4EE0. 62. 9. Pre. Computed. Localized. Property where revisionid in select revisionid from tb. Revision where Local. Update. Id in select Local. Update. Id from tb. Update where Update. Type. ID D2. CB5. A FA9. F 4. AE9 B3. AD5. 4EE0. 62. 9. Driver where revisionid in select revisionid from tb. Revision where Local. Update. Id in select Local. Update. Id from tb. Update where Update. Type. ID D2. CB5. A FA9. F 4. AE9 B3. AD5. 4EE0. 62. 9. Flattened. Revision. In. Category where revisionid in select revisionid from tb. Revision where Local. Type. ID D2. CB5. A FA9. F 4. AE9 B3. AD5. 4EE0. 62. 9. Revision. In. Category where revisionid in select revisionid from tb. Revision where Local. Update. Id in select Local. Update. Id from tb. Update where Update. Type. ID D2. CB5. A FA9. F 4. AE9 B3. AD5. 4EE0. 62. 9. More. Info. URLFor. Revision where revisionid in select revisionid from tb. Revision where Local. Update. Id in select Local. Update. Id from tb. Update where Update. Type. ID D2. CB5. A FA9. F 4. AE9 B3. AD5. 4EE0. 62. 9. Revision where Local. Update. Id in select Local. Update. Id from tb. Update where Update. Type. ID D2. CB5. A FA9. F 4. AE9 B3. AD5. 4EE0. 62. 9. Update. Summary. For. All. Computers where Local. Update. Id in select Local. Update. Id from tb. Update where Update. Type. ID D2. CB5. A FA9. F 4. AE9 B3. AD5. 4EE0. 62. 9The last query is really what we came here for delete from tb. Update where Update. Type. ID D2. CB5. A FA9. F 4. AE9 B3. AD5. 4EE0. 62. 9If at this point you get an error saying something about foreign key constraint, that will be most likely due to the difference between which reports I ran in my WSUS installation and which reports were ran against your particular installation. Fortunately, the error gives you exact location table where this constraint is violated, so you can adjust one of the queries in the batch above to delete references in any other tables. These 1. 6 queries, in my case, dropped a total of 1,3. SUSDB database each WSUS server has its own, obviously. Dont forget to do this on all WSUS servers. Verify Functionality and Try to Synchronize WSUS Hierarchy. This should be pretty straight forward and self explanatory. You will want to make sure that your WSUS systems are functioning as expected before declaring victory. Run index defrags on all WSUS databases see articles cited at the topRestart WSUS console and look for Driver updates you should not see anyClick around in WSUS console and look for any weirdness. Run WSUS Cleanup Wizard from bottom to top of your WSUS infrastructure.