![]() Move VMs to other media - I've used two different external media - USB based drive and SD-Card, both enabled VMs to start up while Webroot was active - Not idealĢ. Hypothesis of Problem: Following upgrade to Windows build 1709, webroot forces VMWare workstation to create temporary locks on files on a "C:\" drive directory, preventing VM to load.ġ. Tested on Surface Pro 4 and Thinkpad T440p VM Workstation 12.5.x and Workstation 14 (according to other similar threads) Ok, I have confirmed someone else post that it appears to be an "undocumented feature" interaction between VMware workstation 12.5.x, Webroot and Windows 10 build 1709, I haven't traced the cause yet. I even copied the virtual machine folder to a root folder - same error.Īny insight would be greatly appreciated. I've given the all users administrative ("Full Control" ) rights to the C:\Users\VM1234\Documents\Virtual Machine folder. T10:14:58.439-04:00| vmx| I125: SNAPSHOT: SnapshotConfigInfoReadEx failed for file 'WIN_7_PRO.vmx': Insufficient permission to access the file (3) T10:14:58.439-04:00| vmx| I125: SNAPSHOT: SnapshotConfigInfoReadEx: Failed to lock 'C:\Users\VM1234\Documents\Virtual Machines\WIN_7_PRO\WIN_7_PRO.vmsd': 'Insufficient permission to access the file'. T10:14:58.438-04:00| vmx| W115: FILE: FileLockCreateEntryDirectory stat failure on 'C:\Users\VM1234\Documents\Virtual Machines\WIN_7_PRO\WIN_7_': Permission denied Since then VMWare Player throws an error every time I attempt to Power On the VM.Ĭould not get snapshot information: Insufficient permission to access the file. ![]() Version - Build Number: 5813279 (latest version)Ī couple of days ago, Windows 10 installed the Fall Creators Update on my PC. Application - VMWare Workstation 12 Player ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
January 2023
Categories |