On 2/13/2024 3:28 PM, Ant wrote:
> sticks <wolverine01@charter.net> wrote:
>> On 2/13/2024 2:00 PM, Ant wrote:
>>> I still see this and no fix with today's automatic monthly updates. It
>>> still has the manual technical script instructions to fix it.
>
>> I've seen you post on this several times. At this point, it's probably
>> not going to fix it unless YOU try something. Have you tried following
>> the instructions, making your windows partition smaller, and increasing
>> the sizer of your ReAgent partition bigger?
>
>> Winston, Paul, and others have been very helpful in assisting me fix
>> this issue on several systems. In the message below, Winston details
>> removing restore points because of the location they get put on the
>> disk. Perhaps that might help you.
>
>> Message ID:
>> news://news.eternal-september.org:119/uq1o6ira1s@dont-email.me
>
> Try telling non-technical users like elders. :P

Did you even look at his post?

I think these, the relative points, are something most people could do.

---
- I deleted all System Restore Points
- Disabled System Restore for the C: drive(it was not enabled for other
drives either)
- Used Windows Disk Cleanup in admin mode to remove everything it showed
as removable(i.e. - all boxes were checked before running) - took about
15 min on that 8 yr old device(Intel Atom chip and 4 GB RAM, 128 GB disk
storage), and WinRE partition had sufficient free space to handle the
Recovery partition updating).
- Turned off Windows Update option 'Receive updates from other Microsoft
products
---

You just take it slowly and get it done. Same goes for the "technical
script", as you call it. I am far from a expert on any of this stuff,
but I am willing to try what these guys suggest. Sometimes it's over my
head, sometimes I jump in the water and get all wet. But if you don't
try, well......

--
Stand With Israel!
NOTE: If you use Google Groups I don't see you,
unless you're whitelisted and that's doubtful.

On 2/13/2024 4:28 PM, Ant wrote:
> sticks <wolverine01@charter.net> wrote:
>> On 2/13/2024 2:00 PM, Ant wrote:
>>> I still see this and no fix with today's automatic monthly updates. It
>>> still has the manual technical script instructions to fix it.
>
>> I've seen you post on this several times. At this point, it's probably
>> not going to fix it unless YOU try something. Have you tried following
>> the instructions, making your windows partition smaller, and increasing
>> the sizer of your ReAgent partition bigger?
>
>> Winston, Paul, and others have been very helpful in assisting me fix
>> this issue on several systems. In the message below, Winston details
>> removing restore points because of the location they get put on the
>> disk. Perhaps that might help you.
>
>> Message ID:
>> news://news.eternal-september.org:119/uq1o6ira1s@dont-email.me
>
> Try telling non-technical users like elders. :P
>

What your blocker is, may vary. This is why we can't exactly
just slap down a single solution. In my sample C: partition
(a Microsoft modern.ie VM from the archives), the System Volume Information
has a file of a decent size, and this appears to prevent shrinkage.

File 0089912 Sector 15426439
File 0089914 Sector 133462015 <=== a Restore point was the blocker before
File 0089915 Sector 66495

I was planning on using a Macrium backup and restore method, to defragment
the partition. You can see how the file number increments, and the sector
number on the right increments, that it does a damn fine job of putting
the files in filenum order. Only one problem. It seems to have
the same sort of habit Microsoft would like -- putting a blocker in
the middle of the partition. Since I never cared about this before,
I never checked for this. All I'd noticed, is you could use Macrium to
defragment a partition (restore to a slightly reduced partition size,
causes Macrium to restore the files in order -- I call this a drag and
drop restore, because of how you handle the restore at restoration time).

File 0000000 Sector 6473727 $MFT
File 0000000 Sector 831 $BITMAP
File 0000001 Sector 125759407 $MFTMirr
File 0000002 Sector 131903
File 0000004 Sector 131911
File 0000005 Sector 131919
File 0000006 Sector 125767167 $BitMap <=== can't be moved
File 0000007 Sector 15
File 0000010 Sector 132175
File 0000025 Sector 132199
File 0000026 Sector 132207
File 0000028 Sector 137327
File 0000028 Sector 138927

File 1
Master File Table Mirror ($MftMirr)
$STANDARD_INFORMATION (resident)
$FILE_NAME (resident)
$DATA (nonresident)
logical sectors 125759400-125759407 (0x77eefa8-0x77eefaf)

File 6
Volume Bitmap ($BitMap)
$STANDARD_INFORMATION (resident)
$FILE_NAME (resident)
$DATA (nonresident)
logical sectors 125759488-125767167 (0x77ef000-0x77f0dff)

But in any case, you can see I've been defeated, so it's looking like
killing the System Protection restore points is still the better option.

I use nfi.exe to get information on where the file is on the disk.
Unfortunately, the output of nfi.exe always needs text filtering
work to get the best value from the output. Skimming through
four hundred thousand files in a text editor as an alternative,
isn't exactly efficient. I get some free exercising of the gawk neurons
while building little filters.

Now, isn't this the activity you signed on for ? :-)
I'm enjoying myself.

Now, if, during the Macrium Restore, I'd shrunk the partition
as small as possible, those little rat bastard files could
not get in the way. So I can fix it. I'm just disappointed that
the "order" Macrium used for restoration, is mostly so pretty,
and only a couple items are not in a very nice place.

[Picture]

https://i.postimg.cc/FFT7CKTB/Macrium-Reflect-Shrink.gif

If a partition won't shrink, yes, you can defeat it. I used
a Macrium CD, a backup and restore of C:, to squeeze it down.

Paul

In article <QWidneGTaZz0V1b4nZ2dnZfqnPudnZ2d@earthlink.com>, Ant wrote...
>
> I still see this and no fix with today's automatic monthly updates. It
> still has the manual technical script instructions to fix it. :(

The "Accepted Answer" here did work for me. It's easy enough - but it would
also be quite easy to do some real damage if you don't follow the instructions
really carefully.

https://learn.microsoft.com/en-us/answers/questions/1495451/windows-update-
issue-(failed-to-install)-0x8007064

--

Phil, London

On 2/13/2024 3:00 PM, Ant wrote:
> I still see this and no fix with today's automatic monthly updates. It
> still has the manual technical script instructions to fix it. :(
>

Where is your sense of adventure.

https://www.ctvnews.ca/polopoly_fs/1.2512395.1439379036!/httpImage/image.jpg_gen/derivatives/landscape_960/image.jpg

He can do that, because he made a backup before doing the procedure.

Paul

On Wed, 14 Feb 2024 02:05:56 -0500, Paul <nospam@needed.invalid> wrote:

>If a partition won't shrink, yes, you can defeat it. I used
>a Macrium CD, a backup and restore of C:, to squeeze it down.

I would just spend a minute or two and use a partition manager. ;-)

I know, I know, you've got a toolbox full of tools and they get offended if you
don't take them out and exercise them from time to time.

On 2/14/2024 11:35 AM, Char Jackson wrote:
> On Wed, 14 Feb 2024 02:05:56 -0500, Paul <nospam@needed.invalid> wrote:
>
>> If a partition won't shrink, yes, you can defeat it. I used
>> a Macrium CD, a backup and restore of C:, to squeeze it down.
>
> I would just spend a minute or two and use a partition manager. ;-)
>
> I know, I know, you've got a toolbox full of tools and they get offended if you
> don't take them out and exercise them from time to time.
>

Realistically though, do you have a Partition Manager For All Occasions ?

I do, but if I were to describe it, there are individuals who
are Orthodox and would object to the things I was describing.

The idea of using Macrium, is "not going too far out into Edge City".

For example, I could hook people up with Paragon PM14 Free, but
if I did that, the support load that would create, it would never
end. Yes, it can do stuff, but... <sigh>.

So while there are partition managers, not all of them are
a good idea. And someone might stub their toe on one.

Your tool box has an angle grinder and a circular saw with no
guard on it, because you like it that way.

Paul

Char Jackson wrote on 2/14/24 9:35 AM:
> On Wed, 14 Feb 2024 02:05:56 -0500, Paul <nospam@needed.invalid> wrote:
>
>> If a partition won't shrink, yes, you can defeat it. I used
>> a Macrium CD, a backup and restore of C:, to squeeze it down.
>
> I would just spend a minute or two and use a partition manager. ;-)
>
> I know, I know, you've got a toolbox full of tools and they get offended if you
> don't take them out and exercise them from time to time.
>
That's a route some may take.

Even so, with WinRE in play, the primary reason in this subject/thread
for shrinking the System partition(Windows, C:), it still is a good idea
to have some foresight and use reagentc to disable winre.wim in advance
before tampering/resizing[enlarging] the WinRE partition.

--
....w¡ñ§±¤ñ

Paul wrote on 2/14/24 12:05 AM:
> On 2/13/2024 4:28 PM, Ant wrote:
>> sticks <wolverine01@charter.net> wrote:
>>> On 2/13/2024 2:00 PM, Ant wrote:
>>>> I still see this and no fix with today's automatic monthly updates. It
>>>> still has the manual technical script instructions to fix it.
>>
>>> I've seen you post on this several times. At this point, it's probably
>>> not going to fix it unless YOU try something. Have you tried following
>>> the instructions, making your windows partition smaller, and increasing
>>> the sizer of your ReAgent partition bigger?
>>
>>> Winston, Paul, and others have been very helpful in assisting me fix
>>> this issue on several systems. In the message below, Winston details
>>> removing restore points because of the location they get put on the
>>> disk. Perhaps that might help you.
>>
>>> Message ID:
>>> news://news.eternal-september.org:119/uq1o6ira1s@dont-email.me
>>
>> Try telling non-technical users like elders. :P
>>
>
> What your blocker is, may vary. This is why we can't exactly
> just slap down a single solution. In my sample C: partition
> (a Microsoft modern.ie VM from the archives), the System Volume Information
> has a file of a decent size, and this appears to prevent shrinkage.
>
> File 0089912 Sector 15426439
> File 0089914 Sector 133462015 <=== a Restore point was the blocker before
> File 0089915 Sector 66495
>
> But in any case, you can see I've been defeated, so it's looking like
> killing the System Protection restore points is still the better option.

+1
SR points location on disk preventing C drive resizing have been an issue
in Windows well before Win 10 and/or Win11.
- All devices? No, the condition may or may not be present.

During Win10 beta(Insider and Internal builds) there were reports of
resizing failures due to end of disk orphan files that were protected
system files associated with current or past Windows updates which
required DiskcCleanup in admin mode for removal.

--
....w¡ñ§±¤ñ

On Wed, 14 Feb 2024 11:56:51 -0500, Paul <nospam@needed.invalid> wrote:

>On 2/14/2024 11:35 AM, Char Jackson wrote:
>> On Wed, 14 Feb 2024 02:05:56 -0500, Paul <nospam@needed.invalid> wrote:
>>
>>> If a partition won't shrink, yes, you can defeat it. I used
>>> a Macrium CD, a backup and restore of C:, to squeeze it down.
>>
>> I would just spend a minute or two and use a partition manager. ;-)
>>
>> I know, I know, you've got a toolbox full of tools and they get offended if you
>> don't take them out and exercise them from time to time.
>>
>
>Realistically though, do you have a Partition Manager For All Occasions ?

So far, yes.

In article <MPG.4036ca9e621eeaef989aa9@news.eternal-september.org>, Philip
Herlihy wrote...
>
> In article <QWidneGTaZz0V1b4nZ2dnZfqnPudnZ2d@earthlink.com>, Ant wrote...
> >
> > I still see this and no fix with today's automatic monthly updates. It
> > still has the manual technical script instructions to fix it. :(
>
> The "Accepted Answer" here did work for me. It's easy enough - but it would
> also be quite easy to do some real damage if you don't follow the instructions
> really carefully.
>
> https://learn.microsoft.com/en-us/answers/questions/1495451/windows-update-
> issue-(failed-to-install)-0x8007064

A more direct link:

https://support.microsoft.com/en-us/topic/kb5028997-instructions-to-manually-
resize-your-partition-to-install-the-winre-update-400faa27-9343-461c-ada9-
24c8229763bf

You operate on disks and partitions by Selecting them by "index" number first.
Be sure to correctly identify the "OS disk index" and distinguish the "OS
partition index" from the "WinRE partition index". As indicated, the Diskpart
commands "list disk" and "list part" will display what's there to choose from,
and I also had Disk Management running just to double-check. I did make one
mistake but I got away with it.

Overview:
1) You disable WinRE
2) You shrink the OS partition
3) You delete the WinRE partition, and then re-create it.
4) You re-enable WinRE

Don't delete the wrong partition!!!!!

It'll take ten minutes of concentration. Yes, it's bizarre we have to do this.

--

Phil, London