S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Nov 5, 2019 #21 Try the following command: BCDBOOT C:\WINDOWS and press Enter.
P PeterLander Active member Joined Nov 4, 2019 Posts 36 Nov 5, 2019 #22 Got "Failure when attempting to copy boot files"
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Nov 5, 2019 #23 Try the following: How to fix the Failure when attempting to copy boot files error
P PeterLander Active member Joined Nov 4, 2019 Posts 36 Nov 5, 2019 #24 Followed the first of those instructions (ie BCDBOOT etc). Error was "Failure when attempting to copy boot files"
Followed the first of those instructions (ie BCDBOOT etc). Error was "Failure when attempting to copy boot files"
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Nov 5, 2019 #25 Okay, try the second one then.
P PeterLander Active member Joined Nov 4, 2019 Posts 36 Nov 5, 2019 #26 I have 7 partitions ... 1. Recovery 2. System 3. Reserved 4. Primary 5. Recovery 6. Primary 7. Primary. So, "select the partition that includes the Windows installation " would be partition 2? Or the first "Primary" (Partition 4)?
I have 7 partitions ... 1. Recovery 2. System 3. Reserved 4. Primary 5. Recovery 6. Primary 7. Primary. So, "select the partition that includes the Windows installation " would be partition 2? Or the first "Primary" (Partition 4)?
P PeterLander Active member Joined Nov 4, 2019 Posts 36 Nov 5, 2019 #28 From 1 to 7 they are 1023MB, 360MB, 128MB, 199GB, 450MB, 1645GB, 15GB. If they look strange, I can only say that this is an inherited machine
From 1 to 7 they are 1023MB, 360MB, 128MB, 199GB, 450MB, 1645GB, 15GB. If they look strange, I can only say that this is an inherited machine
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Nov 5, 2019 #29 The one with 450 mb is the one we are looking for.
P PeterLander Active member Joined Nov 4, 2019 Posts 36 Nov 5, 2019 #30 Partition 5 selected OK. But "active" gave me the error "selected disk is not a fixed MBR disk
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Nov 5, 2019 #31 IMO, at this point, it's time to test the drive and if it passes the health checks, start fresh.
P PeterLander Active member Joined Nov 4, 2019 Posts 36 Nov 5, 2019 #32 So the best I can expect is to buy a USB stick, loss of data, purchase a new Win10 (this PC was gifted - I have no CDs), loss of specialised apps (some will be difficult to recover) BUT maybe, the drive will not need replacing?
So the best I can expect is to buy a USB stick, loss of data, purchase a new Win10 (this PC was gifted - I have no CDs), loss of specialised apps (some will be difficult to recover) BUT maybe, the drive will not need replacing?
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Nov 5, 2019 #33 You will likely be able to recover the data with the stick. As for the rest, pretty much, yes. Unless someone has a better idea.
You will likely be able to recover the data with the stick. As for the rest, pretty much, yes. Unless someone has a better idea.
P PeterLander Active member Joined Nov 4, 2019 Posts 36 Nov 5, 2019 #34 Is there no way to stop the thing from trying to complete the MS update? I keep coming back to that. I have a feeling that a startup that ignored the changes and got right away into loading Windows would work just fine. Is there no registry key saying "continue with update X" that can be turned off via regedit? Grasping at straws, but as a financially poor 78 year old pensioner, I'm hoping to avoid expense as much as I can.
Is there no way to stop the thing from trying to complete the MS update? I keep coming back to that. I have a feeling that a startup that ignored the changes and got right away into loading Windows would work just fine. Is there no registry key saying "continue with update X" that can be turned off via regedit? Grasping at straws, but as a financially poor 78 year old pensioner, I'm hoping to avoid expense as much as I can.
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Nov 5, 2019 #35 Not that I'm aware of, at least not in this state of things. Before you go out and buy stuff, wait for the input of other people. I've done some basic troubleshooting on my end and sadly was unsuccessful. Best of luck.
Not that I'm aware of, at least not in this state of things. Before you go out and buy stuff, wait for the input of other people. I've done some basic troubleshooting on my end and sadly was unsuccessful. Best of luck.
P PeterLander Active member Joined Nov 4, 2019 Posts 36 Nov 5, 2019 #36 OK. Thanks. I'll resume tomorrow. I will hang on to that command line overnight ... it was very difficult to get. I'll use the night to see if I can discover what triggers the "resume updating" activity. It might not be in the registry, but it must be somewhere.
OK. Thanks. I'll resume tomorrow. I will hang on to that command line overnight ... it was very difficult to get. I'll use the night to see if I can discover what triggers the "resume updating" activity. It might not be in the registry, but it must be somewhere.
P PeterLander Active member Joined Nov 4, 2019 Posts 36 Nov 5, 2019 #37 I ran CHKDSK. It found a very large number of (deleting extended attribute set due to presence of reparse point) errors ... and a few other errors. All errors were allegedly fixed. It was too fast. Maybe 10 minutes. I then reran CHKDSK C: /R /F /S. Been going 45 mins and is 1/5th through. I will let it run while I sleep. But what seems to have been confirmed so far is 1] The Windows drive is indeed C: and 2] There does not appear to be any reason to suspect HDD failure as the root cause of my woes.
I ran CHKDSK. It found a very large number of (deleting extended attribute set due to presence of reparse point) errors ... and a few other errors. All errors were allegedly fixed. It was too fast. Maybe 10 minutes. I then reran CHKDSK C: /R /F /S. Been going 45 mins and is 1/5th through. I will let it run while I sleep. But what seems to have been confirmed so far is 1] The Windows drive is indeed C: and 2] There does not appear to be any reason to suspect HDD failure as the root cause of my woes.
P PeterLander Active member Joined Nov 4, 2019 Posts 36 Nov 5, 2019 #38 Completed CHKDSK. Not one single error. Nada. There is no reason to suspect HDD trouble. I am at my original request ... How do I prevent Win10 from trying to complete an installation at boot time? I have admin rights. I have a command line. I have notepad, regedit, and all those commandline tools. All I really really need now is that little tweak which obliterates Win10's memory of a need to complete an install. Anybody?
Completed CHKDSK. Not one single error. Nada. There is no reason to suspect HDD trouble. I am at my original request ... How do I prevent Win10 from trying to complete an installation at boot time? I have admin rights. I have a command line. I have notepad, regedit, and all those commandline tools. All I really really need now is that little tweak which obliterates Win10's memory of a need to complete an install. Anybody?
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Nov 5, 2019 #39 It found a very large number of (deleting extended attribute set due to presence of reparse point) errors ... and a few other errors. Click to expand... This really is a sign of something being wrong. Under normal circumstances, there really should not be a lot of things listed.
It found a very large number of (deleting extended attribute set due to presence of reparse point) errors ... and a few other errors. Click to expand... This really is a sign of something being wrong. Under normal circumstances, there really should not be a lot of things listed.
P PeterLander Active member Joined Nov 4, 2019 Posts 36 Nov 5, 2019 #40 There is very limited documentation for this error. Out of the dozen I studied, only ONE satisfied the user's problem. "Disable fast startup in Windows 10. This mode is hibernate like that leaves the disk in a state that Windows 7 does not understand. This causes it to run CHKDSK. " Several users reported that the problem appeared when either 1) running dual-boot Win7-Win10 systems OR 2) when moving back and forth from Win7-Win10. In zero cases did either Microsoft or other helpers define "extended attribute set" In almost all cases Win10 updates were implicated. In zero cases was an update-fail-restore loop implicated. So, I agree that something is wrong BUT 1) do not believe it indicates HDD problems as such and 2) don't think it is part of my problem.
There is very limited documentation for this error. Out of the dozen I studied, only ONE satisfied the user's problem. "Disable fast startup in Windows 10. This mode is hibernate like that leaves the disk in a state that Windows 7 does not understand. This causes it to run CHKDSK. " Several users reported that the problem appeared when either 1) running dual-boot Win7-Win10 systems OR 2) when moving back and forth from Win7-Win10. In zero cases did either Microsoft or other helpers define "extended attribute set" In almost all cases Win10 updates were implicated. In zero cases was an update-fail-restore loop implicated. So, I agree that something is wrong BUT 1) do not believe it indicates HDD problems as such and 2) don't think it is part of my problem.