Windows 10 1607 cumulative update KB 4034658 wipes out Update History

Topic

New Reply

It’s a minor bug, but a pain in the neck. As best I can tell, it only affects Win10 Anniversary Update, version 1607. Post coming in Computerworld.
[See the full post at: Windows 10 1607 cumulative update KB 4034658 wipes out Update History]

1 user thanked author for this post.

abbodi86

Reply | Quote

Replies

Confirmed on my end, at least on version 1607.

What is the Microsoft’s “Greatest Hits” release date?

Reply | Quote

And as a result hidden updates aren’t hidden anymore.

2 users thanked author for this post.

walker, MrBrian

Reply | Quote

I didn’t realize that. Thank you!

Reply | Quote

Maybe this build deleted file datastore.edb, which holds this information.

2 users thanked author for this post.

ch100, woody

Reply | Quote

More info about datastore.edb:

Clear the Update Failure Information

Where does Windows store hidden-update settings?

2 users thanked author for this post.

ch100, woody

Reply | Quote

Confirming that the previously hidden feature update to 1703 is queued up again after version 1607 receives August 2017 updates.

Reply | Quote

I downloaded this update and installed it a week ago with the intention of getting all the way up to date before going to 1703. It reset my history also. I then updated and the history starts all over. Maybe a little push on Microsoft’s end to remind you to update to 1703 ?? Who knows. A couple of minors bugs in 1703 I noticed are: I have a Dell XPS8900 that came new out of the box with 1511 and the screensaver and startup sounds were messed up and didn’t work right. 1607 fixed the problems and 1703, yep, their back. Windows start up sound does not work on initial start up, only on a reboot and the screensaver set to 15 minutes comes on 20 minutes or later, just whenever it feels like it. annoying, but minor. Everything else is working as it should with no other complaints. Using Windows Pro with the options to regulate updates from the settings side without using gpedit is a plus. The other changes are minor and not much difference on the surface between 1607 and 1703, at least for what I use it for.

1 user thanked author for this post.

woody

Reply | Quote

I have Win 7  and group A.  Awhile back my history was wiped out and started over but I don`t remember which update caused it.

Reply | Quote

I found the same with 1607, but not my test 1703 images. On 1607, you can go to Control Panel, Programs & Features and click the link to View Installed Updates.  You will find this month’s updates are correctly listed there.

Reply | Quote

Sunuvagun! Yes, it’s right there – including an entry for KB 4034658.

Bizarre! But at least that means the data’s still around, somewhere – just not visible through the Settings app.

Reply | Quote

I can also see a update list in the ‘Programs and Features’ Control Panel for Windows 10 1607, however there is much missing data about installed updates. This months cumulative update has not been installed yet, only Flash and the Malware removal tool.

Reply | Quote

What is different about other updates which have wiped the history of installed updates?; Without such a bug (or intentional wiping of the database) I should be able to see all activity back to the Windows 10 1607 Anniversary Update.

Reply | Quote

https://support.microsoft.com/en-us/help/4025334

Addressed issue that requires the addition of a new client-side Group Policy that optionally disables Dual Scan behavior.

i believe this new WUA engine feature requires a refreshment of WU Database (i.e. wipe out)

of course, same WUA version is carried over to KB4034658

3 users thanked author for this post.

ch100, woody, MrBrian

Reply | Quote

It’s weirder than that.

I show previously installed updates in Control Panel, but none in the Update History in the “new” UI.

WUShowHide.diagcab shows NO hidden updates.  Previously it was used to hide 1703 as well as other driver updates.

WUShowHide does show several available updates that I could hide, see screen shot. But that list does not show the 1703 feature update.

Yet 1607 is staying “put” and not trying to force me to update to 1703 on my test workstation when I check for updates.

~ Group "Weekend" ~

2 users thanked author for this post.

ch100, woody

Reply | Quote

CP Installed Updates list shows the actual installed updates, whether from WU or manually

Update History (new UI) reference WU database and only shows updates installed from WU

as you can see in this situation, this database could get wiped out (including the list of hidden updates)

that’s a good thing then, your OS is not fully applicable for version 1703 😀

2 users thanked author for this post.

ch100, woody

Reply | Quote

abbodi86 wrote:

. . . that’s a good thing then, your OS is not fully applicable for version 1703

Actually this was one of my systems last week that I had to actively block 1703 on;  it was going full steam ahead when I caught it and blocked that update successfully.  Given how new it is, I would be pretty surprised if it was not compatible, I’m just not quite ready to let it upgrade.

 

~ Group "Weekend" ~

1 user thanked author for this post.

ch100

Reply | Quote

The “unhiding” of the updates is related to the C:\Windows\SoftwareDistribution\DataStore\DataStore.edb reset, where that information is stored.
This was explained earlier by @MrBrian and @abbodi86 and has been known for a long time.
Moreover, various Windows Update agent updates produced in the past the same effect on Windows 7 and any other Operating System, so this is nothing out of common and not necessary a bug, but rather an unintended side-effect perhaps.
Let’s not forget that DataStore.edb is only a cache and resetting a cache by any means including a software install or update does not represent a bug.

1 user thanked author for this post.

MrBrian

Reply | Quote

The only “accidental” DataStore.edb reset i have seen happens when uninstalling WUA update (i.e. going from a version to lower one)
it’s different in this case as WUA version is higher

1 user thanked author for this post.

ch100

Reply | Quote

In Windows 7, I borked my datastore.edb by settings its compression attribute.

1 user thanked author for this post.

ch100

Reply | Quote

KB 4034658 wiped my history also on 1607. The only place I could see any history at all was in Programs & Features>installed updates.

It also wiped out all but my 2 most recent Restore Points for some reason.

Don't take yourself so seriously, no one else does 🙂
All W10 Pro at 22H2,(2 Desktops, 1 Laptop).

Reply | Quote

Looks like it does the same for Windows 2016 server too.

Reply | Quote

Windows 2016 is build 1607 and receives in general the same patches like Windows 10 64-bit 1607, although strictly speaking Windows 2016 is the “enhanced” server version of Windows 10 64-bit LTSB.

Reply | Quote

After updating to Creators Update, all previous updates were gone from Update history. The latest and only entry was “Feature update to Windows 10, version 1703”. The history is now divided in two categories: Quality and Other updates.

Reply | Quote

Hi together,

we are using in our company W10 LTSB2016 (1607) and are facing the same problem wiping out the update history. But we have second problem. All clients that got the update KB 4034658 via WSUS not only loose their update history, they also loose the connection to the WSUS-Server. Looking for update will time out with 0x8024401c. All clients that have KB 4034658 not yet installed connect with no problems to the WSUS server.

Thanks goodness that we rollout client updates only to small number of clients to see what Microsoft put into present box 🙂

3 users thanked author for this post.

HiFlyer, woody, MrBrian

Reply | Quote

We are using Windows 10 Pro (don’t know what service channel, if any, it is) but we are having the same issue on a few PCs with 1607 not reporting status to WSUS and giving the same error when attempting to update manually.

Reply | Quote

Does this affect anything other than the Update History being blank?

Reply | Quote

I believe it also unhides anything you have hidden. Typical of the datastore being deleted.

3 users thanked author for this post.

walker, ch100, woody

Reply | Quote

I’m surprised they acknwoledged the “lost hidden updates”, since Windows 10 WU doesn’t officially or easily allow to hide updates 😀

Reply | Quote

But then there’s wushowhide, an official Microsoft Windows Tool….. 🙂

1 user thanked author for this post.

ch100

Reply | Quote

True

but that’s for advanced users and who read forums/articles, not those who just use WU 😀

1 user thanked author for this post.

ch100

Reply | Quote

I’m a complete idiot with computers, and I was worried about this. But I have found something which may help. Although if you click Update History it tells you that you have no updates yet, it also offers Uninstall Updates. If you click Uninstall Updates, all the updates are listed (for you to choose which one to uninstall if you wish, but that isn’t compulsory? !!!!!

So your update history is still there, but a little more difficult to get to.

This works for both the computers in this house.

2 users thanked author for this post.

HiFlyer, Elly

Reply | Quote

I applied system updates including
2017-08 Security Monthly Quality Rollup for Windows 7 for x64-based Systems (KB4034664)
http://support.microsoft.com/help/4034664
to my Windows 7 image on 2017-08-08. They when I tried to apply the office updates two times, they did not completely succeed. I have not tried to install the office updates again after that day.

I just noticed that all of the restore points are missing. This behavior might be related.

Reply | Quote

I noticed on my restore points two were made just a couple minutes apart? Very strange, and the rest were wiped after update. Yes, looks as though all my update history was wiped too.

The saga continues as the Windows world turns.

Reply | Quote

Three issues are now documented at KB4034658 (OS Build 14393.1593).

Also, Woody has published article More problems with KB 4034658 August cumulative update for Win10 1607/Server 2016.

Reply | Quote

… and they all end with, “Microsoft is investigating this issue and will provide an update as soon as possible.”
🙂

2 users thanked author for this post.

HiFlyer, Alice

Reply | Quote

And all is related to WUA engine

that “Disable Dual Scan” thing messed thing up 🙂

2 users thanked author for this post.

ch100, woody

Reply | Quote

Ouch. I should write this up. Have any links to sources?

Reply | Quote

I don’t, it’s just a logical analysis 🙂

first two issue related to WU database, third is about WU scan difficulties

and per documentation, that “Disable Dual Scan” policy is what changed/added to WUA

2 users thanked author for this post.

ch100, woody

Reply | Quote

My complaints (from Turkish Win 10-64) since last 3 updates of Win 10, I have had Edge browser problems. 3rd update before last, completely erased Edge browser from my laptop and after hard tryings I could regain Edge browser full fresh without bookmarks etc. 2. update before last erased my Edge browser again but I knew the method and I have able to regain it again full fresh. Last update again erased my bookmarks and left Edge browser as full fresh but fortunately not disappeared. I dont mention alse I have lost my update history too.

Reply | Quote

Is this on Won10 version 1607 Anniversary Update?

Reply | Quote

Yes 1607 updates. Last was several days ago.

Reply | Quote

As you can see from the topic title, erasing the update history is one of the bugs introduced by the latest Win10 1607 Cumulative Update.
We have not seen the problem with the Edge browser before. You are the first to report it.
Thanks.

Reply | Quote

I also have lost my edge browse and cannot get on the Internet.

Reply | Quote

I haven’t heard that problem, either.

Best bet is to contact Microsoft directly –

https://www.reddit.com/r/Windows10/comments/6seula/august_windows_10_cumulative_updates_are_out/

Remember that other people may be having the same problem – so take the time to report it!

Reply | Quote

Hello,
I can confirm the problems in reply #128938 – not only with 1607 LTSB, but also with 1607 corp./enterp.

“Last contact” is still updated in WSUS console, but “last report” is not updated anymore. Which results in those clients no longer manageable through WSUS.
Regards, TP

1 user thanked author for this post.

woody

Reply | Quote

All 1607 variants edition shares the same WUA infrastructure

so any issue affect LTSB will affect Home, Pro, Enterprise and even Server 2016

1 user thanked author for this post.

woody

Reply | Quote

Anyone got fix for this?  My history got wiped and the machines is not reporting back to WSUS server.  I tried to uninstall KB4034658 and got a error uninstall it.  Anyone got this fixed?

Reply | Quote

History is lost for good
but you may check this this files which lists installed updates from WU/WSUS
C:\Windows\SoftwareDistribution\ReportingEvents.log

 

Reply | Quote

Even with KB 4034658 uninstalled, I am getting 0x8024401c.

Reply | Quote

Uninstalling KB 4034658 also did not work with us. Connection to WSUS-Server will time out with error 0x8024401c still remains. Only complete restore of VM´s brings them back to stable condition. We are using 2012 R2 as WSUS-Server, that did not installed this KB 4034658 so we are sure this problem is client-side related. MS confirms that there will be problems with KB 4034658 and WSUS, but we think that other problem installing KB 4034658 on a 2016 WSUS-Server.

Reply | Quote

Does this help?

https://kickthatcomputer.wordpress.com/2017/08/13/wsus-sup-causes-high-cpu-and-clients-fail-updates-scan/

Reply | Quote

Hello,
I can confirm that after installing KB4034658 on Windows 10 (1607) and on Windows Server 2016, the update history has gone and the worst thing – the connection to WSUS is broken with error 0x8024401c
Regards,
Martin

EDIT html to text

Reply | Quote

Another strange thing is happen to our WSUS server since august update.  Every morning I come to work, the WSUS server will get reset node error when I click on refresh button.  I click reset the node and still not working.  It only works after I rebooted.  It will work the rest of the day and then tomorrow happen again.  It has been happen for few days now since I applied the update. Anybody is experiencing that also?

Reply | Quote

Same issue here. Running on Server 2012 R2.

Reply | Quote

Ok, I found a article that fix my issue for now.  It looks like the WsusPool service was stop, not sure why.  I follow the article increase the private memory and started  the WsusPool service in IIS.  Anyone know why service stopped?

Here is the link to article:

 

https://blogs.technet.microsoft.com/configurationmgr/2015/03/23/configmgr-2012-support-tip-wsus-sync-fails-with-http-503-errors/

Reply | Quote

Ok, looks like I fixed the problem.  Well, at least machines are communicating back with my WSUS server.  Here are my steps, I uninstalled KB4034658 and reinstall July cumulative update manually (KB4025339), which I downloaded from Microsoft update catalog.  Now, my machines reporting back to my WSUS server.

Reply | Quote

Microsoft have acknowledged issues with KB4034658, like on 1607, a full scan being actioned after install, and high CPU/memory usage problems with WSUS:

System Center: Configuration Manager
High CPU/High Memory in WSUS following Update Tuesdays
August 18, 2017 by Jarrett Renshaw MSFT

 
Recently, we’ve seen an increase in the number of high CPU/High Memory usage problems with WSUS, including WSUS in a System Center Configuration Manager environment – these have mostly corresponded with Update Tuesdays.

Microsoft support has determined that the issue is driven primarily by the Windows 10 1607 updates, for example KB4022723, KB4022715, KB4025339, etc. See here for the list of Windows 10 1607 updates.

Microsoft is also aware of a known issue with KB4034658 that will cause Windows 10 1607 clients to run a full scan after install – Microsoft is investigating and the latest information is available here.

These updates have large metadata payloads for the dependent (child) packages because they roll up a large number of binaries. Windows 10, versions 1507 (Windows 10 RTM) and 1511 updates can also cause this, though to a lesser extent. Windows 10, version 1703 is still recent enough that the metadata is not that large yet (but will continue to grow).

The symptoms include
* High CPU on your WSUS server – 70-100% CPU in w3wp.exe hosting WsusPool
* High memory in the w3wp.exe process hosting the WsusPool – customers have reported memory usage approach 24GB
* Constant recycling of the W3wp.exe hosting the WsusPool (identifiable by the PID changing)
* Clients failing to scan with 8024401c (timeout) errors in the WindowsUpdate.log
* Mostly 500 errors for the /ClientWebService/Client.asmx requests in the IIS logs
…
Solution:
Configure IIS to stop recycling the App Pool…

 
Read the full blogpost on technet.microsoft.com

4 users thanked author for this post.

abbodi86, woody, MrBrian, ch100

Reply | Quote

The reason for high CPU, high memory in use etc is obvious to those understanding this stuff, but Microsoft only wants to buy more time to come with a politically correct answer. The installation of the CU had a similar effect with resetting the database found here C:\Windows\SoftwareDistribution\DataStore\DataStore.edb
which is the same cache which users sometimes reset themselves as part of fixing Windows Update issues, as it was recommended many times here by me and other members and it is also recommended on many other web sites.
For this reason, at first scan, the database needs to be rebuilt, recreated, required downloads downloaded again which create high CPU, high RAM usage, high network traffic and so on at the endpoint and also at the server if the number of clients is large enough.
As it is usually the case, those affected most by those known issues, now documented in the Microsoft KB, are those who do not regularly update or use dubious techniques to block updates.
For everyone else, it is smooth sailing, although the DataStore.edb is still reset for everyone.
The other issue related to the IIS WSUS Application Pool has been known for many years and it is not new or specific to Windows 10.
https://blogs.msdn.microsoft.com/the_secure_infrastructure_guy/2015/09/02/windows-server-2012-r2-wsus-issue-clients-cause-the-wsus-app-pool-to-become-unresponsive-with-http-503/
https://www.windowsmanagementexperts.com/configmgr-software-update-point-out-of-control-app-pool/configmgr-software-update-point-out-of-control-app-pool.htm
http://iamrusso.com/w3wp-exe-100-cpu-wsus-3-0-and-sccm/

2 users thanked author for this post.

abbodi86, MrBrian

Reply | Quote

Tweet from Microsoft employee Michael Niehaus‏: ‘See the “known issues” list in KB4034658. Installing that update clears the update history, which heavily impacts WSUS on the next scan.’

Reply | Quote

Blog post was updated on August 28 with hotfix info.

Reply | Quote

WSUS issues with Windows 10 Anniversary update with SBS 2011 server (WSUS 3.0)
confirmed

Reply | Quote

From Windows 10: Update history bug documented in KB4034658 (translated from German):

“The Microsoft Update KB4034658 for Windows 10 version 1607 causes a bug that clears the update history. I tested the whole thing in a virtual machine and documented in the blog post.

[…]

Something has gone wrong during the installation of the update and the updating of the DataStore.edb . Either is a faulty data record in the database, so the history can not be read. Or the content has been set to 0 with regard to the entered data records.”

 

1 user thanked author for this post.

ch100

Reply | Quote

Either is a faulty data record in the database, so the history can not be read. Or the content has been set to 0 with regard to the entered data records

The database is completely cleaned, and DataStore.edb is deleted, after the reboot i found it at initial size (~2 MB)

1 user thanked author for this post.

ch100

Reply | Quote

Thanks for confirming. 🙂

Reply | Quote