Can't add new vhd to an existing VM. "The disk is already connected to the virtual machine" error

Hello,

I made a new 1TB fixed vhd, and trying to add it to a VM on Hyper-v 2012. I get the following error (which is not true, this disk is brand new and is not attached to any machine). I googled this and immediately came to a link about a bug in Hyper-v and a hotfix available (https://support.microsoft.com/en-us/kb/2836402). But before going with hotfix I wanted to see what other people think, and if this is really something that is related to the bug, or could be resolved in another way. Please let me know.

I tried to add the new vhd while the VM was running, and as a third disk to an existing virtual SCSI controller. If I shut the VM down and add new SCSI controller and add this disk as the only disk on the controller, do you think that could help?

[Window Title]
Settings

[Main Instruction]
Error applying Hard Drive changes

[Content]
'HA-computer1' failed to add resources to 'HA-computer1'.

Cannot add 'C:\ClusterStorage\Volume9\VOS\computer1\VirtualHardDisks\vcomputer1-archives-fixed.vhd'. The disk is already connected to the virtual machine 'HA-computer1'. (Virtual machine ID A82BE3CA-16E5-4C14-B8C5-2477476B4E06)

[Expanded Information]
'HA-computer1' failed to add resources. (Virtual machine ID A82BE3CA-16E5-4C14-B8C5-2477476B4E06)

Cannot add 'C:\ClusterStorage\Volume9\VOS\computer1\VirtualHardDisks\vcomputer1-archives-fixed.vhd'. The disk is already connected to the virtual machine 'HA-computer1'. (Virtual machine ID A82BE3CA-16E5-4C14-B8C5-2477476B4E06)

[^] Hide details  [Close]

Here is the event id that I also see:

Log Name:      Microsoft-Windows-Hyper-V-VMMS-Admin
Source:        Microsoft-Windows-Hyper-V-VMMS
Date:          5/4/2016 6:21:11 PM
Event ID:      23016
Task Category: None
Level:         Error
Keywords:      
User:          TheCompany\administrator
Computer:      host1.TheCompany.com
Description:
Cannot add 'C:\ClusterStorage\Volume9\VOS\vm123abc\VirtualHardDisks\vvm123abc2-archives-fixed.vhd'. The disk is already connected to the virtual machine 'HA-vm123abc'. (Virtual machine ID A82BE3CA-16E5-4C14-B8C5-2477476B4E06)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Hyper-V-VMMS" Guid="{6066F867-7CA1-4418-85FD-36E3F9C0600C}" />
    <EventID>23016</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x4000000000000000</Keywords>
    <TimeCreated SystemTime="2016-05-05T01:21:11.157222400Z" />
    <EventRecordID>18030</EventRecordID>
    <Correlation />
    <Execution ProcessID="9308" ThreadID="8488" />
    <Channel>Microsoft-Windows-Hyper-V-VMMS-Admin</Channel>
    <Computer>host1.TheCompany.com</Computer>
    <Security UserID="S-1-5-21-319643702-1149925883-2739845290-500" />
  </System>
  <UserData>
    <VmlEventLog xmlns:auto-ns2="http://schemas.microsoft.com/win/2004/08/events" xmlns="http://www.microsoft.com/Windows/Virtualization/Events">
      <VmName>HA-vm123abc</VmName>
      <VmId>A82BE3CA-16E5-4C14-B8C5-2477476B4E06</VmId>
      <Parameter0>C:\ClusterStorage\Volume9\VOS\vm123abc\VirtualHardDisks\vvm123abc2-archives-fixed.vhd</Parameter0>
    </VmlEventLog>
  </UserData>
</Event>