@danjben: Thanks for the report and the error log. We tested this ourselves against a couple other systems with 4.4 and found the same problem.
Right now we're focused on cleaning up the last remaining issues that affect the 4.3 release so that we can have that wrapped up by the middle of July. We'll dig a little deeper into what is causing the problem in 4.4, and if it's a small/simple fix, we'll incorporate that. But we're not going to delay our 4.3 release any longer if the 4.4 issue is time-consuming to either diagnose or to fix. If the 4.4 fix is complex, then I think we'll release the 4.3 variant in July, finish up some work we have for the desktop product's initial betas, and then work on a service pack for 4.4 after that.