@scooke This was indeed a bug in our restore UI. I have fixed this for 4.1.5