Issue with accessing the root drive on Windows 10 without proper root drive permissions

F5F Stay Refreshed Software Operating Systems Issue with accessing the root drive on Windows 10 without proper root drive permissions

Issue with accessing the root drive on Windows 10 without proper root drive permissions

Issue with accessing the root drive on Windows 10 without proper root drive permissions

I

IIlIlIIllIlI
Member

61

06-24-2016, 09:33 AM

#1

I own three storage devices—C, D, and E—and completed a fresh Windows 10 setup on drive C today. My Windows account is the sole one with full admin rights. However, I’m still unable to upload files to the root D: folder, receiving the error “A required privilege is not held by the client.” I’ve tried numerous troubleshooting steps, such as checking D: properties, adjusting security settings, changing the Owner to my account, creating a custom permissions profile with full admin rights, and even switching to administrator privileges. The problem persists only on the D: drive. I spoke with a Microsoft support representative who suggested a possible bug in Windows profile setup and recommended reinstalling Windows 7 followed by an upgrade install instead of a clean install from the same image. I’m hoping this approach might resolve the issue, but I’ve already tried all standard solutions.

I

IIlIlIIllIlI

06-24-2016, 09:33 AM #1

I own three storage devices—C, D, and E—and completed a fresh Windows 10 setup on drive C today. My Windows account is the sole one with full admin rights. However, I’m still unable to upload files to the root D: folder, receiving the error “A required privilege is not held by the client.” I’ve tried numerous troubleshooting steps, such as checking D: properties, adjusting security settings, changing the Owner to my account, creating a custom permissions profile with full admin rights, and even switching to administrator privileges. The problem persists only on the D: drive. I spoke with a Microsoft support representative who suggested a possible bug in Windows profile setup and recommended reinstalling Windows 7 followed by an upgrade install instead of a clean install from the same image. I’m hoping this approach might resolve the issue, but I’ve already tried all standard solutions.