Salta al contenuto principale

bootable media builder error on create an iso

Thread needs solution

i'm receiving this error on creating a iso 

Code: 262.161(0x00040011)
LineInfo: 0x89F41C0C69EF02; File: k:\7048\builder\lib\basic_builder.cpp;
Function: BasicBuilder::GetExistingFileName; Line: 210;

Module: media_builder_vsa64_7048
Fields: name: bootwiz.sys, name2: bootwiz.bin
Message: The specified file does not exist.

how to solve this?

0 Users found this helpful
frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Messaggi: 22
Commenti: 3800

Hi,

Please check the HKEY_LOCAL_MACHINE\Software\Acronis\MediaBuilder registry key on the machine where you run the Media Builder. Most likely you'll need to change "SourceDir" value to C:\Program Files\Common Files\Acronis\MediaBuilder , e.g. the folder which contains the bootwiz.sys and bootwiz.bin files (it may point to Program Files (x86)\ folder erroneously).

Example:

[HKEY_LOCAL_MACHINE\Software\Acronis\MediaBuilder]
"SourceDir"="C:\\Program Files\\Common Files\\Acronis\\MediaBuilder"

Note that there are also paths to WinPE components in [HKEY_LOCAL_MACHINE\Software\Acronis\BootableComponents\Settings] which may also need adjustments to successfully create WinPE-based media.

If the above doesn't help then you'll need to contact our support team for assistance.

Thank you.

when i try to change the key path sourcedir according to your instructions the key reset to default path "program files (x86)"

i'm stuck on this issue! 

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Messaggi: 22
Commenti: 3800

Hi,

An alternative would be to create the folder manually at the same path as specified in registry and put the bootwiz.bin + bootwiz.sys files there. Though I'm not sure how registry keys are changed back to original values on its own - this should not happen. If there are still problems then I'd recommended contact our support team for assistance.

Thank you.