I have the same issue
Another post says this is a known error and there will be a 3.4.1 release that fixes it.