I'm going to give it another try...
When everyone downloads the update it comes across as a whole bunch of 1's and 0's. If you were to print out all the 1's and 0's and place a copy on the seat of the 2015 FLHXSE on the left and another copy on the 2015 FLHXSE on the right and then ask yourself the question... "So the bike on the left has a problem with AVC, and the bike on the right does not. What could be wrong? What is different between the two bikes causing this problem?" First off you would probably discount the identical printout of 1's and 0's sitting on the seat (representing the update software). You would probably say " Since that program is exactly the same, it must be something external to the program that is different." Some input external to the program must be different between the two bikes. Now that could be a whole range of things including user settings, and user operation as Boatman put forward. I don't know what it is. I do know that it must be something external to the 1's and 0's that everyone is supposedly downloading and installing in the bike.
That is why I have been saying look elsewhere in the settings, hardware etc. Ironically, it may be in the end that it gets fixed in another update, where enough robustness is included to handle out of spec sensors or whatever. Then everyone can just say "I knew HighOnHD did not know his a$$ from a whole in the ground!!"
