Insufficient permission to access file. (Windows 10)

[JML54]

The error (Insufficient permission to access file.) continues to occur, regardless of what is attempted.

Base Configuration:

• Windows 10 v1703 (with current updates)
• RAM: 32GB
• OnLine Storage: 20.5TB
• VM Client Location: Non-OS Drive
  • D:\Virtual Machines\Windows 10 x64

The connection of the Hard Drive is intended to be for a specific partition which shall be shared between 2+ VM Clients.

Initial setup is failing with the above message.

Instructions used to build the accessible Hard Drive were pulled from the Workstation Pro 12 User Guide, Chapter 8; Section: Adding a Physical Disk to a Virtual Machine; Sub-Section: Prepare to Use a Physical Disk or Unused Partition, Procedure(1).

The HDD drive used is not defined as a system drive, not defined as an accessible drive by the OS, and is configured as defined in the Procedure(1) specific to Windows 10.

A multitude of attempts have been made, using the same steps as defined.

What is wrong with the approach, and why is it not working.

I have attached an image which depicts the configuration following the layout defined in the procedures used.

[RDPetruska · Accepted solution]

Have you run Workstation "As Admin" when trying to create the physical disks?

[JML54]

Yes.

"Add Disk" built using Admin profile.

Launch of Client using Admin profile.

End-state shall be Client run as standard user, though testing has not moved that far yet.

End-state intended to protect Host from current virus/malware/ransomware now proliferating around the world.

Client's not intended to operate with confidential information, and may be created should infection occur.

Storage space needed though for MS Office Pro suite of applications, and working for client.

Jim

[JML54]

Okay - my bad...

Yes, I'd used my Administrator profile while doing the work.

No, I did not run VMWare "As Administrator"...

Took a bit for it to dawn on me what was being asked.

Conclusion: Multi-tasking doesn't work well for me as it used to...

[JML54]

On a more serious note...

I want to thank you for your time, guidance and help!

It was just the prompt I needed, and the work was completed and with the expected results (it works).

Further testing is now needed as I shall determine if the drive is accessible by my standard profile, when starting VMWare under normal log-in.

Thanks again.

Jim

[RDPetruska]

I believe you can run Workstation normally, not launch it "as admin".  You will get a UAC prompt when starting that VM each time, I believe, due to the physical disk - this is expected behavior according to other posts I have read here on the forum.

[JML54]

Don't know if you received my email - - -

I do want to thank you for your recommendation and support!

Sadly, though, VMWare Workstation Pro only permits access to the HDD (defined from the partition) to be accessed when VMWare is launched "Run as Administrator".

I've checked the authorities on the drive, in both VMWare and in Disk Management.

The security settings appear to be good, in particular for both Group authorities, and explicitly define for user profile authorities.

The authorities were setup prior to the creation of the HDD for VMWare, assigned to a full disk partition.

In this case, as long as I access the partition (Disk 1, Partition 2) under a "Run as administrator" launch, everything works great, up to and including the encryption using BitLocker.

Unfortunately, the client launch in a VMWare host session, NOT launched as "Run as administrator" fails every time with the message as shown in the subject line here.

Since the root-cause for this thread was answered, I'll be launching a new thread, and maybe another kind member shall provide the time and guidance necessary to overcome this next step in the evolution of this effort.

Thank you again!

Jim