Update docs

Documentation/guides/messages/apt2264.md

@@ -29,10 +29,15 @@ you could use
 Which is much shorter and much less likely to encounter path issues.
 
 However this is no always possible. Sometimes a project or a environment requires
-deep folder structures. In this case changing the location of the `$(BaseIntermediateOutputPath)`
-can solve these problems. In order for this to work the setting MUST be changed
-before ANY build or restore occurs. To do this you can make use of the MSBuild
-`Directory.Build.props` support.
+deep folder structures. In this case enabling long path support in Windows *might*
+be enough to get your project working. Details on how to do this can be found
+[here](https://learn.microsoft.com/windows/win32/fileio/maximum-file-path-limitation?tabs=registry#enable-long-paths-in-windows-10-version-1607-and-later).
+
+
+If long path support does not work changing the location of the
+`$(BaseIntermediateOutputPath)` can help solve these problems. In order for this
+to work the setting MUST be changed before ANY build or restore occurs. To do this
+you can make use of the MSBuild `Directory.Build.props` support.
 
 Creating a `Directory.Build.props` file in your solution or project directory which
 redefines the `$(BaseIntermediateOutputPath)` to somewhere nearer the root of the drive