ok, it is working fine. it looks like the Resource name is set in your local user profile (in %APPDATA%/Spark/spark.properties file). This does not get over-riden if you are keeping your old profile while upgrading. To get a new resource, either change that, or kill the %APPDATA%/Spark directory to have it setup a new, fresh one.
the image shows some of my users and their resource name. everyone is on a custom version and all should read as Spark 2.7.0-20131016-jsc, but as you can see, we've got resources all over the place lol (we had a cavalier dev over here for a bit who liked pushing new versions for image changes lol). i have a script someplace that will auto-kill the %APPDATA%/Spark directory... i'll look for it... may help...