Slashdot Mirror
Windows 10 Upgrade Strategies, Pitfalls and Fixes As MSFT Servers Are Hit Hard
MojoKid writes: The upgrade cycle begins, with Microsoft's latest operating system--the highly anticipated Windows 10--rolling out over Windows Update for free, for users of Windows 7, 8 and 8.1. For those that are ready to take the plunge over the weekend, there are some things to note. So far, Microsoft has been rolling out the upgrade in waves and stages. If you are not one of the 'lucky' ones to be in the first wave, you can take matters into your own hands and begin the upgrade process manually. While the process is mostly simple, it won't be for everyone. This guide steps through a few of the strategies and pitfalls. There are two main methods to upgrade, either through Windows Update or through the Media Creation Tool. In either case, you will need to have opted-in for the Windows 10 Free Upgrade program to reserve your license. Currently, the Windows Update method is hit or miss due to the requirement for additional updates needing to be installed first and Microsoft's servers being hit hard, leading to some rather humorous error messages like the oh-so helpful description, "Something Happened." Currently, it would be best to avoid the Windows Update upgrade, at least for the time being. Numerous issues with licensing have been reported, requiring manual activation either through the dreaded phone call, or by running slmgr.vbs /ato at the command prompt to force license registration.
leading to some rather humorous error messages like the oh-so helpful description, "Something Happened."
Warning : Something's gonna happen
Error : Something happened
Debug : It had to happen
Crash : Why me !
Are you upgrading from Windows 7 (or earlier, or Linux), or from Windows 8/8.1?
http://windows.microsoft.com/en-CA/windows-8/what-is-pae-nx-sse2>Windows 8/8.1 introduced a requirement for SSE2, PAE, and NX.
NX is sometimes disabled in the BIOS. As far as I know there's no additional processor limitations on Windows 10.
Looking at how the update was going to be done, I left the machine on overnight idling.
On the thirtieth, I was notified I was ready, and upgraded. Could not have been easier.
I would have thought that reserving on rollout day would have put me in a long waiting line, and of course there would be a lot of serverhammer (c) on the first few days.
The whole process was flawless, and thank gawdd for that. My original plan was to wait until near the end of the update cycle and see how things were going. Make a decision on staying with 7 or not. But a fellow I was doing some software/hardware troubleshooting with foolishly updated to W10 thinking it would fix his problem, so I needed to know a little about ten before I took remote control of his computer
The results stunned me. Everything just worked. I didn't have to go to the web to figure out simple things like I did in W8. After 4 hours of playing around in it, I was ready to support it. Windows 8 was so nasty, I refused to support it.
Perhaps a Ballmerless company grew some balls here, listened to it's customers, and did it right. Really a tough job taking the steaming pile of shit that was W8, and turning it into something a confirmed Unix like devotee such as myself likes.
There's
The shepherds did so well protecting the flock that the sheep no longer believed that wolves existed.
I have a Windows 7 Pro virtualbox vm
Full stop, it doesn't matter what chip the host system is running. You need to ensure that VirtualBox is providing all of the required features in the virtual processor.
And some of them aren't. I don't want MS to be able to access my e-mails or personal data even if they do have a "good faith reason" to do so, thank you. I won't touch Win10 with a barge pole.
== Jez ==
Do you miss Firefox? Try Pale Moon.