Starting x64 uefi loader runtime error

Starting x64 uefi loader runtime error

Сообщения: 2
Благодарности:

Не подходит, конечно спасибо за отклик!Но пока с форматом диска GPT не проходит пришлось все удалять и переводить его в старый добрый MBR особой разницы в производительности не заметил,хотя и говорят что MBR медленнее происходит загрузка ОС!Блин забыл уточнить это на ноуте такие траблы были!там биос то урезан!а по поводу GPT и Secure boot мне не нужно навязанное мнение вендора и мелкософта!Итог :потеря лицензии и полное удаление всех данных которые были. заранее побеспокойтесь о данных и образе системы!
вот способ как превратить GPT в MBR:

Подключить жесткий Диск к другой работающей машинке(компу)
Я для этих целей решил воспользоваться программой Paragon Hard Disk Manager. В этой программе необходимо выбрать наш GPT диск, кликнуть на нем правой кнопкой и в появившемся меню выбрать пункт «Конвертировать из GPT в MBR». После того как мы согласились со всеми предупреждениями, необходимо применить выбранные изменения, кликнув по соответствующей кнопке на панели инструментов. В результате запустится процесс конвертации. В определенных случаях может потребоваться перезагрузка компьютера для преобразования. После выполнения мы получим диск с обычной загрузочной записью и неповрежденными данными.

Заметьте что все вы делаете на свой страх и риск. Не стоит винить автора этого поста, ибо он не виноват!))

Я лично использовал этот способ! И ПОТЕРЯЛ ВСЕ ДАННЫЕ И ЛИЦЕНЗИОННУЮ WINDOWS 8! потому-что не было возможности воспользоваться первым способом!

Для этого нам понадобится установочный диск с операционной системой. Я для этих целей использую свой диск с Windows 7. Загружаемся с него, доходим до выбора раздела, где получаем ошибку, и запускаем консоль. Для запуска необходимо использовать сочетание клавиш . Перед нами появится консоль. Теперь необходимо непосредственно запустить утилиту для работы с жестким диском — diskpart.

После запуска, при помощи команды list disk просматриваем список наших дисков, которые пронумерованы. Затем командой select disk # выбираем диск, с которым будем работать. Вместо # указываем номер нашего диска. После того как диск выбран, все операции будут производиться с ним.

Далее командой clean мы очищаем его от всей информации. После этого мы можем приступать к конвертации.

Команда convert mbr преобразует GPT диск в обычный.

После этого мы можем работать привычным нам образом с диском и устанавливать любую операционную систему.

Кроме того, при помощи этой утилиты можно создать разделы.

create partition primary size=n — создаст основной раздел, размер n мегабайт.

format fs=ntfs label=»System» quick — быстро отформатирует выбранный разде в файловую систему NTFS.

active — назначит раздел активным.

——-
В стремлении подражать кому-то,таиться страшная тайна потерять себя!

Источник

Runtime error starting Acronis UEFI loader

I use Acronis Tru Image Home 2014 on a desktop with Windows 8.1.
Desktop with i7-4770 cpu and 16GB onboard memory.

After installing Acronis startup recovery manager I get a runtime error:

Starting Acronis UEFI Loader
Runtime error: Error 0x10d00e: Failed to find
line info: 0xec492506f42e4db
$module: bootwiz_efia64

What causes this problem and what can I do with it?

Same prob error —
Starting Acronis UEFI Loader
Runtime error: Error 0x10d00e: Failed to find
line info: did not get
$module: bootwiz_efia64

What causes this problem and what can I do with it?

This is because the Startup Recovery manager is attempting to change and take over your Boot Records so that it can manage them itself instead of Windows. This is not a good idea! Would suggest that do not use Startup Recovery Manager as if you loose your system disk for some reason you will not have a good boot record to boot from after recovery. Having UEFI active on your machine produces the error. If you insist on using this feature you should be able to get it working by first disabling UEFI in your machine bios then once it is working reactivate the UEFI.

Источник

Runtime Error 0x1480012

I recently joined this forum because of one specific problem we encounter for a few days now.

We are about to roll out new workstations with their specific storage setup beeing:

Main: 1 SSD for System

Secondary: 2 HDD RAID 0 (LSI SAS2 MPT Controller) for Data

For OS Distribution we are using Acronis Snap Deploy 5 on Windows Server 2012 R2 (latest Updates applied on OS and Acronis Snap Deploy 5)

The Problem: booting via PXE Server, the client connects correctly to our Acronis Server and provides the four options: Acronis Snap Deploy 5 Master Image Creator, Acronis System Report and Acronis Snap Deploy Agent.

But no matter which option we choose: each returns the same error:

Runtime error:
Error 0x1480012
| line info: 0x76df0d19c4c8565a
| $module: bootwiz_efia64

Any previous machines do not have any trouble; all of the Options work fine. And since I wasn’t able to find anything about this specific error on the web or in this forum, I’d really appreciate any help.

Thank you very much in advance!

Martin, it may be that the network drivers are not loaded with the Acronis Linux environment kicks in. Version 1660 seems to be lacking drivers for some of the newer intel NICs. 1662 beta brought in those drivers. 1666 beta brough PCIE NVME support. There is no «official» version newer than 1660 and I’m not sure why that is. However, 1666 appears to be exactly the same as 1660, but with the better driver support. I’ll send you a PM with the link if you want to give it a try.

Also, the error is showing that it is unable to run the UEFI 64-bitloader. Are you pxe booting using legacy PXE or UEFI PXE? You may want to ensure both options are configured in your PXE server and try both options to see if one works better than the other with these newer systems. If possible, makes sure that legacy/CSM boot is enabled on these systems as well. if you are trying to legacy PXE boot on a UEFI only system, this could be another issue.

The Server loads the UEFI PXE, at least it says so before loading the menu. Thank you for the drivers, I’ll have a go with them later that day.

Same problem with v. 1666. In fact, I do not even need to choose any option to get the error. It comes up by itself after a few seconds.

See attached photo for reference.

So this error only occurs on these machines, but not others, correct? What is the make/model of the PC’s?

Do any of the other machines have a hardware raid as well? I am guessing here, but thinking the default Linux media may be choking on the RAID controller as it won’t have the necessary drivers. In Snap Deploy 5, you can create a .wim file and upload it to the server as a boot option too. You would want to be sure that the IRST driver and/or any specific hardware RAID controller drivers are injected into the .wim. FYI, it usually takes a lot longer for the .wim files to copy into RAM and mount so be patient if it looks like it’s taking a lot longr than usual.

Alternatively, have you tried the offline recovery media booting from a flash drive or DVD and using both the Linux media and the WinPE media to see if you can start the process on one of those instead? I have a feeling you’d stukk need to use WinPE for the RAID controller as the Linux media won’t have the necessary IRST drivers or any special controller drivers.

first of all, sorry for the long delay. Other projects kept us occupied until now.

Thank you very much for your suggestions, it worked exactly as you said. We added the IRST driver as well as the network driver to a new .wmi file and botted from this. Worked like a charm and now we got our image distribution back running as intended.

Thank you very much for your support and have a good one!

Happy to help and glad that that adding the drivers to a .wim file allowed things to get back on track!

Hi Bobbo (and anyone else who might help),

I have a problem somewhat similar to Martin’s. My problem is how to recover data that was backed up to a Seagate external hard drive (Seagate). I had used the backup software that came with the drive (DiscWizard, which is associated with Acronis). The backup was made from an old Dell computer running Windows 7, done on a weekly basis, the last one on August 20, 2017. These backup files are .tib files, with automatically generated names in the style of «Entire Internal Hard Disk_inc_b1_s121_v1».

The old computer recently died (would not reboot). I have got a new one (HP Pavilion 510, running Windows 10 Home), but cannot restore the data from the .tib files on the Seagate drive to this new computer. I tried two versions of DisWizard: a Serial-Number-Specific version (an older version) and then their latest version.

The older version of DiscWizard would run fine until it prompts me to restart the computer. But at the start of the restart I get the error message Martin also encountered:

Starting Acronis UEFI Loader(x64)(v.1.1.36)…

| line info: 0x76df0d19c4c8565a

Then the computer completes the restart, but with no data whatsoever restored.

I contacted Seagate and they gave me some generic instructions, including downloading and running their latest version of DisWizard. But this version does not clearly include a tool for data recovery. Only two tools seem possibly relevant. One is CLOSE DISK, which I do not want since I want to keep the Windows 10 on my new computer and not clone the old computer’s Windows 7. The other tool is ACRONIS UNIVERSAL RESTORE, but I would have to upgrade to and pay for Acronis True Image in order to use it. I would not mind doing this if I can be sure that it would enable me to recover the data, but a few quick searches appear to indicate that this tool is for something quite else.

I am not a computer-savvy person. The data on the Seagate drive is very important to me. But I would like to see if I can recover it before taking the costly option of sending it to a lab for recovery. Any help on this would be greatly appreciated! Thank you in advance!

Источник

Starting Acronis UEFI Loader Error 0x14800001

Windows 10, Clone the HD into a new Crucial BX200 SSD.

True Image ask me to reboot in order to clone it.

After confirming the reboot the following appears every time that I try to use the computer.

Starting Acronix UEFI Loader .

Error 0x14800001: An EFI runtime error

| line info: 0xce2309c6f8869211

see file attached

Francisco, try starting the clone from within your offline bootable Acronis recovery instead of in Windows (this is the Acronis recommended method).

1) Perhaps the default Linux envrionment of Acronis on the local machine does not have drivers for your hardware (can be the case with newer PCIE NVME hard drives). Booting wiht thhe offline reocvery media will confirm if you can see your drive this way or not

2) your bios may be preventing the Acronis bootloader from running (secure boot may need to be disabled).

3) Are you cloning to the same size disk? Cloning will fail if the disk is smaller than the original (usable space)

4) Cloing may fail if the sector size of the disks is different. Spinning drives 2TB and smaller use 512kb sector size. Spinning drives larger than 2TB and most SSD’s use sector size of 4K so a clone will fail. IN these cases you need to take a full disk backup and save the backup to another location. Then restore the backup to the new drive. The results will be the same, but you’ll also get a backup in the processs (which is good).

5) If the default Acronis Linux bootable media boots, but does not see your new hard drive, the drive may not be initialized yet. Use «add a new disk» to initialize the new hard drive first. If the disk is not found in this process, the Linux bootable media doesn’t have the necessary drivers for your new hard drive and you will need to create a WinPE bootable disk instead — try all of the other things before we get to that though.

BE VERY CAREFUL when initializing a new disk — this will format/wipe the one you select — if you choose the wrong one, you can wipe your original data and it will not be recoverable unless you have a good backup to revert to already.

Источник

Cannot restore C: drive. ATI aborts.

I’m at a loss. Have been using ATI for at least a decade with no issues. Use on two PC’s, both running Win10 Home. On desktop PC, runs fine. On laptop (Lenovo Y700, purchased March, 2016, came with Win10) ATI worked fine up until I upgraded from 2016 to 2018 versions. Instantly, could no longer restore start-up disk using the ATI backup I have scheduled to run every night. Would run ATI, all systems go, but when ATI forced a restart, something would «break» and the process would abort and take me back to the desktop. This meant that even though I was creating a nightly ATI backup, I couldn’t use that backup to restore the internal C: drive. I finally discovered that I could use another program (Macrium Reflect) to create and restore my C: drive to a second identical NVMe drive in an external USB enclosure. I’d much prefer to use ATI, since prior to these problems I simply had to run ATI to «restore disk», restart, and by the time I got back to the desktop in about 30 minutes I had a fully restored PC. With my Macrium solution, I have to run the restore process, then take my laptop apart to switch in the second NVMe drive. Much more of a hassle. But at least it works.

As I said, I was having absolutely no issues with ATI until I tried upgrading from 2016 to 2018 versions. Once I realized ATI 2018 wasn’t working properly, I uninstalled 2018 and reinstalled 2016 — but now that version no longer worked either. (I left 2018 on the desktop PC, since there were no issues there.) Still hoping for a miracle, I just upgraded to ATI 2019 from 2016, but have struck out again.

So this is where I stand now: ATI is basically useless on my laptop. Below are the messages which flash by on the black screen after a restart, before the Lenovo start-up logo appears, and just before the process aborts and I’m returned to the desktop:

Starting x64 UEFI loader (v.1.1.51).
Runtime error:
Error 0x1480008: Cannot get file «acroldr/kernel64.dat» from the partition with GUID 8520D290-5060-4986-B539-4145BC847E12.
| line: 0x76df0d19c4c85714
| file: K:/51/loader/efi/config.cpp:702
| function: GetFile
| $module: bootwiz_efia64_51
|
| error 0x1480018: Failed to open the volume by GUID.
| line: 0x76df0d19c4c856f8
| file: K:/51/loader/efi/config.cpp:674
| function: GetFile
| $module: bootwiz_efia64_51
|
| error 0x10d00e: Failed to find.
| line: 0xec492506f42e4d9
| file: K:/51/fdisk/volume_efi.cpp:115
| function: OpenVolumeByGuid
| $module: bootwiz_efia64_51

A few other data points:

Do not have a K: drive. I’m assuming ATI creates that drive to use when it forces the restart and then tries to find the K: drive to run the pretty blue ATI screen I used to see during the restore process. (Haven’t seen that screen in months.)

In the ATI forums I found a thread discussing similar issues. A suggestion which seemed to work for that user was installing Intel Rapid Storage Technology; which I did. I also went into my BIOS and made the only change which seemed boot-related, which was to turn on «PXE boot to LAN». Neither had any impact on my system, and I’m still seeing the same messages as above when trying to restore.

My issues may somehow be related to fact that I upgraded internal SSD from SATA 3 to NVMe. Now using 500gb Samsung 970 Evo, which is about as common a drive as is available, so it should work. (I don’t recall the exact timing of when I switched to the NVMe drive, and when I realized ATI wasn’t running properly and I couldn’t do restores of the C: drive.)

I use a RAM disk (disk D:) to handle browser cache and TEMP files. Could ATI be writing something to that disk, but then on startup cannot find it since it’s not loaded yet? Have used RAM disk for years, while using ATI 2016 and previous versions, with no issues.

That’s all I’ve got. If anyone can help me return to being a happy ATI user, I’d appreciate it.

Источник

В операционных системах выше windows 7, это версии 8 и выше, как правило для загрузки системы используется так называемый загрузчик UEFI.
Если система перестала загружаться и выдает например такое сообщение:

File :EFIMicrosoftBootBCD
Error code: 0xc000014CГ

Необходимо восстановить файлы загрузочной области UEFI.

Самый надежный способ, может показаться очень сложным для простого пользователя, но если все делать по пунктам как будет описано ниже, то все получится даже у простого пользователя.

Для восстановления загрузчика нам понадобится загрузочная флешка или диск с любым Windows не ниже версии 8. Но теоретически возможно и с  windows 7 (не проверялось).

Внимание! Вначале внимательно читайте, осознайте, что вы делаете, прочитайте несколько раз, а потом делайте.

Если проявите терпение и внимание то у вас все получится.

Итак начнем:

Вставляем диск в привод или подключаем флешку и загружаемся с него. Как загрузиться с носителя описано в начале этой статьи.

Здесь нажимаем далее

Здесь выбираем Восстановление системы

Затем выбираем по очереди: Диагностика — Дополнительные параметры — командная строка

После того как откроется командная строка набираем команду для запуска утилиты Diskpart:

diskpart

Посмотрим список дисков в системе

list disk

Выберем свой жесткий диск, если он один то это как правило disk 0.

sel disk 0

Посмотрим какие разделы есть на выбранном диске

list vol

после этой команды откроется такой список ваших разделов на выбранном диске

Раздел который нам нужен содержит загрузочный раздел размером 100мб, файловую систему Fat32.

(если его нет и у вас несколько дисков, то возможно вы выбрали не тот диск).

В моем случае это диск 3 (Том 3) — выделен красной рамкой на картинке выше.

Выбираем его

select volume 3

Чтоб работать с ним дальше, присвоим этому разделу свободную букву диска. Например K

assign letter K:

Выходим из утилиты Diskpart

exit

Переходим в директорию самого загрузчика (K— буква которую мы присвоили ранее)

cd /d K:efimicrosoftboot

Перезапишем загрузочный сектор на диске:

bootrec /fixboot

На всякий случай переименуем старую конфигурацию загрузчика

ren BCD BCD.bak

Теперь последний шаг, создадим новую конфигурацию загрузчика

bcdboot C:Windows /s K: /l ru-ru /f ALL

Пояснение: C:Windows — путь где установлена ваша windows, если установлена на другом диске то смените букву диска.

K — буква раздела на который копируются файлы загрузки операционной системы (мы ее присваивали ранее)

/l ru-ru — определяет принадлежность языка вашей операционной системы, в данном случае русский. По умолчанию используется английский.

/f ALL -в сочетании с командой /s это указывает тип встроенного ПО целевого системного раздела. («UEFI», «BIOS» или «ALL»).

Теперь набираем  несколько раз exit , нажимаем enter, пока не закроется окно командной строки.

Перезагружаем компьютер, и радуемся.

На этом все. Удачи!

7 ноября 2016