Screen Shot 2015-06-02 at 8.57.41 AM

How To Upgrade To Windows 10

Microsoft, Systems Administration 3 Comments on How To Upgrade To Windows 10 532

The free upgrade to Windows 10 should be the easiest Windows upgrade ever.  Essentially you should receive a little upgrade icon in your task bar, you then click on it and “Reserve your free upgrade”.  You’ll then receive a notification when the upgrade is available and run through the installation routine.  As long as you have a legit copy of Windows 7 or 8.1 the upgrade process will take between 20 minutes to an hour.

I’ll say it sounds good, but I wouldn’t be in the first batch of people to do the upgrade.  If you’re planning to upgrade make sure you do a bare metal backup of your PC before you start so if it fails you can recover your system.  I would also say that if I had clients I wouldn’t do the upgrade on business machines for approx. 6 months to verify that most of the bugs have been fixed.  I know from experience that device drivers on PC’s can be a beast during an upgrade and with so many different components in systems I would want to make sure vendors have had time to update their drivers.

You can check out Microsoft’s upgrade instructions here:

And make sure to take a look at the FAQ page here:


Eli Etherton

I am Eli "the Computer Guy" and have been in the tech industry for approx. 20 years doing all kinds of odd projects. I started as an electronics tech in the US Army, worked in corporate IT during the IT Boom, was an individual consultant and grew my tech shop to have numerous full time employees and supported small business clients with computer repair/ server maintenance/ web development/ surveillance systems/ telephone systems until the great recession. After that I started creating video training on all the topics I know and now have a YouTube Channel with over 500K subscribers. I am the founder of and my plan is to create a tech "news" site that I would actually find useful if I was still in the server room.

Related Articles


  1. Morten Jakobsen June 2, 2015 at 8:07 am

    I’ve read they are getting rid of windows media center, floppies and playback of DVD’s.

    Also, I noticed you didn’t mention that in the home version of Windows 10, updates cannot be controlled. Which I think is a pretty big deal for home users.

    I could imagine this would be an issue, especially for clients who does not have a good internet connection, or maybe a weak computer (despite most computers today, are pretty decent).

    Though, seen from a security aspect, it’s a good idea to “force” updates upon home users, I’ve sadly seen a lot of cases where little, if no updates at all was installed.

    Good update 🙂

  2. Anub June 2, 2015 at 8:36 pm

    Hey Eli, I was curious, will you be able to take the windows 10 upgrade file and turn it into a live disk for future installation on an empty system? Or does this not work like that?

  3. Phil June 10, 2015 at 2:53 pm

    I would like to echo Eli’s comment on not rolling win 10 to businesses. I had to install windows 7 when it first came out on a client’s laptop. As he was a B2B marketing guru he had this idea that he should look hip and trendy to his clients. I recommended that he wait 6-8 months and let other find the bugs. Like a petulant child he rang back and spoke to a colleague and he advised to go for it. Hand slap to forehead. The client then went out and bought a copy and windows 7 and then brought in his laptop. As my colleague advised the client to upgrade he got the task of upgrading. After we upgraded and we joined the laptop to the network remotely via vpn we handed the laptop back. This was when the fun started. The client was on a SBS 2003 domain. As soon as he logged onto the domain via the laptop the firewall locked down the computer tighter than a submarine door. This only happened on the wireless via Ethernet cable he was fine. It tuned out that if windows 7 even got a sniff of another DHCP server that was not on the domain it spazzed out. The client had a VoIP phone system with cordless handsets on its own ssid. The phone installers could not get their system to use the DHCP server from the domain so they created their own. Half an hour of tinkering and a quick call to Siemens tech support who were amazing (this the name check) we had the phone system using a the domain DHCP problem solved.
    Moral of the story know your clients infra-structure and don’t be an early adopter unless it is in a testing role be it in a workshop or user testing.

Leave a comment

Back to Top