Question

  • Creator
    Topic
  • #2215959

    Error 800401F0 in CoCreateInstance: CoInitialize has not been called.

    Locked

    by debrarae ·

    I have a Laptop that aquired a Trojan. I have cleaned successfully. But now as soon as I log on as the user, I get the error box “Error 800401F0 in CoCreateInstance: CoInitialize has not been called”.
    How can I get rid of this

All Answers

  • Author
    Replies
    • #3005750

      Clarifications

      by debrarae ·

      In reply to Error 800401F0 in CoCreateInstance: CoInitialize has not been called.

      Clarifications

    • #3005747

      Hard to say from here where that is coming from

      by tony hopkinson ·

      In reply to Error 800401F0 in CoCreateInstance: CoInitialize has not been called.

      That is windows telling you, you’ve improperly called a COM control.

      Create another user from admin would be my first step to get going.

    • #3005719

      Interesting

      by rob miners ·

      In reply to Error 800401F0 in CoCreateInstance: CoInitialize has not been called.

      what was the name of the virus.

      Can you still logon to the account.

      If it isn’t a Microsoft Service, msconfig may pick up what is causing the problem.

      Click Start, Run type msconfig and press Enter.

      Now if you have the Configuration Utility open.
      Configure selective startup options
      In the System Configuration Utility dialog box, click the General tab, and then click Selective Startup.
      Click to clear the Process SYSTEM.INI File check box.
      Click to clear the Process WIN.INI File check box.
      Click to clear the Load Startup Items check box. Verify that Load System Services and Use Original BOOT.INI are checked.
      Click the Services tab.
      Click to select the Hide All Microsoft Services check box.
      Click Disable All, and then click OK.
      When you are prompted, save the settings and restart the System.

      If it is working in Normal mode re-enable one item at a time until you find out what is causing the problems.
      When you have it sorted out re-run the Configuration Utility and in the System Configuration Utility dialog box, click the General tab, and then click Normal Startup.

Viewing 2 reply threads