Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > alt.comp.os.windows-11 > #19675 > unrolled thread

Can I update W10 to W11 with the iso?

Back to article view | Back to alt.comp.os.windows-11

Contents

  Can I update W10 to W11 with the iso? T <T@invalid.invalid> - 2025-05-24 05:26 -0700
    Re: Can I update W10 to W11 with the iso? "...winston" <winstonmvp@gmail.com> - 2025-05-24 10:14 -0400
      Re: Can I update W10 to W11 with the iso? T <T@invalid.invalid> - 2025-05-24 07:20 -0700
        Re: Can I update W10 to W11 with the iso? "...winston" <winstonmvp@gmail.com> - 2025-05-24 13:40 -0400
          Re: Can I update W10 to W11 with the iso? Paul <nospam@needed.invalid> - 2025-05-24 16:26 -0400
          Re: Can I update W10 to W11 with the iso? T <T@invalid.invalid> - 2025-05-24 19:42 -0700
            Re: Can I update W10 to W11 with the iso? Paul <nospam@needed.invalid> - 2025-05-25 04:49 -0400
              Re: Can I update W10 to W11 with the iso? T <T@invalid.invalid> - 2025-05-25 03:19 -0700
                Re: Can I update W10 to W11 with the iso? Paul <nospam@needed.invalid> - 2025-05-29 00:27 -0400
            Re: Can I update W10 to W11 with the iso? "...winston" <winstonmvp@gmail.com> - 2025-05-25 12:34 -0400
              Re: Can I update W10 to W11 with the iso? Paul <nospam@needed.invalid> - 2025-05-25 13:56 -0400
                Re: Can I update W10 to W11 with the iso? "...winston" <winstonmvp@gmail.com> - 2025-05-25 15:37 -0400
                Re: Can I update W10 to W11 with the iso? "Bill Bradshaw" <bradshaw@gci.net> - 2025-05-26 10:05 -0800
                  Re: Can I update W10 to W11 with the iso? Paul <nospam@needed.invalid> - 2025-05-26 16:03 -0400
                    Re: Can I update W10 to W11 with the iso? "Bill Bradshaw" <bradshaw@gci.net> - 2025-05-26 13:03 -0800
                      Re: Can I update W10 to W11 with the iso? Paul <nospam@needed.invalid> - 2025-05-26 18:27 -0400
                        Re: Can I update W10 to W11 with the iso? "Bill Bradshaw" <bradshaw@gci.net> - 2025-05-27 09:14 -0800
                          Re: Can I update W10 to W11 with the iso? Java Jive <java@evij.com.invalid> - 2025-05-27 18:36 +0100
                            Re: Can I update W10 to W11 with the iso? Java Jive <java@evij.com.invalid> - 2025-05-27 20:39 +0100
                              Re: Can I update W10 to W11 with the iso? Paul <nospam@needed.invalid> - 2025-05-27 16:51 -0400
                                Re: Can I update W10 to W11 with the iso? Java Jive <java@evij.com.invalid> - 2025-05-28 11:31 +0100
                                  Re: Can I update W10 to W11 with the iso? Paul <nospam@needed.invalid> - 2025-05-28 12:25 -0400
                                    Re: Can I update W10 to W11 with the iso? Paul <nospam@needed.invalid> - 2025-05-28 18:59 -0400
                        Re: Can I update W10 to W11 with the iso? "Bill Bradshaw" <bradshaw@gci.net> - 2025-05-27 09:18 -0800
                          Re: Can I update W10 to W11 with the iso? Paul <nospam@needed.invalid> - 2025-05-27 14:46 -0400
                    Re: Can I update W10 to W11 with the iso? MikeS <mikes@is.invalid> - 2025-05-26 22:07 +0100
                      Re: Can I update W10 to W11 with the iso? Paul <nospam@needed.invalid> - 2025-05-26 18:44 -0400
                        Re: Can I update W10 to W11 with the iso? "...winston" <winstonmvp@gmail.com> - 2025-05-27 01:16 -0400
                          Re: Can I update W10 to W11 with the iso? knuttle <keith_nuttle@yahoo.com> - 2025-05-27 06:54 -0400
                            Re: Can I update W10 to W11 with the iso? Paul <nospam@needed.invalid> - 2025-05-27 09:43 -0400
                            Re: Can I update W10 to W11 with the iso? "...winston" <winstonmvp@gmail.com> - 2025-05-28 21:48 -0400
                              Re: Can I update W10 to W11 with the iso? Paul <nospam@needed.invalid> - 2025-05-28 22:26 -0400
                                Re: Can I update W10 to W11 with the iso? "...winston" <winstonmvp@gmail.com> - 2025-05-29 00:32 -0400
                                  Re: Can I update W10 to W11 with the iso? "...winston" <winstonmvp@gmail.com> - 2025-05-29 00:59 -0400
                    Re: Can I update W10 to W11 with the iso? "...winston" <winstonmvp@gmail.com> - 2025-05-27 01:00 -0400
                      Re: Can I update W10 to W11 with the iso? Paul <nospam@needed.invalid> - 2025-05-27 03:32 -0400
                        Re: Can I update W10 to W11 with the iso? "Bill Bradshaw" <bradshaw@gci.net> - 2025-05-27 09:43 -0800
                        Re: Can I update W10 to W11 with the iso? "Bill Bradshaw" <bradshaw@gci.net> - 2025-05-27 10:13 -0800
                          Re: Can I update W10 to W11 with the iso? Paul <nospam@needed.invalid> - 2025-05-27 14:57 -0400
                            Re: Can I update W10 to W11 with the iso? "Bill Bradshaw" <bradshaw@gci.net> - 2025-05-28 08:43 -0800
                              Re: Can I update W10 to W11 with the iso? Paul <nospam@needed.invalid> - 2025-05-28 19:01 -0400
    Re: Can I update W10 to W11 with the iso? "s|b" <me@privacy.invalid> - 2025-05-24 19:19 +0200
      Re: Can I update W10 to W11 with the iso? Paul <nospam@needed.invalid> - 2025-05-24 16:31 -0400

Page 2 of 3 — ← Prev page 1 [2] 3  Next page →

#19840

On 2025-05-27 21:51, Paul wrote:
>
> On Tue, 5/27/2025 3:39 PM, Java Jive wrote:
>>
>> On 2025-05-27 18:36, Java Jive wrote:
>>>
>>> On 2025-05-27 18:14, Bill Bradshaw wrote:
>>>>
>>>> I also do not have the key for the version.  Right now the partition is 523
>>>> Mb with 441 Mb used leaving 82 Mb unused.  I am positive that at some point
>>>> I created this partition.
>>>
>>> ITYM GB?  At least, I hope you do!
>>
>> Sorry, didn't realise that you were referring specifically to a recovery partition rather than a Windows partition, even so, the size seems small to me, because, although I never have recovery partitions, I keep an image file of the system drive on the data drive, so it gets backed up to the servers.  If I need to restore, I can simply reimage and be back up and running within an hour or so.
>>
>> But these images are themselves approximately a third to a half of the size of the original Windows system partitions of which they are images, as follows (sizes in GB):
>>          Bitness    System drive size    Approx Image size
>>      32         32                   11
>>      64         64-80                30+
>>
>> So you can see why the amount of restorative power from a few hundred MB of recovery partition has never seemed worthwhile to me.
> 
> There are two kinds of Recovery Partition.
> 
> Before Microsoft started messing with it, a Recovery Partition was 15GB of DVD
> images stored in a proprietary format. On a "Factory Restore", C: would be erased
> and it would be restored from the Factory Image information. It might take three
> burned DVDs to hold the same info (for situations where the HDD failed and
> the Factory Recovery Partition is lost). When receiving a Windows 7 laptop,
> one of the first things you would do, is burn your 3 DVD set. The software
> only allowed one copy to be prepared from that information store.
> 
> The Microsoft version of recovery partition, is on the order of 500-600MB.
> It holds a WinRE.wim file system which has a minimal WinPE style of operating
> system in it. This mainly allows scripts or command line interaction
> with a broken C: partition. Maybe the machine is unable to boot, and the
> winRE.wim partition was triggered by the issue.
> 
> Microsoft did not previously "patch" the 600MB partition, but due to some
> sort of Secure Boot exploits, it has now taken to modifying the WinRE.wim .
> And this requires sufficient space, for any patching activity to fit in there.
> The recommended amount of space is not always correct. When they allowed us to
> see an error result in the windows Update history page, that made it possible
> to guess "well, how much bigger should I make this thing". And you could increase
> it, until '4441 installed properly for you.
> 
> an area used for the preparation of patches, is here.
> 
> C:\$WinREAgent\Backup
> 
>     Name: Winre.wim
>     Size: 570403392 bytes (543 MiB)
> 
> You can't just check the top level size, you have to examine each directory
> in there, to get some understanding of what stage it is in at the moment.
> But the Windows Update history, may not hint that an update is failing,
> and that staging area is "churning each time". It might engage DISM and
> build a new one in that staging area.

As always, thanks for the detailed explanation, Paul, but I'm now more 
convinced than ever that recovery partitions are a waste of time and 
energy, and my solution of having an image file on the data partition is 
much better! :-)

-- 

Fake news kills!

I may be contacted via the contact address given on my website: 
www.macfh.co.uk

[toc] | [prev] | [next] | [standalone]

#19851

On Wed, 5/28/2025 6:31 AM, Java Jive wrote:

> 
> As always, thanks for the detailed explanation, Paul, but I'm now more 
> convinced than ever that recovery partitions are a waste of time and energy,
> and my solution of having an image file on the data partition is much better! :-)

The only reason I worry about stuff like this, is if the broken
activity prevents normal security patches from installing. Some
"broken things" in Windows Update, result in a person not
getting patches for three years. You will run into people, who
one way or another discover that the patching on their machine
was broken for long periods of time.

A couple weeks ago, I had some patches in a loop. I used
the WUReset (by using the TroubleShooter and it runs
the script for you). And that didn't fix the problem I had.
Keeping Windows Update healthy, is a "chore". I did a Repair Install yesterday,
and I have a few more steps to go, to discover that it still isn't
fixed. Wish me luck :-)

   Paul

[toc] | [prev] | [next] | [standalone]

#19873

On Wed, 5/28/2025 12:25 PM, Paul wrote:
> On Wed, 5/28/2025 6:31 AM, Java Jive wrote:
> 
>>
>> As always, thanks for the detailed explanation, Paul, but I'm now more 
>> convinced than ever that recovery partitions are a waste of time and energy,
>> and my solution of having an image file on the data partition is much better! :-)
> 
> The only reason I worry about stuff like this, is if the broken
> activity prevents normal security patches from installing. Some
> "broken things" in Windows Update, result in a person not
> getting patches for three years. You will run into people, who
> one way or another discover that the patching on their machine
> was broken for long periods of time.
> 
> A couple weeks ago, I had some patches in a loop. I used
> the WUReset (by using the TroubleShooter and it runs
> the script for you). And that didn't fix the problem I had.
> Keeping Windows Update healthy, is a "chore". I did a Repair Install yesterday,
> and I have a few more steps to go, to discover that it still isn't
> fixed. Wish me luck :-)

The Repair Install worked. I even got a chuckle out of the MSFT solution.

The problem started, when Visual Studio Community Edition decided to
patch itself. The only problem was, three different KB patch articles
started running in parallel. They would throw errors and stop.

After the Repair Install (with network disconnected), I plugged
in the network cable and was waiting for the deluge to come in.
A Visual Studio patch *did* show up, but it was an even later
one than the three that got in a fight with each other. And
it completed, and the others were sent to the rendering vat.
So coincidentally, it managed to fix something.

   Paul

[toc] | [prev] | [next] | [standalone]

#19806

Paul wrote:
> On Mon, 5/26/2025 5:03 PM, Bill Bradshaw wrote:
>
>>
>> I had a backup of the winre.wim so I managed to copy that by setting
>> a partition letter etc.  Ran regentc /enable and now is all good and
>> it is being reported as "enabled."  Sometimes running Windows makes
>> you wonder.
>>
>> <Bill>
>
> It's a great hobby.
>
> Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
> NT\CurrentVersion\WinREVersion
>
>    10.0.19041.5125   ??? Version string ?
>
> Since I don't have that key set on mine, I can't check.
>
> You have to get the automation to set that registry value, because
> manual tool operation does not give that info.
>
> Patches are pushed out on Patch Tuesday, but I don't think the
> thing is closed loop feedback. If you mess with it, Microsoft
> does not scan or sense it. Leaving its maintenance kinda open
> ended.
>
> Microsoft also seems unable/uninterested in resizing the
> partition properly.
>
>   Paul

I also do not have that key value.  The partition is 523 Mb with 441 Mb 
used.  I am pretty sure at some point I created the partiton and not 
Windows.  I always use the Cumulative Update and have not had  a problem 
updating.

<Bill> 

[toc] | [prev] | [next] | [standalone]

#19814

On Tue, 5/27/2025 1:18 PM, Bill Bradshaw wrote:
> Paul wrote:
>> On Mon, 5/26/2025 5:03 PM, Bill Bradshaw wrote:
>>
>>>
>>> I had a backup of the winre.wim so I managed to copy that by setting
>>> a partition letter etc.  Ran regentc /enable and now is all good and
>>> it is being reported as "enabled."  Sometimes running Windows makes
>>> you wonder.
>>>
>>> <Bill>
>>
>> It's a great hobby.
>>
>> Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
>> NT\CurrentVersion\WinREVersion
>>
>>    10.0.19041.5125   ??? Version string ?
>>
>> Since I don't have that key set on mine, I can't check.
>>
>> You have to get the automation to set that registry value, because
>> manual tool operation does not give that info.
>>
>> Patches are pushed out on Patch Tuesday, but I don't think the
>> thing is closed loop feedback. If you mess with it, Microsoft
>> does not scan or sense it. Leaving its maintenance kinda open
>> ended.
>>
>> Microsoft also seems unable/uninterested in resizing the
>> partition properly.
>>
>>   Paul
> 
> I also do not have that key value.  The partition is 523 Mb with 441 Mb 
> used.  I am pretty sure at some point I created the partiton and not 
> Windows.  I always use the Cumulative Update and have not had  a problem 
> updating.
> 
> <Bill> 

the first problem update, was '4441 . They caused the failures to be
removed from the Windows Update history page, which is why you cannot
review how many problems there were.

The 523MB partition, could easily be made 1000MB or 1024MB. That
handles the "normal" case of the upgrade file being a bit bigger.
If it attempted to keep two copies of the 441MB item in the 1000MB
partition, that would still fit too.

This is my hard drive layout, after the maintenance this morning.
Partition 4 and Partition 6 are the two Recovery Partitions,
one partition for each OS to manage.

   [Picture]

    https://i.postimg.cc/pTRygtjZ/Recovery-Partition-Sizing-May27-2025.gif

Disk Management cannot list the quantity of material in the hidden
partitions, but this is mostly an affectation, as the partitions
are easily mounted anyway. Using "diskpart.exe" to assign a drive letter
to a hidden partition, makes it possible to use commands like "dir /ah"
from the command line, with regard to the assigned letter like R: .

   Paul

[toc] | [prev] | [next] | [standalone]

#19771

On 26/05/2025 21:03, Paul wrote:
> On Mon, 5/26/2025 2:05 PM, Bill Bradshaw wrote:
>> Paul wrote:
>>> On Sun, 5/25/2025 12:34 PM, ...winston wrote:
>>>> T wrote:
>>>>> On 5/24/25 10:40 AM, ...winston wrote:
>>>>>> T wrote:
>>>>>>> On 5/24/25 7:14 AM, ...winston wrote:
>>>>>>>> T wrote:
>>>>>>>>> Or do I have cut it to a USB drive and
>>>>>>>>> boot of it?
>>>>>>>>>
>>>>>>>>> I am after an in place upgrade that keep the
>>>>>>>>> old stuff around (not a wipe).
>>>>>>>>
>>>>>>>> For the subject of the post.
>>>>>>>> => Yes
>>>>>>>> - mount the iso and run setup.exe
>>>>>>>>
>>>>>>>> For the USB drive boot
>>>>>>>> => No
>>>>>>>
>>>>>>> Awesome reply. Thank you!
>>>>>>
>>>>>> Now go back and look at the Win10 partition structure.
>>>>>> - To prevent certain upgrade failures due to WinRE and SafeOS
>>>>>> Ensure:
>>>>>> - the device is UEFI/GPT
>>>>>> - All Windows expected partitions are present in this order
>>>>>> System, MSR, Windows 10, Recovery, Data(or other OEM partitions)
>>>>>> - WinRE(winre.wim) is at least this service pack build release
>>>>>> level build or greater and a modified date of at least Mar 2025 or
>>>>>> later(April 2025 was the latest update to WinRE) ServicePack Build
>>>>>> : 5728
>>>>>> Modified : 4/11/2025
>>>>>> - As noted above, Active WinRE partition is adjacent and directly
>>>>>> to the right of Windows partition(in a normal GPT it would be
>>>>>> partition #4) => Run reagentc /info in an admin command prompt to
>>>>>> see the partition# => Run DISM /Get-ImageInfo to determine the
>>>>>> Service Pack build and latest modified date
>>>>>> e.g. for WinRE as partition #4 on Disk 0
>>>>>> DISM /Get-ImageInfo /ImageFile:\\?
>>>>>> \GLOBALROOT\device\harddisk0\partition4\Recovery\WindowsRE\winre.wim
>>>>>> / index:1
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> Thank you!
>>>>>
>>>>> I was going to do a full clonezille of both
>>>>> computes before proceeding. I am super paranoid.
>>>>>
>>>>> I was also going to use the Rufus doctored ISO.
>>>>>
>>>>>
>>>>>
>>>>>
>>>> If WinRE partition is not adjacent to the Windows partition, it
>>>> should be corrected prior to upgrading(any method) from Win10 to
>>>> Win11. - Disable the non-adjacent WinRE using reagentc (this is
>>>> important) => Why is it important...This will place(move) the WinRE
>>>> file(winre.wim) to the C:drive and in the correct
>>>> place[C:\Windows\System32\Recovery folder.}
>>>> - Shrink the Windows partition by 1 or 2 GB(the latter ensures it
>>>> will be sufficient size until Win11 EOL)
>>>> - Delete the disabled WinRE partition
>>>> - Recreate a new WinRE in the unallocated space.
>>>> => The WinRE file on the C drive will be moved to the WinRE partition
>>>> - Verify WinRE is now adjacent to the Windows partition
>>>> - Restart the device, check again. Run Windows Update to ensure May
>>>> 2024 latest SSU, LCU/SafeOS/WinRE is present
>>>>
>>>> If you don't know how to do any of the above, you'll need to ask for
>>>> instructions and also include pictures of current(before doing
>>>> anything) partitions on the main disk.
>>>>
>>>
>>> Working from a diagram helps. Sample.
>>>
>>>    [Picture]
>>>
>>>     https://i.postimg.cc/sDKTV7Zy/sample-partition-table.gif
>>>
>>>   Paul
>>
>> I ran reagentc /info and it reports disabled.  Diskpart shows it is there.
>> Why is it disabled and what is my problem now?
>>
> 
> The purpose of re-agent-c is to have an emergency boot OS when
> the main OS is not available. For example, C: might be encrypted
> and have some problem opening it. Or C: might need a CHKDSK to become
> functional.
> 
> While some machines have reagentc enabled, the location of WinRE.wim is
> on the C: partition itself. While this is used as a parking position,
> if I understand how this is supposed to work, that's a less than optimal
> position. Having the reagentc information in the BCD, point to a
> separate Recovery Partition, is a better solution. The Recovery Partition
> contains no customer files, so it's not a security issue.
> 
> The WinRE.wim occasionally needs security fixes. Presumably it has some
> Secure Boot implications, which is why it needs to be patched. Hardly
> any user computers are properly patched, because the users are expected
> to perform maintenance operations they are totally unfamiliar with.
> Just the fact yours is disabled, indicates how long a walk uphill
> is ahead of you :-)
> 
> When you do a clean install today, the reagentc is typically disabled.
> Maybe the file is on C: . Maybe the file isn't on C: at all. I don't
> track the issue. I only repair them here, as my own special kind of
> hobby.
> 
> The secret sauce, is the PushButtonReset.
> 
>     [Picture]
> 
>      https://i.postimg.cc/qRhGVryW/Push-Button-Reset.gif
> 
> Those two files need to be extracted and put in your work directory.
> 
> The destination is in the Recovery Partition ("Hidden"). It
> can be assigned a drive letter using "diskpart.exe" , as one
> means to traverse there. I'm only using "testdisk.exe" from
> a third party, as a quick means to take a picture and avoid
> the boredom of a lot of "dir /ah" hidden file reveals.
> 
>     [Picture]
> 
>      https://i.postimg.cc/XqD3Zwpr/Recovery-Partition.gif
> 
> Those two work files would go over top of what is in there now.
> The reason for this, is you're "resetting" the thing, and you
> are convincing the OS to forget about the crap already
> spread all over the place, and trust the two new items
> (extracted from the 24H2 DVD) as a replacement.
> 
> To put the files in there, the last time I tried to do that
> from windows, I was repulsed by the permissions. Now, I could
> have made a giant mess of the thing, and beaten it senseless
> with my "computer hammer", but instead I just booted up Linux
> and put the files in there without a fuss. With the right file
> system driver, Linux does not care about permissions. That's
> why dropping the two files in there is so easy.
> 
> Now, you have to craft a command for the running OS, to get it
> to pick up the new info.
> 
> https://www.tenforums.com/performance-maintenance/211034-recreate-winre-files-new-recovery-partition.html
> 
> If I assign the letter R: to the Recovery Partition (partition 4),
> I can do this to have the PBR consumed and instantiated.
> 
>     REAGENTC.EXE /setreimage /path r:\Recovery\WindowsRE /logpath C:\Temp\Reagent.log
> 
> The command will convert the letter reference, to the alternate namespace.
> This is the pointer you'd see in the enabled reagentc /info later.
> 
>     \\?\GLOBALROOT\device\harddisk0\partition4\Recovery\WindowsRE
> 
> You could also direct the operation, by using that identifier, instead
> of using the R: trick and a diskpart letter assignment.
> 
> In the administrator window you're issuing that command, should
> be confirmation it took. You were starting with reagentc disabled,
> before using that command, so that the PBR is "ready-to-take". The
> logic behind that stuff, has many curve balls it can throw at you.
> 
> For the OS to later be able to patch that file, on a Patch Tuesday,
> you need enough space in the partition. Let's say the partition
> is 600MB right now. You should at least *double* the size,
> if you are planning ahead for one of its little party tricks.
> What the stupid thing does, is it can move the WinRE.wim out of WindowsRE
> and put it in a "nearby" folder on the same partition. If it is patching,
> and it runs out of room while holding *two* of those files in its
> possession, instead of copying the moribund file to the C:
> recovery area, that's how it can run out of space. The documentation
> says "it only needs a small increment in space, to handle updates".
> Sure, that's if nothing stupid happens... :-/ Sometimes it moves
> the useless file to the C: storage location, but sometimes it
> moves it within Partition 4 in my example instead.
> 
> Anyway, that's a quick description of doing a PBR, with enough
> detail so you can look it up for a recipe.
> 
> To resize the Recovery Partition, you can use Linux GParted for that.
> Sure, Windows has plenty of little disk editing utilities, but
> the Windows utils don't like the taste of some of the materials
> and won't work on them. The Linux side isn't as picky. There is
> just one thing the Linux won't do, and that is touch in any way,
> the 16MB partition that contains no file system. Macrium knows
> to use "dd.exe" to handle that partition. But other utilities
> are just not prepared for "data not sitting in a file system".
> Otherwise, if your Recovery Partition needs a resize, doing
> it that way avoids all sorts of diskpart.exe ceremonies involving
> deleting the poor partition and creating a new one from scratch.
> which is a whole lot of unnecessary work, when a resize is only
> a reboot away from success.
> 
> Don't forget to change the date setting on the computer,
> on your return from Linux.
> 
>      Paul

I have two PCs running Win11, one from new and the other (7 years old) 
upgraded from Win10. Reagentc works normally on both. Neither has 
received anything other than routine updates so I am mystified by the 
instructions above.

If reagentc reports disabled the first thing to try is running reagentc 
/enable (as admin).

[toc] | [prev] | [next] | [standalone]

#19774

On Mon, 5/26/2025 5:07 PM, MikeS wrote:

> 
> I have two PCs running Win11, one from new and the other (7 years old) upgraded from Win10. Reagentc works normally on both. Neither has received anything other than routine updates so I am mystified by the instructions above.
> 
> If reagentc reports disabled the first thing to try is running reagentc /enable (as admin).
> 

At one time, I used to think like you, that
nothing could possibly happen.

But this topic is poorly handled, and Microsoft
has resorted to hiding error results, so you
can't tell it's not working properly or is
not receiving patches or updates properly.

Is it important ? How would I know. All I know is,
on three or four occasions Microsoft has tried to
patch it (different KB). With wildly variable results.
The one on the daily driver in front of me, the registry
value is not set, indicating no maintenance has
sucessfully ever been done.

If it was working properly, and autonomously, then
this would be set to some version string. Since the
Recovery Partition always seems to be the wrong size,
I can't see how a patch is ever going to work, and
this registry entry is set at the end of it. Even
a clean install, results in reagentc disabled. As far
as I know, a patch can only apply itself to an enabled
system. It checks the registry value, to determine whether
the version is old enough to need patching.

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\WinREVersion

    10.0.19041.5125   <=== example of format used, this is NOT the current value

   Paul

[toc] | [prev] | [next] | [standalone]

#19782

Paul wrote:
> As far
> as I know, a patch can only apply itself to an enabled
> system. It checks the registry value, to determine whether
> the version is old enough to need patching.
> 
> Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\WinREVersion
> 
>      10.0.19041.5125   <=== example of format used, this is NOT the current value
> 
>     Paul
> 

Win10
  - the current version is 10.0.19041.5728
Win11
  - the current version is 10.0.26100.4054

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

[toc] | [prev] | [next] | [standalone]

#19785

On 05/27/2025 1:16 AM, ...winston wrote:
> Paul wrote:
>> As far
>> as I know, a patch can only apply itself to an enabled
>> system. It checks the registry value, to determine whether
>> the version is old enough to need patching.
>>
>> Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows 
>> NT\CurrentVersion\WinREVersion
>>
>>      10.0.19041.5125   <=== example of format used, this is NOT the 
>> current value
>>
>>     Paul
>>
> 
> Win10
>   - the current version is 10.0.19041.5728
> Win11
>   - the current version is 10.0.26100.4054
> 
As of this morning my Windows 11 is at version 26100.4061.  I don't 
remember it upgrading.   05/27/2025 6:54 am Eastern Daylight.

[toc] | [prev] | [next] | [standalone]

#19792

On Tue, 5/27/2025 6:54 AM, knuttle wrote:
> On 05/27/2025 1:16 AM, ...winston wrote:
>> Paul wrote:
>>> As far
>>> as I know, a patch can only apply itself to an enabled
>>> system. It checks the registry value, to determine whether
>>> the version is old enough to need patching.
>>>
>>> Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\WinREVersion
>>>
>>>      10.0.19041.5125   <=== example of format used, this is NOT the current value
>>>
>>>     Paul
>>>
>>
>> Win10
>>   - the current version is 10.0.19041.5728
>> Win11
>>   - the current version is 10.0.26100.4054
>>
> As of this morning my Windows 11 is at version 26100.4061.  I don't remember it upgrading.   05/27/2025 6:54 am Eastern Daylight.

We're comparing WinRE.wim versions rather than the main OS version :-)
Or at least, trying to compare those numbers, if the scheme is working.

The WinRE.wim file is the "SafeOS". It's what a computer boots from
if C: is corrupt or has a problem. The "SafeOS" is how you can run
a CHKDSK to try to fix C: . That's why that mini-OS is there.
It is for emergencies.

If you didn't have the "SafeOS", you can boot the installer DVD and
attempt maintenance from there, but it's not quite as capable.
It's because the human operator has to come up with repair
ideas, when running from the installer DVD.

   Paul

[toc] | [prev] | [next] | [standalone]

#19878

knuttle wrote:
> On 05/27/2025 1:16 AM, ...winston wrote:
>> Paul wrote:
>>> As far
>>> as I know, a patch can only apply itself to an enabled
>>> system. It checks the registry value, to determine whether
>>> the version is old enough to need patching.
>>>
>>> Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows 
>>> NT\CurrentVersion\WinREVersion
>>>
>>>      10.0.19041.5125   <=== example of format used, this is NOT the 
>>> current value
>>>
>>>     Paul
>>>
>>
>> Win10
>>   - the current version is 10.0.19041.5728
>> Win11
>>   - the current version is 10.0.26100.4054
>>
> As of this morning my Windows 11 is at version 26100.4061.  I don't 
> remember it upgrading.   05/27/2025 6:54 am Eastern Daylight.

The reply about Win10/Win11 was relative to the WinRE file's version and 
build, not the installed Windows latest available build number.

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

[toc] | [prev] | [next] | [standalone]

#19879

On Wed, 5/28/2025 9:48 PM, ...winston wrote:
> knuttle wrote:
>> On 05/27/2025 1:16 AM, ...winston wrote:
>>> Paul wrote:
>>>> As far
>>>> as I know, a patch can only apply itself to an enabled
>>>> system. It checks the registry value, to determine whether
>>>> the version is old enough to need patching.
>>>>
>>>> Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\WinREVersion
>>>>
>>>>      10.0.19041.5125   <=== example of format used, this is NOT the current value
>>>>
>>>>     Paul
>>>>
>>>
>>> Win10
>>>   - the current version is 10.0.19041.5728
>>> Win11
>>>   - the current version is 10.0.26100.4054
>>>
>> As of this morning my Windows 11 is at version 26100.4061.  I don't remember it upgrading.   05/27/2025 6:54 am Eastern Daylight.
> 
> The reply about Win10/Win11 was relative to the WinRE file's version and build, not the installed Windows latest available build number.
> 

I've got a quick question for you.

If my boot drive is a dual boot, and looks like this:

   +-------+-------+---------+--------------------------+---------+--------------------------+ - - -
   | (GPT) |  ESP  | W11Home |  Recovery-Partition-W11  | W10Pro  |  Recovery-Partition-W10  |
   +-------+-------+---------+--------------------------+---------+--------------------------+ - - -

Does each OS rely upon and maintain its own Recovery Partition SafeOS, or
is there instead a plan for one Recovery Partition to be shared for the Boot drive ?

I think I made a finger error while doing some work, that may have caused something
to happen, but the W10Pro Repair Install seemed to end up using the partition to the
left of it for the SafeOS, instead of the one to the right. I used a little trick
to stop that from happening, to correct the situation.

   Paul

[toc] | [prev] | [next] | [standalone]

#19881

Paul wrote:
> On Wed, 5/28/2025 9:48 PM, ...winston wrote:
>> knuttle wrote:
>>> On 05/27/2025 1:16 AM, ...winston wrote:
>>>> Paul wrote:
>>>>> As far
>>>>> as I know, a patch can only apply itself to an enabled
>>>>> system. It checks the registry value, to determine whether
>>>>> the version is old enough to need patching.
>>>>>
>>>>> Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\WinREVersion
>>>>>
>>>>>       10.0.19041.5125   <=== example of format used, this is NOT the current value
>>>>>
>>>>>      Paul
>>>>>
>>>>
>>>> Win10
>>>>    - the current version is 10.0.19041.5728
>>>> Win11
>>>>    - the current version is 10.0.26100.4054
>>>>
>>> As of this morning my Windows 11 is at version 26100.4061.  I don't remember it upgrading.   05/27/2025 6:54 am Eastern Daylight.
>>
>> The reply about Win10/Win11 was relative to the WinRE file's version and build, not the installed Windows latest available build number.
>>
> 
> I've got a quick question for you.
> 
> If my boot drive is a dual boot, and looks like this:
> 
>     +-------+-------+---------+--------------------------+---------+--------------------------+ - - -
>     | (GPT) |  ESP  | W11Home |  Recovery-Partition-W11  | W10Pro  |  Recovery-Partition-W10  |
>     +-------+-------+---------+--------------------------+---------+--------------------------+ - - -
> 
> Does each OS rely upon and maintain its own Recovery Partition SafeOS, or
> is there instead a plan for one Recovery Partition to be shared for the Boot drive ?
> 
> I think I made a finger error while doing some work, that may have caused something
> to happen, but the W10Pro Repair Install seemed to end up using the partition to the
> left of it for the SafeOS, instead of the one to the right. I used a little trick
> to stop that from happening, to correct the situation.
> 
>     Paul
> 

It's been some time since I dual booted two Windows' os on the same disk.
  I do recall when I dual booted Win10 21H2 Pro and 22H2 Pro on two 
separate disk(22H2 on Disk 0, 21H1 on Disk 2 - both SSDs(identical size, 
manufacturer, model Samsung 860 EVO 1TB) with Windows and installed 
software); Disk 1 was my 4 TB spinner which had everything else(data, 
drivers, program installers, music, photos, UEFI/BIOS updates etc)
  In that case each os 21H1 and 22H2 on its separate disk had its own 4 
GPT partitions(System, MSR, Windows, Recovery) and the active recovery 
partition for each was the partition immediately right(adjacent) to its 
Windows partition.
  - Note: 21H2 was not a clean install to Disk 2, it was an Acronis 
image restored to the exact same drive it resided on earlier), then 
device configured for dual booting(lol, in hindsight I could have done 
that differently).

  To the best of my recollection when WinRE was first deployed/included 
with the monthly LCU, each os updated and thereafter maintained its own 
WinRE partition on the same disk, but I also seem to recall that prior 
to inclusion/deployment with the LCU the SafeOS/WinRE was deployed 
independently for 21H2 via a separate KB pushed down automatically via 
Windows Update.

My only effort on those Recovery partitions was to check if they were 
updated and current. The purpose of 21H2 as an alternate os was only due 
to using a free M365 subscription card(as an MSFT MVP) for Office 
Insider with a different MSA than the MSA used in W10 22H2). Once that 
free year approached ending, I left the Office Insider program, and 
closed the MSA account, then wiped that SSD...that SSD now sits in my 
Thermaltake USB 3 dual disk caddy(3.5", 2.5") as a temporary 
storage/dump-old no longer needed files then permanent deletion). The 
dual boot scenario iirc, ended when Win10 Pro 22H2 was clean installed 
to its same SSD in Dec 2023.

Since your device has both o/s on the same disk, not sure if the above 
answer's your question, but its the only recent somewhat comparable 
scenario I have to reference.

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

[toc] | [prev] | [next] | [standalone]

#19882

...winston wrote:
> Paul wrote:
>> On Wed, 5/28/2025 9:48 PM, ...winston wrote:
>>> knuttle wrote:
>>>> On 05/27/2025 1:16 AM, ...winston wrote:
>>>>> Paul wrote:
>>>>>> As far
>>>>>> as I know, a patch can only apply itself to an enabled
>>>>>> system. It checks the registry value, to determine whether
>>>>>> the version is old enough to need patching.
>>>>>>
>>>>>> Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows 
>>>>>> NT\CurrentVersion\WinREVersion
>>>>>>
>>>>>>       10.0.19041.5125   <=== example of format used, this is NOT 
>>>>>> the current value
>>>>>>
>>>>>>      Paul
>>>>>>
>>>>>
>>>>> Win10
>>>>>    - the current version is 10.0.19041.5728
>>>>> Win11
>>>>>    - the current version is 10.0.26100.4054
>>>>>
>>>> As of this morning my Windows 11 is at version 26100.4061.  I don't 
>>>> remember it upgrading.   05/27/2025 6:54 am Eastern Daylight.
>>>
>>> The reply about Win10/Win11 was relative to the WinRE file's version 
>>> and build, not the installed Windows latest available build number.
>>>
>>
>> I've got a quick question for you.
>>
>> If my boot drive is a dual boot, and looks like this:
>>
>>     
>> +-------+-------+---------+--------------------------+---------+--------------------------+ 
>> - - -
>>     | (GPT) |  ESP  | W11Home |  Recovery-Partition-W11  | W10Pro  |  
>> Recovery-Partition-W10  |
>>     
>> +-------+-------+---------+--------------------------+---------+--------------------------+ 
>> - - -
>>
>> Does each OS rely upon and maintain its own Recovery Partition SafeOS, or
>> is there instead a plan for one Recovery Partition to be shared for 
>> the Boot drive ?
>>
>> I think I made a finger error while doing some work, that may have 
>> caused something
>> to happen, but the W10Pro Repair Install seemed to end up using the 
>> partition to the
>> left of it for the SafeOS, instead of the one to the right. I used a 
>> little trick
>> to stop that from happening, to correct the situation.
>>
>>     Paul
>>
> 
> It's been some time since I dual booted two Windows' os on the same disk.
>   I do recall when I dual booted Win10 21H2 Pro and 22H2 Pro on two 
> separate disk(22H2 on Disk 0, 21H1 on Disk 2 - both SSDs(identical size, 
> manufacturer, model Samsung 860 EVO 1TB) with Windows and installed 
> software); Disk 1 was my 4 TB spinner which had everything else(data, 
> drivers, program installers, music, photos, UEFI/BIOS updates etc)
>   In that case each os 21H1 and 22H2 on its separate disk had its own 4 
> GPT partitions(System, MSR, Windows, Recovery) and the active recovery 
> partition for each was the partition immediately right(adjacent) to its 
> Windows partition.
>   - Note: 21H2 was not a clean install to Disk 2, it was an Acronis 
> image restored to the exact same drive it resided on earlier), then 
> device configured for dual booting(lol, in hindsight I could have done 
> that differently).
> 
>   To the best of my recollection when WinRE was first deployed/included 
> with the monthly LCU, each os updated and thereafter maintained its own 
> WinRE partition on the same disk, but I also seem to recall that prior 
> to inclusion/deployment with the LCU the SafeOS/WinRE was deployed 
> independently for 21H2 via a separate KB pushed down automatically via 
> Windows Update.
> 
> My only effort on those Recovery partitions was to check if they were 
> updated and current. The purpose of 21H2 as an alternate os was only due 
> to using a free M365 subscription card(as an MSFT MVP) for Office 
> Insider with a different MSA than the MSA used in W10 22H2). Once that 
> free year approached ending, I left the Office Insider program, and 
> closed the MSA account, then wiped that SSD...that SSD now sits in my 
> Thermaltake USB 3 dual disk caddy(3.5", 2.5") as a temporary 
> storage/dump-old no longer needed files then permanent deletion). The 
> dual boot scenario iirc, ended when Win10 Pro 22H2 was clean installed 
> to its same SSD in Dec 2023.
> 
> Since your device has both o/s on the same disk, not sure if the above 
> answer's your question, but its the only recent somewhat comparable 
> scenario I have to reference.
> 
p.s.
  Hopefully, the above wasn't too confusing(21H1 and 21H2 references)
  The Note info. '21H2 was not a clean install etc..." section should read
  " - Note: 21H2 was not a clean install to Disk 2, it was an Acronis
 > image restored to the exact same drive it resided on earlier), then
 > device configured for dual booting, ****then updated to 21H2 via 
Windows Update***(lol, in hindsight I could have done the entire dual 
boot setup and 21H1 to 21H2 update differently)."

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

[toc] | [prev] | [next] | [standalone]

#19781

Paul wrote:
> 
> When you do a clean install today, the reagentc is typically disabled.
> Maybe the file is on C: . Maybe the file isn't on C: at all. I don't
> track the issue. I only repair them here, as my own special kind of
> hobby.
> 

During a clean install winre.wim first resides on the installation 
media(Sources\install.wim or install.esd) [1]
During setup, it is moved to C:\Windows\System32\Recovery, when WinRe 
partition is created and recovery enabled it is moved to the WinRE 
partition(normally Recovery\WindowsRE folder).

cf.
<https://learn.microsoft.com/en-us/windows-hardware/manufacture/desktop/windows-recovery-environment--windows-re--technical-reference?view=windows-11>

[1]
- Install.esd is normally on MCT created media(USB or ISO) and also on 
some OEM media.
- Install.wim is normally on the ISO(from Win11 ISO download page[don't 
need Linux - Win7 or Win10 os can download Win11 ISO - multi-edition x64 
editions] or Virtual Studio or similar Enterprise or Partner plans 
providing access to the MSFT servers hosting the different ISO editions).


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

[toc] | [prev] | [next] | [standalone]

#19784

On Tue, 5/27/2025 1:00 AM, ...winston wrote:
> Paul wrote:
>>
>> When you do a clean install today, the reagentc is typically disabled.
>> Maybe the file is on C: . Maybe the file isn't on C: at all. I don't
>> track the issue. I only repair them here, as my own special kind of
>> hobby.
>>
> 
> During a clean install winre.wim first resides on the installation media(Sources\install.wim or install.esd) [1]
> During setup, it is moved to C:\Windows\System32\Recovery, when WinRe partition is created and recovery enabled it is moved to the WinRE partition(normally Recovery\WindowsRE folder).
> 
> cf.
> <https://learn.microsoft.com/en-us/windows-hardware/manufacture/desktop/windows-recovery-environment--windows-re--technical-reference?view=windows-11>
> 
> [1]
> - Install.esd is normally on MCT created media(USB or ISO) and also on some OEM media.
> - Install.wim is normally on the ISO(from Win11 ISO download page[don't need Linux - Win7 or Win10 os can download Win11 ISO - multi-edition x64 editions] or Virtual Studio or similar Enterprise or Partner plans providing access to the MSFT servers hosting the different ISO editions).
> 

Sure. Those are the materials used by the user, to manually reset it.

*******

There are some sample commands for checking the version number here.

https://support.microsoft.com/en-us/topic/kb5055671-safe-os-dynamic-update-for-windows-11-version-24h2-and-server-2025-april-8-2025-80c632a5-adf9-4eef-991c-997ec2fa56c4#id0ebbh=dism_command

   reagentc /info

      Windows RE location:        \\?\GLOBALROOT\device\harddisk0\partition4\Recovery\WindowsRE

   Dism /Get-ImageInfo /ImageFile:\\?\GLOBALROOT\device\harddisk0\partition4\Recovery\WindowsRE\winre.wim /index:1

      Version : 10.0.22621
      ServicePack Build : 1

   ( My current patch level on the Daily Driver is 23H2 22631.5335 )

   *******
   # This script appears to pull an EXE out of the winre.wim and check
   # the version stamp of the file "winpeshl.exe".

   GetWinReVersion.ps1 PowerShell script

   ...
   $filePath = "$mountedPath\Windows\System32\winpeshl.exe"
   $WinREVersion = (Get-Item $filePath).VersionInfo.FileVersionRaw.Revision

   # Using TestDisk and not even using the Powershell script gives

   File version  10.0.22621.1             # The property of the winpeshl.exe file of the WinRE.wim

   # and matches the determination of the other method.

The one on the W11 installation (Partition 4), has never been patched.
The one on the W10 installation (Partition 6), is 10.0.19041.5728 , which
means if I were to boot that W10, the Registry should be set.

When I boot to the W10 and check, yes, the Registry is set. And it is set
to the same value as the determination in the article. This means patching
on the W10 partition is working, and Partition 6 is 1GB in size.

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion
   WinREVersion   10.0.19041.5728

It looks for my Windows 11, that I might profit from bumping up the
Recovery Partition size. The W11 is not blocked by this setting, and
this setting is OK for the preparation of a WinRE.wim .

PS> fsutil behavior query disablecompression               # Disables compression on all partitions at once.
DisableCompression = 0  (Compression is ENABLED)           # If you change the setting, it requires a reboot to "take".

Off to fix it... :-)

   Paul

[toc] | [prev] | [next] | [standalone]

#19811

Paul wrote:
> On Tue, 5/27/2025 1:00 AM, ...winston wrote:
>> Paul wrote:
>>>
>>> When you do a clean install today, the reagentc is typically
>>> disabled. Maybe the file is on C: . Maybe the file isn't on C: at
>>> all. I don't track the issue. I only repair them here, as my own
>>> special kind of hobby.
>>>
>>
>> During a clean install winre.wim first resides on the installation
>> media(Sources\install.wim or install.esd) [1]
>> During setup, it is moved to C:\Windows\System32\Recovery, when
>> WinRe partition is created and recovery enabled it is moved to the
>> WinRE partition(normally Recovery\WindowsRE folder).
>>
>> cf.
>> <https://learn.microsoft.com/en-us/windows-hardware/manufacture/desktop/windows-recovery-environment--windows-re--technical-reference?view=windows-11>
>>
>> [1]
>> - Install.esd is normally on MCT created media(USB or ISO) and also
>> on some OEM media.
>> - Install.wim is normally on the ISO(from Win11 ISO download
>> page[don't need Linux - Win7 or Win10 os can download Win11 ISO -
>> multi-edition x64 editions] or Virtual Studio or similar Enterprise
>> or Partner plans providing access to the MSFT servers hosting the
>> different ISO editions).
>>
>
> Sure. Those are the materials used by the user, to manually reset it.
>
> *******
>
> There are some sample commands for checking the version number here.
>
> https://support.microsoft.com/en-us/topic/kb5055671-safe-os-dynamic-update-for-windows-11-version-24h2-and-server-2025-april-8-2025-80c632a5-adf9-4eef-991c-997ec2fa56c4#id0ebbh=dism_command
>
>   reagentc /info
>
>      Windows RE location:
> \\?\GLOBALROOT\device\harddisk0\partition4\Recovery\WindowsRE
>
>   Dism /Get-ImageInfo 
> /ImageFile:\\?\GLOBALROOT\device\harddisk0\partition3\Recovery\WindowsRE\winre.wim 
> /index:1
> /index:1
>
>      Version : 10.0.22621
>      ServicePack Build : 1
>
>   ( My current patch level on the Daily Driver is 23H2 22631.5335 )
>
>   *******
>   # This script appears to pull an EXE out of the winre.wim and check
>   # the version stamp of the file "winpeshl.exe".
>
>   GetWinReVersion.ps1 PowerShell script
>
>   ...
>   $filePath = "$mountedPath\Windows\System32\winpeshl.exe"
>   $WinREVersion = (Get-Item
> $filePath).VersionInfo.FileVersionRaw.Revision
>
>   # Using TestDisk and not even using the Powershell script gives
>
>   File version  10.0.22621.1             # The property of the
> winpeshl.exe file of the WinRE.wim
>
>   # and matches the determination of the other method.
>
> The one on the W11 installation (Partition 4), has never been patched.
> The one on the W10 installation (Partition 6), is 10.0.19041.5728 ,
> which
> means if I were to boot that W10, the Registry should be set.
>
> When I boot to the W10 and check, yes, the Registry is set. And it is
> set
> to the same value as the determination in the article. This means
> patching
> on the W10 partition is working, and Partition 6 is 1GB in size.
>
> Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
>   NT\CurrentVersion WinREVersion   10.0.19041.5728
>
> It looks for my Windows 11, that I might profit from bumping up the
> Recovery Partition size. The W11 is not blocked by this setting, and
> this setting is OK for the preparation of a WinRE.wim .
>
>> fsutil behavior query disablecompression               # Disables
>> compression on all partitions at once.
> DisableCompression = 0  (Compression is ENABLED)           # If you
> change the setting, it requires a reboot to "take".
>
> Off to fix it... :-)
>
>   Paul

From Bill:

Deployment Image Servicing and Management tool
Version: 10.0.19041.3636

Details for image : 
\\?\GLOBALROOT\device\harddisk0\partition3\Recovery\WindowsRE\winre.wim

Index : 1
Name : Microsoft Windows Recovery Environment (x64)
Description : Microsoft Windows Recovery Environment (x64)
Size : 2,207,028,650 bytes
WIM Bootable : No
Architecture : x64
Hal : <undefined>
Version : 10.0.19041
ServicePack Build : 1
ServicePack Level : 0
Edition : WindowsPE
Installation : WindowsPE
ProductType : WinNT
ProductSuite :
System Root : WINDOWS
Directories : 3624
Files : 16440
Created : 12/6/2019 - 11:11:48 PM
Modified : 11/9/2024 - 11:14:23 AM
Languages :
        en-US (Default)
The operation completed successfully.

So I know this is what is on the machine because my backup of the WIN came 
from a current Macrium backup.

<Bill> 

[toc] | [prev] | [next] | [standalone]

#19812

Paul wrote:
> On Tue, 5/27/2025 1:00 AM, ...winston wrote:
>> Paul wrote:
>>>
>>> When you do a clean install today, the reagentc is typically
>>> disabled. Maybe the file is on C: . Maybe the file isn't on C: at
>>> all. I don't track the issue. I only repair them here, as my own
>>> special kind of hobby.
>>>
>>
>> During a clean install winre.wim first resides on the installation
>> media(Sources\install.wim or install.esd) [1]
>> During setup, it is moved to C:\Windows\System32\Recovery, when
>> WinRe partition is created and recovery enabled it is moved to the
>> WinRE partition(normally Recovery\WindowsRE folder).
>>
>> cf.
>> <https://learn.microsoft.com/en-us/windows-hardware/manufacture/desktop/windows-recovery-environment--windows-re--technical-reference?view=windows-11>
>>
>> [1]
>> - Install.esd is normally on MCT created media(USB or ISO) and also
>> on some OEM media.
>> - Install.wim is normally on the ISO(from Win11 ISO download
>> page[don't need Linux - Win7 or Win10 os can download Win11 ISO -
>> multi-edition x64 editions] or Virtual Studio or similar Enterprise
>> or Partner plans providing access to the MSFT servers hosting the
>> different ISO editions).
>>
>
> Sure. Those are the materials used by the user, to manually reset it.
>
> *******
>
> There are some sample commands for checking the version number here.
>
> https://support.microsoft.com/en-us/topic/kb5055671-safe-os-dynamic-update-for-windows-11-version-24h2-and-server-2025-april-8-2025-80c632a5-adf9-4eef-991c-997ec2fa56c4#id0ebbh=dism_command
>
>   reagentc /info
>
>      Windows RE location:
> \\?\GLOBALROOT\device\harddisk0\partition4\Recovery\WindowsRE
>
>   Dism /Get-ImageInfo
> /ImageFile:\\?\GLOBALROOT\device\harddisk0\partition4\Recovery\WindowsRE\winre.wim
> /index:1
>
>      Version : 10.0.22621
>      ServicePack Build : 1
>
>   ( My current patch level on the Daily Driver is 23H2 22631.5335 )
>
>   *******
>   # This script appears to pull an EXE out of the winre.wim and check
>   # the version stamp of the file "winpeshl.exe".
>
>   GetWinReVersion.ps1 PowerShell script
>
>   ...
>   $filePath = "$mountedPath\Windows\System32\winpeshl.exe"
>   $WinREVersion = (Get-Item
> $filePath).VersionInfo.FileVersionRaw.Revision
>
>   # Using TestDisk and not even using the Powershell script gives
>
>   File version  10.0.22621.1             # The property of the
> winpeshl.exe file of the WinRE.wim
>
>   # and matches the determination of the other method.
>
> The one on the W11 installation (Partition 4), has never been patched.
> The one on the W10 installation (Partition 6), is 10.0.19041.5728 ,
> which
> means if I were to boot that W10, the Registry should be set.
>
> When I boot to the W10 and check, yes, the Registry is set. And it is
> set
> to the same value as the determination in the article. This means
> patching
> on the W10 partition is working, and Partition 6 is 1GB in size.
>
> Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
>   NT\CurrentVersion WinREVersion   10.0.19041.5728
>
> It looks for my Windows 11, that I might profit from bumping up the
> Recovery Partition size. The W11 is not blocked by this setting, and
> this setting is OK for the preparation of a WinRE.wim .
>
>> fsutil behavior query disablecompression               # Disables
>> compression on all partitions at once.
> DisableCompression = 0  (Compression is ENABLED)           # If you
> change the setting, it requires a reboot to "take".
>
> Off to fix it... :-)
>
>   Paul

From Bill:

Dism /Get-ImageInfo 
/ImageFile:\\?\GLOBALROOT\device\harddisk0\partition3\Recovery\WindowsRE\winre.wim 
/index:1
Deployment Image Servicing and Management tool

Version: 10.0.19041.3636

Details for image : 
\\?\GLOBALROOT\device\harddisk0\partition3\Recovery\WindowsRE\winre.wim

Index : 1
Name : Microsoft Windows Recovery Environment (x64)
Description : Microsoft Windows Recovery Environment (x64)
Size : 2,207,028,650 bytes
WIM Bootable : No
Architecture : x64
Hal : <undefined>
Version : 10.0.19041
ServicePack Build : 1
ServicePack Level : 0
Edition : WindowsPE
Installation : WindowsPE
ProductType : WinNT
ProductSuite :
System Root : WINDOWS
Directories : 3624
Files : 16440
Created : 12/6/2019 - 11:11:48 PM
Modified : 11/9/2024 - 11:14:23 AM

The WIN file came from a very recent backup with Macrium.  I am pretty sure 
I created the recovery partition and not Windows which is 523 Mb with 441 Mb 
used.  So maybe I need to figure out how to increase the recovery partition 
size.

<Bill>

[toc] | [prev] | [next] | [standalone]

#19815

On Tue, 5/27/2025 2:13 PM, Bill Bradshaw wrote:
> Paul wrote:
>> On Tue, 5/27/2025 1:00 AM, ...winston wrote:
>>> Paul wrote:
>>>>
>>>> When you do a clean install today, the reagentc is typically
>>>> disabled. Maybe the file is on C: . Maybe the file isn't on C: at
>>>> all. I don't track the issue. I only repair them here, as my own
>>>> special kind of hobby.
>>>>
>>>
>>> During a clean install winre.wim first resides on the installation
>>> media(Sources\install.wim or install.esd) [1]
>>> During setup, it is moved to C:\Windows\System32\Recovery, when
>>> WinRe partition is created and recovery enabled it is moved to the
>>> WinRE partition(normally Recovery\WindowsRE folder).
>>>
>>> cf.
>>> <https://learn.microsoft.com/en-us/windows-hardware/manufacture/desktop/windows-recovery-environment--windows-re--technical-reference?view=windows-11>
>>>
>>> [1]
>>> - Install.esd is normally on MCT created media(USB or ISO) and also
>>> on some OEM media.
>>> - Install.wim is normally on the ISO(from Win11 ISO download
>>> page[don't need Linux - Win7 or Win10 os can download Win11 ISO -
>>> multi-edition x64 editions] or Virtual Studio or similar Enterprise
>>> or Partner plans providing access to the MSFT servers hosting the
>>> different ISO editions).
>>>
>>
>> Sure. Those are the materials used by the user, to manually reset it.
>>
>> *******
>>
>> There are some sample commands for checking the version number here.
>>
>> https://support.microsoft.com/en-us/topic/kb5055671-safe-os-dynamic-update-for-windows-11-version-24h2-and-server-2025-april-8-2025-80c632a5-adf9-4eef-991c-997ec2fa56c4#id0ebbh=dism_command
>>
>>   reagentc /info
>>
>>      Windows RE location:
>> \\?\GLOBALROOT\device\harddisk0\partition4\Recovery\WindowsRE
>>
>>   Dism /Get-ImageInfo
>> /ImageFile:\\?\GLOBALROOT\device\harddisk0\partition4\Recovery\WindowsRE\winre.wim
>> /index:1
>>
>>      Version : 10.0.22621
>>      ServicePack Build : 1
>>
>>   ( My current patch level on the Daily Driver is 23H2 22631.5335 )
>>
>>   *******
>>   # This script appears to pull an EXE out of the winre.wim and check
>>   # the version stamp of the file "winpeshl.exe".
>>
>>   GetWinReVersion.ps1 PowerShell script
>>
>>   ...
>>   $filePath = "$mountedPath\Windows\System32\winpeshl.exe"
>>   $WinREVersion = (Get-Item
>> $filePath).VersionInfo.FileVersionRaw.Revision
>>
>>   # Using TestDisk and not even using the Powershell script gives
>>
>>   File version  10.0.22621.1             # The property of the
>> winpeshl.exe file of the WinRE.wim
>>
>>   # and matches the determination of the other method.
>>
>> The one on the W11 installation (Partition 4), has never been patched.
>> The one on the W10 installation (Partition 6), is 10.0.19041.5728 ,
>> which
>> means if I were to boot that W10, the Registry should be set.
>>
>> When I boot to the W10 and check, yes, the Registry is set. And it is
>> set
>> to the same value as the determination in the article. This means
>> patching
>> on the W10 partition is working, and Partition 6 is 1GB in size.
>>
>> Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
>>   NT\CurrentVersion WinREVersion   10.0.19041.5728
>>
>> It looks for my Windows 11, that I might profit from bumping up the
>> Recovery Partition size. The W11 is not blocked by this setting, and
>> this setting is OK for the preparation of a WinRE.wim .
>>
>>> fsutil behavior query disablecompression               # Disables
>>> compression on all partitions at once.
>> DisableCompression = 0  (Compression is ENABLED)           # If you
>> change the setting, it requires a reboot to "take".
>>
>> Off to fix it... :-)
>>
>>   Paul
> 
> From Bill:
> 
> Dism /Get-ImageInfo 
> /ImageFile:\\?\GLOBALROOT\device\harddisk0\partition3\Recovery\WindowsRE\winre.wim 
> /index:1
> Deployment Image Servicing and Management tool
> 
> Version: 10.0.19041.3636
> 
> Details for image : 
> \\?\GLOBALROOT\device\harddisk0\partition3\Recovery\WindowsRE\winre.wim
> 
> Index : 1
> Name : Microsoft Windows Recovery Environment (x64)
> Description : Microsoft Windows Recovery Environment (x64)
> Size : 2,207,028,650 bytes
> WIM Bootable : No
> Architecture : x64
> Hal : <undefined>
> Version : 10.0.19041    \_____
> ServicePack Build : 1   /
> ServicePack Level : 0
> Edition : WindowsPE
> Installation : WindowsPE
> ProductType : WinNT
> ProductSuite :
> System Root : WINDOWS
> Directories : 3624
> Files : 16440
> Created : 12/6/2019 - 11:11:48 PM
> Modified : 11/9/2024 - 11:14:23 AM
> 
> The WIN file came from a very recent backup with Macrium.  I am pretty sure 
> I created the recovery partition and not Windows which is 523 Mb with 441 Mb 
> used.  So maybe I need to figure out how to increase the recovery partition 
> size.
> 
> <Bill>

Seeing as it has never been updated, yes, there is a good chance a bigger
partition would help.

The Windows procedure for this, is highly unsavory. It requires deleting
the partition and creating a new one and setting the attributes and so on
correctly.

How I do these is:

1) Resize C: while still in Windows and using "diskmgmt.msc" for its
   graphical goodness. When the Shrink dialog appears, you can type in
   the precise amount of space needed. 1024-533=491 . This will leave
   a 491MB gap at the end of C: after you resize.

2) Boot Linux, such as Linux Mint 221  and use gparted

   a) sudo gparted            # We're running from the USB stick or the DVD disc
                              # No password needed in that case

   b) Select the Recovery Partition. I usually push it to the left
      as the first operation. Then click the Apply box to Apply it,
      For the second operation, I grab the right bar of the Move/Resize
      dialog and pull it to make the partition full size (1024). Click Apply.

   Linux sets the Dirty Bit, on completion. The Partition will be scanned by Windows.

3) Boot back to Windows. When it says it is about to scan something, let it continue.
   When in windows, open "control.exe" and the Date/Time control panel and
   update the time so it reads correctly.

Result: Doing a "reagentc.exe /info" should reveal nothing broke and it is still enabled.
        Diskmgmt.msc should now show a larger partition in place of the previous smaller one.
        No reloading of the partition need be done, as the 441MB file will still be there.

For a Linux boot media, you can use the mirror item at the top.
This is so you won't have to traverse the LM site itself and find the file.
I prefer simple FTP-like displays of the things to be downloaded. The Cinnamon
one at the top is fine. Open a terminal from the bottom left of the Linux
screen, and "sudo gparted" in that Terminal, to get started.

https://mirror.csclub.uwaterloo.ca/linuxmint/stable/22.1/

  Paul

[toc] | [prev] | [next] | [standalone]

#19853

Paul wrote:
> On Tue, 5/27/2025 2:13 PM, Bill Bradshaw wrote:
>> Paul wrote:
>>> On Tue, 5/27/2025 1:00 AM, ...winston wrote:
>>>> Paul wrote:
>>>>>
>>>>> When you do a clean install today, the reagentc is typically
>>>>> disabled. Maybe the file is on C: . Maybe the file isn't on C: at
>>>>> all. I don't track the issue. I only repair them here, as my own
>>>>> special kind of hobby.
>>>>>
>>>>
>>>> During a clean install winre.wim first resides on the installation
>>>> media(Sources\install.wim or install.esd) [1]
>>>> During setup, it is moved to C:\Windows\System32\Recovery, when
>>>> WinRe partition is created and recovery enabled it is moved to the
>>>> WinRE partition(normally Recovery\WindowsRE folder).
>>>>
>>>> cf.
>>>> <https://learn.microsoft.com/en-us/windows-hardware/manufacture/desktop/windows-recovery-environment--windows-re--technical-reference?view=windows-11>
>>>>
>>>> [1]
>>>> - Install.esd is normally on MCT created media(USB or ISO) and also
>>>> on some OEM media.
>>>> - Install.wim is normally on the ISO(from Win11 ISO download
>>>> page[don't need Linux - Win7 or Win10 os can download Win11 ISO -
>>>> multi-edition x64 editions] or Virtual Studio or similar Enterprise
>>>> or Partner plans providing access to the MSFT servers hosting the
>>>> different ISO editions).
>>>>
>>>
>>> Sure. Those are the materials used by the user, to manually reset
>>> it.
>>>
>>> *******
>>>
>>> There are some sample commands for checking the version number here.
>>>
>>> https://support.microsoft.com/en-us/topic/kb5055671-safe-os-dynamic-update-for-windows-11-version-24h2-and-server-2025-april-8-2025-80c632a5-adf9-4eef-991c-997ec2fa56c4#id0ebbh=dism_command
>>>
>>>   reagentc /info
>>>
>>>      Windows RE location:
>>> \\?\GLOBALROOT\device\harddisk0\partition4\Recovery\WindowsRE
>>>
>>>   Dism /Get-ImageInfo
>>> /ImageFile:\\?\GLOBALROOT\device\harddisk0\partition4\Recovery\WindowsRE\winre.wim
>>> /index:1
>>>
>>>      Version : 10.0.22621
>>>      ServicePack Build : 1
>>>
>>>   ( My current patch level on the Daily Driver is 23H2 22631.5335 )
>>>
>>>   *******
>>>   # This script appears to pull an EXE out of the winre.wim and
>>>   check # the version stamp of the file "winpeshl.exe".
>>>
>>>   GetWinReVersion.ps1 PowerShell script
>>>
>>>   ...
>>>   $filePath = "$mountedPath\Windows\System32\winpeshl.exe"
>>>   $WinREVersion = (Get-Item
>>> $filePath).VersionInfo.FileVersionRaw.Revision
>>>
>>>   # Using TestDisk and not even using the Powershell script gives
>>>
>>>   File version  10.0.22621.1             # The property of the
>>> winpeshl.exe file of the WinRE.wim
>>>
>>>   # and matches the determination of the other method.
>>>
>>> The one on the W11 installation (Partition 4), has never been
>>> patched. The one on the W10 installation (Partition 6), is
>>> 10.0.19041.5728 , which
>>> means if I were to boot that W10, the Registry should be set.
>>>
>>> When I boot to the W10 and check, yes, the Registry is set. And it
>>> is set
>>> to the same value as the determination in the article. This means
>>> patching
>>> on the W10 partition is working, and Partition 6 is 1GB in size.
>>>
>>> Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
>>>   NT\CurrentVersion WinREVersion   10.0.19041.5728
>>>
>>> It looks for my Windows 11, that I might profit from bumping up the
>>> Recovery Partition size. The W11 is not blocked by this setting, and
>>> this setting is OK for the preparation of a WinRE.wim .
>>>
>>>> fsutil behavior query disablecompression               # Disables
>>>> compression on all partitions at once.
>>> DisableCompression = 0  (Compression is ENABLED)           # If you
>>> change the setting, it requires a reboot to "take".
>>>
>>> Off to fix it... :-)
>>>
>>>   Paul
>>
>> From Bill:
>>
>> Dism /Get-ImageInfo
>> /ImageFile:\\?\GLOBALROOT\device\harddisk0\partition3\Recovery\WindowsRE\winre.wim
>> /index:1
>> Deployment Image Servicing and Management tool
>>
>> Version: 10.0.19041.3636
>>
>> Details for image :
>> \\?\GLOBALROOT\device\harddisk0\partition3\Recovery\WindowsRE\winre.wim
>>
>> Index : 1
>> Name : Microsoft Windows Recovery Environment (x64)
>> Description : Microsoft Windows Recovery Environment (x64)
>> Size : 2,207,028,650 bytes
>> WIM Bootable : No
>> Architecture : x64
>> Hal : <undefined>
>> Version : 10.0.19041    \_____
>> ServicePack Build : 1   /
>> ServicePack Level : 0
>> Edition : WindowsPE
>> Installation : WindowsPE
>> ProductType : WinNT
>> ProductSuite :
>> System Root : WINDOWS
>> Directories : 3624
>> Files : 16440
>> Created : 12/6/2019 - 11:11:48 PM
>> Modified : 11/9/2024 - 11:14:23 AM
>>
>> The WIN file came from a very recent backup with Macrium.  I am
>> pretty sure I created the recovery partition and not Windows which
>> is 523 Mb with 441 Mb used.  So maybe I need to figure out how to
>> increase the recovery partition size.
>>
>> <Bill>
>
> Seeing as it has never been updated, yes, there is a good chance a
> bigger
> partition would help.
>
> The Windows procedure for this, is highly unsavory. It requires
> deleting
> the partition and creating a new one and setting the attributes and
> so on
> correctly.
>
> How I do these is:
>
> 1) Resize C: while still in Windows and using "diskmgmt.msc" for its
>   graphical goodness. When the Shrink dialog appears, you can type in
>   the precise amount of space needed. 1024-533=491 . This will leave
>   a 491MB gap at the end of C: after you resize.
>
> 2) Boot Linux, such as Linux Mint 221  and use gparted
>
>   a) sudo gparted            # We're running from the USB stick or
>                              the DVD disc # No password needed in
> that case
>
>   b) Select the Recovery Partition. I usually push it to the left
>      as the first operation. Then click the Apply box to Apply it,
>      For the second operation, I grab the right bar of the Move/Resize
>      dialog and pull it to make the partition full size (1024). Click
> Apply.
>
>   Linux sets the Dirty Bit, on completion. The Partition will be
> scanned by Windows.
>
> 3) Boot back to Windows. When it says it is about to scan something,
>   let it continue. When in windows, open "control.exe" and the
>   Date/Time control panel and update the time so it reads correctly.
>
> Result: Doing a "reagentc.exe /info" should reveal nothing broke and
>        it is still enabled. Diskmgmt.msc should now show a larger
>        partition in place of the previous smaller one. No reloading
> of the partition need be done, as the 441MB file will still be there.
>
> For a Linux boot media, you can use the mirror item at the top.
> This is so you won't have to traverse the LM site itself and find the
> file.
> I prefer simple FTP-like displays of the things to be downloaded. The
> Cinnamon
> one at the top is fine. Open a terminal from the bottom left of the
> Linux
> screen, and "sudo gparted" in that Terminal, to get started.
>
> https://mirror.csclub.uwaterloo.ca/linuxmint/stable/22.1/
>
>  Paul

I have gparted on a usb boot drive and will that work without using Mint, 
etc.

<Bill> 

[toc] | [prev] | [next] | [standalone]

Page 2 of 3 — ← Prev page 1 [2] 3  Next page →

Back to top | Article view | alt.comp.os.windows-11

csiph-web