A few words about this issue:Maria, I followed the instructions in that KB and this was what I got, on both my machines running the fully updated Parallels 10
View attachment 10074
I did that and when I try to install Win 10 it says my win 8 key is not correct. I verified the key by using a an app to extract it from the installation.I managed to update to Windows 10 by going to the microsoft site and upgrading manually, using the tool. After upgrade to Windows 10, virtual machine works fine.
http://windows.microsoft.com/en-us/windows-10/media-creation-tool-install
Hi BrianB1,I ran into this using the Windows 10 app. Thanks to this thread I was able to follow that link, download it and install seamlessly. Parallels also updated seamlessly after Windows 10 was installed. Seems like a minor glitch with the Get Windows 10 app which I'm assuming is there to let Microsoft control how many people are getting Windows 10. I thought that was the only way until I found this thread. Extremely happy so far with the process.
I certainly hope the people struggling with this right now are able to get it to work. My Macbook pro is a late 2013 model running Yosemite.
Hi BrianB1,
After the install how is the Control Center appears. I mean when you launch Parallels to start the VM. Mine is showing win 7.
Regards
Please try to reinstall Parallels Tools and check the issue.I had to change all language and region settings to US before I could run the upgrade tool. Now the remaining issues are completely due to Parallels 10 being incompatible with Windows 10 in coherence mode.
With reference to the screenshot below, one can see that the Start menu is obscured by the dock. I also prefer the Start menu to pop up right from the Windows icon, like with Windows 7.1
Also, background processes appear as applications in the dock. I do not want to turn off this option as I prefer to have running programs show up in the dock but background processes should not appear.
All of this just goes to show how incompatible Parallels 10 is with Windows 10.
I understand your concern Peter, but unfortunately we have no ETA before the fix is available.Maria@Parallels - Thanks for your continued responses in this forum. My current question is this: Is there any timeline that Parallels is willing to go on record with as to when this issue is properly addressed? The workarounds may be fine for some, but many folks (myself included) cannot trust various workarounds for fear of really losing data in the process.
Should have been included in a new version and not let us search in the Forum. Would have saved a lot of problems.Guys, and what about this KB? Did you try it?