Macrium Rescue Media (USB), doesn't show in File Explorer.

As the title says, I can't see the MR rescue media in File Explorer, like I used to be able to.
It has also disappeared from the "Safely Remove Hardware" in the system tray.

However, it's visible everywhere else, and the MR Rescue Media stick... works fine.
I didn't notice this change until I made the .6036 Rescue Media USB stick, about 1.5 months ago. It's still the same on .6161
Before that, it WAS visible in File Explorer as well, and it showed as possible to "eject" on the "Safely Remove Hardware".

I don't know if MR changed or Windows 10 Home changed.
Before the change, I used to see... Macrium_PE (N:), in File Explorer.

SFC and DISM come up clean, multiple runs. No other issues with Win 10.
It's exactly the same in all USB ports (motherboard and case).

1 Have you used Disk mgmt to assign a drive letter? Let's say Q for my example below.

2 If you then want to assign drive letters automatically [instead of the hard-boiled one that Step 1 assigned], go to
HKEY_LOCAL_MACHINE\SYSTEM\MountedDevices
then find the
\DosDevices\Q:
entry and delete it.
- I have not been able to test this from your starting point because I have not had the problem but I think this procedure will still work because Step 1 creates a new 'starting point'.
- I tested the procedure from one that already had an automatically-assigned drive letter - I set it to Q in Disk mgmt., went to the Registry key & deleted it, pulled out the USB then put it back in and it was automatically assigned a drive letter.
- I also have a vague recollection of a Diskpart method of doing this to end up with an automatically-assigned drive letter.

If any problem remains, do check that you have not assigned a network drive to the same drive letter that you assigned to this USB in Disk mgmt.
See Using same letter for a drive and a mapped network drive hides that drive from FE [Kari #10] - TenForums

All the best,
Denis

@Try3

Well that worked. I assigned it drive letter N:, and it stayed assigned.
Lemme reboot and see if it stays assigned.


/edit

It stays assigned. I wonder what caused it to become un-assigned in the first place?
It was always auto assigned before about 1.5 months ago.


And... I don't seem to have a... \DosDevices\Q:





Drive letters currently used... C, D, E, F, G, H, I, J, K, L, M (SSD and HDDs), P, (DVD), and the just assigned N: for the USB stick.

Just plugged in my other USB stick (NTFS) and it came up no problem as... Local Disk (N:), and it shows up in AIDA64 Temperatures.

The other stick, (Macrium FAT32) doesn't show up in AIDA64 temps.

Q was just the example I used in my post.

Try3 said:

… Let's say Q for my example ...

If you want to return the USB to being auto-assigned a drive letter each time, my Step 2, then you'll need to find & delete your
\DosDevices\N:
entry.

All the best,
Denis

Ghot said:

...I wonder what caused it to become un-assigned in the first place?
It was always auto assigned before about 1.5 months ago.

When Macrium creates a rescue usb it only reformats the usb as a last resort, if it's already Fat32 it just copies the files to it. And if that usb already has a letter assigned it will remain assigned.

If Macrium needs to reformat a usb it will effectively appear to the OS as a new drive and will need to be assigned a new letter (quite possible reusing the one it had before). If Automount is turned off then a new drive may not be assigned a drive letter automatically.

Enable or Disable Automount of New Disks and Drives in Windows

Bree said:

When Macrium creates a rescue usb it only reformats the usb as a last resort, if it's already Fat32 it just copies the files to it. And if that usb already has a letter assigned it will remain assigned.

If Macrium needs to reformat a usb it will effectively appear to the OS as a new drive and will need to be assigned a new letter (quite possible reusing the one it had before). If Automount is turned off then a new drive may not be assigned a drive letter automatically.

Enable or Disable Automount of New Disks and Drives in Windows

Yeah. NoAutoMount is/was already set to ZERO. @Try3 had the right solution.

This will now be marked solved.