New
#80
That particular error has been around a long time, and is almost always seen with Windows Update. We were seeing it back in the days of Win7.
https://support.microsoft.com/en-us/...-or-0x80070003
I do know this - I was using Edge to download all the ISOs for Creator's update from Download Windows 10 Insider Preview Advanced (and I mean all - including SDK, ADK, etc.) and after I had downloaded about 6 of them, I started getting the following error a very similar error, where it told me to contact Microsoft Support Center with a similar error code and also another ID of some sort. I just tried it again and it is letting me download again, but it was not early this morning before 16170 was released.
I wonder if that error is actually the exact same thing as it was back in the Win7 days - WU simply cannot establish a reliable connection to the servers to download the update because it is just over worked....
On a different note - yesterday I spent a good part of the day evaluating my system performance, wrt whether or not I should use the optimized, more recent and WHQL-certified driver for my Marvell 9128 chipset that runs my 2 SATA 6.0 GBps ports. So, after making the decision to go ahead and take the plunge, I used Snappy Driver Installer to update all of the other drivers that Windows had not done since my clean install last month.
Upon having 16170 installed, I ran SDI again - no drivers were out of date.
IOW, 16170 did not mess with my drivers like previous builds have once I've installed my own 3rd party drivers.