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).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.
One recovery partition. As the screenshot shows: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.
That was my previous computer about a year or so ago...see above for my current computer.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.
Windows 10: How to get rights to copy to Root of C:
-
New 11 Mar 2018 #21
-
-
New 11 Mar 2018 #22
Time you updated your system specs thendahermit said:
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
youremachines ET1331G-03wHP 6305 was supplied with Windows 7UltimateProfessional 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.
-
New 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.
-
-
New 12 Mar 2018 #24
"Setup should able to create a new recovery partition..." A statement. I do not understand what I am supposed to do.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.
"system image"? I have a clone of the drive...is that a "system image"?As a precaution, it's always a good idea to make a system image of the existing drive before making changes like these.
Here is an expanded screenshot:
-
New 12 Mar 2018 #25
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.dahermit said:
-
New 12 Mar 2018 #26
I can figure out how to shrink the C: partition by 1GB.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.
But have no idea how to proceed from there.
-
New 12 Mar 2018 #27
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).dahermit said:
Quote
New
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.
New
13 Mar 2018
#29
No joy. After download and reboot:
"Feature update to Windows 10 version 1709- Error 0xc1900200"
New
13 Mar 2018
#30
Nothing has worked. Windows Update Assistant still tries to download the 1709 update which still ends in error 0xc1900200.dahermit said:
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.
Related Threads
Can't save to c: root in General Support So is C: root unavailable per default? in User Accounts and Family Safety $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
