Suspending workaround for a bug in Windows 10 version 1803 (April 2018 update), fixed in version 1809 (October 2018 update), that caused drag&drop downloads to Windows Explorer end in a wrong folder.

(cherry picked from commit 8a45844e2c4e41b2cb84c4f4be8adac541bfea87)

# Conflicts:
#	source/windows/WinConfiguration.cpp

Source commit: 62917f136b66c88dbf75f744cd8c00c91dc7c4a7

source/forms/CustomScpExplorer.cpp

@@ -158,7 +158,8 @@ public:
 //---------------------------------------------------------------------------
 bool UseDirectoryMonitorDragDrop()
 {
-  return IsUWP() || (GetWindowsBuild() >= 17134);
+  int Build = GetWindowsBuild();
+  return IsUWP() || ((Build >= 17134) && (Build < 17763));
 }
 //---------------------------------------------------------------------------
 __fastcall TCustomScpExplorerForm::TCustomScpExplorerForm(TComponent* Owner):
@@ -6649,7 +6650,8 @@ void __fastcall TCustomScpExplorerForm::DDExtInitDrag(TFileList * FileList,
 
   Created = true;
 
-  if ((IsUWP() && !WinConfiguration->IsDDExtRunning()) || (GetWindowsBuild() >= 17134))
+  int Build = GetWindowsBuild();
+  if ((IsUWP() && !WinConfiguration->IsDDExtRunning()) || ((Build >= 17134) && (Build < 17763)))
   {
     FDragFakeMonitors = new TObjectList();
     for (char Drive = FirstDrive; Drive <= LastDrive; Drive++)