Internet Explorer Has Encountered a Problem - NTDLL.DLL

Since an update to the database definitions to FSecure all our work stations (Windows 7 and Windows 10) are receiving errors saying Internet Explorer has encountered a problem and needs to close when trying to access various sites.  If we uninstall FSecure the issue does not happen. It appears to be a definition update for Ultralight released yesterday afternoon that is causing the problem.

 

Is anyone else having problems?

 

I have logged a call with support.

MarkT

Best Answer

  • LakshLaksh Posts: 4,432 Community Manager
    Accepted Answer

    Hello Tamas,

     

    The fix has been released to the update channel as F-Secure Ultralight Core Update 2018-04-03_01. Please check if the device has this update installed, if not, please proceed to download the latest virus definition updates.

    etomcatMarkT

Comments

  • MarkTMarkT Posts: 9

    We are having huge problems today with sites that trigger connection control, more tests needed but same symptoms as the OP.

    Marcrp
  • ZoltarZoltar Posts: 23

    Hi All,

     

    Yes - we are having big issues as well with IE 11 on Windows 7 .

     

    Before I saw this post I had just posted the same question.

    This looks like it could be linked to the  Ultralight Updater update released yesterday 28 March around 12:11 GMT.

    Thanks

  • Rick1978Rick1978 Posts: 2

    Hi There,

     

    We are all facing the same issues.

    It has definately something to do with F secure 's recent updates.

    For some reason i found out that disabling the Shockwave flash plugin solves the crashing.

     

    Just wanted to share this info

     

    Geetings Rick

  • ZoltarZoltar Posts: 23

    Dupicate of the data in the other record for Internet Explorer Issues:-

     

    Hi Rick

     

    Thanks for that update.

    I just got an update from F-Secure.

     

    For a test on just one system, they got me me unregister the fsamsi32.dll & fsamsi364.dll  files.

    (We had identified the fsamsi32.dll  file as being as the cause of the crashing in some crash dumps we got out of IE)

     

    This action also seems to resolve the IE crashing issue.

     

    This has been fed back to F-Secure.
    They also  said that are now working on this issue as a "major incident" so hopefully we might see a permanent fix being released soon?

    (I do hope we see a global fix soon - I have a lot  of customers who are very unhappy with me :<(  )

  • ZoltarZoltar Posts: 23

    Is there anybody from F-Secure who could keep all the members / customers updated via this forum  on the progess / timescales of this "major incident"?

  • ZoltarZoltar Posts: 23

    Hi F-Secure

     

    Can we have update on when you hope to release the fix for the “bad” Ultralight update of 28 March?

     

    Currently I cannot get any response from Support about this “major incident”, and I feel a bit deserted by F-Secure at the moment.

     

    I have a work around in place for customers who have connected to our domain, but I have hundreds of customers who are working standalone who will not get this internal fix, and will not be able use our corporate Internet Explorer browser.

     

    They are relying on F-Secure to release a fix via their update channel

     

    Does anyone else have a way into support and know any updates on this issue?

     

    Thanks

    etomcat
  • etomcatetomcat Posts: 1,318 Superuser

    Hello,

     

    Please tell us if the hotfix has already been released for automatic distribution? I am seeing the IE crash problem on a Win7-x64 home computer protected by FSIS.

     

    Thanks in advance, Yours Sincerely: Tamas Feher, Hungary.

  • MarkTMarkT Posts: 9
    Update appears to have corrected the problems, thank you.
    etomcat
  • If the ntdll.dll file is creating an issue when you access it then it is not a common issue you have to delete that file before your computer has beed crashed and download ntdll.dll file again from the authorized website and it might be solve the issue.

This discussion has been closed.