BurnAware Patch 1.11 (Premium/Pro x86/x64)

RELEASE INFO

  • Date: 2024-02-29
  • Version: 1.11
  • Type: Patch
  • File: Patch.exe
  • SHA256: F856A422295AB0312C3E907BC5580FBE3604E612937DD93512EF611E0D752E3C
CHANGELOG
  • Release for BA 17.5: Fixed new license/integrity checks.
Password: RDX2024

Comments

  1. Making ISO does not work after latest Patch and shows Access violation error, Can you please fix that?

    ReplyDelete
    Replies
    1. Because you're using installers from the developer site downloaded after the day that I posted this release. The dev always changes or add new license checks after I release the patch. Remove the copy you have, use the installers I provide in this post and you won't have any issue.

      Delete
    2. I installed "burnaware_pro_17.5_x64" from "BA 17.5 Installers Backup" link, but same error occurred again, here is the steps to reproduce the issue:
      1. Open BurnAware 17.5
      2. From "ISO Images" menu Select Make ISO
      3. Drag some files onto it
      4. Click on Make
      5. Give it a name and click on Save
      6. You will see this error:
      Access violation at address 00007FFC405AFF1D in module 'badata_x64.dll'. Read of address 0000000000000000
      ---------------------------
      BurnAware
      ---------------------------
      Some problems occurred while checking files.

      Would you like to continue anyway?
      ---------------------------
      Yes No
      ---------------------------
      I hope you find a solution to this problem, thanks

      Delete
    3. I always test that functionality along the rest. Here you have a GIF with a screen recording of the test I did:

      https://i.postimg.cc/3wPDHz5n/e-XUEt-Wt-WYU.gif

      As you can see, everything went ok. Hence (and because nobody else reported such problem so far) I presume that must be something in your system that is causing that issue. Check your AV just in case.

      Also can be a bug in the program that manifests under some environments or system configuration. In that case depends on the dev to fix it.

      Delete

Post a Comment