Hey Mitchel,
Thank you for bringing this up. I have heard that this issue is known and the corresponding parties may be investigating further.
A possible cause of this issue is:
Entering the command
>> path(<new directory>)
instead of
>> addpath(<new directory>).
This command changes the search path to its argument, which should be a string of folders. Herein specifying only one folder, renders MATLAB installation unusable, since MATLAB cannot find any of the important .m files it needs to execute while processing any commands entered - workspacefunc.m being one of them.
Exiting and restarting MATLAB should resolve this issue, since the default MATLAB path is restored if "savepath" is not called.
In the future, instead of the "path" command, please use the "addpath" command. This simply adds an extra folder to the pre-existing path instead of overwriting the entire MATLAB path
Hope this helps!
