Has anyone had any success recovering a virtual Hyper-V client via BMR?

In this scenario I'm not using NMM and treating the Hyper-V client as a seperate entity.

Our environment in primarily VMWare and we're able to use the same process successfully however when recovering the Hyper-V virtual client we get the Windows Server 2012 BSOD stating a Critical Process has died and then continues to the Windows Boot Manager with:

Status: 0xc000000f

Info: A required device isn't connected or can't be accessed.

I've tried a few procedures where I boot from CD and try to fix the boot blk which looks like it works but final command fails as it can't find any bootable device.

There seems to be very little info regarding this situation as it's primarily dominated by talk about NMM I can't find anything to say it's unsupported either so will soldier on for a bit longer.

Some details:

Client: NW8.1.1 on Windows Server 2012 R2 (Hyper-V Gen2)

Host: Windows Server 2012 R2

NetWorker Server: 8.1.1 on Windows Server 2012 R2

Thanks in advance

Andrew