an error massage when creating rescue CD

Discussion in 'ESET Smart Security' started by George942, Mar 22, 2010.

Thread Status:
Not open for further replies.
  1. George942

    George942 Registered Member

    Joined:
    Oct 11, 2008
    Posts:
    13
    hi,
    when i try to create rescue cd i am getting error:
    "selected MSI file does not exist"

    i have eset smart security 4.2.35.0 64bit installed on windows 7 home premium 64bit
    how i can solve the problem?
    thank's
     
  2. Mantis

    Mantis Registered Member

    Joined:
    Apr 24, 2010
    Posts:
    3
    Same issue on Windows Vista Home Premium x64. Could this be an issue with the Windows version installed?
     
  3. agoretsky

    agoretsky Eset Staff Account

    Joined:
    Apr 4, 2006
    Posts:
    4,032
    Location:
    California
    Hello,

    ESET SysRescue discs make use of the 32-bit version of WinPE, which requires an installation of the 32-bit version of ESET NOD32 Antivirus or ESET Smart Security. If you are running the 64-bit version of either ESET program, use your license credentials to download and save the 32-bit .MSI installation package for ESET NOD32 Antivirus, then start the ESET SysRescue wizard. On the Current Settings page, click on the Change button to view the properties for the recovery disc you are creating, select the ESET Antivirus tab and specific the path to the 32-bit MSI file you downloaded in the ESS/EAV files section of the dialog. Click on OK at the bottom of the dialog and continue with making the ESET SysRescue recovery disc.

    Regards,

    Aryeh Goretsky
     
  4. Cudni

    Cudni Global Moderator

    Joined:
    May 24, 2009
    Posts:
    6,956
    Location:
    Somethingshire
    Any plans to make it run using 64bit installer?
     
  5. agoretsky

    agoretsky Eset Staff Account

    Joined:
    Apr 4, 2006
    Posts:
    4,032
    Location:
    California
    Hello,

    Support for 64-bit versions of Microsoft Windows PE might be added in the future.

    Regards,

    Aryeh Goretsky
     
Thread Status:
Not open for further replies.