Why do I have VMMS Checkpoint Errors at every start-up?

On every startup I see 7 errors associated with the 7 checkpoints I have for the various VMs installed on my PC. I have shown one of the errors below. These happen even though I do not start any of the VMs during the boot process.

I can open and run all my VMs normally so I am not aware of any problems. Should I just ignore these errors or is it a sign that something is wrong? Why would the checkpoints even be trying to load at startup?

Code:

Log Name:      Microsoft-Windows-Hyper-V-VMMS-Admin
Source:        Microsoft-Windows-Hyper-V-VMMS
Date:          02/11/2017 14:28:01
Event ID:      16320
Task Category: None
Level:         Error
Keywords:      
User:          SYSTEM
Computer:      DESKTOP-PH66QL2
Description:
Cannot load a checkpoint configuration: The process cannot access the file because it is being used by another process. (0x80070020). (Checkpoint ID C86220F1-0033-4A01-B9B9-25AB78D16902)
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>16320</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000000</Keywords>
    <TimeCreated SystemTime="2017-11-02T14:28:01.051680100Z" />
    <EventRecordID>423</EventRecordID>
    <Correlation />
    <Execution ProcessID="3776" ThreadID="6056" />
    <Channel>Microsoft-Windows-Hyper-V-VMMS-Admin</Channel>
    <Computer>DESKTOP-PH66QL2</Computer>
    <Security UserID="S-1-5-18" />
  </System>
  <UserData>
    <VmlEventLog xmlns="http://www.microsoft.com/Windows/Virtualization/Events">
      <VmName>
      </VmName>
      <VmId>C86220F1-0033-4A01-B9B9-25AB78D16902</VmId>
      <ErrorMessage>%%2147942432</ErrorMessage>
      <ErrorCode>0x80070020</ErrorCode>
    </VmlEventLog>
  </UserData>
</Event>

I'm still getting these errors and they have persisted with the April 2018 Update. @Kari do you have any idea?

For the record, these errors have stopped with the cumulative update KB4103721.