cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
smartcat
Level 8
Report Inappropriate Content
Message 1 of 3

Fire wall UI problem ( new UI) v 16.0 fire wall v. 18.4

I just got new update for Mc.. Total protection. In new interface. By clicking on Fire wall on 2 of my 3 PC I do not see any associated drawers on the UI! Now I can not configure the firewall ports and applications and such. Are the any way to roll back to the old UI? Any solution to fix an issue? All PCs are windows 7 pro.2018-09-13 14_53_44-McAfee® Total Protection.png2018-09-13 14_53_06-gateway - Remote Desktop Connection.png

2 Replies
sanjay
Reliable Contributor
Reliable Contributor
Report Inappropriate Content
Message 2 of 3

Re: Fire wall UI problem ( new UI) v 16.0 fire wall v. 18.4

@smartcat

Which version of McAfee to you find installed on the Win 7 machines? Could you try runing MVT and see if it fixes the issue. If not please try reinstalling McAfee.

 

Cheers

Sanjay S

If this information was helpful in any way or answered your question, please mark it as the accepted solution and give Kudos if appropriate.
smartcat
Level 8
Report Inappropriate Content
Message 3 of 3

Re: Fire wall UI problem ( new UI) v 16.0 fire wall v. 18.4

As stated in title of this topic v 16.0 fire wall v. 18.4.
I found this solution very typical for McAfee , any issues ... "go ahead and reinstall, AND see if it fix the  problem".
I want to understand a release testing process in McAfee, if any.
Not so far ago new GUI was introduced to a customers which had 50% of tools ( options) missing ... then it was rolled back to an old GUI. Now a new GUI appeared again with different issues.
As I know McAfee has all its customers emails, why not to send a little update that " we are planning a major release, expectations are... new release will required latest win patches make sure you have it...", McAfee why don't you try to be proactive? Some of us stay with you for more then a decade, I think we deserve a better communication!

Its appeared that GUI changes are depends on . NET Frame work update KB4457918.
So first why deployment package does not check for dependency? Secondly why some portion of a Framework is not a part of a deploy? Millions of customers have different system configurations, that validation of minimum requirements before deploy MORE then necessity.  I am pretty sure that McAfee doing its development and testing  on latest win systems like 10 and win 7 with all KB installed that is why it is away has an issue.

Lucky for me that I am a developer my self and have an ability to debug and figure things out.

How Many Badges Can You Collect?
Ready for a little competition? Members like you are earning badges and unlocking perks for their helpful answers. Are you? Click here to find out.

Community Help Hub

    New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.

  • Find Forum FAQs
  • Learn How to Earn Badges
  • Ask for Help
Go to Community Help

Join the Community

    Thousands of customers use the McAfee Community for peer-to-peer and expert product support. Enjoy these benefits with a free membership:

  • Get helpful solutions from McAfee experts.
  • Stay connected to product conversations that matter to you.
  • Participate in product groups led by McAfee employees.
Join the Community
Join the Community