Recent content by PlateauRealm

You answered my question perfectly. Thank you. I was concerned that performing a later in-place upgrade to a later build would install a good deal of the bloat back which was blocked by the initial boot installation autounattend.xml file.

What about the application of autoattend.xml with future in-place build upgrades? Someone mentioned that I rename the autoattend.xml to unattend.xml and import it in the Windows\System32\Sysprep\ folder of the ISO build (using Anyburn) before doing an in-place upgrade with the newer build ISO...

There is a lot of neglected areas like this in Windows. For instance, no version of Windows (WinXP+) to date has ever allowed me to scroll the Disk Management's bottom disk partition table panel using the mouse or trackball middle scroll wheel, while other windows do. This has never been...

I'm just amazed that no one has ever noticed this basic GUI problem before and that the flaw in window panel navigation in the Disk Management app in Windows has existed for over two decades without correction.

I've always wondered why any mouse or trackball's scroll-wheel will not scroll the the top or bottom panels set to Graphical View in the Disk Management app. When the top or bottom panel view is set to 'Disk list' or 'Volume list' the mouse scroll wheel will respond, but when either panel is...

Thanks, Bree. The app worked great! I was able to successfully created an ISO of 22621.963

UUPDump.net takes me to a Discord server that wants access verification by providing them with my phone number? WTF

Woke-ism is coming to an end soon. Keep the Boop avatar.

When I follow your procedure, reagentc /info (last step) reports that Windows RE status is enabled and diskpart lists the fs of the recovery partition as NTFS. After a reboot though, diskpart lists the recovery partition as RAW and reagentc /info reports that Windows RE status is Disabled...

BTW, after following this procedure, diskpart correctly lists the recovery partition as NTFS and reagentc /info reports Enabled, but upon reboot reagentc /info reports Disabled and diskpart reports the recovery partition as RAW. This is consistent no matter how many times I repeat this...

I started this thread. Believe me, I tried every solution mentioned here to fix my recovery partition. Nothing suggested here "stuck" other than one -- deleting the recovery partition, re-formatting the unallocated partition as NTFS, settings its id and gpt attributes with diskpart and then...

Following aubergine's steps, I copied the file to C:\Windows\System32\Recovery folder. It is no longer there after running reagentc /enable. I assume that it was moved to the recovery partition. Diskpart's list vol lists the volume 4 partition as RAW instead of NTFS. I can't get inside it.

Yeah, that's sort of a hail-mary solution, doing an in-place upgrade or disk image restoration. I was hoping, though, for some other solution not involving an in-place upgrade or disk image restoration.

Your steps enabled my recovery partition. reagentc /info reported Enabled. Unfortunately, upon rebooting and running reagentc /info again, reagentc /info reported the Windows RE status as being Disabled. Running reagentc /enable prompted me with 'The Windows RE Image was not found'.