New
#220
I've had no issues with Spartan, not with composing posts (copy & paste, attachments, typing), not with anything else. Spartan in 10049, installed clean.
Well based on these I think I'll keep my current build and also create a new VM with the new build too. That way I can clean install rather than upgrade too.
Best of both worlds :). And easy enough to delete one of the VMs.
Curious that there has been no mention of problems using 10049 on a VM being resolved. Or did I miss it? I read this whole thread and saw nothing here about it.
You were possibly thinking about not being able to activate the Hyper-V role on a clean install of 10049 host. This was published as a known issue before 10049 came out.
This was fixed a couple of weeks ago by some KB update - I forget the exact number. I have tested Hyper-V host both as upgrade (which always worked) and clean install (which works after getting all the current Windows updates).
I gave up on trying to upgrade 10041 to the 49 version, it was causing too many problems even trying to get it.
I have it in VMWare the free version, but I haven't restarted it for a few days as I got so frustrated trying to upgrade thought I'd have a break from 10 for awhile.
Gabriel Aul @GabeAul · 20m 20 minutes ago @Henburyman Right now we think we cannot take 10049 to Slow because of the slow install bug. We cannot hotfix for it.