Update still redirects to page WITHOUT McAfee opt-out

[Ash0D4D]

Hello, I have seen this as an issue in the past (as long ago as 2013) and experienced the same as others did. I updated Flash Player from an Adobe window that would usually open on start-up of my computer. I followed a link to update (https://get3.adobe.com/flashplayer/update/plugin/) -- this link DOES NOT have the checkbox to opt-out of McAfee Security Scan Plus. There is also no option to stop the download once it has started. Please fix this redirect link, otherwise the user has to uninstall McAfee after installation. I'm tired of people saying users are negligent and blindly agreeing when in fact the OPTION ISN'T THERE on this update link that is navigated to from the Adobe update notification.

[Ash0D4D]

If you refresh this page you can see in the middle "About:" section where the normal "Optional Offer:" section begins to load and then is replaced with this About section. I realize one could download Flash Player from the download page that does have the opt-out, but this link should still be fixed. I have tried turning off any antivirus browser extensions and can still reproduce this issue.

[Ash0D4D]

UPDATE: After trying with different browsers, this does not happen on Chrome or Edge. It also does not happen on Firefox Private windows for me. It only happens on normal Firefox (extensions are disabled).

[Test Screen Name]

If the problem has been around since 2013, I hold out little hope this will change in the 4 months before Flash Player shuts down forever... there are probably other priorities. 

[Ash0D4D]

A good point!

[jeromiec83223024 · Accepted solution]

Just for transparency, I spent some time on the forums tonight while I was imaging a machine and ran across this thread.  I attempted to reproduce this, but I'm not able to.  

This is Firefox 81 on Win 10 from my home network:

https://documentcloud.adobe.com/link/track?uri=urn:aaid:scds:US:53f6ae60-41c3-44d9-9063-0ada598a5148

I did notice that when I checked on Firefox for Mac I was not presented with an opt-out dialog, but that's because there's not a bundled offer targeting that browser and OS combination in the US.  In that instance, the product download center provided the full 21MB installer without a bundled offer payload.

As you've observed, Adobe monetizes Flash Player downloads through various bundled offers delivered via the Adobe Product Download Center.  The distribution happens downstream (I work on the actual product), and my knowledge of how that system works is fairly high level.  The gist is that the downloads are typically monetized through some kind of product offer.  Those offers vary depending on the operating system, browser, language and geographical location of the user.  

I'm always more than happy to take a look at stuff like this, and to advocate for users where I can.  Also, to be clear, I'm not disputing that this happened.  At the same time, I can't have an actionable conversation with another engineering team without the kind of high quality forensic detail that would allow them to conduct an effective investigation.

The easiest way would be to reproduce it, but given the complexity of that targeting ecosystem, that's pretty hard.  Where I can't see the issue, if I had something like a screenshot, are pretty precise time (e.g. the file creation timestamp from your end) that the problem happened, your public IP, the operating system and browser (and versions), and the name and/or hash of the file that was downloaded, then I could realistically send someone to go digging through the literally billions of records in Splunk to determine a root cause and get it fixed.

If you run into this again, please absolutely feel free to send me a DM.  I'll do my best to escalate it internally and get it fixed.  I don't have any input on our business approach, but I'm invested and empowered to make sure that those systems perform to spec.  I'm more than happy to continue to advocate on this front when I have enough info to be effective.