Built a self-healing WinRE manager for Windows 11 — sharing the failure modes and what I learned about the recovery partition lifecycle

trevo said:

Have some decorum, if he wants to engage or otherwise, his decision.

Click to expand...

If you've followed this thread you'll notice one thing, I met those that were willing to test my project halfway! I even provided early access to v48 in one instance! I also bent over backwards to write a wrapper that was safe for the person that requested it to just go silent! I have so many projects which I'm not releasing yet until I'm absolutely confident in them!

trevo said:

Have some decorum, if he wants to engage or otherwise, his decision.

Click to expand...

Besides, foodle decorum, we're not playing politics here! In fact, we flipping hate politics! Decorum is something politicians do when they foodle us over! Here we produce results!

More likely he is doing something that is keeping him away from all his peeps here.

I was going to go down a rabbit hole of hardening v48 patch 2, but foodle that, v48 patch 2 is the most stable! I'm absolutely confident in my project! Know the worst thing my script will do? The worst thing my code will do is shovelall!

I desinged my project with this philosophy:
1. Never break Windows RE.
2. Never leave a machine without a working recovery route — to the extent the machine, its OS, and its storage stack allow.
3. Minimize the reagentc /disable → reagentc /enable window.
4. Do no work unless needed. When work is needed, prepare everything before touching anything.

Who would've thought writing a script to repair Windows RE would be so complicated and flipping convoluted? My script isn't v48 patch 2 for no apparent reason!

While Banjoman301 was concerned about elevation, I'm concerned about more serious and severe issues, like the fact that if your Winre.wim is really missing, my script will download a clean and untouched Winre.wim from my GitHub repository, you won't be able to tell if you can actually trust the Winre.wim on my repo? What if in spite of GitHub's new requirement of 2FA, my account gets hacked? Don't get me wrong, I've taken every security precaution, and my project is extremely well documented, and I have a security policy in place, but still... In an ideal world I'd like to pull original and untouched Winre.wim images from Microsoft directly! However, it isn't possible! In order for you to get a clean Windows RE image if yours are non-existent, you'd need to download the Windows installation media and extract the Windows RE image from there... We're now talking about a 6~10GB download just to extract a clean 700~MB Windows RE image, notwithstanding the time and overhead to get Winre.wim extracted from the Windows image! If i figure out a way to obtain a clean Winre.wim from Microsoft direct, I have the holy grail! I already have the holy grail, buy this would increase my rep!

I'm not sure if the guys here can appreciate that in order to get or do:
1. Never break Windows RE.
2. Never leave a machine without a working recovery route — to the extent the machine, its OS, and its storage stack allow.
3. Minimize the reagentc /disable → reagentc /enable window.
4. Do no work unless needed. When work is needed, prepare everything before touching anything.

It takes about 6500 lines of PowerShell code!