7 Replies Latest reply on Feb 9, 2012 6:01 AM by mfaizal

    is there a problem with 6613?

      Hi there,

      I'm getting v2datdet.msc not found after i placed 6613 on my ePO and now none of my clients are updated.


        • 1. Re: is there a problem with 6613?

          Discussion moved from Community Interface Help to VirusScan Enterprise for better attention.


          Message was edited by: Ex_Brit on 08/02/12 7:34:45 EST AM
          • 2. Re: is there a problem with 6613?

            What do you mean when you say 'placed'?


            - Checked in via ePOs 'Update Master Repository' task

            - Checked in via a superDAT install

            - Moved from the 'evaluation' or 'Previous' branches into 'Current'

            - or just randomly copied a file to a folder.

            • 3. Re: is there a problem with 6613?

              Are you able to complete the update succesfully once you uncheck the Block option from VSE AP "Common Standard Protection: Prevent modification of McAfee Scan Engine files and settings".

              • 4. Re: is there a problem with 6613?

                Sorry, checked-in via Checked-in-Package -- Updates -- Current branches. Because I use FTP as mean of client updates, I copied over ePO/DB/Software/Current directory to Ftproot. It work for years now till yesterday.

                I even remove DAT from Source Repository and re-added it again, still no joy. Btw, I use avvepo6613dat.zip (DAT for ePO)

                And have just did what "hem" suggest..still failed.

                • 5. Re: is there a problem with 6613?

                  Ok. I may know what's wrong now. deleting V2datdet.mcs on client machine managed to update DAT. somehow the file in client machine seems bigger than ones on ePO. Now I just need to find a way to delete v2datdet.mcs on every client machine to sort this out.

                  Any ideas how I can do this from ePO??

                  • 6. Re: is there a problem with 6613?

                    I have seen on another thread is this forum that someone suggested marking it as a PUP (potentially unwanted program) and VSE will detect it and remove it.


                    Obviously as it's a McAfee file it comes under the protection of the 'Access Protection - Prevent Modifications of Mcafee settings and files' policy so if you were to go down a scripted batch file route you'll to disable that policy temporarily.


                    I'll see if i can remeber where the other thread was and link it.




                    found It https://community.mcafee.com/thread/42366?start=0&tstart=0 post 9 in this thread


                    Message was edited by: Tristan on 09/02/12 09:56:00 GMT
                    1 of 1 people found this helpful
                    • 7. Re: is there a problem with 6613?

                      Many thanks Tristan. I'll try it out and hopefully can be made on my old ePO 3.6. It doesnt happen on my ePO 4.6 though..strange.


                      Not sure what's introduce in newer DAT, reckon starting 6612 and above.