Build error in plugin: [Adaptive unity build] Disabling PCH for excluded files

I’m running into the following error in a plugin’s code when trying to build a project after updating to Unreal 4.20:

1>[Adaptive unity build] Disabling PCH for excluded files. Set bAdaptiveUnityDisablesPCH to false in BuildConfiguration.xml to change this behavior. 
1>[Adaptive unity build] Excluded from MyUnrealPlugin unity file: MyFile.cpp

As an experiment, I disabled bAdaptiveUnityDisablesPCH as suggested by the error message, but doing so simply replaced the error above with this:

<>c.<PrintExceptionInfo>b__4_1: ==============================================================================
<>c.<PrintExceptionInfo>b__4_0: UnrealBuildTool: ERROR: UBT ERROR: Failed to produce item: E:\GameDirectory\UE4\MyGame\Plugins\MyPlugin\Intermediate\Build\Win64\UE4Editor\Development\MyPlugin\UE4Editor-MyPlugin.lib
<>c.<PrintExceptionInfo>b__4_0:                         (see ../Programs/UnrealBuildTool/Log.txt for full exception trace)
<>c.<PrintExceptionInfo>b__4_1: 
<>c.<PrintExceptionInfo>b__4_1: BuildException: UBT ERROR: Failed to produce item: E:\GameDirectory\UE4\MyGame\Plugins\MyPlugin\Intermediate\Build\Win64\UE4Editor\Development\MyPlugin\UE4Editor-MyPlugin.lib
<>c.<PrintExceptionInfo>b__4_1:    at UnrealBuildTool.ActionGraph.ExecuteActions(BuildConfiguration BuildConfiguration, List`1 ActionsToExecute, Boolean bIsRemoteCompile, String& ExecutorName, String TargetInfoForTelemetry, EHotReload HotReload) in D:\Build\++UE4\Sync\Saved\CsTools\Engine\Source\Programs\UnrealBuildTool\System\ActionGraph.cs:line 570
<>c.<PrintExceptionInfo>b__4_1:    at UnrealBuildTool.UnrealBuildTool.RunUBT(BuildConfiguration BuildConfiguration, String[] Arguments, FileReference ProjectFile, Boolean bCatchExceptions) in D:\Build\++UE4\Sync\Saved\CsTools\Engine\Source\Programs\UnrealBuildTool\UnrealBuildTool.cs:line 1673
<>c.<PrintExceptionInfo>b__4_1: ==============================================================================

Any thoughts on what I should do to correct this?

Thanks so much!

Turned out to be a red herring. The actual error was further above in the log output and involved a warning in Windows Kit 8 that had been upgraded to an error in Windows Kit 10.
Disabling these warnings, as in this context they’re not a thing that affects us, corrected it.

#pragma warning(disable:4668)	// x  is not defined as a preprocessor macro, replacing with '0' for '#if/#elif'
#pragma warning(disable:4005)	// 'TEXT': macro redefinition