Migrating from one edition of Windows 10 to a different edition of the same release is also supported. This includes upgrading from one release of Windows 10 to later release of Windows 10. You can upgrade to Windows 10 from Windows 7 or a later operating system.
Some interesting stuff in there including a new OOBE (out of box experience) screen that asks users to identify typical PC roles, so the OS can recommend tools, utilities and the occasional tweak or customization.This topic provides a summary of available upgrade paths to Windows 10. So sigh again, as I start digging int this latest Release’s capabilities. I certainly will be taking a bit more time to review Known issues going forward - for the next few releases anyway, until the sting of this current mis-step subsides a bit.Īnd indeed, that’s the way things sometimes go here in Windows-World, where some wounds can only be described as “self-inflicted.” Guilty as charged in this case. Take a lesson from my haste, and slow down to read those notes yourself before downloading and installing a new Dev Channel (or other Insider Preview) build. I have now been reminded that a bit more attention pays off in avoiding unnecessary reports of problems that, while they do exist, are already known to the developers and in the process of being fixed. I Should Know Better, and RTFM More Carefullyįlying through the release notes will occasionally - as was the case for me and Build 20231– cause a person (me, in this case) to fall victim to a known and documented gotcha. I guess that means I need a second helping of crow for not realizing the false alarm had an equally false cause. That small oversight corrected, I determined that as the Release Notes say “Office should still be there and working fine.” Indeed, once I actually had the software installed, that’s just how things turned out. Interestingly, it turns out that the default UWP app Microsoft Office Click-to-Run is enough to trigger the false alarm.Īfter a long series of troubleshooting steps, I got Office 365 installed on that PC (a Lenovo X380 Yoga laptop) when it had actually never been fully instantiated there.
Go figure!īut upon further investigation, I realized that I didn’t actually have MS Office installed on one of the two test machines that threw the Compatibility Assistant error. Though MS does say that this is a false alarm, things get more interesting when the Office Click-to-Run app is its cause.
0 kommentar(er)
