Guess what sports fans?
On two of our PC's (the ones that DIDN'T have any problem installing KB4054517), they both got that same error code 0x80070643 when installing the "new" patch KB4056892. However, the build number did increment, so we're treating this as another false negative.
Ironically, our other two PC's that DID get the error installing KB4054517 in December, did NOT get any error codes when installing KB4056892. GO FIGURE !
In all cases, when one of our computers reports the 0x80070643 error during the installation of either 4054517 or 4056892, that computer immediately ceases to be able to display other PC's on our Ethernet/LAN network in File Explorer -> Network, although the PC's ARE actually accessible. Strangely, wireless PC's and printers ARE still visible in File Explorer.
GO FIGURE 2.0 !!
Also, lag times between requesting a print and hearing the printer start up increased dramatically as each of our PC's installed the fall creators update.
WHY IS IT THAT WHILE MICROSOFT IS BUSY CRAMMING IN A BUNCH OF NEW CAPABILITIES INTO EACH W10 FEATURE UPDATE THAT I'LL NEVER USE, THEY ARE ALSO BREAKING OR DEGRADING BASIC FUNCTIONS LIKE NETWORKING AND PRINTING AND UPDATING OUR OS?