Forum Discussion

Alpay's avatar
Alpay
Icon for New Contributor rankNew Contributor
6 months ago

Corrupted Early Power Estimator (EPE) for Cyclone V (epe_zlib_64bit.dll not found)

Hello,

I downloaded Cyclone V Early Power Estimator using the following link: Early Power Estimators (EPE) and Power Analyzer | Altera

It seems the provided Excel file is corrupted. Even though I followed the instructions under "Known issues for Early Power Estimator (EPE) tools" and the following discussion (Cyclone V Early Power Estimator not opening - Intel Community), I am not able to run the macro. For this reason, I created a new post.

My colleagues also have the same issue. All of us have Windows 11 OS and the latest version of Microsoft Excel. Even our IT department could not solve the issue in case there was a problem regarding Microsoft.

I attached the screenshot for the error that I got. (epe_zlib_64bit.dll not found)



In the near-past (even a couple of weeks ago), I was able to use the tool. Now I cannot edit my files too for previous early power estimations.

Is there anyone facing with same problem and could overcome the issue?

Thank you in advance.

Best Regards,
Alpay

8 Replies

  • WZ2's avatar
    WZ2
    Icon for Frequent Contributor rankFrequent Contributor

    Hi there,

    here is my colleague Nazrul Naim's response in your old question, is it helpful u or didn't solve issue?

    Regarding your issue. Please follow the steps below :


    Microsoft has released an update to fix this issue, please go to the corresponding Microsoft Support Page based on your Excel version:

    · Excel 2013*: https://support.microsoft.com/en-us/kb/2920754

    If the above update doesn't fix the issue, or if you do not have access to these updates, try the following workaround steps:

    1. Reboot the computer if you've installed the above update.

    2. Close all Microsoft Office applications including the Excel* and Word* applications.

    3. Open a Windows* Explorer, and enter "%temp%" (without quotes) into the address bar.

    4. Press "Ctrl" + "F" and enter ".exd" (without quotes) into the search box.

    5. If any files with extension ".exd" are found, select and delete ALL the files that are found.

    6. Next, enter "%appdata%" (without quotes) into the address bar. Again, press "Ctrl" + "F" and search for ".exd", and delete ALL the files that are found.

    7. Reopen the EPE.

    If the issues remain, follow these steps:

    1. Launch the EPE tool, go to File -> Info-> Compatibility Mode, and click Convert.

    2. If a pop-up appears, click OK to proceed with conversion, and then click Yes to reopen the workbook.

    The previous steps convert the original ".xls" EPE file into a ".xlsm" file. The newly created file should not exhibit the original issue.

    Microsoft's description for this issue can be found at:

    https://support.microsoft.com/kb/2726958


  • Alpay's avatar
    Alpay
    Icon for New Contributor rankNew Contributor

    Hello,

    Thank you for your response. I followed the steps that you provided once more and unfortunately it did not work. We use Microsoft 365 and Windows 11 OS. Unfortunately, none of my colleagues are able to run the macro due to same environment. Until a month back, we were able to run it, now we are not.

    Could you try to run it in your side too? Please let me know if you can run the macro without an error.

    Kind Regards,
    Alpay

  • WZ2's avatar
    WZ2
    Icon for Frequent Contributor rankFrequent Contributor

    Hi there,

    Could u try these step in your pc:

    1. Close all Excel processes (including EPE).
    2. Go into Windows Explorer (File explorer)
    3. Type %TEMP%\EPE_Tool into the address bar
    4. Remove everything in this directory.
    5. Try opening EPE again.

    ​Best regards,

    WZ


  • Alpay's avatar
    Alpay
    Icon for New Contributor rankNew Contributor

    Hello,

    I followed the instruction that you suggested. Unfortunately, I still get the same error.

    It seems it is possible to run the macro on a PC W11 23H2 but not on a PC W11 24H2. Since we all have PC W11 24H2, we still have this issue.

    Regards,
    Alpay

  • dloesch's avatar
    dloesch
    Icon for New Contributor rankNew Contributor

    I seems the issue isn't solely Intel’s side; I found this link:

    https://learn.microsoft.com/en-us/answers/questions/2288277/dll-file-not-found-when-invoking-function-from-exc

    (it references another thread that i haven't found)

    But it seems like excel has changed the way it references dll files and so these files will be broken on all up-to-date systems until intel update their excel files.

    I'm using windows 10 and office 365 excel and have the same experience of everything working a couple months ago and then all my historic and freshly downloaded files giving errors.

    The sheet is password protected and so i can't go in and change the vb code to change the reference to the dll, and guess intel don't want a discussion on how to bypass this. But as it will affect all files that references a dll (so assume all intel’s exl file) we should see an update soon. I'm using the MAX 10 for example.

  • dloesch's avatar
    dloesch
    Icon for New Contributor rankNew Contributor

    Just for those looking here hoping to find an answer, I submitted a ticket and was told the excel sheets aren’t being updated as they are final and I need to install a legacy version of excel to run the sheet.

    I have confirmed the issue is the relative file paths and putting in full file paths should fix it, but intel has also refused to share the password to the excel sheet due to IP concerns.

    I guess it will need someone with more sway than me to get intel to update the excel sheets.

  • Hello everyone.


    I also encountered the same issue on Windows 11 24H2, Excel Version 2507 Build 19029.20184.

    I recalled that EPE was working earlier this year, so I thought rolling back Excel might resolve this issue and tried it—and it actually worked.

    I used the link How to revert to an earlier version of Office and rolled back to Excel Version 2501 Build 18429.20132.

    While this doesn't provide a fundamental solution to the issue of it not working in the latest version of Excel, given Intel's lack of enthusiasm for fixing the EPE vulnerability, I believe this method is currently the most straightforward option.

    ​Best regards

  • I was able to get the EPE to work finally on my Windows 11 PC running Office 365. When I first opened the EPE, it created the epe_zlib_64bit.dll file in the same directory as the EPE, but that still did not enable the macros in the EPE. I made copies of the epe_zlib_64bit.dll file in these folders:

    • c:\Windows\System32
    • c:\Windows\SysWOW64

    I closed all instances of Excel, opened the EPE, and the macros worked fine.