No mouse black screen when connecting via RDP to Windows 2012 R2 hyper v guest

We have a client with Windows 2012 R2 Hyper V host server and 3 virtual machines AD AP and DN
A couple of weeks ago the client starting getting a black screen when using RDP to connect to one the virtual machines DN
The other machines work fine. Teamviewer to DN the mouse works fine.
I rolled back to a backup a couple of days before and the issue went away for a week, then appeared again.
Check windows updates and nothing was recently installed.

When attempting to RDP the system log below is generated. RDP tries to utilise this PS2 mouse driver which does not load and hangs the session just giving a black screen.

Log Name:      System
Source:        Microsoft-Windows-Kernel-PnP
Date:          7/27/2015 6:05:03 PM
Event ID:      219
Task Category: (212)
Level:         Warning
User:          SYSTEM
Computer:      DN.domain.local
The driver \Driver\mouclass failed to load for the device TERMINPUT_BUS\UMB\2&2c22bcc9&0&Session2Mouse1.

Connecting to the VM through hyperv manager has similar issue, screen shows and keyboard but no mouse.
Device manager shows other devices
Microsoft PS/2 Mouse
Standard PS/2 Keyboard
with warning message the drivers for this device are not installed.
Uninstalling and attempting to rescan hardware does not resolve - they they show as Unknown Device
running sfc scan did not fix (thinking maybe corrupt driver)
Trying to reinstall integration components says the same version is already installed.
Any other ideas before completely rebuilding the VM?
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Robin CMSenior Security and Infrastructure EngineerCommented:
Are you seeing the following devices and associated drivers files showing in Device Manager?
Human Interface Devices
  Microsoft Hyper-V Input
Mice and other pointing devices
  Remote Desktop Mouse Device
  Microsoft PS/2 Mouse
  HID-compliant mouse

If you are, are any of them disabled?
Also, open regedit and go to HKLM\System\CurrentControlSet\Services and check for each of the .sys file names (minus the .sys bit), e.g. i8042prt and ensure the Start DWORD value is set to 3.
Not all the hid* ones will have entries, but you should additionally have a hidserv with Start set to 3.
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
What kind of mouse and keyboard are attached? If PS/2 for both then flip them out for a USB pair and see if that resolves the problem.

Is the VM a P2V? That is, was it once on physical hardware and now running in a virtual machine?
KingComputerAuthor Commented:
We ended up trashing the VM and rebuilding. Its been fine since.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
Good to hear it was not a critical workload. :)
KingComputerAuthor Commented:
It fixed the issue.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.