{"id":13974,"date":"2020-04-07T00:02:00","date_gmt":"2020-04-06T22:02:00","guid":{"rendered":"http:\/\/159.69.82.204\/win\/?p=13974"},"modified":"2020-04-06T17:05:19","modified_gmt":"2020-04-06T15:05:19","slug":"potential-errors-in-the-windows-update-database-part-2","status":"publish","type":"post","link":"https:\/\/borncity.com\/win\/2020\/04\/07\/potential-errors-in-the-windows-update-database-part-2\/","title":{"rendered":"Potential errors in the Windows update database – Part 2"},"content":{"rendered":"

[German<\/a>]In Part 1<\/a> I had taken up a reader's note that after Windows fails to install updates, there are potential errors in the Windows Update database which can't be repaired by Update trouble shooter. In part 2 I describe further diagnosis steps, a root cause for the issues and a repair approach. <\/p>\n

<\/p>\n

\"\"From Part 1<\/a> there was the suspicion that a driver install issues may be involved the Windows Update database error reported by the troubleshooter. The suspicion is: Does the troubleshooter report something wrong because the error is in the event logs?<\/p>\n

Is the troubleshooter reporting something false?<\/h2>\n

For Andi, the findings from part 1 were followed by the question: \"Is it conceivable that the troubleshooter reports \"potential errors in the update database\" as a false diagnosis and instead the text \"potential errors in the event viewer\" should be displayed?<\/p>\n

Therefore he decided to selectively delete the event logs. This is not a problem, since the log could be saved before the events were deleted. And if any errors that occurs are logged as events again. Once the error is gone, no new entry is written in the event display, of course. <\/p>\n

\"Event<\/p>\n

The Event Viewer display is structured hierarchically. The entries relevant for the following test are located in the Windows Logs<\/em> branch (see figure above). The entries are divided into various categories. <\/p>\n

The entries can be deleted in the Windows Logs<\/em> branch of the Event Viewer running with administrative rights via the context menu or in the Action\/Delete<\/em> menu.<\/p>\n

#1 Delete events under Application<\/h3>\n

In the first step, Andi deleted the entries in the Windows Logs\\Application<\/em> branch of the Event Viewer. Then the troubleshooter was executed. The result was the message: \"potential errors in the Windows Update database\", which was actually to be expected. <\/p>\n

#2 Delete events under Security<\/h3>\n

In the next step, the entries in the Windows Logs\\Security<\/em> branch of the Event Viewer were deleted. Afterwards, the troubleshooter was performed, which returned the message: \"potential errors in the Windows Update database\". This was also to be expected, since errors in the update database should not have anything to do with security events.<\/p>\n

#3  Delete events under Installation<\/h3>\n

There is another branch called Installation in the Event Viewer. This should be a 'hot candidate' for a test, as it's where problems that occur during the installation of components in Windows are entered. So in a further step in the Event Viewer, delete the entries in the Windows Logs\\Installation<\/em> branch. <\/p>\n

Then the Windows Update troubleshooter was launched to analyze the data base for errors. And Bingo, there was a change! The troubleshooter suddenly reported: \"The problem could not be identified by the troubleshooter\" (see figure below).<\/p>\n

\n

Note: In the following text, Andi suggests deleting the entries in the System branch instead of the Installation branch. My recommendation here would be to successively delete the individual branches under Windows Logs, if necessary.<\/p>\n<\/blockquote>\n

Verifying the process again<\/h2>\n

After these steps Andi decided to run all tests again to document this. In the German screenshots below, he shows the date and time in the background (taken from as time service). <\/p>\n

Start with no Windows Update database error<\/h3>\n

The test was started in a state that the troubleshooter does not report an error in the Windows Update database. <\/p>\n

\"Windows<\/p>\n

So first, Andi checked what the troubleshooter determines about the state of the update database. This ended with the result shown in the figure above. The troubleshooter reported: \"The problem could not be identified by the troubleshooter\". <\/p>\n

Uninstalling and reinstalling drivers<\/h3>\n

Then Andi uninstalled the Intel Wireless Bluetooth driver in Device Manager (see the following figure). <\/p>\n

\"Treiber<\/p>\n

He then had Windows Update check for updates. During this step a driver should be found and installed. <\/p>\n

\"Bluetooth-Treiber-Update\"<\/p>\n

A driver was found (see figure above) and he had it installed. Then it was checked whether the Bluetooth driver was installed. <\/p>\n

\"Treiber<\/p>\n

Check the update database for errors<\/h3>\n

Exciting question: What does the troubleshooter will report after installing the Bluetooth driver initiated by Windows Update? <\/p>\n

\"Problembehandlung<\/p>\n

The troubleshooter reports again and as expected, an error in the Windows Update database. <\/p>\n

''Repair' the update database via the Event Viewer<\/h3>\n

So the next step is to repair the Windows Update database by 'Delete the event logs'. To do this, you can access the event viewer by either searching the taskbar or right-clicking on the Windows logo in the left corner of the taskbar, followed by a left-click on \"Event Viewer\". <\/p>\n

\"Ereignisanzeige:<\/p>\n

Then double-click on the Windows Logs<\/em> branch in the left column. Right-click on System<\/em> to open the context menu and choose the context menu command Delete Log<\/em>… is selected. Confirm the deletion in the dialog box shown.<\/p>\n

\n

Andi wrote: The cmd window unfortunately disappeared after clicking on the event viewer. Therefore no proof of the Windows version is possible here. And he deleted here entries in System instead of Installation. It's mandatory to try, which Event viewer branch need to be deleted to fix the database error. <\/p>\n<\/blockquote>\n

Repair of the Windows Update database was successful after this step, as the troubleshooting diagnosis for Windows Update shows afterwards.<\/p>\n

<\/p>\n

This proved that the diagnosis of the Windows Update troubleshooter reported false results and can't fix broken things. <\/p>\n

Conclusion of the whole action<\/h2>\n

Anyone running into issues with Windows Update on Windows 10 and is using the Windows Update troubleshooter, must remain vigilant. If the troubleshooter reports errors in the Windows Update database that can't be fixed, they might be the result of corresponding entries in the event logs. <\/p>\n

Anyone who gets into this situation should try to clear the logs in the Event Viewer under Windows Update. The procedure has been described above in detail – and this clearing has no consequences for Windows functionality (only entries that could be used for troubleshooting are gone – and this can be prevented by saving the entries before deleting them). <\/p>\n

Andi was successful with approach in Windows 10 version 1803. This approach should help with \"potential errors in the Windows update database\" even with newer versions of Windows 10. At this point my thanks to Andi for the extensive testing and preparation, so that I could publish this in this blog post.<\/p>\n

Article series:<\/strong>
Potential errors in the Windows update database<\/a> – Part 1
Potential errors in the Windows update database<\/a> – Part 2<\/p>\n

Similar articles
<\/strong>How to decode Windows errors?
<\/a>Windows 10: Analyze upgrade errors
<\/a>Windows: How to decode update 0x8024\u2026. errors<\/a>
Check and repair Windows system files and component store<\/a>
Windows Update Error 0x80246001<\/a>
Windows Update Error 0x8007042B<\/a>
Windows Update error 0x8024200D<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

[German]In Part 1 I had taken up a reader's note that after Windows fails to install updates, there are potential errors in the Windows Update database which can't be repaired by Update trouble shooter. In part 2 I describe further … Continue reading →<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[463,22,2],"tags":[2366,466,195,76],"class_list":["post-13974","post","type-post","status-publish","format-standard","hentry","category-issue","category-update","category-windows","tag-ereignisanzeige","tag-problem","tag-update","tag-windows-10"],"_links":{"self":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/13974","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/comments?post=13974"}],"version-history":[{"count":0,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/13974\/revisions"}],"wp:attachment":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/media?parent=13974"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/categories?post=13974"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/tags?post=13974"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}