I recently ran into this issue when we attempted to roll out an upgraded policy with 7.5.3.20938. Endpoints currently have 7.5.1.20833. I have a TAC case open about all of the failed upgrades- roughly 60%. I believe this is caused/triggered when the ...

We are experiencing the same issue. Retroactive device quarantine after failed attempts to quarantine and retrieve the .js files. The following are just a few for everyone's reference.  FilenameSHA-256model.js04a2d4cc48a18f82d46a1bd70d7115916c8f87a52...

Almost a year and we just purchased this device, without FMC, and even our professional services partner is unable to accomplish this. Any update on your end?.... If you can remember