This is another post for my own use, but others may find it helpful.

The problem is Windows update KB4023057, which fails to install.  It is a re-release of a December update of the same title, and the problem is that it was likely already installed.

Note that Build 1809 and any subsequent updates will not install until this issue is resolved.

You’ll see the following message in Windows Updates:

Despite the convoluted (and sometimes dangerous) “solutions” you’ll find on the internet, the answer is pretty obvious: uninstall the previous version and let Windows Update install the new version. You can confirm that this is the issue in the Windows Event Viewer under Administrative Events:

Note that unlike most Windows updates, this package appears in Control Panel under Programs and Features. Select it and then uninstall.

Then reboot, go to Windows update, and check for new packages. This update should install correctly.

This is a tech post primarily for my own use. It involves a change to the Windows 10 Registry, and it is not for newbies. You can turn your machine into a doorstop if you get it wrong.

I’ve started to notice repeated errors in the Windows Event Logs following installation of the Windows 10 Fall Creators Update. This issue occurred in four machines following this update, and it interferes with the startup of a number of services and devices:

The source of the problem lies in a bad key in Windows Registry, apparently due to a URL change at Microsoft.

Registry Key:

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Device Metadata

Incorrect Value:

http://go.microsoft.com/fwlink/?LinkID=252669&clcid=0x409

Change To:

http://dmd.metaservices.microsoft.com/dms/metadata.svc

Posted this mainly for my own use. A client had a commercial business management application that could not “see” legitimately mapped drives, in this case, to select a target for a data backup. This registry fix resolved the issue.

Ran into a little glitch with two unrelated third party applications that relates to mapped network drives. Right after the Windows 10 upgrade, mapped drives were still in place, and the contents of these directories were completely visible from Explorer on the host machine, but not from inside the application software, as if they didn’t exist.

The solution is a missing Windows registry key at:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System.

Look for a key named “EnableLinkedConnections” and a DWORD data value of 1.

If this key is not present, you may have to add it manually. Spelling is strict, so be very careful.

Then reboot. Repeat for each workstation.

You may also have to remap the drive on the “server” machine.

That worked for me.