This sounds like an issue with writer itself so I would suggest MS case. Having both might be good idea and MS likes to push back when not using their software so there might be some ping-ping before someone really takes a closer look at what is going on.
ble1
4 Operator
•
14.4K Posts
0
August 23rd, 2018 07:00
This sounds like an issue with writer itself so I would suggest MS case. Having both might be good idea and MS likes to push back when not using their software so there might be some ping-ping before someone really takes a closer look at what is going on.
ttobey
32 Posts
0
August 28th, 2018 10:00
With hyper-v vss writer failed have you checked the hyper-v-vmms\admin event log?
That will show the VM(s) that is causing an issue. Then you can trouble shoot each VM that has an issue.