We just got our 'second Tuesday' updates () on our W10 machine running V1709. The cumulative update KB4054517 failed with an error code of 0x80070643. The only thing we've discovered so far is that this machine will not display our other 3 PC's on the network when we select 'Network' in File Explorer.
But all three other PC's can 'see' and access this PC no problem. And we ran a batch backup job on the affected PC and it was able to copy files from all three other PC's. So it's just a display problem in File Explorer ->Network.
Problem Installation of Microsoft Patch KB948109 fails during SQL or Backup Exec Database update Solution. May 27, 2016 Microsoft patch KB3148812 (Link to the KB article has been removed by Microsoft), has an know issue when you have a WSUS server installed on you MS Windows. Install SQL Server from the Command Prompt. Before you install a SQL Server Database Engine failover. The valid values are 'MU' to search Microsoft Update.
We've run Windows Update Troubleshooter and told it to Apply Fixes whenever it prompted us, and it DID report that it found and fixed three issues: Potential Windows Update Database Error - Fixed Windows Update Component Must Be Repaired - Fixed Check for pending updates - Fixed After exiting the Troubleshooter, we clicked on 'Check for Updates' again and it said 'Your device is up to date'. We noticed that the build number after the 'failed' update had changed to 16299.125. So the system thinks it DID install something newer than it had before, but Windows Update thinks the cumulative patch failed to install.
BTW, the other 'Second Tuesday' patches (Adobe Flash KB4053577 and Windows Malicious Software Removal Tool KB890830) both installed OK. Hi, The issue you're experiencing with updating your Windows might be due to corrupted components or files. That being said, have you tried restoring your PC from a recent restore point or performing a System Restore? This will take your PC back to the time you haven't installed the update yet. If you haven't tried it yet, you may consider it by following the steps under the Restore from a system restore point selection found. After doing a system restore, you may try installing the update again.
Let us know how it worked for you. Based on the experiences of the other people who have already replied on this thread (including a clean install and re-update that failed again!), we don’t think performing a RESTORE and re-running Windows Update would result in any different outcome. After installing the Quality update on 4 different PC’s, we believe the installation problems are being caused by different versions of the Windows Update Client software.
Please read the following carefully to see why we have reached this conclusion. PC BUILD NUMBERS BEFORE AND AFTER QUALITY UPDATES We have 4 Windows 10 PC’s.
Two of them installed the Fall Creators update (V1709) on 11/14/17, and the other two installed the Fall Creators Update on 12/9/17. The V1709 Build number was NOT the same between these two groups. The two PC’s that had the later Build of V1709 did NOT report the installation error on the Quality Update, and they appear to be functioning normally. Fruity L Studio 9.055 Plus;).
Build Status Before and After Quality update: Computers A and B – Version 1709 Build 16299. 64 (Installed ) updated to Build 16299.125, but reported an installation error code of 0x80070643 on the KB4054517 Cumulative Update. Computers C and D – Version 1709 Build 16299. 98 (Installed 12/9/2017) updated to Build 16299.125 without any installation errors reported on any of the 12/12/17 Quality updates. Note that even for the two PC’s reporting error code 0x80070643, they ALL now display the SAME Build number (16299.125) after the Quality update. DIFFERENCES IN QUALITY UPDATE PROCESSES BASED ON PREVIOUS BUILD NUMBER During the Quality Updates, we observed VERY significant differences in the update sequence and messaging, depending on the pre-update Build number. This leads us to believe that the Windows Update software being used was different for Build 16299.64 versus 16299.98.
Here are some of the major differences we observed between the “.64” updates and the “.98” updates: DIFFERENCES IN UPDATE PROCESS The “.98” updates followed the “normal” progression we’ve observed over the last two years for cumulative updates – namely after pressing “Restart Now”, it works on updates through 30%, does a Restart, works on updates 30-100%, then displays lock screen. The “.64” updates followed a much different sequence and displayed a host of messages that were new to us. They worked on updates through 30%, then did a Restart, then displayed messages like “Stage 1 of 2 – Working on Features”, “Stage 1 of 2 – Getting Windows Ready”, “Stage 2 of 2 – Setting Up Updates”, and “Stage 2 of 2 – Working on Updates” and then did ANOTHER Restart and worked on updates from 30-100%.