Windows 10: How to get rights to copy to Root of C:

Page 3 of 5 FirstFirst 12345 LastLast
  1.    11 Mar 2018 #21

    That doesn't make sense, that's far too large to have been created by installing Windows. That size is consistent with an OEM factory reset recovery partition.
    To the best of my memory, that is how the drive came when I bought this computer (Hewlett Packard Compact Pro, 6305 Small Form Factor)...used from a refurbisher/reseller, with Windows 10 Pro, preinstalled. I have had this computer a year, give or take...I do not remember anything about how the partitions were set-up on it when I got it...remember, I am 74 years old (my memory for details is fading).
    How many recovery partitions does disk management say you have? That may not be the one that Windows is actually using as the active recovery partition.
    One recovery partition. As the screenshot shows:
    Click image for larger version. 

Name:	screenshot.JPG 
Views:	52 
Size:	68.8 KB 
ID:	180553
    EDIT: your emachines ET1331G-03w was supplied with Windows 7 Ultimate 64-bit. That 16GB recovery partition will almost certainly contain the Windows 7 factory reset image. Windows 10 will likely be using another partition.
    That was my previous computer about a year or so ago...see above for my current computer.
      My ComputerSystem Spec


  2. Posts : 7,690
    10 Home x64 (1803) (10 Pro on 2nd pc)
       11 Mar 2018 #22

    dahermit said: View Post
    That was my previous computer about a year or so ago...
    Time you updated your system specs then :)

    Is disk 0 the only disk? Unfortunately your screenshot does not show all details, please read this tutorial.

    Disk Management - How to Post a Screenshot of

    your emachines ET1331G-03w HP 6305 was supplied with Windows 7 Ultimate Professional 64-bit Edition. https://www.cnet.com/products/hp-com...-series/specs/

    It still follows that the 16GB recovery partition would contain the Windows 7 factory reset image. Looks like the refurbisher/reseller upgraded the existing system (probably after a factory reset) to W10 rather than wiping the drive and doing a clean install.

    Windows may be using the existing 16GB recovery partition. With a system image already in there, there may not be enough room for Setup to update that to 1709.

    I suggest you shrink the C: partition by at least 600MB, preferably 1GB. If (as it seems) this is an MBR partitioned drive, there can be up to four partitions, so there can be one more. Setup should able to create a new recovery partition in the unallocated space you'd create at the end of the drive.

    As a precaution, it's always a good idea to make a system image of the existing drive before making changes like these.
    Last edited by Bree; 11 Mar 2018 at 19:10.
      My ComputersSystem Spec

  3.    12 Mar 2018 #23

    The plot thickens...on the current automatic attempt to install "important security upgrades on your pc", error code 0xc0000005 was generated.
      My ComputerSystem Spec

  4.    12 Mar 2018 #24

    I suggest you shrink the C: partition by at least 600MB, preferably 1GB. If (as it seems) this is an MBR partitioned drive, there can be up to four partitions, so there can be one more. Setup should able to create a new recovery partition in the unallocated space you'd create at the end of the drive.
    "Setup should able to create a new recovery partition..." A statement. I do not understand what I am supposed to do.

    As a precaution, it's always a good idea to make a system image of the existing drive before making changes like these.
    "system image"? I have a clone of the drive...is that a "system image"?
    Here is an expanded screenshot:
    Click image for larger version. 

Name:	screenshot.JPG 
Views:	42 
Size:	84.2 KB 
ID:	180598
      My ComputerSystem Spec


  5. Posts : 7,690
    10 Home x64 (1803) (10 Pro on 2nd pc)
       12 Mar 2018 #25

    dahermit said: View Post
    "system image"? I have a clone of the drive...is that a "system image"?
    Yes, that should be OK. I just wanted to be sure you could get back to a working unmodified system if any changes go badly wrong.
      My ComputersSystem Spec

  6.    12 Mar 2018 #26

    I suggest you shrink the C: partition by at least 600MB, preferably 1GB. If (as it seems) this is an MBR partitioned drive, there can be up to four partitions, so there can be one more. Setup should able to create a new recovery partition in the unallocated space you'd create at the end of the drive.
    I can figure out how to shrink the C: partition by 1GB.

    But have no idea how to proceed from there.
      My ComputerSystem Spec


  7. Posts : 7,690
    10 Home x64 (1803) (10 Pro on 2nd pc)
       12 Mar 2018 #27

    dahermit said: View Post
    I can figure out how to shrink the C: partition by 1GB.

    But have no idea how to proceed from there.
    Just try the update to 1709 again. If you shrink C: there will be 1GB unallocated space at the end of the drive. This is available for the upgrade to use if (as I suspect) it wants to create a recovery partition of its own (and currently fails due to lack of space).
      My ComputersSystem Spec

  8.    12 Mar 2018 #28

    Shrunk C: drive by 1GB. The screenshot of the drive as shrunk, I will attempt the Windows 10 upgrade tonight and see how it goes. I should know if it works tomorrow A.M.

    Click image for larger version. 

Name:	screenshot.JPG 
Views:	38 
Size:	84.0 KB 
ID:	180679
      My ComputerSystem Spec

  9.    13 Mar 2018 #29

    No joy. After download and reboot:
    "Feature update to Windows 10 version 1709- Error 0xc1900200"
      My ComputerSystem Spec

  10.    13 Mar 2018 #30

    dahermit said: View Post
    No joy. After download and reboot:
    "Feature update to Windows 10 version 1709- Error 0xc1900200"
    Nothing has worked. Windows Update Assistant still tries to download the 1709 update which still ends in error 0xc1900200.
    I have given up. The hell with it. Not worth the aggravation. I found a workaround on this forum where one can uninstall Windows Update Assistant, delete the folder: C:\Windows\UpdateAssistant, delete the tasks, Update Assistant and UpdateAssistantCalenderRun. According to the post where I found it, it keeps the Update Assistant from running and automatically trying to download the 1709 update.
      My ComputerSystem Spec


 
Page 3 of 5 FirstFirst 12345 LastLast

Related Threads
Solved Can't save to c: root in General Support
Get error message when I try to save a document or picture on c:\ 'A required privilege is not held by client.' Is there a way to fix this? Thank you.
Solved So is C: root unavailable per default? in User Accounts and Family Safety
I just came across an error regarding use rights in the root of C:, I can not place files there. I can create a folder and place files inside the folder, but not in root. Is this to be expected? I got error 0x80070522 when trying and found...
$xxx Folders in Root of C: in General Support
I was under the impression that these folders would go away or can be deleted, BUT !! Has been some time from 1511 build was installed. C:\ $Windows -W " - BT C:\ $sysreset Still have .log and .xml from 12/26/2015 in...
[Help] Need Admin. Rights to do a simply copy paste. in User Accounts and Family Safety
Why? Why do I need to confirm this? I'm the Admin in my system. Is there a way to disable this stuff? I got rid of UAC (thank God!) but now this. I saw this in Windows 8 a while back in a friend's laptop and I didn't understand it. Please, people...
Allow write access to C:/ root in User Accounts and Family Safety
Even though I am administrator on my PC, I do not have write access to C:/. (Win 10 Pro) Has anyone else had this problem, or does anyone know of a fix? Thanks
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 22:24.
Find Us