The problem is quite easy to reproduce:
1. Map a .VMDK file belonging to VM to the host (any letter) using "File->Map Virtual Disk" (any drive letter, read-only or write mode).
2. Unmap it.
Get a nice Win 10 BSOD.
↧
Channel:
VMware Communities: Message List
X
Are you the publisher?
Claim or
contact us
about this channel.
X
0
Channel Details:
- Title: VMware Communities: Message List
- Channel Number: 11993333
- Language: English
- Registered On: April 15, 2013, 6:25 am
- Number of Articles: 217440
- Latest Snapshot: November 6, 2020, 8:31 am
- RSS URL: http://communities.vmware.com/community/feeds/messages?rssusername=einstein-a-go-go
- Publisher: https://communities.vmware.com/?view=discussions
- Description: Most recent forum messages
- Catalog: //communities1179.rssing.com/catalog.php?indx=11993333
© 2025 //www.rssing.com