(1) I am trebly overjoyed that pesky letter R is gone & still gone many reboots later. I felt a tad responsible for it, though you never blamed me. But I'm not much more than 86% a genius because some educated guesswork was involved. You did well,
too, entering some dangerous & obscure commands that neither of us fully understood (despite I tested them first). You've always gotten them right even when I was a bit unclear. Good going.
(2) "So, C on the C vol, D is on the Push Button volumne"
Let us be happy, if C: will stick. That's the most convenient one. Now I'm getting spotty results with that, but C: still holds...
Microsoft Windows [Version 10.0.19041.1]
(c) 2019 Microsoft Corporation. All rights reserved.
X:\windows\system32>diskpart
Microsoft DiskPart version 10.0.19041.1
Copyright (C) Microsoft Corporation.
On computer: MININT-GJIS8KS
DISKPART> list vol
Volume ### Ltr Label Fs Type Size Status Info
---------- --- ----------- ----- ---------- ------- --------- --------
Volume 0 G DVD-ROM 0 B No Media
Volume 1 C PCR Hard NTFS Partition 930 GB Healthy
Volume 2 D WinRE 2004 NTFS Partition 847 MB Healthy
Volume 3 ESP FAT32 Partition 99 MB Healthy Hidden
Volume 4 E ULTRA 1 NTFS Removable 57 GB Healthy
Volume 5 F ULTRA 2 FAT32 Removable 57 GB Healthy
DISKPART> exit
Leaving DiskPart...
The more drives you plug in, the more the letters will scramble. I set "D", "C", & "R", & came back after plugging in two Removable's, & found the above. At least C: is C:, & ESP got no letter. Let's just hope the dog goes back to sleep before making it
worse.
(3) "Oh, and I will try to peruse Gateway/Acer to see if I can find that Gateway stuff. If so, I suppose we don't really even need Part 6. First I have to figure out what it is called."
Yes, go to that site I posted, & type in your serial number or SNID. If you see the Gateway addons that you think you'll miss, definitely we should just delete Partition 6. Put a new regular partition in its place, & see whether Acronis will approve. If
so, either keep the new partition, or delete it & put the space into C:partition.
(4) "And that means we have only Part 6 to address now"
Your "ReagentC /Info" mentions Partition 6 (like it mentions Partition 5)...
C:\WINDOWS\system32>ReagentC /Info
Windows Recovery Environment (Windows RE) and system reset configuration
Information:
Windows RE status: Enabled
Windows RE location: \?\GLOBALROOT\device\harddisk0\partition5\Recovery\WindowsRE
Boot Configuration Data (BCD) identifier: 06a7379d-d1bb-11ea-8997-b888e3b1b2f5
Recovery image location: \?\GLOBALROOT\device\harddisk0*partition6*\RecoveryImage
Recovery image index: 2
Custom image location:
Custom image index: 0
REAGENTC.EXE: Operation Successful.
I expected to see a mention of Partition 6 in your BCD (like it mentions Partition 5). If it were there, we could back it up to restore had it disappeared after we deleted the partition. But it isn't there. So, I don't know where ReagentC is getting its
information from regarding Partition 6.
We didn't worry about Partition 5, because ReagentC had a way to restore the connection which was "SetREImage"...
C:\WINDOWS\system32>ReagentC /?
Configures the Windows Recovery Environment (Windows RE) and system reset.
REAGENTC.EXE <command> <arguments>
The following commands can be specified:
/info - Displays Windows RE and system reset configuration information.
/setreimage - Sets the location of the custom Windows RE image.
/enable - Enables Windows RE.
/disable - Disables Windows RE.
/boottore - Configures the system to start Windows RE next time the system starts up.
/setbootshelllink - Adds an entry to the Reset and Restore page in the boot menu.
For more information about these commands and their arguments, type
REAGENTC.EXE <command> /?.
Examples:
REAGENTC.EXE /setreimage /?
REAGENTC.EXE /disable /?
REAGENTC.EXE: Operation Successful
Notice it doesn't mention SETOSImage up there (which is Install.wim in Partition 6). However, if we specifically ask it about SetOSImage, it does say...
C:\WINDOWS\system32>ReagentC /SetOSImage /?
Sets the location of the recovery image used by system reset.
Note: Permissions on the recovery image file must be set so that only users
in the Administrators group can write to and modify it.
REAGENTC.EXE /setosimage /path <dir_name> /index <image_index> [/target <dir_name>]
/path <dir_name> - Specifies the directory that contains the recovery image.
/index <image_index> - Index of the recovery image Windows imaging (WIM)
file to be used by system reset.
/target <dir_name> - Specifies the Windows installation. If this argument
is not specified, the running operating system is used.
Example:
REAGENTC.EXE /setosimage /path r:\Recovery\WindowsRE /index 1
REAGENTC.EXE /setosimage /path r:\Recovery\WindowsRE /index 1 /target C:\Windows
REAGENTC.EXE: Operation Successful.
I read, ReagentC used to be able to do that, but it can't any longer. But that's what we'll have to try, if you lose the connection. So...
(a) What do you want to do?
(b) Let's see Install.wim...
Put a letter, say, X, on Partition 6, &, at a Command Prompt, enter...
DISM /Get-WimInfo /WimFile:X:\RecoveryImage\Install.wim /Index:1