INTELLISENSE NOT WORKING ON MICROSOFT .NET ASSEMBLIES

I observe the same issue here (with 2.1 or 3.0 assemblies and .NET Framework 4.6.1), using the Roslyn parser.
The following analysis was done with the "SnippetParser" sample: I added this code to a public method in the "VBMethodParser" class:
RoslynSolution rosSol = (RoslynSolution)this.RoslynSolution;
string strAssemblyPathAndName = rosSol.ResolveAssemblyName("mscorlib");

Project project = rosSol.Solution.GetProject(rosSol.ProjectId);
MetadataReference metaRef = project.MetadataReferences.FirstOrDefault(meta => meta.Display.ToLower() == strAssemblyPathAndName.ToLower());
PropertyInfo pi = metaRef.GetType().GetProperty("DocumentationProvider", BindingFlags.Instance | BindingFlags.NonPublic);
RoslynDocumentationProvider rosDocProv = (RoslynDocumentationProvider)pi.GetValue(metaRef);

MethodInfo mi = rosDocProv.GetType().GetMethod("LoadDescriptions", BindingFlags.Instance | BindingFlags.NonPublic);
object descInfo = mi.Invoke(rosDocProv, new object[] { CultureInfo.CurrentCulture });
MethodInfo mi2 = descInfo.GetType().GetMethod("LoadDescriptions", BindingFlags.Instance | BindingFlags.NonPublic);
mi2.Invoke(descInfo, null);
The "documentation Provider" properties:
RoslynDocumentationProvider.SystemPath = C:\Windows\Microsoft.NET\Framework\v4.0.30319\
RoslynDocumentationProvider.FullPath = C:\Windows\Microsoft.NET\Framework\v4.0.30319\mscorlib.dll

The "descInfo" variable (Alternet.Syntax.Parsers.Roslyn.CodeCompletion.RoslynDocumentationProvider.DescriptionInfo) has this content:
"SystemPaths":
C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5\
C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.0\
C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v3.5\
Property "Descriptions" is empty.
In "C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.0", there is a mscorlib.xml with this content:


The redirected path contains the full "mscorlib.xml".
Do you have any idea?
I found this Roslyn bug report, which sounds related:
https://github.com/dotnet/roslyn/issues/13529
Best regards
Wolfgang