Yes, this is still reproducible, have just tried it now.
Note: I have security profile set to Secured. I think the last time I used firmware update in VRM I was still on Unsecured. I might try with Unsecured again over the weekend as I am not sure if this is also causing this problem: