1 2 Previous Next 11 Replies Latest reply on Nov 29, 2012 6:29 AM by Peter M

    McAfee's Security History no longer accessible

    stephe

           Ever since the introduction of the version of McAfee's Security

      History that allows the user to choose from day or week or whatever,

      it has been taking longer and longer to access my Security History. 

      Now, I can't get access to it at all.  I think that this might be a

      glitch on McAfee's part.

       

      Quoted from McAfee Communities user dwdeclare at

        https://community.mcafee.com/message/264851 :

       

      "The security history for my mcafee internet security 11.6 will not load.

      when i click on "security history" i get the "please wait" prompt and the

      mcuihost.exe begins to take up a lot of cpu. when i close the security

      history window after waiting for several minutes, the mcuihost.exe is

      still going and i have to end the process via windows task manager."

       

           I am in the same situation as user dwdeclare.

       

           It reminds me of the situation with Navigation > Quarantined

      and Trusted Items > Quarantined Potentially Unwanted Programs, where

      it used to be that if you had McAfee set to detect and delete cookies,

      the list of Quarantined Potentially Unwanted Programs would become

      so large that the feature would be inaccessible.  There was a fix for

      that problem, though, whereby the file could be located on one's hard

      drive and flushed.  I wish there was a similar fix for the Security

      History issue.

       

           I have the process management program called Process Lasso Pro

      (made by Bitsum Technologies), and there is a feature where if you

      click on the All processes tab and place your cursor over a process,

      you will get a box that shows a whole lot of information, including

      the location of the process on your hard drive.

       

           This is the location given for mcuihost.exe (see attachment for

      screen capture JPG of Process Lasso's information):

       

      "C:\PROGRA~1\McAfee\MSC\mcuihost.exe"

      /body:misp://mscjsres.dll::logs.html/id:misp://mscjsres.dll::logs.html

       

           The presence of html in the pathway makes me wonder whether

      McAfee's current Security History feature requires retrieving data

      from the internet.

       

      Message was edited by: stephe on 11/28/12 1:33:54 PM CST
        • 1. Re: McAfee's Security History no longer accessible
          Peter M

          As I said in your other post perhaps it's best to contact Technical Support in this case as I am not too sure if it's possible to delete logs without corrupting the installation.   FYI my Security History (same version of MSC) took around 10 minutes to load, but they did load.

          • 2. Re: McAfee's Security History no longer accessible
            stephe

            >FYI my Security History (same version of MSC) took around 10

            >minutes to load, but they did load.

             

                 Don't you think 10 minutes is about 9 minutes too long?  The

            previous version of Security History didn't have this problem.  I

            hope McAfee fixes this.  I think the problem lies in the feature

            loading scads and scads of data regardless of whether the user

            wants data from only that day, or for the whole week or month.

             

                 I think it's a great imposition to make every user wait so

            long every time.  It makes one think that the component is broken.

             

                 I have not tried waiting more than four minutes.  I shall

            now.  I'll give it the ten minutes that you said you had to wait.

             

                 Thanks for the tip.

            • 3. Re: McAfee's Security History no longer accessible
              Peter M

              Oh I agree with you, it shouldn't take as long.   I'll bring this up with McAfee at our next conference call on Monday afternoon.

              • 4. Re: McAfee's Security History no longer accessible
                stephe

                     Okay, it took six minutes.

                 

                     I think the problem is that the file that McAfee loads is

                prohibitively large.  There are option pulldown menus for "Show"

                and "For," and they have way too many things to choose from.

                Specifically . . .

                 

                Show:

                . Everything

                . Scans run

                . Spam update activity

                . Incoming connections blocked

                . Outgoing connections blocked

                 

                     I preferred it when each of the above could be selected

                separately before having to wait for the whole kit and caboodle

                to load.

                 

                For:

                . Last 24 hours

                . Last 7 days

                . All days

                 

                     Well, there's the problem.  I shudder to think of what

                McAfee interprets as "All days."

                 

                >Oh I agree with you, it shouldn't take as long.   I'll bring this

                >up with McAfee at our next conference call on Monday afternoon.

                 

                     Yay!  Thank you, thank you! 

                • 5. Re: McAfee's Security History no longer accessible
                  Peter M

                  LOL on mine All Days didn't elicit any more items for some unknown reason.  I agree that something isn't quite right here and have made it a topic for our next conference call.

                  • 6. Re: McAfee's Security History no longer accessible
                    Hayton

                    Ten minutes? Less than 60 seconds on mine, but for a good reason : there's hardly anything there. As I noted in another thread the latest information was added to Security History on the 13th - just notes of 3 scans since that date.

                     

                    As for the intense activity during the loading phase, it looks like that's because it's querying one or more SQLite databases.

                     

                    mcuihost thread.JPG

                    • 7. Re: McAfee's Security History no longer accessible
                      Peter M

                      Well maybe less but it did give me time to boil a kettle and make a cuppa.

                      There are 2275 items in mine.

                      • 8. Re: McAfee's Security History no longer accessible
                        stephe

                             I've been getting about 250 cases of

                         

                        Suspicious incoming connection blocked

                         

                        notices per day for awhile now.

                         

                             (A lot of them come from the IP address 73.157.160.1 for

                        some reason.)

                         

                             Presumably, that is why it takes so long for McAfee to show

                        my Security History.

                        • 9. Re: McAfee's Security History no longer accessible
                          Peter M

                          That belongs to Comcast Cable according to utrace.   I get quite a lot each day too and always have since I first went on the web.

                          1 2 Previous Next