I feel really stupid & really sorry. I'd never called reagentc /info. I wanted to see the cmd window on my daily rider before on my dust collector. I must have had a senior moment. Sorry..................
bjm_, You don't have to do anything about your areas of Free Space. For my own entertainment I looked at several free apps to see if they could do the job. Boot media is needed as you have to Slide (Move) the Windows partition. The Pro versions can make boot media... Paragon Partition Manager. The boot UFD doesn't load. MiniTool Free. You can't make boot media, EaseUs Partition Manager Free. You can't make boot media, AOMEI Partition Assistant Free. You can't make boot media, Active Partition Manager Free. Can't do a Slide. GParted. This can do the job but it would take many hours as it doesn't do a proper Slide. It moves all sectors. Sectors in use and sectors not in use. BootIt UEFI. My favourite but not free. Although there is a Trial. When doing a Slide it only moves sectors in use (your data). It could do the job in a few minutes.
That's what I did, I blew away both, one of which was the actual Recovery partition But good thing I imaged them both first, so I was able to restore, blow away the right one, and retain the correct one. I tested and was able to boot to the RE. I've never heard of Reagentc before. Handy command
Even if you delete the Recovery partition and don't have a backup you can create a new functioning Recovery partition. Using BootIt UEFI in my case.
I found a procedure online but it looked like more work than I wanted to bother with, plus I wanted to test Hasleo's Partition Restore mode.
It sounds like the SOURCE drive may be unique (as far as driver requirements are concerned... some sort of NvME maybe?) and the necessary driver is not on the Rescue Media. If it was "standard" NvME/Sata it would not be an issue. There was a report on the 11-Forums about certain NvMEs not being seen by early Beta versions of v4 but the Public v4 seems to have solved that issue. If you're on the Public v4 (16Nov) I would recreate your Rescue Media with that version.
Thanks for introducing me to BootIt UEFI. I could even be without Terabyte Image Backup and Restore as I find Macrium easier to work with at my level of competence (maybe more so Hasleo, but haven't switched over - yet), but not BootIt UEFI has been really useful. OT
Hi Brian! This whole thing may be a bit convoluted... more than one issue maybe. In the September time frame, MicroSloth issued an update that messed up the WinRE WIM on users Systems. All of a sudden, newly created Recovery Media (multiple apps) started failing when they started. It took about a month before users started to recognize that the WinRE.wim used in their Rescue media was blown. Suggestions were made at that time for users to recreate their media with WinPE WIMs instead... this indeed corrected the problem, at least until MS finally somewhat fixed the issue. As we know, WinRE-based WIMs tend to contain all the drivers needed for the System the WinRE was created on... so before Rescue MEdia failures began, users were happy (all even special drivers were on the media). As soon as broken media were recreated with WinPE... only basic driver sets from MS aere available on that media. The MS WinPE driver base does include a somewhat "standard" NvME driver... but not all NvME devices use that driver... yet. If a user has one of those "special" NvMEs, they need to specifically add it to the WinPE media creation process to make sure it gets on the media correctly. That's what caused my interest in this problem. If the OPs Rescue Media is WinPE-based, AND they have one of these special NvMEs in their System, if the special driver wasn't added during the WIM/media build process, that NvME will not be seen by the Rescue media. If the media was built using a working WinRE (not the MS scrogged one), then the driver for that special NvME will indeed be available... and the device will show up just like any other. This issue is like a convolution of multiple problems happening at the same time. In October, MS did offer an update for their error (without ever mentioning the error) and the broken WinRE.wim was supposedly fixed... I have never verified that, I don't use the WinRE.wim for any of my Rescue Media, only WinPE WIMs (I manage my own special driver needs... which has been very limited with my Systems). In the case of the OP's Macrium Recovery Media, if it was built with the bad WinRE, it won't even BOOT up properly. If it was built with WinPE, and they have a special driver required device, AND the driver wasn't made available during the media build... the media will not be able to see that device.
Macrium Windows environment & Recovery environment used to see source. Something went wonky some years back.
In the case of Hasleo's Recovery Media, with their newly PUBLIC released v4 (16 November), they now use WinPE for the basic media creation, but they make an attempt to add any needed System drivers for the System the media is being created on rather than use the resident WinRE WIM (which they have used from the beginning of the product). This process should find all those strange "needed" drivers and add them to the Recovery Media creation process. I have not checked this personally... I would have to piece together a strange System to check whether this whole process works. BUT... a user on 11 Forums had this exact problem using their Beta (he had to add his special NvME driver to the WIM build), and they report that the issue was resolved with the v4 Public release. That gives me some confidence that their newer driver finding protocol seems to be functional.
Very interesting, that answers some underlying questions. I mean, I can easily restore my system from within Windows but in the event of a catastrophic failure (somewhat higher risk in Windows Insiders), you obviously need the Recovery environ. I'm going to wait until this component is more mature before I attempt to add this on. Maybe in a few months.
TRF, Superb explanation for why there are boot disk issues with seeing certain drives. My confusion is why Macrium 8 can't see the internal drive in Windows. In bjm_'s computer. Hasleo and AOMEI can see the drive in Windows.
I did not realize REFLECT couldn't see the "internal" drive LIVE in Windows... the internal drive being lost is not the OS drive for sure. I have to reread his post to get back on track here
The strange thing is when @bjm_ ran the 1st ReagentC, he had (2) disks attached, one internal and (1) external. ReagentC found what looks like a whole System on Disk1 and identified its Recovery partition. When you asked him to disconnect Disk1 (the external), ReagentC found a slightly different full System on Disk0 and identified, correctly, its Recovery Partition. I don't know what kind of System that is, but @bjm_ should disconnect his external once again, then try and run Macrium and find a source disk. In fact, if he really had (2) full Systems connected when he installed Macrium, I'm not sure what it would see. My second recommendadtion would be to completely uninstall Macrium (everything), disconnect the ext drive, reBOOT the System, reInstall Macrium then reconnect the ext disk. Some wild, off the cuff, recommendations...
Quick question here on the Emergency Disk UFD. Cleaned up one and after installing newest HASLEO BACKUP SUITE 4 waiting on the selection of downloading from m.com. However there is an option to select OFFLINE PE Components. I'm not sure what that means exactly but would certainly be infinitely faster for the Windows 8.1 system this one is going to be used for with a HBS UFD. Something about m.com i have reservations about since the 8.1 to them is of no importance any longer. By the way, the HBS 4 installer threw a weird message. Twice. First time i had to Terminate the box, Second time it finished installing yet still with this weird box. Any ideas from those of you with 8.1?
Researched it on Windows Club dot com. Apparently nothing more than my 8.1 desktop security refusing shortcut creation.
@EASTER - See HERE for how to obtain an off-line version of the most recent WinPE offered by MicroSloth. It's a simple download tool that let's you get the currently supported Off-Line version of WinPE. It resides in the form of an .OPE file. Once you have it as resident, it may be selected during the Emergency Disk creation and eliminate the MS download issues. This has been available for years for use with all Hasleo/EasyUefi products, if needed. I keep the most current versions available for Win10/11 and Win07... the OSes I use the most. PS - MS moves very slowly when it comes to changing "ofishul" WinPE releases... waaaaaay less than windows updates.
Took HOURS but it did finish and i now have the HASLEO ufd ED ready to test today. TRF- Microsoft has have the absolute WORSE SERVERS ever. Believe it or not it's been that way for me since way back on 98 & XP. Nothing has changed with them on that. Ugh. But it did finish without hassle and HBS did the rest smoothly-efficiently! I will take a peek at your suggestion if nothing else just to have it on hand so i don't have to wait again on those MS snail crawl servers.
A little update on a possible PORTABLE version... The Devs have been playing around with my request to come up with a portable version that will work with any "matching" (x86/x64) WinPE... they are almost there. I have successfully tested one of their offerings with most of my x64-based diagnostic WinPEs (Strelec, AnkhTech, Macrium) and all have worked fine. I also tried that version as a fully portable version running under LIVE Windows (x64). An anomaly was discovered having to do with uninstalling a previously installed version of HBS (naughty, naughty... something they weren't doing that they should have) then trying to run the WinPE version as a portable. Once the anomaly was removed (by me, manually), the WinPE version worked fine as a portable. There's still some more work to do but it seems to be moving ahead nicely. This application, eventually available as a fully portable entry, would be a very nice edition to the world of imaging. For those who remember the AX64 imaging team... this group ain't them
