Direkt zum Inhalt

Bootable media creation - 1. How to include additional drivers for internal SSD drive? 2. Where can the drivers be found?

Thread solved

Dear community members,

after having taken the first hurdles with Acronis True Image 2020 a new problem came up:

I have created a bootable media on a USB stick by the so called “Simple method”. As far as I understand, this way a WinRE-based media with Acronis plug-in was to result. At first glance it seemed all was fine. I was able to boot the system and subsequently the plug-in showed up.

My problem: After checking different issues with the plugin, I concluded that probably the internal SSD drive (system drive c) is not being recognized properly. Although the drive somehow was to be seen as drive c, but in difference to others, e..g., existing folders are missing. Moreover, when I tried to recover a data file to drive c:, the recovery process failed. My conclusion: Some of the drivers were missing. Was this correct?

               grafik

Next, I tried the “Advanced method” with again the WinRE-based method (toolkit one below).

                         grafik 0

The following window for driver inclusion popped up:

                         grafik 1

My further question:

What exactly is requested here, what folder or folders, what content? Where can I find the missing drivers? (My hope is that I can find the necessary drivers somewhere on the system drive. So, e.g., a folder >this computer> c (OS:)>Drivers is existing.

Some additional information:

The system I am using is a brand-new notebook Dell Inspiron 3501, the internal SSD system drive is a Western Digital NVMe PC SN530 NVMe WDC 512 GByte. The device manager is delivering the following information

              C:\Windows\systems32\Drivers\disksys

               C:\Windows\systems32\drivers\EhStorClass.sys

               C:\Windows\systems32\Drivers\fltsrv.sys

               C:\Windows\systems32\drivers\partmgr.sys

which seems to be incomplete.

Please, may I ask you for your help again.

Thank you very much!

 

 

0 Users found this helpful

Lothar, the device drivers only have one purpose which is to make the disk drive(s) visible and accessible in the rescue media environment, they do not have any bearing on the content of the disk drive or what folders may be shown or not.

If you are seeing your WD NVMe 500GB SSD then you have the correct device drivers.

One important factor with using the Acronis Rescue Media is to always boot this using the same BIOS mode as used by your Windows OS.

When booted into Windows, run the command msinfo32 and look at the BIOS mode value shown in the right panel of the report shown.  This should be UEFI for an NVMe boot drive, and this is how you should boot the rescue media too.

KB 59877: Acronis True Image: how to distinguish between UEFI and Legacy BIOS boot modes of Acronis Bootable Media

Lothar,

I see in your picture capture that you have 2 drives with the same name.  In the image they are represented by letters C: and F:   Be advised that when booted to the bootable media your normal drive letters may not be the same as they appear in Windows.  This leads to my question, did you select the F: drive and look inside?  It just might contain your missing folders.

It is recommended that you assign unique names to your disk drives so that you do not have to rely on their letter to determine which drive they are due to the condition above.

If it turns out that you need the driver for your OS disk look in my signature below for a link on a how-to on the subject.

Hello Steve, hello Enchantech,

thank you very much for your quick responses. You helped me very much to solve my problems.

Perhaps two comments to the solution:

The issue was not the BIOS mode, I had checked it already before having written my post.

Therefore, I inserted drivers into the rescue media (second link, Enchantech, a great tutorial!). However, when executing the first time the procedure the .wim-file creation terminated with screen

                                          grafik 2

It helped to reformate the USB-stick and to reboot the system with the connected USB-Stick. The subsequent execution of the Rescue Media Builder was successful.