USB Bootable stick Drive C mixup

[Klaver7]

Hi am am kind new to this program, purchased a family package, but where I only like to work with bootable media I found some strange happenings.
When I am booted up with the "resque" and attempt to make a backup it wants to place it on C:\ =  thats my Drive E: in real time !
So is this Normal ? It sure messes with my old head as Macrium and others show true drive letters. Been around for a long times on computers, MS dos / Vic20 / Commodore 64 etc.
Next question is with Command Line, I it gives me the same mix-up with C:\ = act E:\  in other words I cannot get the real C: boot drive ! it does not show up in the browser.
Like I said before, I only work with bootable media as the full HD install would get into my way.
Thank you for a great program I think, just have to get used to the "Latin" drive mixup ...   ?? 


           
Anybody's help would be appreciated 

[CDC9762]

I never fool with the Rescue version unless I need to rescue which is virtually never. However, I booted my Rescue USB and said it would place the image on D:\... . This is the location specified in my default storage location which I setup when I first ran the real Windows version. If you haven't, maybe setting that up will do something but I don't really know and I also don't know to what extent Hasleo is concerned about parameters in the Windows version vs the Rescue version.
While there are drive letters, remember Windows always wants to call its active installation C: regardless of where it really is.

[Froggie]

First of all, Windows (the version being used in the running of the Recovery Media), under a WinPE BOOTable RAM image (almost all Recovery Media) does not use "C:", it uses "X".

My guess on Klaver7's problem is that his Recovery Media does not include the driver necessary for that storage device type to show up using the Recovery Media.  As such, we need to know a few things. Your 1st image shows the LIVE System device to be a Western Digital NvME Solid State disk.  So now we need to know... how was your recovery media built (were you using the Microsoft download option <WinPE> or not <the resident WinRE would be used>.

Depending on your method, the required driver for the Recovery Media seems to be missing or you would see that device in the 3rd image.  I would try rebuilding the Recovery Media using the option not used for the original attempt.  A Recovery Media built using the resident WinRE should have that driver in its residency.  A Media built with the WinPE option (Microsoft download + Automatic Driver injection) should also have that driver in residence.

If neither work, there is an issue with the needed driver for that System device.

[Froggie]

The other thing that appears to be wrong with this SYSTEM Image is that the Windows Recovery Partition is not selected in its configuration (Image#1).  This cannot be done manually when selecting a System Image backup (only during a Disk Image backup).  This is caused by Hasleo not being able to find a "registered" Windows Recovery partition when configuring a proper System Image task... how it got unregistered I haven't a clue.  If it really is unregistered, I don't know how Hasleo can effectively use the WinRE build option to produce a proper Recovery Media.

Maybe the Devs can jump in on this one.

[Froggie]

@Klaver7, to be sure you can rebuild your Recovery Media with any and all options, best to re-Install Hasleo which will get rid of leftovers from its previous build and allow you all the necessary options to do your new Recovery build.