diff --git a/releases/net471/KnownIssues/523633 - Setup - OS upgrade to Windows 10 gets the product in bad state.md b/releases/net471/KnownIssues/523633 - Setup - OS upgrade to Windows 10 gets the product in bad state.md
index 920a78b..0d4c008 100644
--- a/releases/net471/KnownIssues/523633 - Setup - OS upgrade to Windows 10 gets the product in bad state.md	
+++ b/releases/net471/KnownIssues/523633 - Setup - OS upgrade to Windows 10 gets the product in bad state.md	
@@ -12,10 +12,10 @@ Consider the following scenario:
 Note:  Windows 10 Anniversary Update (version 1607) comes pre-installed with .NET Framework 4.6.2, and you can install .NET 4.7.1 on it using an offline (or web) installer. Similarly, Windows 10 Creators Update (version 1703) comes pre-installed with .NET Framework 4.7.
 
 ## Cause
-This issue occurs because the .NET Framework 4.7.1 product installation gets into a corrupted state after the OS upgrade.  The OS upgrade preserves all the .NET 4.7.1 assemblies in the GAC as is, but the in-box assemblies are reverted to the in-box version (4.7). Due to this mixed state, the .NET applications exhibit unexpected behaviors.
+This issue occurs because the .NET Framework 4.7.1 product installation gets into a corrupted state after the OS upgrade.  The OS upgrade preserves all the .NET Framework 4.7.1 assemblies in the GAC as is, but the in-box assemblies are reverted to the in-box version (4.7). Due to this mixed state, the .NET applications exhibit unexpected behaviors.
 
 ## Impact
-Applications may experience unexpected crashes in certain scenarios.
+Applications may experience unexpected crashes in certain scenarios. For example, Visual Studio will experience a crash soon after opening a C# or VB project when .NET Framework is in this corrupted state.
 
 Note: This issue does not occur when you do an upgrade from Windows 10 Anniversary Update (version 1607) to Windows 10 Fall Creators Update (version 1709).