Jump to content

anon

Member
  • Posts

    23
  • Joined

  • Last visited

Posts posted by anon

  1. Download the installer from here=

    http://www.online-armor.com/downloads.php

    although it says "Version 5.5.0.1557"

    contains the new version 6.0.0.1736.

    Note:

    New version (v6) dowloaded and installed. No problems.

    But when I made an update (through the "Update now")

    I had a message for a new version which needs an PC restart.

    PC restarted.

    Can you guess which was the "new version"?

    The old v.5.5!!!!! :o

    v6 installed once again, I switched the auto update "off" and I'm waiting to see what's going on.

  2. Adobe Flash did not drop a temp file when it ran until version 11 (or was it 11.2 when they made that change?). If you were to install Flash 10, you wouldn't see notifications about that temp file in OA 5.5.0.1557 like you did (although using outdated versions of Adobe Flash is a security risk, and is not recommended).

    The issue with the certificate not being trusted was an issue with OA 5.5.0.1557, however you only saw it when trying to install or update Flash until Adobe changed how Flash worked. Now, thanks to updates to Flash that cause it to run in a way that seems rather odd, you get to see the notification every time the Flash plugin loads.

    Thanks.

  3. Thanks for verifying :)

    temp files creation is not caused by OA.

    This is just how adobe flash works.

    "how adobe flash works" .....Since when?

    As far as I know the above mentioned story started in OA version 5.5.0.1557 with Adobe Flash Player version

    v.11.2.202.228

    http://support.emsisoft.com/topic/7839-flash-update-being-blocked/page__view__findpost__p__47815

    In previous OA/Adobe Flash Player versions everhing was normal (no old temp files for adobe flash player).....

  4. Unfortunately, we don't have an ETA. There is a fix, and it has been in testing, however there is a lot more than just this one fix that has been incorporated into the new Online Armor update, so it needs to undergo a lot more testing than would be required for just a single fix.

    Hi GT500,

    Version 5.5.0.1616 arrived (without fix :angry: ), problem remains..........

  5. ....

    EDIT: Well...I've cheered too soon. Just got the first popup again. I've came up with this workaround:

    1. Close IE.
    2. Delete all "FlashUtil32_11_2_202_228_ActiveX.exe" and "fpb.tmp" lines in Online Armor's "Programs" section.
    3. Add "FlashUtil32_11_2_202_228_ActiveX.exe" (from C:\Windows\SysWOW64\Macromed\Flash\) manually and allow and trust it (don't mark it as "Installer" though).
    4. Run Ccleaner to delete all IE related temp stuff.
    5. Start IE and navigate to some page with flash content.

    Done. Since we've trusted "FlashUtil32_11_2_202_228_ActiveX.exe" there should be one "tpb.tmp" line in Online Armor's "Programs" section now which is allowed and trusted too. Problem solved for me. ^_^

    May I ask you how can be added "manually"?

  6. After some testing, it looks like the the Flash plugin's BHO (Browser Helper Object) is loading as a randomly named temp file. I was able to stop it from popping up, however. I selected the checkbox to remember my decision, and I clicked theAllowbutton. I had to do that about 5 times before it stopped warning me about the temp file, however it no longer pops up now that I have done that.

    I made that also (3 days ago).

    There are no longer red pops up but...

    ... every time (when the IE starts), a new (allowed) temp file is created....

    ..... and a lot of greyed (old temp files) are accumulated.

    What about yours?

    Please see once again the fist screenshot "Programs" (1 allowed and running & 6 greyed old temp files) =

    http://support.emsis...7743#entry47743

    Delete all the temp files?

    Then, same story starts =>

    1. Red pop up (second screenshot).

    2. Select the checkbox to remember my decision, and click the "Allow" button.

    :mad:

  7. OK, I'll do some testing, and see if I can learn some more about this issue. It doesn't sound like it is related to an update, so I want to see if I can figure out why the Flash plugin is creating and running a randomly named temp file every time it loads.

    Theoretically, when the update is released to Online Armor that resolves the issue with installing/updating the Flash plugin, it should fix this as well. I will let you know more once I have had a chance to test this. ;)

    BTW: Is your Windows Vista 32-bit or 64-bit?

    Many thanks for your prompt reply.

    Windows Vista Home Premium SP2 32-bit.

  8. I've split this off into a new topic, since this looks like it is a different issue. I noticed this morning that Adobe added a new update mechanism here recently, and that must be what is being blocked.

    Please try downloading the latest version of Adobe Flash from this link, and let me know if installing it makes the notifications stop.

    It makes no sense as the latest version (v.11.2.202.228) for Adobe Flash Player (for IE) already dowloaded from this link=

    Flash Player 11.2.202.228

    (32 bit)

    Windows / Internet Explorer / Download EXE Installer

    http://www.adobe.com...tribution3.html

    it's the same installler as =

    3. Download and install the latest Flash Player version

    http://helpx.adobe.c...er-windows.html

    or that one from your link=

    Adobe Flash Player 11.2.202.228 (3.93 MB)

    http://get.adobe.com.../?promoid=BUIGP

    and the uninstaller from here=

    http://helpx.adobe.c...er-windows.html

  9. Did you mark the Flash installer as an installer?

    Yes, marked as Trusted and as Installer.

    IE closed

    IE opened again ----> A new pop-up comes every time => It appears that it generates a differently named .tmp file each time

    So far, everyone else has said that marking it as Trusted and as Installer has resolved the issue, and you're the first to mention that the temp file isn't trusted.

    So what?

  10. Just a quick follow up: I have just spoken to Andrey and he has confirmed the following information:

    • The fix will be tested in our next internal beta.
    • There is currently no ETA on a public release.
    • For now, simply mark the installer as Trusted and as an Installer in Online Armor to bypass the issue.
    • If proper rules are set up in Online Armor for the installer, then the temp file should be ignored.

    I have the same problem as skypilotpete.

    Your suggestion:

    "For now, simply mark the installer as Trusted and as an Installer in Online Armor to bypass the issue."

    not works because => "It appears that it generates a differently named .tmp file each time."

  11. 1) What's the MD5 (or SHA1) hash of the file you received via the updates?

    2) What's the MD5 (or SHA1) hash of the file you got after performing an upgrade install?

    1) -

    2) -

    3) Uninstall OA Free, clean remnants with Ccleaner, then manually downloaded and run the new setup (v5.1.1.1395 ) of OA Free (clean install)

    =>

    a2trust.dat: 01/11/2011

    a2wl.dat: 02/11/2011

    =

    a2trust.dat MD5 : fcbaeda2193291712a7158f353052d87 SHA1 : cd5b68aaacfc1f6b996a97ee83e89a78604fa7b2

    SHA256: 9da4f06b7cb7221dfdbedbde6d88d1e839774b2c370400ad46f76a69bfed118c

    a2wl.dat MD5 : d5cac90e622854cf82044e6bad5607f4 SHA1 : 88c7c54bec4fa4ec7f6420dee9ee0e6c2a3656ee SHA256: ff1fdde97804da7a9ed4e8a57b9c8985880f1491347fa76ff678a066a886a12c

  12. Any chance one of you could grant me access to his machine so I can debug it further? Because when I try to update on my test systems everything works just fine.

    Hi Fabian,

    I' m an old OA user (since Tall Emu & Mike Nash).

    Please let me know if you need a debug log.

    You should be able to get updates now and there should also be a new update to 5.1.1.1395 :). Be aware that the update server will most likely be a bit busy in the next 24 hours. So you may want to consider just downloading a new setup :).

    Please read post #15.

    Same story again. :(

  13. Thank you very much, Fabian.

    On my father's laptop, OA Free automatically downloaded the new program update and asked to reboot the system in order to install the new version.

    After the update process was completed, I immediately checked the a2trust.dat and a2wl.dat files:

    a2trust.dat: 19/10/2011

    a2wl.dat: 1/11/2011

    At that point I manually downloaded and run the new setup over the same version of OA Free.

    Now both files seems to be updated: 1/11/2011 11.33 (considering the date and time I guess those two updated files come with the installation package though).

    Anyway, I'll manually check for blacklist/whitelist updates in the next few days and see what happens.

    Hi Nick,

    Confirm the same problem here.

    1. OA Free automatically downloaded the new program update and asked to reboot the system in order to install the new version.

    => a2trust.dat: 01/11/2011 - a2wl.dat: 02/11/2011

    2. manually downloaded and run the new setup over the same version of OA Free.

    => a2trust.dat: 01/11/2011 - a2wl.dat: 02/11/2011

    3. Uninstall OA Free, clean remnants with Ccleaner, then manually downloaded and run the new setup (v5.1.1.1395 ) of OA Free (clean install)

    => a2trust.dat: 01/11/2011 - a2wl.dat: 02/11/2011

    a2trust.dat: 28 KB

    a2wl.dat: 318 KB

    ------------------

    With version 5.1

    http://support.emsis...ll-51-released/

    updates was just fine.

    Update problems started with version 5.1.1.1383

    http://support.emsis...11383-released/

    and continue now with the latest version 5.1.1.1395

    http://support.emsis...11395-released/

×
×
  • Create New...