Glad to hear that the “new” 5.10.1.1 fixed the issue for you. Personally I think they should have released it as 5.10.1.3 to indicate a change, but I suppose they didn’t because there is no reason to update unless you had a problem with the original version of the update.
|