All of my areas reverted to Parallel. Is that where yours was set before the firmware?
also after the update? not good. I’ve seen it happen it was because I hadn’t received the firmware. it’s just the angles I don’t mow grass in. 
Yes, mine did too and I reported this as an issue when I got the update. Updates should never change or override user defined settings without warning the end user.
I’ve learned that you need to check every damn setting after every update. They break every typical software practice they can find.
Negative. My spirals remained spiral and my parallels remained parallel.
Apparently YMMV.
Must be the dreaded Checkerboard that @bryan.wheeler and I use 
At some point I should try the checkerboard. Although, then I’d have to reset it after updates. 
It is all about us after all!
Don’t worry, you just haven’t found your Easter eggs yet.
I’m sure they’re hiding around here somewhere…
Same backs up, hits the button, then sits out there yelling til I notice
“Emergency STOP!” 
I just got my firmware update this morning after I had to stop the current work plan it was working on because of another issue. But I haven’t really had a chance to go back and double check settings. I suppose I should do that tomorrow.
One thing I did notice while I was working this afternoon is that the area perimeters and drawn no-go zones appeared to still be functioning correctly, but a number of the purely circular template no-go zones I placed appeared to not only be off in position (by 6-12 inches), but now appear to be the wrong size. If I didn’t know any better, I would almost swear that the map/rover is treating the radius as a diameter instead when it physically goes to navigate the map. In fact, I had two nogo zones that I had to almost double the original size before the rover would actually clear the related areas. Also I had a weird thing where the area that I was trying to restart after the firmware update when it got to a certain point in the map if I stopped the plan and tried to restart it at the same progress level, the app would give me a cannot map root error. But if I changed the present done to any other value it seemed to map just fine. Despite that, when I did get it to restart with an appropriate routing, it completed running that portion of the map without any issue.
Weird…
very strange. If you know the times, I’d submit a ticket so they can take a look.
The update shouldn’t change your area settings, so this behavior isn’t expected. I’ve already shared this issue with our team and sorry for the inconvenience caused.
I confirm…firmware update performed and everything remained unchanged.
Do you use checkerboard? I know both @cobradunn and I do and we were set to parallel after.
I have a spiral zone and the other adaptive
That could be why. I think it may have been related to the route angle that forced it for some reason. Just a guess.
Ok