This is caused by .NET 2.0

I resolved it by canceling the prompt and proceeding with the upgrade (which broke .NET 2.0) then using the .NET cleanup tool
...