A PC - W10 - that I support for a friend has started to fail a Windows<snip>
Update because the Recovery Partition is too small.
On Thu, 30 May 2024 18:37:22 +0000, David wrote:
A PC - W10 - that I support for a friend has started to fail a Windows Update because the Recovery Partition is too small.<snip>
Microsoft instructions here - long URL
<https://support.microsoft.com/en-us/topic/kb5028997-instructions-to- manually-resize-your-partition-to-install-the-winre- update-400faa27-9343-461c-ada9-24c8229763bf>
It all looks very complicated and doesn't explain why you have to delete
and recreate the partition.
All sorts of tools will just shrink and extend partitions and this
normally works without having to tell the OS that things have changed.
Getting more baffled by the minute.
In article <lbs0m6Fe14uU5@mid.individual.net>, David wrote...
...
On Thu, 30 May 2024 18:37:22 +0000, David wrote:
A PC - W10 - that I support for a friend has started to fail a<snip>
Windows Update because the Recovery Partition is too small.
Microsoft instructions here - long URL
<https://support.microsoft.com/en-us/topic/kb5028997-instructions-to-
manually-resize-your-partition-to-install-the-winre-
update-400faa27-9343-461c-ada9-24c8229763bf>
It all looks very complicated and doesn't explain why you have to
delete and recreate the partition.
All sorts of tools will just shrink and extend partitions and this
normally works without having to tell the OS that things have changed.
Getting more baffled by the minute.
I've used those instructions and it worked for me. I can't explain why
you have to do it this way; I just took it on trust from MS. As I
understand it (backed up with a quick flick through Google) you can
always delete "Recovery" partitions but you lose the ability to Reset
from within Windows. But as you're re-creating a Recovery partition,
that doesn't seem a problem.
Worst case? If the machine has ever run at all it'll be licensed and activated, so just reinstall. Back up user data first (OneDrive?), and
log any application you may need to reinstall.
On Fri, 31 May 2024 10:29:42 +0100, Philip Herlihy wrote:
In article <lbs0m6Fe14uU5@mid.individual.net>, David wrote...
...
On Thu, 30 May 2024 18:37:22 +0000, David wrote:
A PC - W10 - that I support for a friend has started to fail a<snip>
Windows Update because the Recovery Partition is too small.
Microsoft instructions here - long URL
<https://support.microsoft.com/en-us/topic/kb5028997-instructions-to-> manually-resize-your-partition-to-install-the-winre-
update-400faa27-9343-461c-ada9-24c8229763bf>
It all looks very complicated and doesn't explain why you have to
delete and recreate the partition.
All sorts of tools will just shrink and extend partitions and this
normally works without having to tell the OS that things have changed.
Getting more baffled by the minute.
I've used those instructions and it worked for me. I can't explain why
you have to do it this way; I just took it on trust from MS. As I
understand it (backed up with a quick flick through Google) you can
always delete "Recovery" partitions but you lose the ability to Reset
from within Windows. But as you're re-creating a Recovery partition,
that doesn't seem a problem.
Worst case? If the machine has ever run at all it'll be licensed and
activated, so just reinstall. Back up user data first (OneDrive?), and
log any application you may need to reinstall.
My tentative plan is to delete the second (non-active) Recovery Partition
of over 10 GB and then let Windows Update have a go at creating a new
larger one as per the script.
This should hopefully not impact the system as it already has an active Recovery Partition which isn't quite big enough.
On 31 May 2024 at 12:33:58 BST, "David" <wibble@btinternet.com> wrote:
On Fri, 31 May 2024 10:29:42 +0100, Philip Herlihy wrote:
In article <lbs0m6Fe14uU5@mid.individual.net>, David wrote...
...
On Thu, 30 May 2024 18:37:22 +0000, David wrote:
A PC - W10 - that I support for a friend has started to fail a<snip>
Windows Update because the Recovery Partition is too small.
Microsoft instructions here - long URL
<https://support.microsoft.com/en-us/topic/kb5028997-instructions-to-> >>>> manually-resize-your-partition-to-install-the-winre-
update-400faa27-9343-461c-ada9-24c8229763bf>
It all looks very complicated and doesn't explain why you have to
delete and recreate the partition.
All sorts of tools will just shrink and extend partitions and this
normally works without having to tell the OS that things have
changed.
Getting more baffled by the minute.
I've used those instructions and it worked for me. I can't explain
why you have to do it this way; I just took it on trust from MS. As I
understand it (backed up with a quick flick through Google) you can
always delete "Recovery" partitions but you lose the ability to Reset
from within Windows. But as you're re-creating a Recovery partition,
that doesn't seem a problem.
Worst case? If the machine has ever run at all it'll be licensed and
activated, so just reinstall. Back up user data first (OneDrive?),
and log any application you may need to reinstall.
My tentative plan is to delete the second (non-active) Recovery
Partition of over 10 GB and then let Windows Update have a go at
creating a new larger one as per the script.
This should hopefully not impact the system as it already has an active
Recovery Partition which isn't quite big enough.
Delete both so it can make a full size one. There's no additional risk,
the existing one can't be used so bin it.
There's zero benefit to having a recovery partition there anyway if
you're able to make a USB installer on another machine.
Cheers - Jaimie
Delete both so it can make a full size one. There's no additional risk,
the existing one can't be used so bin it.
There's zero benefit to having a recovery partition there anyway if
you're able to make a USB installer on another machine.
Cheers - Jaimie
Deleted the big one so there is 10GB free at the end of the disc.
Still refusing to install the update.
It looks as though Windows Update is broken.
I've done the usual sfc /scannow and this reported fixing some problems
but it now reports no problems and the update will still not work.
I may try the longhand command prompt process described up thread but lack
of space to create a new partition is not really an issue now.
If I just turn off restore (part of the command prompt process) I wonder
if that will allow the updates to proceed?
As you say, the full script is daunting (especially getting some of the
long partition names correct) and I am bracing myself for that.
In article <lbu317Fe14uU8@mid.individual.net>, David wrote...
(Jaimie's smarter than me, so always believe him rather than me!)Delete both so it can make a full size one. There's no additional
risk,
the existing one can't be used so bin it.
There's zero benefit to having a recovery partition there anyway if
you're able to make a USB installer on another machine.
Cheers - Jaimie
Deleted the big one so there is 10GB free at the end of the disc.
Still refusing to install the update.
It looks as though Windows Update is broken.
I've done the usual sfc /scannow and this reported fixing some problems
but it now reports no problems and the update will still not work.
I may try the longhand command prompt process described up thread but
lack of space to create a new partition is not really an issue now.
If I just turn off restore (part of the command prompt process) I
wonder if that will allow the updates to proceed?
A couple of observations:
SFC rarely worked for me until I discovered the DISM command, which can repair the repository from which SFC gets its "spares". See: https://adamtheautomator.com/dism-cleanup-image/
That article is very comprehensive; it's easier than it seems.
Essentially: Scan using DISM to see if the 'store' is healthy.
DISM /Online /Cleanup-Image /ScanHealth If it is, then run SFC.
If it isn't, then fix it using:
DISM /Online /Cleanup-Image /RestoreHealth. If that works, then run
SFC.
If the /RestoreHealth errors, you'll need to download an ISO, mount it,
and use that to repair the store - details are in the article.
I did follow the "longhand command prompt process" described up thread.
I found I _really_ had to concentrate - it's very easy to make mistakes.
After a near-disaster I copied the steps into OneNote (Word will do
fine) and colour- coded it all, emphasising the parameters. That made
it easier to follow! I had to disable Bitlocker to get one of the steps (delete the existing active Recovery partition, if I remember correctly)
so check if Bitlocker is enabled -
I was surprised to find it was, apparently out-of-the-box on the
friend's machine I was working on.
Bitlocker reference: https://learn.microsoft.com/en-us/windows/security/operating-system- security/data-protection/bitlocker/operations-guide?tabs=powershell
Bitlocker commands I used:
List:
manage-bde.exe -protectors -get C:
Suspend:
manage-bde.exe -protectors -disable C:
Resume:
manage-bde.exe -protectors -enable C:
Hope that helps.
I am astonished that ordinary users are expected to jump through these
hoops to get an update to work. What are they thinking of...?
(Jaimie's smarter than me, so always believe him rather than me!)
In article <lc0i4pF55atU2@mid.individual.net>, David wrote...
As you say, the full script is daunting (especially getting some of theCopy and paste is your friend here! Good luck!
long partition names correct) and I am bracing myself for that.
On Sat, 01 Jun 2024 13:26:35 +0100, Philip Herlihy wrote:
In article <lc0i4pF55atU2@mid.individual.net>, David wrote...
As you say, the full script is daunting (especially getting some ofCopy and paste is your friend here! Good luck!
the long partition names correct) and I am bracing myself for that.
Many thanks for the help so far.
Falling at almost the first hurdle, though.
<https://support.microsoft.com/en-us/topic/kb5028997-instructions-to- manually-resize-your-partition-to-install-the-winre- update-400faa27-9343-461c-ada9-24c8229763bf>
"First, check if the disk partition style is a GUID Partition Table
(GPT)
or a Master Boot Record (MBR).
To do that, run list disk.
Check if there is an asterisk character (*) in the “Gpt” column. If there is an asterisk character (*), then the drive is GPT. Otherwise,
the drive is MBR."
However:
"C:\WINDOWS\system32>list disk 'list' is not recognized as an internal
or external command,
operable program or batch file."
Ah!
A command for within diskpart.
[Note to self, when developing instructions on your own computer for
another computer, be very careful not to run any!!]
Pause at this point as the machine under therapy is almost out of hard
drive space.
I glanced at the numbers and saw a 167 and assumed GB but it is MB.
I will clear that issue by extending the C: partition, after first
recovering the Restore partition, and then get on with recreating stuff.
I am so out of practice at this stuff!
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 415 |
Nodes: | 16 (1 / 15) |
Uptime: | 34:31:01 |
Calls: | 8,719 |
Calls today: | 2 |
Files: | 13,276 |
Messages: | 5,956,023 |